Latch · MCP Client Coordination
Coordinate authenticated interactions between LATCH systems and Model Context Protocol clients with integrated payment handling.
What it does
Coordinate authenticated interactions between LATCH systems and Model Context Protocol clients with integrated payment handling.
- Orchestrate multi-step agent workflows with payment gates
- Authenticate MCP client sessions
- Route tasks between LATCH and external tools
Ideal buyer
Developers building MCP-compatible agent systems requiring authenticated coordination.
Run this through your governed agent wallet.
- 01Bootstrap AXON once with
npx @axon402/init. - 02Use the AXON runtime MCP tools to
search_x402_servicesorinspect_x402_offerfor this service. - 03Quote, test-buy, then run the governed paid fetch through AXON.
Send this
Prompt for your agent
A natural-language instruction for your LLM agent — with this endpoint exposed as a tool — to call this resource. Not sent to the endpoint; the endpoint consumes the JSON body below.
Pasting this prompt into a raw ChatGPT or unconfigured agent will notexecute the paid endpoint flow. Run it through an agent with the AXON runtime / MCP tools exposed (see “Use with AXON” above) so the 402 challenge, quote, and governed fetch are handled for you.
“Initialize MCP session with LATCH for authenticated task execution”
Endpoint request body
The JSON payload your agent sends to the endpoint.
Advanced HTTP details
For integrators who need the raw protocol surface. Most agents should use AXON above instead of calling these directly.
Endpoint URL
curl fallback
curl https://x402.latchmcp.app/mcp \ -H "Content-Type: application/json" \ -H "X-PAYMENT: [signed_payment_envelope]"
Payment & settlement details
Raw on-chain settlement parameters. AXON above handles these automatically through quote / test-buy / governed fetch.
Price & network
Trust & risk
More in Tools
Browse all →Other resources in this category
Category proxy — we don't track live co-purchase signals yet.