Inspect Ai Visibility
inspect_ai_visibility(domain: string, competitors?: string[], platform?: enum)How a domain shows up in AI answers, vs named competitors.
Compares how frequently your domain is mentioned in generative AI answers compared to named competitors, including share-of-voice calculations.
Input Parameters
3 arguments| Parameter | Type | Requirement | Default / Constraints | Description |
|---|---|---|---|---|
domain | string | required | Your domain to measure AI brand mentions for. | |
competitors | string[] | optional | Named competitor domains to compare against. | |
platform | enum | optional | AI platform to inspect (google = AI Overview; chat_gpt = ChatGPT). |
Return Envelope (OFE / 1.0)
Open Fact EnvelopeEvery response adheres to the strict ofe/1.0 envelope schema, returning verified data, typed facts, entity references, and follow-up tool suggestions:
data Payload
Compares how frequently your domain is mentioned in generative AI answers compared to named competitors, including share-of-voice calculations.
coverage & Freshness
Reports returned count vs total items, observation timestamp as_of, and scope notes. Evaluated live per request.
resources (Dataset Exports)
If a query yields high row counts (e.g. >1,000 queries in Search Console), full unpaginated tables are persisted to R2 and linked as an mcpseo:// URI for follow-up retrieval via export_dataset.
next_actions
Provides suggested follow-up tool calls with pre-filled arguments so your AI agent can navigate from discovery to detailed inspection autonomously.
Emitted Facts & Entities
Knowledge GraphTyped Facts
Facts emitted in the facts[] array with provenance receipts:
| Fact Type | Claim Description | Emitted Data Fields |
|---|---|---|
ai_visibility.brand_mentions | How often a domain is mentioned in AI answers, its share of voice among the domains compared, and the sources cited most. | domainis_youmentionsai_search_volumeshare_of_voicetop_cited_sources |
Registered Entities
Entities registered in the entities[] array to establish subject relationships:
Target domain and competitor domains.
Request & Response Examples
Live MCP PayloadsExact JSON schemas transmitted over Model Context Protocol (stdio or HTTP SSE transport):
1. Client Tool Invocation
{
"tool": "inspect_ai_visibility",
"arguments": {
"domain": "linear.app",
"competitors": [
"jira.com",
"asana.com"
],
"platform": "google"
}
}2. Server Envelope Response
{
"schema_version": "ofe/1.0",
"domain": "ai_visibility",
"data": {
"domain": "linear.app",
"competitors": [
"jira.com",
"asana.com"
],
"platform": "google"
},
"facts": [
{
"type": "ai_visibility.brand_mentions",
"subject": [
"urn:domain:linear.app"
],
"data": {
"domain": "linear.app",
"is_you": true,
"mentions": 42,
"share_of_voice": 0.38
},
"provenance": {
"source_class": "ai_answer",
"method": "ai_answer_mentions",
"confidence": 0.5,
"observed_at": "2026-09-24T00:00:00Z",
"cache_hit": false
}
},
{
"type": "ai_visibility.brand_mentions",
"subject": [
"urn:domain:jira.com"
],
"data": {
"domain": "jira.com",
"is_you": false,
"mentions": 51,
"share_of_voice": 0.46
},
"provenance": {
"source_class": "ai_answer",
"method": "ai_answer_mentions",
"confidence": 0.5,
"observed_at": "2026-09-24T00:00:00Z",
"cache_hit": false
}
}
],
"entities": [
{
"id": "urn:domain:linear.app",
"kind": "domain",
"label": "linear.app"
},
{
"id": "urn:domain:jira.com",
"kind": "domain",
"label": "jira.com"
}
],
"coverage": {
"returned": 2,
"total": 3,
"as_of": "2026-09-24T00:00:00Z",
"scope_note": null
},
"deltas": [],
"resources": [],
"next_actions": []
}LLM Agent Workflow
Claude & Cursor IntegrationPrompt Trigger
"What is linear.app's share of voice in Google AI Overviews compared to jira.com?"
Agent Decision & Reasoning
The agent compares multi-brand presence in generative search to quantify LLM visibility changes over time.
Recommended Follow-up Tools
Provenance Guarantees & Error Handling
ReliabilityEvery fact emitted by Vouched includes source_class, method, observed_at ISO timestamp, and a published confidence score. LLM agents can inspect these citations to distinguish first-party verified facts (e.g. Search Console) from modeled competitor estimates.
Billing & API Keys
Paid market data, on Pro and Team. A call typically costs about $0.10 per domain compared of market data, so Pro's included $4 covers roughly 40 domains compared. Self-hosted, it uses your own DataForSEO key and bills you directly, with nothing added. See pricing for what each tool costs.