Leadee developer documentation

The Leadee API and MCP server are the planned surface behind the Leadee dashboard: running Visibility Tracker prompts across AI engines, reading the Citation Graph, and working Fix Engine tickets.

Updated

Start here

  • Getting started

    How the Leadee API and MCP server will work once the backend ships.

  • Authentication

    A single API key per workspace, sent as a header on every request.

  • Conventions

    Response envelopes, pagination, errors and rate limits.

Modules

  • Visibility Tracker

    Run your prompt set across AI engines and read back every metric with a confidence interval.

  • Citation Graph

    See which domains and URLs AI engines cite in your niche.

  • Fix Engine

    Fix tickets generated from a run, plus the re-measurement loop after you ship a fix.

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.