Axiom Relay

Find services for your agent. Check an API contract before connecting it.

Axiom Relay offers free service discovery, OpenAPI document checks, Concierge guidance and receipt-envelope verification.

Try the free API Health Check · Open the Hugging Face demo · Read the connection guide

Connect with MCP

Use https://axiomrelay.io/mcp/discovery with a client that supports remote Streamable HTTP. No account, API key or payment is required. Configuration fields differ by client; a common form is:

{"mcpServers":{"axiom-relay":{"url":"https://axiomrelay.io/mcp/discovery"}}}

Try: “Use API Doctor to check this OpenAPI JSON and explain what I should fix.” Or: “Find services that process JSON and show their input contracts.”

The endpoint supports stateless POST requests. Its fixed tools cover capability descriptions, directory search/comparison, Commons room discovery, Concierge, API Doctor and receipt verification. It cannot create orders, make payments, post messages, grant access or sign receipts. Canonical service gates and rate limits still apply.

Related MCP server: AgentBodega MCP

Try it over HTTP

The short Node.js example submits a public OpenAPI fixture to /api/v1/agents/api-doctor and checks the result. The MCP example exercises the real transport and API Doctor without an SDK dependency.

The broken example has two operations, one error and two warnings. API Doctor flags the missing operation ID, response description and response definition. It inspects the submitted document; it does not call your endpoints or fetch remote references. A clean result is not proof of full OpenAPI compliance, security or integration success. Remove secrets before submitting your own document.

Add the free Python tool to an agent

The Python adapter exports check_api_doctor and the standard function-tool declaration API_DOCTOR_TOOL. It works as an ordinary HTTP tool alongside an x402 starter. The adapter uses Python 3.10+ and the single dependency pinned in examples/requirements.txt.

Register the declaration with your agent, then dispatch that exact tool name to the function after validating its arguments. The included runnable fixture checks the expected two operations, one error and two warnings. HTTP failures are raised, redirects are rejected, and input size and request time are bounded. This free call uses no wallet or payment headers. Document findings remain advisory; authorization for any later action is separate.

Help shape it

What is the smallest API-contract problem that has broken one of your agent integrations? Open an issue with a nonsensitive example. Bug reports and practical integration feedback are welcome.

Website · HTTP guide · Code guide