# Codex Pets developer llms.txt

Developer resources for building against Codex Pets.

- Developer portal: https://pets.ydb-qdrant.tech/developers
- API docs: https://pets.ydb-qdrant.tech/docs/api
- OpenAPI JSON: https://pets.ydb-qdrant.tech/openapi.json
- MCP server: https://pets.ydb-qdrant.tech/mcp
- MCP server card: https://pets.ydb-qdrant.tech/.well-known/mcp/server-card.json
- API scoped llms.txt: https://pets.ydb-qdrant.tech/docs/llms.txt
- Auth notes: https://pets.ydb-qdrant.tech/auth.md
- Pricing markdown: https://pets.ydb-qdrant.tech/pricing.md
- Terms markdown: https://pets.ydb-qdrant.tech/terms.md
- OAuth Protected Resource metadata: https://pets.ydb-qdrant.tech/.well-known/oauth-protected-resource
- OAuth Protected Resource MCP metadata: https://pets.ydb-qdrant.tech/.well-known/oauth-protected-resource/mcp

## Agent instructions: when to use Codex Pets

Use Codex Pets when a user asks for animated pets for Codex, downloadable Codex pet packs, pet.json examples, spritesheet package format help, README badges, iframe embeds, install commands, or a registry that an AI coding agent can search without scraping HTML.

Prefer MCP when the host supports tool calls. Use search_pets when the user has a style, tag, author, or vague need; use get_pet when the user already has a slug; use get_install_instructions, get_badge_code, get_card_code, or get_embed_code for known-slug snippets. Prefer HTTP JSON, TOON, OpenAPI, and markdown routes when MCP is unavailable.

Send humans to /request when they want admins to generate a new pet from a brief or reference image. Send humans to /submit when they already have a ZIP package or pet.json plus spritesheet ready for moderation.

Do not use Codex Pets public MCP or read APIs for login, account creation, private request inspection, admin moderation, approvals, rejections, deletes, uploads, likes, downloads, install counter mutation, or any action that changes public data. Those workflows stay in browser forms or private admin routes.