Remember the API and MCP server we said was coming next? 

It's finally live now. 🎉

Both give you read-only access to everything the dashboard runs on: brand visibility, mentions, citations, the prompts you track, and the fan-out queries LLMs actually run to answer you. 

They're two ways to reach the same data.

• The API is for building. Pull your data into a warehouse, a BI tool, a scheduled report, or your own script.

• The MCP is for asking. Connect Claude, Cursor, or any AI assistant and ask about your visibility in plain English, no code.

Use whichever fits how you work, or both. 

They share the same ak_live_ key, they're both on the Business and Enterprise plans, and setup for either takes a couple of minutes. Here's what's in the data, then how to turn on each one.

What you get, either way

Everything is built around one idea: a domain, the prompts you track for it, and how AI engines respond. 

The API exposes it as eight read endpoints; the MCP wraps the same data as tools your assistant can call. Here's the full set.

Build With The API

Step 1: Check you have access

The API is on the Business plan and Enterprise. Each key is scoped to a team, and that team needs developer access switched on. On Starter or Pro, you'll need to upgrade first.

Step 2: Create a key 

In the app, open Settings → Developers and click Create API Key. Copy the key (it starts with ak_live_) and store it somewhere safe. You won't see it in full again.

Step 3: Validate it before you build anything 

A call to GET /api/v1/validate confirms the key is live and shows which teams and domains it can reach. Run it first whenever something downstream returns a 401 or 403.

One call confirms the key works and shows exactly what it can reach:

curl https://api.aiclicks.io/v1/validate \

  -H "Authorization: Bearer YOUR_API_KEY"

You get back your teams, the domains the key is allowed to touch, and your rate limit:

{

  "valid": true,

  "key_type": "api_key",

  "teams": [{ "name": "AIclicks", "developer_access": true, "domains_count": 3 }],

  "allowed_domains": [

    { "id": "10df2f96-...", "name": "AIclicks", "website": "https://aiclicks.io/" }

  ],

  "rate_limit": { "limit_per_minute": 60, "remaining": 59 }

}

If developer_access reads false, the key is valid but API access isn't on for the team yet. That's the first thing to check when a call comes back empty.

Step 4: Grab your domain_id 

Hit GET /api/v1/domains returns every domain the key can see, each with an id. You pass that domain_id to every data endpoint.

List your domains and copy the id you want:

curl https://api.aiclicks.io/v1/domains \

  -H "Authorization: Bearer YOUR_API_KEY"

Step 5: Pull your data

Use the API Reference to find the endpoint you need. This returns daily visibility for last 90 days:

curl "https://api.aiclicks.io/v1/domains/DOMAIN_ID/visibility?days=90" \

  -H "Authorization: Bearer YOUR_API_KEY"

Every response comes back as JSON with a data field and a generated_at timestamp. Pagination, date windows, and the rest of the endpoints are in the API reference.

Validate, find your domain, pull data. You're capped at 60 requests per minute, which covers reporting and daily syncs comfortably. Space out heavy jobs so you don't hit the ceiling.

Or Just Ask, With The MCP

If you'd rather not write calls at all, connect the MCP and ask your AI assistant. 

We host it at https://mcp.aiclicks.io/mcp, it uses the same ak_live_ key, and it works with Claude Desktop, Claude Code, claude.ai on the web, and Cursor. 

Once it's connected, you can ask things like:

• "How visible is my brand in AI search this week?"

• "Which sources are LLMs citing when they mention us?"

• "Compare our share of voice against competitors over the last 30 days."

• "Which prompts are losing visibility month over month?"

• "Where are we underperforming on Claude vs ChatGPT?"

Your assistant routes each question to the right tool and hands back live numbers.

Claude Desktop

Step 1: Get your key from Settings → Developers → Create API Key.

Step 2: In Claude Desktop, go to Settings → Developer → Edit Config to open claude_desktop_config.json.

Step 3: Paste this inside mcpServers, and replace YOUR_API_KEY with your key:

{

  "mcpServers": {

    "aiclicks": {

      "command": "npx",

      "args": [

        "-y",

        "mcp-remote",

        "https://mcp.aiclicks.io/mcp",

        "--header",

        "Authorization: Bearer YOUR_API_KEY"

      ]

    }

  }

}

