AI visibility from Claude

Every setting of a client's AI visibility module is reachable through the API, so through the MCP server: you can set it up, review it and launch a capture from a conversation in Claude, without opening the dashboard.

The quickest way in is the ai_visibility_setup prompt: it reads the configuration, the tracked questions, the latest results and the tracked keywords, proposes changes as a list, and writes them only after a yes.

A conversation, step by stepCopy Anchor Link

"Review the AI visibility of Acme and add the competitors ChatGPT names instead of them."

1. Find the client and its configuration. list_records on clients, then on geo-settings with filter[clientId] set to the client's public id. enabled says whether the module is switched on for that client.

2. Read the latest results. read_action on clients, action ai-visibility: the score, mention and citation rates, the competitors each engine named instead of the brand (questions[].instead), and latest.market — what each market panel says (share of voice, competitors' shares, cited domains, and the client's presence in Google's AI Overviews).

3. Change the competitors without resending the list. run_action on geo-settings, action edit-competitors:

   Copy Text

   {
     "resource": "geo-settings",
     "action": "edit-competitors",
     "id": "g7k2m9p4qx",
     "input": { "add": ["Agence Nord"], "remove": ["Old Rival"] }
   }

   Case is ignored and a name already there keeps its spelling; at most 25 competitors. edit-aliases does the same for other spellings of the brand.

4. Tune the questions. list_records on geo-prompts with filter[clientId]; create_record to add one, update_record to change its text or topic, and active: false to pause it — prefer that to a delete, which removes its history.

5. Check the keywords. rank-settings and rank-keywords (rank tracking, archive to stop following one) and seo-keywords (saved keywords), all filterable by clientId.

6. Run a capture, if you want fresh figures. run_action on geo-settings, action capture. It answers started at once; the results appear in ai-visibility a few minutes later.

What each setting maps toCopy Anchor Link

What a credential cannot doCopy Anchor Link

• Switch the module on. Activating AI visibility for a client is what bills that client, so it stays in the dashboard, with a member who holds billing.manage. enabled is readable, never writable, and no action changes it.
• Capture without the right to. capture spends the agency's AI-visibility allowance, exactly like the dashboard's « Lancer une capture » button. It needs the geo-settings:write scope and a credential whose owner currently holds reports.manage. It is refused when the module is off for the client (geo_not_ready), the agency lacks the add-on (plan_required), a capture is already running (conflict) or no question is active. The monthly budget is checked by the capture itself: when it is reached, the refusal shows in lastError on the configuration.