Topic hub

Developer mascots that are installable, shareable, and API-ready

A developer mascot should do more than sit in a hero image. On AgentPets it becomes an installable asset with a public page, share card, badge, embed, and API payload.

Mascots as distribution assets

The best mascot is not just a logo. It appears in README badges, launch posts, docs, and profiles where developers already share proof of work.

Keep attribution obvious

Creator pages, credits, and public profile links help the asset travel without stripping the person behind it out of the story.

Make it easy to remix later

The builder and API are intentionally versioned surfaces. They let the product evolve toward custom pet design without breaking existing install and share flows.

Can I use a pet as a GitHub README badge?

Yes. AgentPets exposes SVG badge URLs that can be embedded in READMEs and linked back to the pet page.

Can a mascot point to my creator profile?

Yes. Approved pets keep creator credit and public profile paths so the sharing loop can bring users back to the creator.