AI visibility tool with API access
Yes, through Limelit's MCP server: a JSON-RPC 2.0 API over HTTPS that any client can call with a personal API key, free on every account.
How the API works
- One endpoint
- Your code or any MCP client sends JSON-RPC 2.0 requests over HTTPS to the MCP server, with a personal API key from Settings.
- No REST API for your data
- There is no REST API for your visibility data. The dashboard's /rest/v1 routes use your browser session (a cookie), not an API key.
- Keys are shown once
- A key is shown once, when you create it, and Limelit stores only a SHA-256 hash of it. Afterwards you see its first 8 characters, so you can tell keys apart.
- Never more than your role
- A key's role is the lower of the role it was created with and your current role, checked on every call, so a demoted user's keys lose access at once.
- Reads are free
- Reading your data is free. Tools that start runs or write drafts spend credits, so confirm the cost per tool before you call it.
- ChatGPT signs in instead
- The ChatGPT app signs in to your Limelit account (OAuth) instead of using a key.
What it does not do
- Offer a REST API for your visibility data: the MCP server is the API.
- Publish an OpenAPI spec: clients list the tools over MCP itself.
- Show a key again after you create it.
Where to send requests
The endpoint is https://api.limelit.co/mcp.Claude Desktop, Claude Code, Cursor, VS Code and Windsurf connect with the same key. Every tool is listed by name on the MCP server page.
The things people ask us first.
Yes. Limelit's MCP server is a JSON-RPC 2.0 API over HTTPS, and any MCP client, or your own code, can call it with a personal API key.
No. The dashboard's /rest/v1 routes use your browser session, not an API key; the MCP server is the API.
No. The MCP server is free on every account. Reading your data is free; tools that start runs or write drafts spend credits.
No. The key is shown once and stored only as a SHA-256 hash; afterwards Limelit shows just its first 8 characters.
No. A key takes the lower of the role it was created with and your current role, checked on every call.