Capabilities
The business-capability model: what the catalog's APIs let a business DO, and the quoted contract fragments that evidence each claim.
The business-capability model.
What the catalog's APIs let a business DO — top-level capabilities across every industry, each with how many providers reach it. The entry point for "what can I actually build from this catalog", as opposed to "who is in it".
query Parameters
qFree-text filter.
limitpageThe business-capability model. › Responses
The capability model.
modelThe evidence behind a capability.
Every edge landing on a capability: the provider, the tag, the exact OpenAPI file, a calibrated confidence, and THE QUOTED FRAGMENT OF THE PROVIDER'S OWN CONTRACT that justifies the claim. Only edges at confidence >= 0.7 whose evidence was found verbatim in the source are published, so an edge here is checkable rather than asserted. This is what you cite when someone asks "says who?".
path Parameters
idThe evidence behind a capability. › Responses
The edge table.
What one vendor's APIs let a business do.
One provider's published APIs rolled up by capability, with the tag-level evidence under each. Answers "what is this vendor actually for" from its own contracts rather than its marketing. NOT /providers/{slug}/capabilities, which is artifact counts and agent-readiness dimensions and is free — the names predate this section.
path Parameters
slugProvider slug (e.g. twilio).
What one vendor's APIs let a business do. › Responses
The provider's capability map.

