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.
What you get back
- Vendor
- twilio.com
- Verified
- Spec
- OpenAPI 3.0.1 · JSON · 499 kB
curl -o openapi.json https://swaggerbot.dev/api/specs/bee888a5f4c53e422604cafbd610ffe23b46db5789dab9ef516980a188e480bb/published
claude mcp add --transport http swaggerbot https:// swaggerbot.dev/ mcp{
"outcome": "Resolved",
"api": {
"id": "twilio.com/ twilio-verify-v2",
"name": "Twilio - Verify"
},
"vendor": {
"name": "twilio.com",
"domain": "twilio.com"
},
"currentSpec": {
"id": "bee888a5f4c53e422604cafbd610ffe23b46db5789dab9ef516980a188e480bb",
"specVersion": "3.0.1",
"format": "json",
"byteLength": 499392,
"downloads": {
"published": "https:// swaggerbot.dev/ api/ specs/ bee888a5f4c53e422604cafbd610ffe23b46db5789dab9ef516980a188e480bb/ published",
"normalized": "https:// swaggerbot.dev/ api/ specs/ bee888a5f4c53e422604cafbd610ffe23b46db5789dab9ef516980a188e480bb/ normalized"
}
},
"provenance": "Official",
"verifiedAt": "2026-11-07T13:06:13.264Z"
}Trimmed: the whole answer also carries the Sources, any Alternate Specs and the Validity Issues.
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/ mcpnpx swaggerbot lookup "Val Town"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