Developers

Your AI agent can read the battle card.

Every number in your reports, over a simple REST API. Included with every account, no enterprise gate: create a key in your dashboard and go.

Authentication

curl https://saymetry.com/api/v1/scans \
  -H "Authorization: Bearer sk_live_..."

Every key is read-only (the API is GET-only). When you create one you can scope it to a single client, so it returns only that client's scan and nothing else about your account. Agencies use this to hand a client API access to their own report without exposing the rest of the roster. A scoped key requesting any other scan gets a 404. Scope a key from the API-keys panel in your dashboard.

Endpoints

GET /api/v1/scans
Your scans: company, status, run date, rank.
GET /api/v1/scans/{id}
Summary: rank, sentiment, engines, and the sampling block (mention probability with its 95% interval).
GET /api/v1/scans/{id}/leaderboard
Every name the AIs surfaced, ranked. Add ?detail=engines for per-engine breakdowns.
GET /api/v1/scans/{id}/citations
The cited domains, and with ?level=url the exact pages.
GET /api/v1/scans/{id}/actions
The prioritized plan and market opportunities, grounded in the scan’s own evidence.
GET /api/v1/scans/{id}/landscape
Competitor battle cards and the open ground nobody owns. No other vendor has an attack-plan endpoint.
GET /api/v1/scans/{id}/press-targets
Where to get published, scored and ordered.
GET /api/v1/scans/{id}/history
The weekly time series for tracked scans.
GET /api/v1/account
Plan, scan count, rate-limit state.

Limits and roadmap: 60 requests/minute per key, JSON responses, keys managed in the dashboard (max 5). Coming next: an MCP server so Claude, Cursor and ChatGPT can query your visibility directly, and POST /v1/scans to order scans programmatically. Want either sooner? Tell us.