Skip to content
SwaggerBot
Get an API keyGet a key

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 “Replicate API”

Replicate API

ResolvedProvenance: Officialanswered in 1.9 ms

By replicate.com · Verified

curl -o openapi.json https://swaggerbot.dev/api/specs/4500bf86453ef1ab65a9e133929ce97f468cff9aa62ab7512d00fd588abb8b39/published

The whole answer, as JSON:

curl -X POST https://swaggerbot.dev/api/lookup -H "Content-Type: application/json" -d '{"name":"Replicate API"}'

Spec details

API id
replicate.com/api
API Version
1.0.0-a1
Spec
OpenAPI 3.1.0 · JSON4500bf86453ef1ab65a9e133929ce97f468cff9aa62ab7512d00fd588abb8b39
Validity Issues
1 finding; none stops the Spec being used
  • Property query is not expected to be here /paths/~1models
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://api.replicate.com/openapi.jsonLast verified

How it was answered

Answered from the Index in 1.9 ms; no later step was needed.

The six steps of a Lookup
  1. IndexSpecs verified before. Answered in milliseconds, no key needed.Answered here
  2. APIs.guruThe public directory of API descriptions.Not needed
  3. Developer PortalFound with a web search.Not needed
  4. Vendor domainKnown paths, apis.json, then a shallow crawl.Not needed
  5. GitHubThe Vendor's organisation first, then the rest.Not needed
  6. JudgedIs it the API you meant, and its Spec? Not sure means we say so.Not needed

Look up another API