Skip to content
Leadee

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.

Updated

Planned credential: the API key

Leadee's API will authenticate with a single workspace-scoped API key, sent as a bearer token header on every request:

http
Authorization: Bearer <leadee_api_key>

Each paid plan includes a monthly allowance of API/MCP calls (see the pricing page); MCP (Model Context Protocol) is the open standard that lets an AI agent call tools like Leadee's directly. The key you use is counted against your workspace's allowance regardless of whether the call comes from your own code, a script, or an MCP-connected AI agent.

How do I create and rotate an API key?

Once the dashboard ships, API keys will be created and revoked from your workspace settings. Rotating a key immediately invalidates the old one — there is no overlap window, so plan a coordinated deploy when you rotate a key already in use.

MCP server

The same API key will authenticate requests from the Leadee MCP server, so an AI agent with MCP access can read Visibility Tracker metrics or Fix Engine tickets using the same credential as a direct API call.

Never publish a key client-side

API keys are a server-side credential. Leadee has no separate "public" or browser-safe token — never embed an API key in a browser bundle or a public repository.

Related

Authentication questions

How many API keys does a Leadee workspace get?

One active, workspace-scoped API key that authenticates every request, including calls made through the Leadee MCP server. Once the dashboard ships, that key is created and rotated from your workspace settings.

Is it safe to use a Leadee API key in browser code?

No. API keys are a server-side credential only — Leadee has no separate public or browser-safe token, so never embed one in a browser bundle or a public repository.

What happens to requests made with an old key after I rotate it?

They will fail immediately. Rotating a key invalidates the old one with no overlap window, so plan a coordinated deploy of the new key before you rotate one already in use.

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.