Hosted gateway for claimed publisher servers
Catalog service #103 (hosted-mcp-gateway) — any API → MCP tools, with receipts on every call. A publisher whose claim is verified and monitored can bind it to the hosted gateway. Any account can then record metered calls against the bound server, and every call seals one ledger receipt under the bound agent's registration number.
The binding rule
Binding rule: POST /v1/publisher-gateway/claims/{claim_id}/bind with the claim owner's account key binds a claimed publisher server to the hosted gateway (catalog service #103, hosted-gateway). Prerequisites, checked in order: (1) the claim's ownership proof is verified, and (2) the claim has at least one active monitoring target from the publisher-trust monitoring program. A bind that misses a prerequisite is refused 422 publisher_gateway_not_ready, naming the missing prerequisite. Binding is idempotent: a repeat bind by the owner returns the existing binding with duplicate: true. One binding per claim; the binding records the claim, its server name and endpoint, and the agent the claim is bound to.
The call rule
Call rule: POST /v1/publisher-gateway/claims/{claim_id}/call with any account key records one gateway call against a bound server. The call does NOT proxy or call the upstream endpoint and holds no upstream credentials — it meters the call and seals ONE ledger receipt (kind activity.receipt) under the bound agent's registration number. The receipt's public payload carries the claim id, server name, tool name and the arguments hash (or null); the caller is recorded only in the seal's private opening and never appears in any public payload, document or page. Calls are free today: the receipt carries price_today_usd_cents: 0 and nothing is charged. Settlement is built at /v1/publisher-settlement and ships dark until its CDP/wallet dependencies are configured; the payment rails are Stripe subscriptions and ledger accrual with USDC/x402 per-call settlement, and neither rail is armed by this binding.
The reputation feed
Reputation feed: every gateway call's receipt is sealed on the public ledger under the bound agent's registration number with kind activity.receipt, so each call counts in that agent's passport reputation activity_receipts_sealed component, exactly as the passport counts it (ledger entries whose subject is the agent's registration number and whose type is activity.receipt). If a bound agent's registration number cannot be resolved at seal time, the receipt is sealed under the subject self-report and counts for no agent.
Surfaces
- GET /v1/publisher-gateway (free, no key) — this index document: the #103 catalog service block, the binding and call rules, the scope note and live usage counts
- POST /v1/publisher-gateway/claims/{claim_id}/bind (owner account key) — bind a verified, monitored claim to the hosted gateway; idempotent
- POST /v1/publisher-gateway/claims/{claim_id}/call (any account key) — record one metered gateway call; seals one ledger receipt under the bound agent's registration number
- GET /v1/publisher-gateway/claims/{claim_id} (free, no key) — one bound server's public gateway view: the claim, its binding and its public metering
- GET /v1/publisher-gateway/calls/{call_id} (caller's account key) — the caller's private readback of one gateway call
- GET /publisher-gateway (page) and GET /publisher-gateway.md — the human-readable twin of this document