Vendor documentation last checked 13 Nov 2026

How do you get AI visibility data into your own code? Guides to the REST APIs, MCP servers and connectors that expose it.

mcp.json
{
  "mcpServers": {
    "finseo": { "url": "https://api.finseo.ai/v1/mcp" },
    "ahrefs": { "url": "https://api.ahrefs.com/mcp/mcp" },
    "semrush": { "url": "https://mcp.semrush.com/v2/mcp" },
    "dataforseo": { "url": "https://mcp.dataforseo.com/v3/mcp" },
    "peec": { "url": "https://api.peec.ai/mcp" },
    "profound": { "url": "https://mcp.tryprofound.com/mcp" },
    "otterly": { "url": "https://data.otterly.ai/mcp" },
    "rankscale": { "url": "https://mcp.rankscale.ai/mcp" }
  }
}
Published MCP endpoints, from vendor docs
Documented here
  • Finseo
  • Profound
  • Peec AI
  • Otterly.AI
  • Semrush
  • Ahrefs
  • Scrunch
  • Promptwatch
  • Rankscale
  • DataForSEO

Every access path, documented. Endpoints, auth and the plan that unlocks each.

All guides
Aerial photograph of rows of shipping containers in a port terminal, a straddle carrier moving between lanes

Browse by access path. Five topics, one hub page each.

From AI answer to your stack. Every guide covers one hop of this path, or shows how to build it yourself.

  • ChatGPT
  • Google AI Mode
  • Gemini
  • Perplexity
  • Claude
  • Copilot
Tracking platformprompts · answers · citations
  • Your code
  • AI assistant
  • Looker Studio · BigQuery
Or skip the platform: build your own tracker

Checked against vendor documentation. Endpoints, auth and plans, last verified 13 Nov 2026.

How we test