DABYTE AI Visibility Index
v1.0.1Measured share of answer for 20 SaaS brands. An open dataset, not an audit of your site.
Endpoint health
online- Last checked
- 11/20/2026, 5:16:00 AM
- Latency
- 137 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:ai.dabyte%2Fvisibility-index
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"ai.dabyte/visibility-index": {
"url": "https://dabyte.ai/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
Look up one brand
get_brand_visibility
One brand's standing in the current DABYTE release: share of answer per engine, rank, quadrant, how many panel prompts name it, and which ones. Use this when a specific brand is named. Takes a slug, not a display name — call list_tracked_brands first if you are unsure, or read the slug from get_visibility_index. An unknown slug is not a failure to hide: the error names every valid slug, so a second attempt can succeed. A brand absent from the index has not been measured at all, which is different from a measured zero. Only SaaS & AI tools brands are tracked. For the field as a whole use get_visibility_index; for this brand over time, get_history. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.
Schema valid · SHA-256 bf3504b2a3fd…
View input schema
{ "type": "object", "properties": { "slug": { "type": "string", "pattern": "^[a-z0-9-]{1,80}$", "description": "Brand slug, lowercase with hyphens — 'slack', 'coinbase', 'monday-com'. Not the display name." } }, "required": [ "slug" ], "additionalProperties": false }Full measurement time series
get_history
Every DABYTE release ever published, as a series per brand: share of answer at each weekly measurement with the date and panel version it was taken under. Use this for any question about change — is a brand rising, when did it enter the index, how volatile is the category. Two limits decide whether an answer is honest. Figures are comparable only WITHIN a panel version: the panel is frozen between releases and a version change alters the denominator, so a difference across that boundary is not a trend. And small moves sit inside language-model noise: since panel v3 (2026-08-10) each prompt runs three times per engine per release and the figure is the share of runs; earlier releases ran each prompt once, so one mention on one engine was a whole scale step there. Either way a one-step movement should not be reported as a gain or a loss. Call get_methodology for the exact step size. For the current release alone use get_visibility_index. Re-measured weekly, so the same call returns the same figures until the next release. Data is CC BY 4.0 and free: no key, no account, no rate limit — cite the release date and dabyte.ai when quoting a number.
Connections
streamable-http
https://dabyte.ai/mcp