Search

The power endpoint. Choose what kind of object to return with return (apis by default), then constrain with any combination of q, tags (match=any|all), providers, and artifact_types. Use fields for sparse responses and include=content to inline artifacts.

Example — messaging APIs across providers that ship an OpenAPI, returning just the spec and pricing artifacts:

Code
/search?return=apis&tags=Messaging&artifact_types=OpenAPI,Pricing
       &fields=aid,name,provider_slug,properties

A hand-checked set of APIs that need no key (or an instant, free, self-serve one), cost nothing, and have no real-world side effects. Every entry carries an example_request URL that returned HTTP 200 to an unauthenticated GET on the date shown, so an agent can call it immediately with no setup. The recommended first call for a new client.

Name, version, and how many providers, APIs, tags and artifacts the catalog holds. The cheapest way to confirm you are talking to the right service and to see its size before paging anything.

Which providers expose a path matching your terms. "Who has a POST /refunds" had no answer before this: you could ask what ONE provider exposes, and you could search tags, but a tag is what a company says about itself while a path is what its API accepts. Terms match path SEGMENTS and all of them must appear, so q=payment intents finds /payments/v1/intents. One row per real operation — a provider's spec is split per tag, so the same call can live in several of its documents, and apis lists them. Matching providers' surfaces are read up to max_providers; when more matched than were read, meta.query.truncated says so rather than a partial answer passing as a complete one.

Every provider publishing at least one operation its own OpenAPI marks deprecated, ranked by how many — the lifecycle view of the catalog. Invisible before this, because a provider's own ?deprecated=true filter needs you to already suspect that provider. Drill in with /providers/{slug}/operations?deprecated=true.