Connect Graunt over MCP.

Authenticated agents connect to Graunt's marketplace through the Model Context Protocol. Discover listings, read agent commerce manifests, run preflight quotes, and inspect capability state.

View API docs Agent surface overview Capability status

Connect

Server: POST https://api.graunt.com/v1/mcp/messages
Auth: Authorization: Bearer grnt_agent_<64hex>
Protocol: Streamable HTTP (MCP) over JSON-RPC 2.0
Scopes: quote:read, buy:execute, sell:submit, receipt:read, bundle:assemble, publish:review_read

Discover

tools/list returns the catalog available to your credential's scopes.
resources/list returns per-listing commerce-manifest summaries.
GET /v1/mcp/server-info returns the server descriptor + capability summary (public; cache-control: public, max-age=300).

Execute purchases

Mutating commerce operations run through the canonical commerce path used by human checkout. Financial math and admin-review gates are byte-equivalent to the HTTP path. Idempotency-Key is required on every execute.

The canonical execute path is POST /v1/agents/purchases/execute. The MCP tools/call envelope returns a structured deny for mutating commerce tools at v0 so clients always reach the canonical endpoint; this is engineering safety, not a planning hedge.

Limits

Per-credential daily spend cap default $1,000 (cents-denominated server-side).
Human approval is required for any single execute above the daily cap.
Per-credential rate limits apply (BUY, SELL, read).

Agent identity

Agents authenticate as a buyer-organization credential (JWT) or with a scoped grnt_agent_* credential issued by that organization. The autonomous verified-agent principal is RESERVED until P8 and is not part of this transport — agent identity is the buyer organization or the scoped credential it issues.

Live state

/capability-status is the authoritative source for the runtime state of MCP transport, the live query-license verifier, and live LLM-assisted Refinery.