CLI commands
cnry runs --tail --format jsonOpen source · Self-hosted
Canonry watches what ChatGPT, Claude, Gemini, and Perplexity say about you, joins it to your search and server evidence, and hands your agent the tools to fix what it finds.
Latest release v4.192.0. Local SQLite. Your provider keys. Your infrastructure.

brew tap canonry/canonrybrew install canonryThen run cnry init and cnry serve.
Any agent · Local workflow
CLI, REST, MCP, webhooks, or a native Codex or Claude Code plugin. AUQ, a SaaS SEO and AEO agency, reviewed that surface from the outside.
Use the native plugin or standalone MCP, not both. Plugin guide
codex plugin marketplace add Canonry/canonrycodex plugin add canonry@canonryFirst run cnry init --skip-skills --skip-mcp, then cnry start.
One typed system
cnry runs --tail --format jsonGET /api/v1/citationstools/competitor_gapcitation.gainedMeasurement context
Align by date and URL. Patterns, not attribution. Server events catch the crawler and referral activity a browser analytics tag never records, and the full walkthrough covers the loop from first sweep to client report.
Impressions · Clicks · CTR

Crawlers · Fetches · Referrals

The operating loop
Full operating surface
Two-minute walkthrough
Watch on YouTubeDirect answers
Canonry is the operating system for AEO: an agent first AEO + web analytics monitoring and execution platform that is open source and self-hosted. It tracks how AI answer engines mention and cite a site, joins that evidence with search, analytics, technical, and traffic data, and exposes the same system through a dashboard, CLI, REST API, MCP tools, and webhooks.
No. Canonry is the layer underneath it. It supplies evidence, typed tools, budgets, and verification to the agent and local workflow you already use, through CLI, REST, MCP, webhooks, or a native Codex or Claude Code plugin. Aero ships as the built-in agent.
Canonry is self-hosted and single-tenant. By default, its project data lives in one SQLite file on your machine or server. You control the provider keys, backups, and deployment.
Canonry supports Gemini, OpenAI, Anthropic Claude, Perplexity, and OpenAI-compatible local models. A browser provider can also capture citations from supported consumer interfaces when the web experience differs from an API response.
Codex and Claude Code can install the native Canonry plugin from the Canonry marketplace. The CLI remains the simplest universal path because every command can return JSON. Canonry also exposes a versioned REST API, an MCP adapter with toolkits that load on demand, and signed webhooks for event-driven workflows.
Yes. The source, issues, architecture, and documentation are public in the Canonry GitHub repository. The npm package is published as @canonry/canonry under the Functional Source License, which converts to Apache 2.0.
Open source · Local-first
Install Canonry and run the whole loop yourself.