Link the raw JSON or YAML file, not a documentation page. Nothing is stored; the document is parsed and discarded.

What this preview does, and does not do

It fetches the document you link (public URLs only, with the same safety rules as the audit), parses it, and applies fixed rules: operations become candidate tools, GET becomes a read, POST and PUT become writes, DELETE and consequential verbs such as cancel or refund become guarded actions. It notices pagination and idempotency keys when the document mentions them. The same rules run every time; no language model is involved, so the result is repeatable and says nothing it cannot see.

It does not choose the right tools for your customers, write descriptions an assistant can act on, decide confirmation boundaries, check permissions, or price anything. That is the design work, and it is what the free audit does next, followed by the paid setup if you want it built and hosted. The generator comparison shows why the mechanical part is the easy part.

Try it on our sample API

No document to hand? Use the sample shop that all our examples wrap: https://raw.githubusercontent.com/apitoagents/mcp-examples/main/sample-api/openapi.json. It has five operations and the preview finds a read with pagination, an idempotent write and a guarded cancellation.

API to Agents is a brand of Neoval GmbH. The preview is limited to twelve requests per hour per address and two megabytes per document.