# About Codex Pets

Codex Pets is a moderated community gallery and agent-readable registry for downloadable Codex pet packs. Each approved listing is a portable package with pet.json metadata, a validated spritesheet atlas, downloadable ZIP assets, stable public URLs, and install guidance for Codex users.

## What the site provides

- Public gallery pages for approved pets.
- Package assets: pet.json, spritesheet.webp or spritesheet.png, and ZIP downloads.
- Agent-readable discovery through llms.txt, llms-full.txt, OpenAPI, JSON, TOON, markdown fallbacks, and MCP.
- Human workflows for requesting a new generated pet or submitting an existing package for moderation.

## Authority and citations

Wikipedia and Wikidata are off-site authority signals. The application can expose stable names, canonical URLs, structured data, and discovery files, but a Wikipedia article or Wikidata entity should only be created after independent coverage establishes notability. When a valid Wikidata item exists, it should use official website property P856 for https://pets.ydb-qdrant.tech/.

## 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.