API
Read your presence data from your own stack.
Updated October 20, 2026
A read-only HTTP API for teams who want the numbers inside their own reporting rather than in a console. Available on the plans that include API access.
What it exposes
Two routes. GET /api/v1/projects lists your projects, and GET /api/v1/projects/:id/:resource reads one of overview, prompts, ai-searches, sources, citations, runs, opportunities or timeseries.
What it is for
Pulling presence, prompts, runs and sources into a warehouse, a client dashboard or a weekly report that you already build somewhere else. It is backed by the same read layer as the console, so the numbers match, and by the same access rules, so a key can never reach a project its account does not own.
What it is not for
Writing. The API does not create prompts, trigger runs or change configuration: that is what the MCP connection is for, and keeping writes on one path keeps the audit trail in one place.
Keys are bearer tokens
A key is shown once, carries the access of the account that made it, and should live in your secret store rather than in a repository. Rotate it by making a new one and deleting the old.