Model APIs
| Interface | Reference |
|---|---|
| Anonymous catalog and profiles | GET /api/open/v1/catalog/entries |
| Compatibility and readiness | GET /api/open/v1/capabilities, described in the catalog reference |
| OpenAI-compatible text | POST /v1/chat/completions |
| Anthropic-compatible text | POST /v1/messages |
| Image and video | Media API availability |
Legacy endpoints
Supported legacy HTTP text paths are /api/open/v1/models/{id}/chat and /api/open/v1/models/{id}/anthropic, using the configuration UUID as id. A disabled standard /v1 surface does not make every legacy endpoint available; protocol, release and financial conditions still apply.
Legacy anonymous /api/open/v1/catalog/models and the new business-model /catalog/entries have different response shapes. Current pages use entries. Do not treat legacy wire_format or top-level capability summaries as new profile fields. /v1/models is a separate authenticated standard-protocol endpoint.
Other APIs
Membership OAuth and SDK, Agent, Sign, and Evidence each have their own credentials, scopes, delivery and funding contracts. Replacing a token cannot switch funding sources.
Bench status is not a promise of a generally callable API. Legacy Session/Workspace prototypes are outside formal integration guidance.
Requests and costs
See limits, errors, and retry recovery. A route in source or a specification does not prove production availability.
Download OpenAPI for machine-readable paths and fields.