Quick answer: Of 11 platforms checked on 30 October 2026, five document a REST endpoint that returns a share-of-voice field: Profound, Peec AI, Otterly.AI, Ahrefs Brand Radar and Scrunch. Conductor and Semrush return AI-visibility data without one. For seoClarity and BrightEdge we found no public endpoint reference, and Bing Webmaster Tools and Google Search Console have no API route.
This page is for the person who already knows what AI share of voice is and now wants the numbers in a warehouse, a Looker Studio board or a weekly script rather than in another vendor dashboard. For each platform we read the vendor’s own developer documentation and pricing page and recorded five things: whether a public API exists, which endpoint returns share of voice or mentions, which plan unlocks it, the published rate limit or quota, and which AI engines it tracks. The engines named across the 11 platforms include ChatGPT, Perplexity, Gemini, Claude, Microsoft Copilot, Grok, DeepSeek, Meta AI, Google AI Overviews and Google AI Mode.
Where Zian fits
Zian does not sell an AI-visibility or share-of-voice tool, and nothing on this page ranks it against the platforms below. Zian is an AI sales and reception agents platform, and it fits at the step after a share-of-voice number moves: when a buyer who found you through ChatGPT or Perplexity calls or messages, Zian’s agents answer incoming calls 24/7 as an AI receptionist and follow up by voice, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger.
That matters for anyone wiring share-of-voice data into a dashboard. A rising AI share of voice is an impression, not a meeting, and the only way to know whether it is worth paying for is to join it to what happens when those buyers make contact. Zian is in a partnership-application beta; each of its three listed plans, including Intel + Widgets (Free Forever), starts with a partnership application.
Which platforms expose AI share-of-voice data through an API?
How we scored every row. “API: Yes” means a key-authenticated REST endpoint, documented on the vendor’s own developer site, that returns brand-level AI mention or visibility data. “Partial” means the vendor says the data can be reached programmatically (on a marketing page or through an MCP server) but we found no public endpoint reference. “No” means the vendor’s own API reference lists no method for its AI-visibility report. The share-of-voice column names a field only where the vendor’s reference names it. Engines and plan names are copied as each vendor writes them. Everything was read on 30 October 2026; plans and limits change, so treat every cell as “as at 30 October 2026”.
| Platform | Public API | Share-of-voice endpoint or field | Engines tracked (vendor’s wording) | Plan that unlocks the API | Published rate limit or quota | Source |
|---|---|---|---|---|---|---|
| Profound | Yes | POST /v2/reports/visibility, metric share_of_voice; raw rows via POST /v2/prompts/answers |
Enterprise: up to 9 – ChatGPT, Perplexity, Google AI Mode, Gemini, Microsoft Copilot, DeepSeek, Anthropic Claude, Google AI Overviews, Exa Search | Enterprise only (Trial: “API None”) | 600 requests per hour per API key | Profound API docs |
| Peec AI | Yes (v0 beta) | POST /customer/v1/reports/brands, field share_of_voice |
Starter to Advanced: choose 3 of ChatGPT, AI Mode, AI Overviews, Microsoft Copilot, Gemini, Naver AI. Enterprise: up to 13, adding API models (Claude Sonnet 4, GPT 5 Search, Grok, Deepseek, Qwen, Mistral, Meta Spark) and Perplexity. On Starter to Advanced, extra models (Perplexity among them) are paid add-ons | Pro, Advanced, Enterprise and agency plans; not Starter | 200 requests per minute per project | Peec AI API docs |
| Otterly.AI | Yes | GET /v1/reports/brand/{reportId}/stats, fields shareOfVoice, totalMentions, brandCoverage |
4 included: ChatGPT, Google AI Overviews, Perplexity, MS Copilot. Claude, Google AI Mode and Gemini as paid add-ons | Standard, Premium, Enterprise; not Lite | 2,000 API requests a month (Standard), 5,000 (Premium), custom (Enterprise) | Otterly.AI API docs |
| Ahrefs Brand Radar | Yes | /v3/brand-radar/sov-overview and /sov-history, field share_of_voice |
chatgpt, google_ai_overviews, google_ai_mode, gemini, perplexity, copilot, claude (custom prompts only), grok | Lite, Standard, Advanced (“API and MCP access”); Enterprise (“Uncapped API access”). Those plans include a daily quota of 5, 10 or 20 custom prompts; Brand Radar AI, which researches any brand across Ahrefs’ own prompt database, is sold as a separate product | 60 requests per minute by default; minimum 50 API units per billable request | Ahrefs API docs |
| Scrunch | Yes | Query API GET /v1/{brand_id}/query, fields brand_share_of_voice, competitor_share_of_voice |
Core: ChatGPT, Perplexity, Google AIO, Copilot. Enterprise: 9 – adds Claude, Gemini, Meta AI, Google AI Mode, Grok | Agency and Enterprise | No number in its rate-limit FAQ | Scrunch Query API docs |
| Conductor | Yes | No share-of-voice field. /data-api/v1/async/ai_search_brands returns per-brand mention rows tagged You, Partner, SEO Competitor or Other |
“Google, ChatGPT, Perplexity, Google AIO, and more”; your account’s list comes from ai_search_config |
Subscription to Conductor’s Intelligence product | 5,000 calls per day and 2 calls per second per API key | Conductor API docs |
| Semrush (AI Visibility Toolkit Prompt Tracking) | Yes | No share-of-voice field. v3 Position Tracking organic positions report (type=tracking_position_organic) returns rankings and visibility for campaigns on any Position Tracking engine, “including ChatGPT”; Semrush says Share of Voice is “not available” for its AI engines. Enterprise AIO separately says “Link AIO data … via API” |
Prompt Tracking: ChatGPT Search, Google’s AI Mode, Gemini. Brand Performance (share of voice, interface): ChatGPT, Google AI Mode, Perplexity, Gemini | AI Visibility Toolkit subscription for the Prompt Tracking campaign, plus Standard API access (SEO Toolkit Business subscription and purchased API units) | Up to 10 requests per second and 10 simultaneous requests per account; the organic positions report costs 100 API units per keyword | Semrush Position Tracking API |
| seoClarity (ArcAI) | Partial | ArcAI API page promises “share-of-voice metrics”; no public endpoint reference | ChatGPT, AI Overviews, AI Mode, Claude, Gemini, Perplexity, Co-Pilot, Grok, DeepSeek | “fully included with your seoClarity subscription” | Not published on the pages we read | ArcAI API page |
| BrightEdge (AI Catalyst) | Partial | No public REST reference for AI Catalyst; its MCP server offers “AI citation tracking”; tables export to CSV | ChatGPT, Perplexity, Google AI Overviews, Google AI Mode, Gemini “and other AI platforms” | BrightEdge customers (MCP needs BrightEdge login credentials) | Not published on the pages we read | BrightEdge MCP page |
| Bing Webmaster Tools (AI Performance) | No | Citation Share shown in the interface only; no API method | Microsoft Copilot, AI-generated summaries in Bing, select partner integrations | Free with a verified site | Not applicable | IWebmasterApi reference |
| Google Search Console | No | No generative AI type in the Search Analytics API | AI Overviews and AI Mode (in the report, not the API) | Free with a verified property | Not applicable | Search Analytics reference |
Count the rows before you quote them: 5 platforms return a named share-of-voice field, 2 return AI-visibility data without one (Conductor’s brand-mention rows and Semrush’s Position Tracking rankings), 2 are partial, and 2 have no API route. “Partial” is not “no”: it means you will need a sales conversation, a customer login or an MCP client to find out what the endpoint actually returns.
How each vendor defines share of voice
An API that returns a field called share_of_voice does not mean every vendor’s field measures the same thing. The definitions below are quoted from each vendor’s own documentation, and they divide by different denominators. This is the single biggest reason two tools disagree about the same brand in the same week, and it is the concept our explainer on share of model as an AI-search metric introduces before any tooling question.
| Vendor | Field | Numerator | Denominator | What changes it without your visibility changing |
|---|---|---|---|---|
| Peec AI | share_of_voice |
Your mention_count |
Sum of mention_count across brands in scope |
Filtering brand_id in filters “collapses SoV to 1.0”; Peec says to filter in having instead |
| Scrunch | brand_share_of_voice |
Your brand’s mention responses | Mention responses for your brand plus all active competitors | Adding or archiving a competitor; the denominator “always reflects the full brand-plus-competitors set” |
| Profound | share_of_voice |
Responses that mention your brand | Total brand mentions across all responses | Any brand named counts, not only your configured competitors; Profound computes it per AI model, then averages the models with equal weight |
| Profound | visibility_score |
Responses that include your brand | Responses that include at least one brand | Prompts where nobody is named drop out of the denominator; also computed per AI model, then averaged |
| Ahrefs | share_of_voice |
Described only as “Estimated share of voice for your brand” | The brand and competitors you pass in the request |
|
| Otterly.AI | shareOfVoice |
Returned as a number alongside totalMentions; the API reference we read on 30 October 2026 does not print the formula |
The competitors in the brand report | |
| Bing Webmaster Tools | Citation Share (interface only) | Citations attributed to your site | All citations shown across all sites for the same grounding query | It is per grounding query, and Microsoft says it is “not a ranking system or a competitive scoreboard” |
The practical rule: a share-of-voice API number is only comparable with the same vendor’s number, on the same competitor set, over time. If your board report mixes Peec’s figure for one engine with Profound’s for another, the comparison is between two formulas, not two engines.
Want the buyers that AI answers send you handled the moment they make contact? Zian’s AI agents answer inbound calls 24/7 and follow up across voice, SMS, email, WhatsApp, Instagram DMs and Facebook Messenger. Apply For Partnership
Who each share-of-voice API is wrong for
Every API above has a sentence in its own documentation that should slow you down. Here they are, vendor by vendor, so you meet them before the invoice does.
Profound is wrong for anyone who wants to test the API before committing: its API pages say “Available on: the Enterprise plan”, and its pricing page lists the Trial’s API as “None”. In return, the v2 report endpoints have streaming variants and the raw /v2/prompts/answers endpoint returns model responses, mentions, citations and search queries, which is what you want if you plan to recompute share of voice yourself. At 600 requests per hour per key, a nightly pull is comfortable; a dashboard that queries live on every page view is not.
Peec AI is wrong for teams that cannot absorb a breaking change. Its changelog says “The API is currently in v0 (beta)” and that “breaking changes may occur”, and its rate-limit page says the 200-requests-per-minute limit “may be adjusted”. It is also the API most likely to give you a wrong number through your own filter: putting brand_id in filters rather than having shrinks the denominator to your own brand, and your share of voice reads 100%.
Otterly.AI is wrong for high-frequency polling. Its quota is monthly (2,000 or 5,000 requests by plan), and when it runs out the API answers 429 with “Quota exhausted.” Three of its seven engines (Claude, Google AI Mode and Gemini) are paid add-ons, so data for them exists only if you bought those add-ons.
Ahrefs Brand Radar is wrong if your priority is Claude coverage from a ready-made prompt set: its reference says the claude source “supports only custom prompts”. Cost is metered in API units, the minimum billable request is 50 units, and Ahrefs warns that “API units once consumed are non-refundable”. The upside is unusual: share-of-voice requests that return only your own custom-prompt data are free.
Scrunch is wrong for single-brand teams on its Core plan: API keys can be created only on Agency and Enterprise plans, though its docs say support can “discuss an override”. Two smaller cautions: its rate-limit FAQ publishes no number, and the ai_platform dimension in the Query API reference lists five values (chatgpt, perplexity, google_ai_overviews, meta, claude) against nine engines on the Enterprise pricing card, so confirm which engines your key actually returns.
Conductor is wrong if you want a finished percentage. Its AI Search endpoints return per-brand mention rows (23 columns, including the engine, prompt, persona, brand attribution and whether a web search was triggered) and no share-of-voice column, so the calculation is yours. Its endpoints are asynchronous, and Conductor warns that every poll counts against both the 2-per-second and 5,000-per-day limits.
Semrush is wrong if you want a share-of-voice figure from the API. Its v3 Position Tracking API reference says the organic positions report “supports campaigns targeted to all Search Engine options available in Position Tracking, including ChatGPT”, and that “Rankings and visibility data will be returned based on the specific search engine selected in the campaign configuration.” Prompt Tracking, which needs an AI Visibility Toolkit subscription, covers ChatGPT Search, Google AI Mode and Gemini. But Semrush’s own help page says “Estimated Traffic and Share of Voice metrics are not available” for those engines, and we could not find the Brand Performance reports, where its share of voice lives, in its public API reference, as at 30 October 2026. API access itself needs an SEO Toolkit Business subscription plus purchased API units, and this report costs 100 API units per keyword. Its API usage restrictions allow up to 10 requests per second and add a condition that matters if the plan is a warehouse table: “You can’t cache the information received via API for more than one month without Semrush’s express written consent.” Separately, Semrush Enterprise’s AIO page says you can “link AIO data and tailor reports across systems via API”.
seoClarity and BrightEdge are wrong for anyone who must see the endpoint before signing. seoClarity’s ArcAI API page describes share-of-voice metrics, an in-platform API playground and token-based access, and seoClarity also offers an ArcAI MCP server, but we found no public endpoint list on its website, and its knowledge base at kb.seoclarity.net would not load for us (HTTP 403), as at 30 October 2026. BrightEdge’s MCP server, open to customers with BrightEdge login credentials, offers “AI citation tracking” and lists Share of Voice and AI Catalyst among the data it draws on; its Connect API page describes web-analytics data, and we found no public REST reference for AI Catalyst in its 3,438-URL sitemap. Its API host, api.brightedge.com, tells visitors to “refer to the Software Development Kit that was provided for documentation”, which points to customer-only docs.
What Bing Webmaster Tools and Google Search Console give you instead
The two free first-party sources are useful and API-less. Microsoft introduced the AI Performance report in Bing Webmaster Tools as a public preview on 10 February 2026, covering “Microsoft Copilot, AI-generated summaries in Bing, and select partner integrations”, and added Intents, Topics, Citation Share and Compare in preview on 16 June 2026. Citation Share is the closest thing to a share-of-voice number either engine publishes about itself: the percentage of citations attributed to your site out of all citations shown for the same grounding query. But Microsoft is explicit that it “does not expose competitor domains”, and the published IWebmasterApi interface lists methods for crawl, keyword, query and traffic statistics with no AI Performance method.
Google’s position is simpler. The Search Analytics API accepts six types (discover, googleNews, news, image, video, web), none of which isolates AI Overviews or AI Mode; we covered what the interface-only report does show in our walk-through of Search Console’s generative AI performance report. Neither report covers ChatGPT or Perplexity, which is why every vendor in the table runs its own prompts.
Build your own: the share-of-voice calculation from raw answer rows
Six of the APIs above return raw answers as well as aggregates: Profound’s /v2/prompts/answers, Peec AI’s chats endpoints, Otterly.AI’s AI-responses endpoint, Scrunch’s Responses API, Ahrefs’ ai-responses and Conductor’s ai_search_response. Semrush’s Position Tracking endpoint returns rankings and visibility, not answer text. seoClarity’s ArcAI API page also promises “word-for-word responses”, but we found no public endpoint reference for them. A home-grown poller returns the same shape as the six. Once you hold rows of “one answer, the brands it named”, you can compute every vendor’s metric yourself and stop arguing about whose formula is right. For how to design the poller and what to store on each run, see our guide to what an AEO poll harness should measure.
Worked example. You run 12 prompts once each on ChatGPT and Perplexity: 24 answers. You track yourself and two competitors, A and B. Counting each brand at most once per answer:
- 8 answers name none of the three brands; 16 name at least one.
- You appear in 6 answers, A in 10, B in 6, so there are 6 + 10 + 6 = 22 brand mentions.
| Metric | Formula | Arithmetic | Result | After competitor C joins (named in 5 of the 8 empty answers) |
|---|---|---|---|---|
| Mention rate | Answers naming you ÷ all answers | 6 ÷ 24 | 25.0% | 6 ÷ 24 = 25.0% (unchanged) |
| Share of voice (the Peec AI and Scrunch formula) | Your mentions ÷ all tracked-brand mentions | 6 ÷ 22 | 27.3% | 6 ÷ 27 = 22.2% |
| Visibility (Profound’s ratio, applied to tracked brands only) | Answers naming you ÷ answers naming any tracked brand | 6 ÷ 16 | 37.5% | 6 ÷ 21 = 28.6% |
Same 24 answers, three honest numbers between 25.0% and 37.5%. Then add one competitor to the tracked set and two of the three numbers fall, by 5.1 and 8.9 points, although not a single answer changed. Mention rate is the only one of the three that ignores who else you track, which makes it the safest trend line; share of voice is the right number for a competitive slide, provided the competitor set is frozen and stated. One caution if you reconcile with Profound: its metrics guide says every report metric is computed for each AI model separately and then averaged with equal weight, so pooling the ChatGPT and Perplexity rows as above will not reproduce its figure. Profound also counts any brand named in an answer, not only your configured competitors, so in Profound C’s five answers count in both columns whether or not you add C to your list.
The calculation is short enough to run anywhere. We ran this script against a 24-row JSON fixture built to the counts above, then against a copy with competitor C added, and it printed exactly the figures in the table:
import json, sys
rows = json.load(open(sys.argv[1])) # [{"answer_id": 1, "engine": "chatgpt", "brands": ["You", "A"]}, ...]
brand = "You"
answers = len(rows)
with_any = sum(1 for r in rows if r["brands"])
you = sum(1 for r in rows if brand in r["brands"])
all_mentions = sum(len(set(r["brands"])) for r in rows)
print("mention rate ", round(100 * you / answers, 1), "%")
print("visibility ", round(100 * you / with_any, 1), "%")
print("share of voice", round(100 * you / all_mentions, 1), "%")
Two things the script deliberately does not do. It does not count a brand twice in one answer, because a list that names you in the intro and the summary is still one recommendation. And it does not treat a citation as a mention: a cited URL and a named brand are different events with different value, which is the distinction behind our comparison of cited versus recommended AI-visibility metrics. If you want a citation share as well, compute it separately as your cited URLs divided by all cited URLs per prompt, the way Bing computes it per grounding query.
Which share-of-voice API should you choose?
| If this is your situation | Start with | Why |
|---|---|---|
| You want the API on a self-serve plan, below enterprise | Ahrefs (Lite and up), Peec AI (Pro and up) or Otterly.AI (Standard and up) | Of the five with a named share-of-voice field, the three whose pricing pages put API access below an enterprise or agency tier |
| You need raw answer text to recompute metrics yourself | Profound, Peec AI, Otterly.AI, Scrunch, Ahrefs or Conductor | Each documents a raw-response endpoint, not just aggregates |
| You will poll many times a day | Peec AI (200 per minute per project), then Conductor (2 per second, capped at 5,000 a day) and Ahrefs (60 per minute) | The highest published request rates among the share-of-voice and brand-row APIs; Semrush allows 10 a second but bills 100 API units per keyword, Profound allows 600 an hour and Otterly.AI meters requests by the month |
| Your board wants one competitive percentage | Any vendor with a named field, with the competitor set frozen | The denominator moves whenever the competitor list does |
| You need Copilot data in a pipeline | A share-of-voice API that tracks Copilot (Profound, Peec AI, Otterly.AI or Ahrefs; Scrunch’s pricing lists Copilot, but its API’s ai_platform values do not) |
Bing’s own AI Performance data has no API method |
| You track under about 30 prompts on 2 or 3 engines and have an engineer | Your own poller plus the script above | At that size the subscription buys less than the engineer’s time costs |
The last row is a judgement, not a measured threshold: below a few dozen prompts, the hard part is storing raw rows consistently, not collecting them, and no vendor API removes that job.
Frequently asked questions
Which AI visibility tools have a share-of-voice API?
Of the 11 platforms we checked on 30 October 2026, five document a REST endpoint that returns a field they call share of voice: Profound, Peec AI, Otterly.AI, Ahrefs Brand Radar and Scrunch. Two more return AI-visibility data without a share-of-voice field: Conductor’s brand-mention rows, and Semrush’s Position Tracking API for ChatGPT, Google AI Mode and Gemini campaigns. seoClarity and BrightEdge describe programmatic access without a public endpoint reference, and Bing Webmaster Tools and Google Search Console expose no AI-visibility method in their APIs.
What is the cheapest way to get AI share-of-voice data through an API?
Among the five platforms with a named share-of-voice field, three put API access on a self-serve plan below enterprise: Ahrefs lists “API and MCP access” on Lite, Standard and Advanced, though those plans include a daily Custom Prompts quota of only 5, 10 or 20 prompts and Brand Radar AI, its prompt database, is sold separately; Peec AI includes the API on Pro and above but not Starter; and Otterly.AI includes it on Standard (2,000 API requests a month) and Premium (5,000). Profound’s API is Enterprise-only, Scrunch’s is Agency and Enterprise, and Conductor’s needs its Intelligence subscription. Check each vendor’s pricing page for the current figures before you buy.
Can I get Copilot citation data from the Bing Webmaster Tools API?
Not as at 30 October 2026. Bing Webmaster Tools shows Copilot and Bing AI citations, grounding queries and Citation Share in its AI Performance report, but Microsoft’s published IWebmasterApi method list contains no AI Performance or citation method, and Microsoft describes Citation Share as “an observational metric – not a ranking system or a competitive scoreboard” that does not expose competitor domains.
Does the Google Search Console API include AI Overviews data?
No. The Search Analytics API accepts the types discover, googleNews, news, image, video and web, and none of them isolates AI Overviews or AI Mode, according to Google’s Search Analytics query reference.
Why does my share of voice differ between tools?
Because the vendors divide by different things. Peec AI divides your mention count by the sum of all mention counts; Scrunch divides your mention responses by the mention responses for your brand plus all active competitors; Profound’s separate Visibility score divides responses that include you by responses that include at least one brand, per AI model, then averages the models. The same 24 answers can produce 25%, 27.3% or 37.5% depending on the formula, so compare a tool only with itself.
Should I build my own share-of-voice tracker instead of paying for an API?
Build your own when you track a few dozen prompts on two or three engines and someone on your team can maintain a scheduled job; buy an API when you need many engines, countries or personas, or when the poll volume would cost more in engineer time than the subscription. Either way, store the raw answer rows, not just the percentage, so you can recompute when your competitor set changes.
Where every figure on this page comes from
| Figure | Who published it | Link | Date read |
|---|---|---|---|
Profound API Enterprise-only; 600 requests per hour per key; /v2/reports/visibility and share_of_voice |
Profound | docs.tryprofound.com/rest-api/introduction | 30 Oct 2026 |
| Profound Trial “API None”; Enterprise up to 9 answer engines | Profound | tryprofound.com/pricing | 30 Oct 2026 |
| Profound share of voice and Visibility score definitions | Profound | docs.tryprofound.com/answer-engine-insights/about | 30 Oct 2026 |
| Profound metrics computed per AI model, then averaged with equal weight; any named brand counts | Profound | docs.tryprofound.com metrics guide | 30 Oct 2026 |
| Peec AI API on Pro, Advanced, Enterprise and agency plans | Peec AI | docs.peec.ai/api/introduction | 30 Oct 2026 |
| Peec AI 200 requests per minute per project | Peec AI | docs.peec.ai/api/ratelimits | 30 Oct 2026 |
Peec AI share_of_voice formula and brand_id filter behaviour |
Peec AI | docs.peec.ai/api-reference/reports/get-brands-report | 30 Oct 2026 |
| Peec AI API v0 (beta) | Peec AI | docs.peec.ai/api/changelog | 30 Oct 2026 |
| Peec AI engines; choose 3 models; additional models as paid add-ons; up to 13 on Enterprise | Peec AI | peec.ai/pricing | 30 Oct 2026 |
| Otterly.AI 2,000 and 5,000 API requests a month; 4 engines plus 3 add-ons | Otterly.AI | otterly.ai/pricing | 30 Oct 2026 |
Otterly.AI shareOfVoice stats endpoint; 429 “Quota exhausted.” |
Otterly.AI | docs.otterly.ai stats reference | 30 Oct 2026 |
Ahrefs Brand Radar sov-overview, share_of_voice, data sources, free custom-prompt requests |
Ahrefs | docs.ahrefs.com/reference/brand-radar.json | 30 Oct 2026 |
| Ahrefs 60 requests per minute; minimum 50 units; units non-refundable | Ahrefs | docs.ahrefs.com/api/docs/introduction | 30 Oct 2026 |
| Ahrefs “API and MCP access” on Lite, Standard, Advanced; “Uncapped API access” on Enterprise; Brand Radar AI sold as a separate product | Ahrefs | ahrefs.com/pricing | 30 Oct 2026 |
| Ahrefs daily Custom Prompts quota: Lite 5, Standard 10, Advanced 20 | Ahrefs | ahrefs.com/brand-radar | 30 Oct 2026 |
| Scrunch API keys on Agency and Enterprise plans | Scrunch | developers.scrunch.com/getting-started/authentication | 30 Oct 2026 |
Scrunch brand_share_of_voice definition; five ai_platform values |
Scrunch | developers.scrunch.com/api-reference/query/overview | 30 Oct 2026 |
| Scrunch Core 4 LLMs, Enterprise 9 LLMs | Scrunch | scrunch.com/pricing | 30 Oct 2026 |
| Scrunch rate-limit FAQ (no number published) | Scrunch | Scrunch API FAQs | 30 Oct 2026 |
| Conductor Data API needs Intelligence subscription; AI Search endpoints | Conductor | conductor.com/docs/api/introduction | 30 Oct 2026 |
| Conductor 5,000 calls per day, 2 calls per second | Conductor | conductor.com/docs/api/rate-limits | 30 Oct 2026 |
| Conductor 23-column brand rows; You, Partner, SEO Competitor, Other | Conductor | AI Search – Brands reference | 30 Oct 2026 |
| Semrush organic positions report supports Position Tracking engines “including ChatGPT”; 100 API units per keyword | Semrush | developer.semrush.com Position Tracking API | 30 Oct 2026 |
| Semrush Prompt Tracking needs AI Visibility Toolkit; ChatGPT Search, Google AI Mode, Gemini; Share of Voice “not available” | Semrush | semrush.com/kb/1503 | 30 Oct 2026 |
| Semrush API: up to 10 requests per second, 10 simultaneous requests; no caching beyond one month without written consent | Semrush | developer.semrush.com API usage restrictions | 30 Oct 2026 |
| Semrush Standard API needs SEO Toolkit Business subscription plus API units | Semrush | developer.semrush.com API access | 30 Oct 2026 |
| Semrush Brand Performance share of voice engines (ChatGPT, Google AI Mode, Perplexity, Gemini) | Semrush | semrush.com/kb/1595 | 30 Oct 2026 |
| Semrush Enterprise AIO “via API” | Semrush | enterprise.semrush.com/solutions/ai-optimization | 30 Oct 2026 |
| seoClarity ArcAI API engines, share-of-voice metrics, included with subscription | seoClarity | seoclarity.net ArcAI API | 30 Oct 2026 |
| seoClarity ArcAI MCP server | seoClarity | seoclarity.net/ai-seo/mcp-server | 30 Oct 2026 |
| BrightEdge AI Catalyst engines and CSV export | BrightEdge | brightedge.com/products/ai-catalyst | 30 Oct 2026 |
| BrightEdge API documentation via the Software Development Kit provided to customers | BrightEdge | api.brightedge.com | 30 Oct 2026 |
| BrightEdge MCP “AI citation tracking”; draws on Share of Voice and AI Catalyst; customer login required | BrightEdge | brightedge.com/brightedge-mcp | 30 Oct 2026 |
| Bing AI Performance public preview, 10 February 2026 | Microsoft | Bing Webmaster Blog | 30 Oct 2026 |
| Bing Citation Share definition, 16 June 2026 | Microsoft | Bing Search Blog | 30 Oct 2026 |
| Bing Webmaster API method list (no AI Performance method) | Microsoft | Microsoft Learn | 30 Oct 2026 |
| Search Analytics API six types | Google for Developers | 30 Oct 2026 | |
| Worked example (24 answers; 25.0%, 27.3%, 37.5%; 22.2%, 28.6%) | Zian AI, illustrative fixture | This page | 30 Oct 2026 |
Turn AI-search visibility into booked conversations. Zian’s AI sales and reception agents answer, qualify and book across calls, SMS, email, WhatsApp, Instagram and Facebook Messenger. Apply For Partnership