Docs Home
For agents and integrators

Which protocol, where

Writ speaks several agent-payment protocols at once. This page says, honestly, which ones are live right now, which are built but switched off by default, and which are listed somewhere but not yet published — so nobody has to guess from a marketing page or discover a 404 mid-integration.

Live today

MCP

Live

Hosted, unauthenticated, Streamable HTTP (spec 2025-11-25). One URL, no signup: an agent calls fastpay_sandbox_join and the six sandbox-journey tools work immediately in the same session.

  • POST/mcp — JSON-RPC 2.0 (initialize / tools/list / tools/call)
  • DELETE/mcp — end a session

Honest scope: the hosted endpoint deliberately serves only the sandbox journey (fastpay_sandbox_join, fastpay_check_budget, fastpay_list_policies, fastpay_pay, fastpay_get_receipt, fastpay_verify). Escrow and delegation-chain introspection exist only on the self-run stdio server (mcp-server.js, clone-and-run). A listing for the official MCP Registry is prepared (deploy/distribution/mcp-registry/server.json) but not yet published — that needs a DNS verification step, not code.

x402

Live

Writ is both an x402 facilitator (it can verify and settle payments for any x402-speaking resource server) and an x402 resource (it sells a protected endpoint of its own, so you can see the whole loop — 402, pay, deliver — without standing up a merchant). Internal test rail; refuses to serve on any real-money deployment.

  • GET/x402/.well-known — facilitator discovery
  • GET/x402/supported — supported schemes/networks
  • GET/x402/bazaar — this deployment's own paid-resource listing
  • GET/x402/premium/quote — the example paid resource (402 → pay → deliver)

Honest scope: this deployment is not yet listed in the public x402 Bazaar/ecosystem directory — the protocol conformance is live and tested (x402-conformance.test.js), the external discovery listing is a separate, not-yet-done step.

Arc

Live · testnet

Self-service onboarding onto Circle's Arc network: an agent gets a wallet, delegates a bounded USDC allowance to Writ, and pays through /api/pay exactly like the internal rail — Writ never custodies the funds.

  • GET/api/arc/config — network + contract config for this deployment
  • POST/api/arc/join — onboard a new agent + wallet
  • GET/api/arc/wallet/:owner · POST/api/arc/challenge — wallet lookup / key-recovery challenge

Quickstart page: /arc.html.

Honest scope: Arc testnet only (the onboarding route itself refuses to activate against a mainnet network config — see ARC_ONBOARDING_TESTNET_ONLY). No real value moves.

Built, not live by default

Adapters below are implemented and tested against Writ's real policy/settlement engine, but each is mounted OFF unless the deployment explicitly turns it on — so pointing at writ.money today, these routes answer 404, not a partial or unsafe implementation.

AP2

Adapter built · not live

Google's Agent Payments Protocol: Intent → Cart → Payment mandate chain, translated at the edge into the same policy check and settlement engine every other rail uses.

  • GET/ap2/v1/.well-known · POST/ap2/v1/checkout
  • POST/ap2/v1/authorize · POST/ap2/v1/pay

Off unless the deployment sets AP2_ENABLED=1 — unset here, so nothing is mounted, not even discovery. Proven against real Postgres in customer-pilot/ap2-resource.pg.test.js.

ACP

Adapter built · not live

The Agentic Commerce Protocol — checkout sessions plus delegated payment tokens, for platforms that authenticate by bearer token rather than an agent key.

  • POST/acp/checkout_sessions · GET/acp/checkout_sessions/:id
  • POST/acp/checkout_sessions/:id/complete
  • POST/acp/checkout_sessions/:id/cancel
  • POST/acp/agentic_commerce/delegate_payment

Off unless the deployment sets ACP_ENABLED=1 and configures ACP_MERCHANT/ACP_PLATFORMS. Structurally distinct from the other adapters: ACP settles through the durable execution layer directly rather than looping back through /api/pay, because its payment token deliberately never carries an agent key — see the comment above the mount call in customer-pilot/server.js for why, and what customer-pilot/acp-resource.js checks that path is missing before it will mount anywhere real value could move.

llms.txt Full API docs Home