Ranking · #5 of 9
Letter reviewBest for developer-led teams
Letter is a coding agent for growth. Its Measure primitive reads AI answers to the questions you track and records whether they name or cite you; its Fix and Build modes change your site's repository through pull requests. Everything is reachable from the API, the CLI, an MCP server or Slack.
Last reviewedVerdict · 65/100
The pick for developer-led teams: measurement and fixes you script through an API, CLI or MCP, with plans and per-token rates priced in public. Not for anyone who wants a point-and-click dashboard.
Who it suits: Developer-led teams that want scriptable, API- and MCP-accessible primitives to measure AI visibility and ship the fixes as pull requests.
Wrong fit: Pick something else if nobody on the team writes code, if you want a ready-made reporting dashboard, or if your site lives only in a no-code builder.
Pricing as published
- Hobbyist: $25/mo, 2,500 tokens
- Basic: $100/mo, 10,000 tokens
- Starter: $500/mo, 50,000 tokens
- Growth: $1,000/mo, 130,000 tokens
- Scale: $2,500/mo, 400,000 tokens
- Enterprise: $10,000/mo; Custom on request
- AI visibility answer: 12 tokens each; 1,000 free tokens to start
Strengths
- API, CLI and MCP on every plan, so Claude Code, Codex or any MCP agent can read visibility data and act on it.
- Fixes land as pull requests on your own repo (llms.txt, structured data, thin pages), with a preview before anything merges.
- Usage pricing with published plans and rates: Hobbyist from $25 a month; an AI visibility answer read costs 12 tokens.
- Every account starts with 1,000 free tokens, no card.
Limits
- Not a point-and-click dashboard: visibility data is read through the API, CLI, MCP or Slack, and reports are what you script.
- Which AI engines it reads is not listed on its public pages; ask Letter or check letter.dev before buying.
- No CSV export or BI connector is listed; you pull the data yourself.
- Built for teams that work in git: the fixes assume your site lives in a repository.
At a glance
| Tracked engines | Not listed publicly: check letter.dev or ask Letter |
|---|---|
| API / MCP access | API, CLI and MCP on every plan |
| Reporting | Through the API, CLI, MCP and Slack; no dashboard reports or CSV listed |
| Beyond tracking | Changes: opens pull requests that fix the site and add pages |
| Pricing model | One token pool, usage-based; plans up to Enterprise public, Custom on request |
| Best-fit team | Developer-led teams and technical founders |
Score breakdown
Each criterion is scored 0 to 3 by the rule on How we rank.
| Criterion | Weight | Score | Why |
|---|---|---|---|
| Engine coverage | 25% | 0 / 3 | The engines it reads are not listed on its public pages, so it scores zero here until they are. |
| API and MCP access | 20% | 3 / 3 | API, CLI and MCP on every plan, from $25 a month. |
| Reporting and exports | 15% | 2 / 3 | Full data through the API and MCP; no CSV export or BI connector listed. |
| Pricing transparency | 15% | 2 / 3 | Hobbyist to Enterprise are priced publicly with per-token rates; a Custom plan is quoted on request. |
| Measurement and optimisation | 15% | 3 / 3 | Opens pull requests that change the site: fixes, structured data, new pages. |
| Cost to start | 10% | 3 / 3 | Hobbyist costs $25 a month, and every account starts with 1,000 free tokens. |
| Total | 100% | 65 | Sum of weight × score ÷ 3, rounded. |
Checked against: Letter pricing, Letter API docs, Letter agents.md