Ask your AI assistant
Connect Claude, Cursor or VS Code and ask which prompts you are losing, who wins them and which sources they cite.
Read the same visibility, share of voice, source and answer data you see in Gensiv from your own code, or ask an AI assistant about it through the MCP server. One API key, every brand in your workspace.
Answers captured from 6 AI engines, in every market you sell in.
The Gensiv API is a read-only REST API for the AI visibility data Gensiv collects: metrics per brand, competitor, day, engine, prompt and topic, the sources AI engines cite, every individual answer, alerts, action plans, articles, Reddit opportunities and AI referral traffic. The MCP server exposes the same data to AI assistants such as Claude and Cursor, so you can ask questions instead of writing queries.
The numbers from your Gensiv dashboard, in the tools your team already uses.
Connect Claude, Cursor or VS Code and ask which prompts you are losing, who wins them and which sources they cite.
Workspace keys, shown once, stored hashed, deleted in one click.
JSON responses, cursor pagination, clear error codes and a full OpenAPI spec.
Any table as CSV and any dashboard as a PDF, with your date range and filters applied.
Demo data for Cadence, a fictional project management brand.
| Name | Last used | |
|---|---|---|
Looker Studio reportgsk_4f9aQ2… | Today | |
Claude MCPgsk_b21cT8… | Today | |
Warehouse syncgsk_7d0eL5… | Yesterday |
Your data leaves Gensiv only through keys you create, and only as much as you ask for.
The API and MCP server can read your data but never change brands, prompts or settings.
A key reads every brand in its workspace and nothing else.
Each key can make 120 requests a minute, with clear headers and retry times.
Every endpoint, field and metric formula is in the developer docs.
Last updated
Every Pro tier and Enterprise. Workspace owners and admins create keys in Settings → API keys.