Getting started

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

Updated

What you will be able to build

The Leadee API will cover the full GEO 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 server.

  • 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].