Wire AI-visibility data into your systems and agents
One API key, two surfaces: REST Open API v1 for your code, and an MCP endpoint your AI agents (Claude, Cursor, any MCP client) can call directly.
1 ยท Get an API key
Create an API key on the Settings page after logging in (the plaintext is shown only once โ store it safely). Open API and MCP are Pro-plan features; each key is limited to 600 requests per hour.
2 ยท REST Open API v1
Three read-only endpoints plus one for logging publications (JSON; scores/counts are server-computed strings โ don't recompute):
GET /api/v1/brandsmonitored brandsGET /api/v1/brands/:id/scoreslatest overall + per-engine + 30-day trendGET /api/v1/brands/:id/citationstop 20 cited domains (workspace-level aggregate; :id is for ownership validation)GET / POST /api/v1/brands/:id/publicationslog a publication that has already happened, plus the monitored questions it targets, for per-question before/after
โ The publications endpoint records facts that have already happened โ OrcaScope never publishes anything on your behalf. There is no DELETE: correct mistakes in the console, where you can see exactly which record you are removing.
The POST response includes utmStatus (compliant / partial / untagged) and utmWarnings: we check the link against the UTM convention (utm_source=platform, utm_medium=earned-content, utm_campaign=batch). utmWarnings is an array of machine codes, not prose โ one of unparsable / missing_source / missing_medium / medium_mismatch / missing_campaign, where medium_mismatch also carries an actual field with the value we found. Codes rather than sentences so you can automate against them: wording changes with language and revision, codes do not. โ Non-compliance never blocks registration โ it is recorded as-is. โ This is link-parameter compliance only, not traffic attribution: traffic data lives in your own analytics tool.
curl https://orca-scope.com/api/v1/brands \
-H "Authorization: Bearer geo_live_..."3 ยท MCP endpoint (for AI agents)
A standard MCP (Model Context Protocol) Streamable HTTP endpoint โ stateless JSON-RPC 2.0. Add it to any MCP client and your agent can query brand visibility scores, citation sources, industry benchmarks and the engine list directly.
Endpoint
POST https://orca-scope.com/api/mcp
Authorization: Bearer geo_live_...Tools (first batch, all read-only)
list_brandsget_brand_scoresget_brand_citationsget_benchmarkslist_engines
Client config (Claude Code / Cursor, generic format)
{
"mcpServers": {
"orcascope": {
"type": "http",
"url": "https://orca-scope.com/api/mcp",
"headers": { "Authorization": "Bearer geo_live_..." }
}
}
}Or verify with curl
curl -X POST https://orca-scope.com/api/mcp \
-H "Authorization: Bearer geo_live_..." \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Design discipline
- The first batch of tools is read-only: no write, email or billing capability is reachable via MCP or the Open API.
- Identity comes only from the API key: tool parameters never contain tenant/user fields, and isolation is enforced by database row-level security (RLS).
- When data is insufficient we return null/empty honestly (same degradation discipline as the product) โ numbers are never fabricated.