Overview.
The Spend Graph is built to be read by machines without a human in the loop, with no API key, signup, or integration meeting to clear first. An agent discovers the endpoints, pays per call, and queries the record in one motion. This page describes that loop.
Discovery.
Endpoints are auto-discoverable: an agent that finds the Spend Graph can enumerate what it answers (merchants, categories, geographies, windows) without provisioning.
The 402 flow.
x402 is the open standard for machine payment over HTTP, built on the 402 status code the web reserved for exactly this purpose. The loop:
- The agent requests a resource and receives 402 Payment Required
- It pays the quoted amount in the same exchange, with no account or billing relationship
- It retries with proof of payment and receives the data
It pays for exactly the data it queries, per call.
MCP.
The Spend Graph ships as MCP tools, so reasoning systems can call spend data mid-chain-of-thought instead of guessing at macro. Ground truth arrives as a tool call rather than a six-week integration. Join the waitlist to hear when it ships.
Acting on the data.
An agent doesn’t have to stop at querying. Spend Market resolves on the same record the agent just read: monitor a category, and when the data moves, take the position, all on one record. See Spend Market and the Agentic AI page.