Skip to content
SwaggerBot
Get an API keyGet a key

Name it. Get the Spec.

No fake Specs.

SwaggerBot hands you an API's OpenAPI Spec, where it came from and how sure it is, or tells you straight why there isn't one.

API Version (optional)

What you get back

Twilio - Verify

ResolvedProvenance: Officialanswered in 2.7 ms
Vendor
twilio.com
Verified
Spec
OpenAPI 3.0.1 · JSON · 499 kB
curl -o openapi.json https://swaggerbot.dev/api/specs/bee888a5f4c53e422604cafbd610ffe23b46db5789dab9ef516980a188e480bb/published

Every answer is one of five

Precision over coverage: when SwaggerBot isn't sure, it says so as plainly as when it is.

  • Resolved

    The name is one API, and its Spec is confirmed to describe it. With Provenance and Sources.

  • Unconfirmed

    The API and a Spec were found, but not confirmed as this API's. The Spec comes with the reasons for doubt.

  • Ambiguous

    The name could mean more than one API. You get the candidates to pick from.

  • No Spec

    The API is known, but no Spec exists at a Provenance you allowed.

  • Unknown

    The name can't be matched to any API.

Use it from code

For agents and programs: the same answers over MCP and the HTTP API, and for people at a terminal, the CLI. From the Index, anyone. Past it, Discovery, with an API key.

claude mcp add --transport http swaggerbot https://swaggerbot.dev/mcp

npx swaggerbot lookup "Val Town"

Read the docsGet a key

Benchmark

On 23 Sept 2026: 0 wrong of 20 Resolved answers, on 2 runs over the 40-name set, after two label corrections. The Index now holds 21 Vendors, 21 APIs and 34 Specs. How it was measured