Agents: request Accept: text/markdown or append /index.md.

# SliceRun docs

SliceRun is an API/application marketplace, not a content site. The Worker serves these public documents itself so agents do not depend on a paid Cloudflare zone setting.

## Roles

- **Shop** — posts deliveries, sees only their own jobs
- **Driver** — sees nearby open jobs as a preview; after accept, sees the full assigned ticket
- **Admin** — sees everything, reviews verification

## Verification sandbox

| Shop status | Job lane | Who can accept |
| --- | --- | --- |
| verified | real | verified drivers |
| unverified / pending / rejected | sandbox | non-verified drivers |
| suspended | none | nobody |

A sandbox job stays sandbox even if the shop is verified later.

## Agent surfaces

All of these obey the same visibility, verification, and authentication rules as the UI.

1. MCP tools at `https://slicerun.pages.dev/mcp` (Cloudflare Agents SDK `McpAgent`)
2. REST at `https://slicerun.pages.dev/api`
3. Browser WebMCP tools on the public pages (no private drop-off data)

## Web Bot Auth

SliceRun does not send outbound crawler or agent HTTP requests to other sites. The matcher stays inside this Worker (D1 + optional Workers AI). There is no `/.well-known/http-message-signatures-directory` because this app is not a Signature Agent. If SliceRun later fetches third-party sites, publish a JWKS there and sign those requests with `Signature-Agent` / `Signature-Input`. Inbound bot traffic is governed by `robots.txt` Content-Signals and AI user-agent rules.

## Commerce (not implemented)

x402, ACP, UCP, and MPP are future work. SliceRun has no payments yet. Those checks do not count toward the Agent Readiness score.