Resolved
The name is one API, and its Spec is confirmed to describe it: here it is, with where it came from.
You looked up “Infisical API”
Infisical API
ResolvedProvenance: Officialanswered in 247.7 msBy infisical.com · Verified
curl -o openapi.json https://swaggerbot.dev/api/specs/6136900749bbc1f6970f430ba4f9df8705566e4c5b3e9b5a97410c6b11fcfa45/published
The whole answer, as JSON:
curl -X POST https:// swaggerbot.dev/ api/ lookup -H "Content-Type: application/ json" -d '{"name":"Infisical API"}'swaggerbot lookup "Infisical API"The same answer in a line; --json prints it whole. An Index answer needs no key.
claude mcp add --transport http swaggerbot https:// swaggerbot.dev/ mcpThen call the tool; an Index answer needs no key:
lookup_api {"name":"Infisical API"}{
"outcome": "Resolved",
"api": {
"id": "infisical.com/ api",
"vendorId": "infisical.com",
"name": "Infisical API"
},
"vendor": {
"id": "infisical.com",
"name": "infisical.com",
"domain": "infisical.com"
},
"currentSpec": {
"id": "6136900749bbc1f6970f430ba4f9df8705566e4c5b3e9b5a97410c6b11fcfa45",
"apiId": "infisical.com/ api",
"specVersion": "3.0.3",
"apiVersion": "0.0.1",
"isPreview": false,
"supersededAt": null,
"format": "json",
"byteLength": 15056655,
"downloads": {
"published": "https:// swaggerbot.dev/ api/ specs/ 6136900749bbc1f6970f430ba4f9df8705566e4c5b3e9b5a97410c6b11fcfa45/ published",
"normalized": "https:// swaggerbot.dev/ api/ specs/ 6136900749bbc1f6970f430ba4f9df8705566e4c5b3e9b5a97410c6b11fcfa45/ normalized"
},
"normalized": "ready"
},
"alternateSpecs": [],
"provenance": "Official",
"sources": [
{
"id": 216,
"specId": "6136900749bbc1f6970f430ba4f9df8705566e4c5b3e9b5a97410c6b11fcfa45",
"url": "https:// infisical.com/ openapi.json",
"provenance": "Official",
"firstSeenAt": "2026-11-06T16:29:32.384Z",
"lastVerifiedAt": "2026-11-06T16:29:32.384Z"
}
],
"verifiedAt": "2026-11-06T16:29:32.384Z",
"validityIssueCount": 0
}Trimmed: the whole answer also lists the Validity Issues, below.
Spec details
- API id
- infisical.com/api
- API Version
- 0.0.1
- Spec
- OpenAPI 3.0.3 · JSON6136900749bbc1f6970f430ba4f9df8705566e4c5b3e9b5a97410c6b11fcfa45
- Validity Issues
- None
- Normalized Form
- Download the Normalized Form · one bundled document in the current OpenAPI version
Alternate Specs
None: the Current Spec is the only one.
Sources
- Provenance: Officialhttps://
infisical.com/ openapi.jsonLast verified
How it was answered
Answered from the Index in 247.7 ms; no later step was needed.
The six steps of a Lookup
- IndexSpecs verified before. Answered in milliseconds, no key needed.Answered here
- APIs.guruThe public directory of API descriptions.Not needed
- Developer PortalFound with a web search.Not needed
- Vendor domainKnown paths, apis.json, then a shallow crawl.Not needed
- GitHubThe Vendor's organisation first, then the rest.Not needed
- JudgedIs it the API you meant, and its Spec? Not sure means we say so.Not needed