Expose an OpenAPI file agents can find

Publish the OpenAPI file where agents follow links to it, and decide when to wrap it as MCP. 156 directory companies publish an OpenAPI file, and 21 of 7,472 top-10,000 domains do. First step: Serve openapi.json at a stable URL.

Steps

1. Serve openapi.json at a stable URL.
2. Link it from docs and the home page.
3. Consider agents.json flows for multi-call tasks.
4. Wrap key operations as MCP tools through a gateway or your own server.

What the sources say

• Ora's lab found agents reached openapi.json in 21 percent of traced runs on sites that ship one, 97 percent through a link (19 Oct 2026). (ora.ai, dated 19 October 2026, read 4 November 2026)
• AgentReady.org lists a public API with OpenAPI as an act-layer SHOULD. (ora.ai, dated 19 October 2026, read 4 November 2026)
• agents.json 0.1.0 extends OpenAPI with flows and links at /.well-known/agents.json. (github.com, read 4 November 2026)
• Kong's AI MCP Server entity turns existing APIs into MCP tools. (developer.konghq.com, read 4 November 2026)
• Stripe exposes its API through stripe_api_search, stripe_api_details, stripe_api_read and stripe_api_write instead of one tool per method. (docs.stripe.com, read 4 November 2026)

How many publish one, and how it was found

156 of 1,336 directory companies publish an OpenAPI file at a path or in their docs. In the top 10,000, 21 of 7,472 probed domains serve a valid /openapi.json (0.28%).

Ora's lab found agents reached openapi.json on 21 percent of traced runs on sites that ship one, and 97 percent of those fetches came through a link (source, read 4 November 2026; a vendor-published finding). Link the file from your docs.