For agencies & developers

Bring website evidence into the tools you build.

Use the REST API for reporting and applications, or connect an AI assistant through MCP. Both read the same AnswerMetrix records with scoped access. Compatible remote MCP clients use OAuth; services and legacy clients can use API keys.

Open Settings

In the AnswerMetrix dashboard, go to Settings → API keys.

Create a key

Name it after its use (e.g. "Reporting dashboard") and copy it immediately — the full key is shown only once.

Send it as a Bearer token

Pass the key in the Authorization header of every request.

One set of records. Two ways to work with it.

Build with REST when your application needs structured responses. Use MCP when an approved assistant needs to inspect website findings. Both respect the same site restrictions, access scopes, plan requirements and evidence states.

Limit what each key can read: Select individual evidence scopes — including scores, scan history, crawled pages, issues, fixes, rankings, and briefs — and optionally restrict a key to selected sites.
Handle incomplete results explicitly: AI visibility evidence requires Growth or above. Responses retain complete, partial, unavailable and stale states, so your application can distinguish missing evidence from a measured result.
Separate measurement from site changes: The optional scan:start scope can request or reconnect to a measurement-only scan. It cannot edit a site, approve or deploy fixes, or roll back changes.

Use these records to report observations. They do not establish that a change caused a ranking, citation or traffic result.

Authenticate with a Bearer token

Every request needs an Authorization header with your API key. Each key resolves to your account and can be limited to selected sites and evidence scopes.

curl https://app.answermetrix.com/api/v1/sites \
  -H "Authorization: Bearer amk_live_your_key_here"

{
  "sites": [
    {
      "id": 42,
      "name": "Acme Plumbing",
      "url": "acmeplumbing.co.za",
      "normalizedDomain": "acmeplumbing.co.za",
      "platform": "webflow",
      "createdAt": "2026-06-01T08:00:00.000Z"
    }
  ]
}

Endpoints

All GET endpoints are read-only and return JSON. Replace :id with a site id from GET /api/v1/sites. The scan endpoint appears only for keys explicitly created with the scan:start scope.

GET/api/v1/sitesList your sites

GET/api/v1/sites/:id/scoreLatest AI visibility score snapshot

GET/api/v1/sites/:id/score-historyScore history, oldest first (?limit=1–100)

GET/api/v1/sites/:id/scan-summaryMost recent completed scan summary

GET/api/v1/sites/:id/scan-summary/:snapshotId/:scanRunIdOne exact historical scan summary

GET/api/v1/sites/:id/scan-runsDurable scan status, progress, and snapshot evidence

GET/api/v1/sites/:id/pagesCrawled-page metadata, health, and freshness

GET/api/v1/sites/:id/fixesGenerated fixes and recorded delivery outcomes

GET/api/v1/sites/:id/issuesAudit issues (?status= &category= &severity= &limit=)

GET/api/v1/sites/:id/ai-visibilityRecorded AI visibility evidence (Growth plan and above)

GET/api/v1/sites/:id/rankingsTracked keyword rankings (cached)

GET/api/v1/sites/:id/briefThe site's research brief

POST/api/v1/sites/:id/scanStart or reconnect to a measurement-only scan (scan:start scope)

curl -X POST https://app.answermetrix.com/api/v1/sites/42/scan \
  -H "Authorization: Bearer amk_live_scan_enabled_key"

# Response
{
  "state": "started",
  "status": "scanning",
  "scanRunId": 314,
  "measurementOnly": true
}

Rate limits

Read requests allow 120 requests per minute per key. Scan starts are separately limited to 4 per 15 minutes per key, and overlapping requests reconnect to the active run.

Errors

Errors use a consistent envelope: { "error": { "code", "message" } } — e.g. invalid_api_key, not_found, plan_gated.

Ask your AI assistant about your sites

MCP lets a compatible AI assistant connect to AnswerMetrix and answer questions from your website records. For example: “What did the latest scan find on each site, and which results are incomplete?” The remote server uses OAuth for compatible clients. Before connecting, the browser approval screen shows the requested evidence scopes and sites. API-key headers are available for services and legacy clients. Connections explicitly granted scan access also receive the request_scan tool.

Server URL:
  https://app.answermetrix.com/api/mcp

Header:
  Authorization: Bearer amk_live_your_key_here

For clients that use JSON config (e.g. Cursor):
{
  "mcpServers": {
    "answermetrix": {
      "url": "https://app.answermetrix.com/api/mcp",
      "headers": { "Authorization": "Bearer amk_live_your_key_here" }
    }
  }
}

Use the dashboard connection check or the read-only check endpoint to validate access before you build. It reports effective scopes and site restrictions and can check access to a selected site and evidence type. It does not start a scan or change a website.

curl -X POST https://app.answermetrix.com/api/mcp/check \
  -H "Authorization: Bearer amk_live_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{ "siteId": 42, "evidenceType": "ai-visibility" }'

Claude

Add the remote server URL and complete its OAuth connection flow. AnswerMetrix will ask you to approve the precise scopes and sites.

ChatGPT & Cursor

Add the remote MCP server URL and use OAuth when the client supports it. For legacy configuration-only clients, use the API-key fallback shown above.

Existing keys and new default keys expose read-only tools only. Scan-enabled keys may start a measurement-only scan, but cannot approve, deploy, or roll back fixes.

Find your next useful website improvement.

Start with a free scan of up to 50 pages. Review the findings before choosing what to change.

Start Free Scan

No credit card required. Ongoing delivery needs an eligible plan and a supported connection.