Skip to content
Leadee

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.

Updated

What will I be able to build with the Leadee API?

The Leadee API will cover the full GEO (generative engine optimization) workflow: run a prompt set across AI answer engines, read back mention rate, citation rate, position, share of voice and sentiment with confidence intervals, pull the Citation Graph for your niche, and read or create Fix Engine tickets. The same API backs the Leadee dashboard and the MCP (Model Context Protocol) server, the open standard that lets an AI agent call tools like Leadee's directly.

  • Base URL: https://api.leadee.ai/v1
  • Format: JSON requests and responses over HTTPS
  • Versioning: v1 is the only planned version. Changes inside v1 will be additive.
  • Machine-readable spec: /docs/openapi.json, rendered in the interactive API reference

The free scan, today

The one endpoint that is real right now is the free scan: POST /v1/free-scan, which takes a domain and returns an AI-crawlability score. Try it on the home page or the free tools hub.

Where to go next

  1. Authentication: the planned API key scheme.
  2. Conventions: response envelopes, pagination, errors and rate limits.
  3. Visibility Tracker: run prompts across engines and read back metrics.
  4. Citation Graph: which domains and URLs get cited in your niche.
  5. Fix Engine: fix tickets and the re-measurement loop.
  6. API Reference: the current OpenAPI stub for every planned endpoint.

Support

Questions about the roadmap or the API: email [email protected]. For which plan includes which API/MCP call allowance, see pricing. For the full documentation index, see the docs home.

Getting started questions

Is the Leadee API live today?

Not yet. The only endpoint that is real right now is the free AI-crawlability scan (POST /v1/free-scan); the Visibility Tracker, Citation Graph and Fix Engine endpoints described in these docs are planned and documented ahead of implementation.

What will I be able to do with the Leadee API once it ships?

Run a prompt set across AI answer engines, read back mention rate, citation rate, position, share of voice and sentiment with confidence intervals, pull the Citation Graph for your niche, and read or create Fix Engine tickets — the same API that will back the Leadee dashboard and MCP server.

Does the Leadee API support MCP (Model Context Protocol) today?

Not yet — MCP support ships alongside the rest of the planned API. Once it does, an MCP-connected AI agent will call the same endpoints and authenticate with the same workspace API key as a direct API call.

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.