Questions,
answered.

A hosted endpoint that lets AI agents — Claude Code, Claude Desktop, Cursor, or any MCP-capable client — read your AI-visibility data and trigger audits without leaving the tool. It exposes your projects, visibility reports, citations, mentions, recommendations, and score history.

Every paid plan — Pro, Agency, and Enterprise. Access turns on automatically once your account has a paid project; there is no separate enablement step. Free and Lite do not include API or MCP access.

Account owners create keys in Settings → API access (the Connect (MCP) tab links there too). The full key is shown once at creation — store it in your secrets manager. A read-only key covers every read tool; choose "read and trigger audits" to let an agent start audits.

Add the server with your key as a Bearer token:

claude mcp add --transport http citesurge https://citesurge.com/api/mcp \
  --header "Authorization: Bearer <YOUR_KEY>"

Clients that launch local servers use mcp-remote to reach the hosted endpoint at https://citesurge.com/api/mcp. The full config block is in the MCP documentation.

Yes. A key with no project scope sees every project in the account: the agent calls list_projects, then passes the project slug to each tool. Scope a key to specific projects when you create it if you want to limit its reach.

Install the CiteSurge agent skills (citesurge-fix and citesurge-report) with one command:

npx @citesurge/skills            # into ./.claude/skills
npx @citesurge/skills --global   # into ~/.claude/skills

A 401 means the key is missing, malformed, revoked, or expired — create a new one. A 403 means the account has no paid project and no access yet — add or upgrade to a paid project. Confirm the header is exactly Authorization: Bearer cs_live_….

It gives you programmatic access to everything the dashboard shows: scores, citations, mentions, findings, and board-ready reports (Markdown or PDF), plus audit triggers. It uses the same API keys as the MCP server and is included on every paid plan — Pro, Agency, and Enterprise. See the API documentation for the full endpoint list.

The full machine-readable spec is published as OpenAPI 3.1 at /api/v1/openapi.json — import it into Postman, Insomnia, or your client generator of choice.

Yes. Register an endpoint in Settings → API access to receive signed audit_run.completed and audit_run.failed events instead of polling. Every delivery is signed so you can verify it came from CiteSurge; the API documentation covers the signature scheme.