Skip to content
Leadee

Leadee developer documentation

The Leadee API and MCP server are the planned developer surface behind the Leadee dashboard: authenticating requests, running Visibility Tracker prompts across AI answer engines such as ChatGPT and Gemini, reading results from the Citation Graph, and working Fix Engine tickets programmatically instead of through the web dashboard.

By the Leadee team at Netbase JSC · Updated

Start here

  • Getting started

    The Leadee API and MCP server will let you run the Visibility Tracker, read the Citation Graph and manage Fix Engine tickets programmatically once the backend ships; today the only live endpoint is the free AI-crawlability scan. This page walks through the planned workspace, authentication and first-call flow end to end.

  • Authentication

    Leadee API requests will authenticate with a single workspace-scoped API key sent as a header on every call, counted against your plan's monthly API/MCP allowance whether the caller is your own code, a script, or an MCP-connected AI agent. This page covers creating, rotating and safely storing that key.

  • Conventions

    Every planned Leadee API response follows the same shape: a data envelope, cursor-based pagination, HTTP status codes for errors, and rate-limit headers tied to your plan tier. This page documents those conventions so client code written against the v1 API keeps working as new fields get added.

Modules

  • Visibility Tracker

    Leadee's Visibility Tracker API will let you start a run of your prompt set across AI answer engines such as ChatGPT and Gemini, then read back mention rate, citation rate, position, share of voice and sentiment, each with a confidence interval, through the planned endpoints described on this page.

  • Citation Graph

    Leadee's Citation Graph API will return which domains and URLs AI engines cite for your prompt set, built from the same answers the Visibility Tracker already collects, so there is no separate run to configure. This page documents the planned citation-listing endpoint and the gap report that flags citations only other market players get.

  • Fix Engine

    Leadee's Fix Engine API will turn a visibility drop into a concrete ticket, such as a schema fix or a content brief, and trigger a re-measurement run once you mark it resolved, closing the loop between finding a problem and confirming the fix worked. This page documents those planned endpoints.

Reference

  • API Reference

    The planned API surface with request and response schemas, as an OpenAPI 3.0 document.

Looking for something else?

How we compute confidence intervals and define each metric is on the methodology page. Running GEO for client brands? See the Agency plan.

Documentation questions

Can GEO guarantee results?

No. AI answer engines change their output frequently, and no vendor — including Leadee — can guarantee a ranking or a mention. Leadee publishes confidence intervals on every metric so you can see how much a result can vary run to run.

How does Leadee measure AI visibility?

Leadee runs your prompt set against each AI engine on a weekly to daily schedule, depending on plan, through official vendor APIs (OpenAI, Gemini, Perplexity, Anthropic, DataForSEO) — never by scraping consumer chat interfaces — and reports mention rate, citation rate, average position, share of voice and sentiment with a 95% confidence interval.

Who do I talk to?

Email support@leadee.ai or use Talk to an expert at https://leadee.ai/contact-sales — the Netbase JSC team behind Leadee replies by email or WhatsApp — or WhatsApp the CEO directly at https://wa.me/84937869689.