> ## Documentation Index
> Fetch the complete documentation index at: https://areyoufoundbyai.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Share client AI data with scoped access keys

> Create Are you found by AI? MCP access keys scoped to specific client sites, hand them over with one copy, and revoke them in one click.

Your agency network page is a live MCP server: add its link to Claude, Cursor or any MCP client and your AI reads every client's scores, movement, mentions and fix plans mid-conversation. Scoped keys extend that to your team without handing everyone everything. Each key reaches only the client sites you choose. The network link is yours, scoped keys are theirs, and every key can be watched and revoked without touching anything else.

## What scoped keys are

A key is a credential for the network catalogue of the Are you found by AI? MCP server. Whoever holds it can connect their AI to the sites that key covers, and nothing else. There is no login and no password to manage, so share a key the way you would share a password.

A key works the same way a monitor token does. The recommended form is the static endpoint `https://areyoufoundbyai.com/mcp` with the key in an `Authorization: Bearer` or `x-api-key` header. The path form also works:

```text theme={null}
https://areyoufoundbyai.com/mcp/KEY-TOKEN
```

Your own network link covers your whole network. A scoped key covers only the sites you tick when you create it.

## What a key can do

A key holder's AI can use the [network catalogue](/docs/mcp/tools#agency-network-catalogue) for the sites the key covers:

* List those sites with their latest visibility and readiness, week movement and verdict
* Read each site's scores and subscores, saved engine answers, rivals, citations, mentions, fix plan, personas and post brief
* Read each site's saved evidence (crawler access, AI-referred traffic, agent view, benchmark, share of voice, cited queries, source profiles, citation sources, structured data, regional observations, weekly brief and grants check), its existing scan allowance with `get_balance`, and its setup reads
* Queue a capped on-demand re-measure for a covered site with `run_check`, and collect the result with `get_run`. This only works for a site with active monitoring, and it uses the same capped runs as the console's own re-measure

## What a key cannot do

A key cannot:

* Reach any site outside its scope, including other clients in your network
* Add or remove sites
* Change account settings or touch billing
* Open your network page

## How to create a scoped key

<Steps>
  <Step title="Open AI access on your network page">
    On your network page, open **AI access**. Name the key after the person or team who will use it, which makes auditing and revoking it easier later.
  </Step>

  <Step title="Tick the sites the key should cover">
    Tick the client sites this key should reach, or choose the whole network. A whole-network key picks up new sites automatically.
  </Step>

  <Step title="Copy the setup and hand it over">
    Press **Copy setup** next to the new key. It copies a complete handoff message, with the key's URL and the exact steps for the Claude app, Claude Code and Cursor, ready to paste into an email or chat.
  </Step>
</Steps>

## Using a scoped key with an AI assistant

To add a key to Claude Code:

```bash theme={null}
claude mcp add --transport http found-by-ai-client https://areyoufoundbyai.com/mcp/KEY-TOKEN
```

In the Claude app, add it under **Settings**, then **Connectors**, then **Add custom connector**. In Cursor, add a custom MCP server with HTTP transport. Any other MCP client works the same way.

Once connected, the useful questions are plain ones:

* "Which of my clients moved this week?"
* "What should we do for this client this month?"
* "Draft a post brief for that client from the measured data."
* "Which buyer questions is this client still invisible on, and who is AI naming instead?"

The AI answers from the saved measurements, not memory.

## Auditing and revoking keys

Each key on your network page shows how many times it has been used and when it was last used. A key that should be active and shows no recent use tells you something too: it may not have been connected correctly.

Revoking a key is one click on the network page. It takes effect immediately, and nothing else changes.

Scope is checked against live network membership on every call, not only when the key is created. Remove a site from your network and every key that covered it loses that site at the same moment, with no keys to recreate or update.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.