Developers

Codex Pets Developer Portal

Build against the public Codex Pets registry with OpenAPI, MCP, JSON endpoints, TOON mirrors, and explicit authentication notes.

OpenAPI JSON API docs Full LLM context

Start with MCP

codex mcp add codexPets --url https://pets.ydb-qdrant.tech/mcp

The MCP server is read-only and exposes approved public pet data plus request workflow discovery.

Developer resources

OpenAPI JSON: Canonical OpenAPI 3.1 specification for public Codex Pets endpoints.
API docs: Human-readable API docs for JSON, TOON, MCP, request, and submission routes.
Full LLM context: Expanded markdown context with API reference, auth notes, examples, and webhooks status.
OAuth resource metadata: Machine-readable public access metadata that states OAuth is not currently supported.
Pricing: Free community registry terms: no paid plans, no invoices, and best-effort public APIs.
Terms: Public agent access, moderation, and versioning policy for stable v1 endpoints.
MCP metadata: MCP Registry metadata for the public Streamable HTTP server.
Developer llms.txt: Scoped developer-resource index for API, OpenAPI, MCP, auth, and agent guidance.
MCP markdown: Markdown MCP server guide with MCP App resource and CSP notes.

Auth and webhooks

Public read endpoints do not require authentication.
AppSessionCookie is used by browser account flows and optional signed-in request attribution.
ProxyBasic is supported when the deployment is protected by a trusted reverse proxy.
OAuth 2.0 is not currently supported.
OAuth Protected Resource metadata is published for agents, but it intentionally does not advertise authorization servers.
Webhooks are not currently available.

Versioning and deprecation

Current unversioned public endpoints are stable v1. Additive response fields and new routes may be added without notice. Breaking public-agent contract changes require a new path or a published deprecation notice.