# Citaeo > The growth engine for the agentic web. Citaeo watches where ChatGPT, > Perplexity, Gemini and Claude cite a brand — or its rivals — drafts the > fixes in the brand's voice, and proves every AI visitor that arrives > with a cookieless first-party pixel. ## What Citaeo does - Watch: weekly probe sweeps return verbatim answers across ChatGPT, Perplexity, Gemini and Claude — where the brand is cited, where rivals are, and the exact wording. Never a black-box score. - Fix: every visibility gap arrives as an evidence-backed card with the fix already drafted in the brand's voice by a named agent crew (Vesper watches rivals, Echo asks the engines, Wren writes, Moss tends the authority map). A human always approves before publishing. - Prove: a cookieless pixel verifies AI crawlers (GPTBot, ClaudeBot, PerplexityBot) reading the site and AI-referred visitors arriving. No cookies, no fingerprinting — identity is a daily-rotating server-side hash. - Compound: a Brand Brain learns from every probe, edit, and verified visit, so each cycle outperforms the last. ## Pricing Starter $99/mo · Growth $249/mo · Agency $599/mo. Every brand starts with 14 days of full Growth access, no card required. Drafts are unlimited on every tier. ## Agent access (MCP) Citaeo is operable by agents. Any MCP client — Claude, Claude Code, or a custom agent — can connect at https://citaeo.vercel.app/api/mcp/mcp?key= (streamable HTTP; tokens are minted per brand in Settings -> Agent access). Keys carry a role their minter chose: suggest keys read everything (brand, visibility, verbatim answers, queue, Brain, traffic, authority map, content) and file briefs as proposed cards; operate keys also act with the minting editor's authority — decide queue cards, edit drafts, publish (the agent receives the deploy-ready SEO/GEO bundle and reports the live URL back for verification), schedule, comment, write Brain notes, and run engine cycles. Every action is attributed to the human who minted the key. ## Start Enter a domain at https://citaeo.vercel.app/signup — the engine starts reading it immediately; the account is created at the end of onboarding.