Correction (2026-10-02): this post described the catalog as it stood in June 2026. It now also sells model-backed products (the /v1 model gateway, the report products, media and answer tools), each marked modelBacked on /api/pricing; the determinism described below is true of the utility tools.
Most tool APIs were designed for human developers: sign up, get an API key, read the docs, handle auth, manage quotas. That friction is invisible to a person, but it's a wall for an autonomous agent.
We built Agent402 around a simple idea: every tool should be callable with a single HTTP request and a micropayment. No registration, no API keys, no OAuth flows. The x402 protocol makes this possible - the agent's wallet is its identity, and payment is authorization.
Why deterministic?
An agent that calls a tool needs to know what it will get back. If a "summarize" endpoint silently calls an LLM, the output varies on every call. That makes testing impossible, caching meaningless, and debugging a nightmare.
The pure-computation tools are deterministic: same input, same output, every time. This means agents can cache results, retry safely, and CI can verify them automatically. Our test suite calls each tool with its example input and checks the response.
Why x402 over API keys?
API keys create a management burden. An agent operating across dozens of services needs dozens of keys, each with its own rate limits, billing dashboard, and revocation policy. x402 replaces all of that with a single mechanism:
- No signup. The agent sends a payment header with its request. Done.
- No per-key quotas. You pay per call, so there is no plan to outgrow. (Safety limits still apply, such as a cap on repeated failed settlements from one wallet.)
- No vendor lock-in. x402 is an open protocol. Any server can accept it, any client can send it.
- Micropayments that actually work. A stablecoin payment on Base, or on any of the other chains listed at /api/rails, settles in seconds for fractions of a cent in gas. (Chain list updated 2026-10-11: it now points at the live rail list rather than naming chains, which were added after this post.)
The result: an agent with a funded wallet can discover Agent402 tools via MCP, call them, and pay - all without a human ever creating an account.
Open source, self-hostable
Agent402 is AGPL-3.0-licensed (the buyer SDK, MCP connector, and tollbooth stay MIT). You can run your own instance, add your own tools, set your own prices. The hosted version at agent402.tools is just one deployment of the same codebase that's on GitHub.
We think the future of agent infrastructure is open protocols, not walled gardens. x402 is the payment layer, MCP is the discovery layer, and Agent402 is the tool layer that ties them together.