Connect your agent to your AI Visibility data.
Ask Claude which of your clients were cited this week, open the receipt behind a score, pull the content plan for a client and write the post. The server hands your agent the same data your console shows, under your login, with nothing written back.
Four steps in Claude.
- In Claude, open Settings, then Connectors, then Add custom connector.
- Paste the server URL. Under advanced settings choose Use your own OAuth client, paste the client ID and leave the secret empty.
- Click Connect. You are sent to a sign-in page in your own name; sign in with the login you use for this console and approve.
- Back in Claude, ask it to list your sites. Every call is checked against your login and recorded here.
Any agent that can use a pre-registered OAuth client works the same way. Agents that insist on registering themselves are not supported yet.
Sign in with the login you use for your console. Partners can see who on their team has connected, and revoke anyone, on the Connect page of their console.
What your agent can ask for.
| Tool | What it returns | Who |
|---|---|---|
| list_sites | The sites the caller may read. Partner-admins see their partner's clients; super-admins see all. | Operator, Partner, Client |
| get_tracked_queries | Active tracked queries for one site. Requires site_id; the site must be in the caller's scope. | Operator, Partner, Client |
| list_clients | Clients visible to the caller, with plan. A client is an account with at least one site. Super-admin only in v1. | Operator |
| get_scoreboard | Citation scoreboard for one site: recent tracking runs and, for the latest completed run, one row per query per engine. Each row names its engine and carries the id to open with get_receipt. A row with engine_ok=false is a failed engine call (the provider was down or out of credit): treat it as unknown, not as not cited. | Operator, Partner, Client |
| get_receipt | The evidence behind one citation cell: the answer snippet plus the sources the engine returned. Requires site_id and citation_id. | Operator, Partner, Client |
| get_citation_map | Which domains AI cites for this site's queries, with directory metadata. The off-site authority to-do list. | Operator, Partner, Client |
| get_content_plan | The current content plan for one site: the ranked page ideas (menu, opportunities) and, under `video`, the ranked YouTube ideas. Each idea says what to make, why, and which query it targets. | Operator, Partner, Client |
| get_entity_presence | Entity findings for one site: which directories and surfaces carry the business, and what is missing or inconsistent. | Operator, Partner, Client |
| get_ai_traffic | Visits arriving from AI engines, per day and engine, for one site. | Operator, Partner, Client |
| get_site_spend | SUPER-ADMIN ONLY. Our cost to serve one site, per tracking run. Never exposed to a partner. | Operator |
Built so you can hand it to an agent.
Read only
The server can read your clients' data and nothing else. It cannot start a scan, generate content or change a setting. Changes to a CRM or a website happen through the connectors your agent has for those systems.
Scoped to you
A partner sees the clients they manage. A client sees their own business. There is no tool that reads across accounts, and there never will be.
Every call recorded
Who read what, and when, is written down on every call and shown in your console. Arguments are recorded; the data returned is not copied into the log.
Revocable in one click
Revoke a person from your console and their next call is refused, whatever token their agent still holds. Restore them just as easily.