mend.rest

BETA site map
Status  Development instance. The official benchmark held-out execution is BLOCKED pending independent steward isolation. Nothing on any page here is a production or assurance claim.

Every public page, and what each one is for

Nine pages. The whole site.

A small site does not need a map to be navigable — it needs one so you can see the whole shape at once and tell that nothing is hidden. There is also a machine-readable sitemap carrying the same list and nothing more.

Start here

What the service is, and the two steps to using it.

Overview/ — what mend.rest is: it appraises delegated work against a contract declared before the work, hands the orchestrator bounded repair, verifies the fix independently, and reports reproducibly. Carries the standing list of what this instance does not claim, and the donation section.
Sign up/signup — give an address, open the confirmation link it emails you, and your API key is issued there, shown exactly once. No password and no cookie. Whether a code is needed is an operator setting the page cannot read, so it asks the server rather than guessing.
Connect/connect — integration, ranked by what is known to work today: browser sign-in with no key to paste, or an API key for scripts and CI. MCP over HTTPS for Claude Code and any MCP client, raw JSON-RPC for no MCP at all, the self-hosted adapter for anyone who wants to read it first, all 14 mend.* methods, and the failure modes in the order they actually bite.

Your account and your work

Both of these are read with your own credential; this site stores nothing.

Dashboard/dashboard — who a key belongs to, every key on the tenant, and issue or revoke. The key is the session; nothing is stored on this site.
Reports/reports — the receipts river: read your own task reports and verdict receipts in the browser, with your own credentials, including the fact digest each report reduces to.

Checking us, and telling us

One page exists so you need not trust this site. The other only ever runs if you press the button.

Verify/verify — how to re-check a report without trusting this website: recompute the fact digest yourself (with the known sharp edge about integers and floats spelled out), or run the open verifier over a receipt bundle on your own machine, offline. Also states plainly what a green exit code does and does not buy you.
Share/share — send one report, on purpose. Nothing is collected automatically: you paste the report, you see exactly what it contains, and nothing leaves the page until you press Send. Opt-in is the entire mechanism.
/verify serves two readers. Without a query it is the offline verification document above; the confirmation link mailed at signup arrives at the same path carrying a token, and that serves the confirmation page instead. The same confirmation page is at /confirm for anyone who wants the URL on its own. It is a transactional landing page rather than something to browse, so it is not listed in the machine-readable sitemap.

The documents

Both are starting drafts and neither has been reviewed by a lawyer. Both say so at the top.

Terms/terms — development-grade with no warranty and no SLA; evidence rather than guarantees, and the relying party's decision stays their own; acceptable use; key custody; donations as voluntary gifts that are not purchases; termination and change. Carries three visible placeholders only the owner can fill.
Privacy/privacy — what is collected, what is not done with it, what the host operator can read (all of it — isolation is process and directory permissions, there is no at-rest encryption), where a network address is and is not retained, how deletion works and what append-only history it keeps by design, the third parties, and why report sharing is opt-in only.
Site map/sitemap — this page. /sitemap.xml carries the same URL list for crawlers, with no dates, because a date this file cannot substantiate would be a claim it should not make.
What is not on this map