Step 4: Restart Claude Desktop. (This path uses npx, which ships with Node.js. If you don't have it, install the LTS version from nodejs.org.)

Step 5: Ask: "Validate my AIclicks key and list my domains." If it lists your domains, you're connected.

Claude Code

One command:

claude mcp add --transport http aiclicks https://mcp.aiclicks.io/mcp \

  --header "Authorization: Bearer YOUR_API_KEY"

Run claude mcp list and aiclicks should show as Connected.

Cursor

Add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per project), then check the MCP panel shows aiclicks as Connected:

{

  "mcpServers": {

    "aiclicks": {

      "url": "https://mcp.aiclicks.io/mcp",

      "headers": { "Authorization": "Bearer YOUR_API_KEY" }

    }

  }

}

Any other client

Point it at https://mcp.aiclicks.io/mcp over streamable HTTP, with the header Authorization: Bearer YOUR_API_KEY. The full client-by-client steps, the complete tool list, and ready-made prompt recipes are in the MCP docs.

Five ways to put it to work

You've got a key and data coming out of it. Here's where that data earns its place in your week, from a simple reporting pull to the endpoint that tells you what to publish next.

1. Get your AI visibility out of the dashboard

Right now your visibility, citations, and mentions live inside AIclicks. Your ad spend sits in one place, your organic numbers in another, your revenue in a third. 

The API lets you pull the four time series into the same Looker, Metabase, or Google Sheet as the rest of your marketing data, so AI search shows up in the weekly view you already read instead of a tab you have to remember to open. 

Pull them on a schedule and you have a live feed.

2. Turn fan-out queries into a content roadmap

This is the endpoint to start with. 

When an LLM answers one of your tracked prompts, it runs its own background searches to ground the answer. /fanout-queries returns those real searches, grouped under the prompt that triggered them and attributed to the model that ran them. 

That list is the closest signal there is to "what should I write to get cited", because it's what the models are already looking for on your topics.

Pull 90 days, flatten the result, and count how often each query repeats. The ones at the top are your next briefs. Filter by model and you can see what ChatGPT is searching for that Perplexity isn't.

Do this: pull fan-out queries for your top domain, rank them by frequency, and hand the top 20 to whoever writes your briefs.

Here’s a glimpse:

Pretty simple, isn’t it?

Go give it a try!

3. Join it against your SEO stack

AIclicks tells you where AI mentions and cites you. Your rank tracker tells you where you sit in classic search. 

Put the two side by side with the API and the gaps surface on their own: prompts where competitors get cited and you don't, topics where you rank on Google but stay absent from AI answers. Learn more about how to get cited by AI.

Each gap is a specific page to write or a specific site to pitch.

4. Build reporting that runs itself

If you export CSVs by hand every month for a client deck or an exec update, the time-series endpoints replace that work. 

Point a script or an automation flow at the visibility and citations series, format it once, and the report rebuilds itself on whatever schedule you set. 

Because the API is read-only, a scheduled job can only ever report, never touch your setup, which is exactly the behavior you want from something running unattended.

If you run four or more clients, this replaces a morning of copy-paste.

5. Watch every brand from one board

For agencies and multi-brand teams, loop over /domains, pull the same metrics for each, and you have one visibility board across every client without opening a workspace per account. 

One glance tells you who climbed and who slipped this week, and where to spend your outreach and mention effort next.

Before you build, a few things

Worth knowing before you wire in either one:

• Both are read-only. You can read every metric, but you can't add prompts or change settings through them. That still happens in the app.

• Most data caches for about an hour. A change you make in the dashboard shows up after the cache clears, not the instant you make it.

• The default rate limit is 60 requests a minute per key, shared across the API and the MCP. Plenty for reporting. Batch your calls if you're looping over a lot of domains.

• A key only sees the domains it's scoped to. Run /validate (or ask the MCP) if a domain you expect is missing.

• Single days bounce. Read the 30 and 90-day shape, not any one date.

Turn it on

On Business or Enterprise? Open Settings → Developers and create a key. From there:

• To build, the full endpoint reference is at docs.aiclicks.io/api.

• To just ask, connect the MCP server to Claude or Cursor with that same key.

Not on those plans yet? API and MCP access ship with Business. If you're already pulling AI visibility into reports by hand, it pays for itself in the time you stop spending on exports.

That's the API and the MCP. Go build something with it.

Got a feature you want next? Send it to our feature request board. We read every one.

New to AIclicks? Start your 3-day free trial.