AI Brand Monitor: GEO / AI Search Visibility Tracker
Pricing
Pay per event
AI Brand Monitor: GEO / AI Search Visibility Tracker
Track how your brand appears in AI answers across ChatGPT, Gemini & Claude. Measure mention rate, share-of-voice vs competitors, ranking & cited sources β with multi-sample reliability. GEO / AEO visibility data for SEO agencies, brand & PR teams. Pay-as-you-go.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Berkan Kaplan
Maintained by CommunityActor stats
0
Bookmarked
7
Total users
1
Monthly active users
6 days ago
Last modified
Share
AI Brand Monitor β Answer Visibility π€
π Monitor how AI assistants talk about a brand β no login, no API key, one row per prompt/brand, with mentions, sentiment, citations and competitor context. Built for GEO/SEO, marketing and brand teams.
π What is the AI Brand Monitor β and when should you use it?
Give this actor brands, prompts or domains and it returns matching brands from live AI-assistant answers (brand-mention monitoring) β as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run queries the source live, so the data is as fresh as the registry itself.
Use it when you need: a brand company list for outreach; formation / status monitoring; or a canonical registry record for KYB and due diligence.
Use something else when: you need classic search rankings β this monitors AI-answer mentions, not search positions.
π€ Use with AI agents
Already on the Apify MCP server? Ask for this Actor by name: foxlabs/ai-brand-monitor.
Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire β no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.
Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:
I want to pull brand company records using the Apify Actor `foxlabs/ai-brand-monitor`.Input: `queries` is a list of brands, prompts or domains. `maxResultsPerQuery` caps rows per query.Start with: {"queries":["undefined"],"maxResultsPerQuery":50}Ask me what to look up, run the Actor, then summarise the rows as a table.
The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/ai-brand-monitor.md.
π Overview
Everything you need to turn live AI-assistant answers (brand-mention monitoring) into clean, structured data β in one actor, with no login, cookies or API key.
Why teams pick this actor:
- β Whole analysis, one call β name or ID in, matching brands out.
- π§Ή No empty-promise columns β only fields this registry actually fills; degenerate columns are removed.
- π Stable identifiers β every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
- π° Pay only for results β per-row pricing, empty/failed lookups never billed.
- π€ Agent-ready β MCP + x402 agentic payments.
β¨ Features
- π Name or ID lookup β relevance-ranked name search or exact registry-ID lookup.
- π’ Full entity profile β status, legal form, formation date, address and the registryβs own contact fields.
- π§Ή Clean schema β deduplicated camelCase rows, ready for CSV/Excel/JSON.
π¬ Quick Start
curl -X POST "https://api.apify.com/v2/acts/foxlabs~ai-brand-monitor/runs?token=YOUR_TOKEN" \-H "Content-Type: application/json" \-d '{"queries":["undefined"],"maxResultsPerQuery":50}'
π Getting Started (3 steps)
- Choose your targets β brands, prompts or domains.
- Set the cap β
maxResultsPerQuerylimits rows per query. - Run and export β get a clean dataset as JSON, CSV or Excel.
π₯ Input
{"queries":["undefined"],"maxResultsPerQuery":50}
| Field | Type | Description |
|---|---|---|
queries | array | Brands, prompts or domains. |
maxResultsPerQuery | integer | Caps rows per query. |
maxConcurrency | integer | How many queries to fetch at once. |
includeRaw | boolean | Attach the sourceβs untouched record under raw. |
π€ Output
One row per company, saved to the dataset. Every row also carries query, scrapedAt, and β when a lookup fails β an error explaining why (never silently dropped, never billed).
| Field | Description |
|---|---|
type | Type |
brand | Brand |
engine | Engine |
engineLabel | Engine Label |
prompt | Prompt |
samples | Samples |
brandMentioned | Brand Mentioned |
brandMentionedSamples | Brand Mentioned Samples |
brandMentionRatePct | Brand Mention Rate Pct |
mentionStabilityPct | Mention Stability Pct |
brandRank | Brand Rank |
avgRank | Avg Rank |
mentionCount | Mention Count |
positionScore | Position Score |
sentiment | Sentiment |
excerpt | Excerpt |
citationsCount | Citations Count |
sourcesText | Sources Text |
answer | Answer |
category | Category |
engines | Engines |
promptsPerEngine | Prompts Per Engine |
samplesPerPrompt | Samples Per Prompt |
totalQueries | Total Queries |
visibilityIndex | Visibility Index |
indexBand | Index Band |
previousVisibilityIndex | Previous Visibility Index |
visibilityIndexDelta | Visibility Index Delta |
visibilityScorePct | Visibility Score Pct |
shareOfVoicePct | Share Of Voice Pct |
shareOfVoiceBreakdown | Share Of Voice Breakdown |
overallSentiment | Overall Sentiment |
sentimentBreakdownPct | Sentiment Breakdown Pct |
perEngine | Per Engine |
enginesSkipped | Engines Skipped |
topCitedSources | Top Cited Sources |
topCitedSourcesText | Top Cited Sources Text |
generatedAtIso | Generated At Iso |
πΌ Use cases
1. Brand monitoring β track a brandβs presence in AI answers. Input: brands or prompts. Output: mentions + sentiment. Use: a monitoring dashboard.
2. Reputation watch β catch negative AI answers early. Input: brand + prompts. Output: sentiment + citations. Use: an alert feed.
3. GEO strategy β find prompts to influence. Input: prompts. Output: presence + gaps. Use: a content plan.
π Integration
JavaScript / Node.js
import { ApifyClient } from 'apify-client';const client = new ApifyClient({ token: 'YOUR_TOKEN' });const run = await client.actor('foxlabs/ai-brand-monitor').call({"queries":["undefined"],"maxResultsPerQuery":50});const { items } = await client.dataset(run.defaultDatasetId).listItems();console.log(items[0]);
Python
from apify_client import ApifyClientclient = ApifyClient('YOUR_TOKEN')run = client.actor('foxlabs/ai-brand-monitor').call(run_input={"queries":["undefined"],"maxResultsPerQuery":50})for item in client.dataset(run['defaultDatasetId']).iterate_items():print(item)
Automation (n8n / Zapier / Make): schedule or webhook β HTTP request to the actor API with your queries β handle the JSON dataset β push to a sheet, CRM or dashboard.
π Pricing
Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.
β FAQ
Do I need an account, login or API key? No. This reads live AI-assistant answers (brand-mention monitoring).
What do I search by? Brands, prompts or domains.
How current is the data? Every run queries the source live, so results are as fresh as the registry.
What does it measure? Brand mentions, sentiment, citations and competitor context across AI-assistant answers for your prompts.
Can I export to CSV / Excel / JSON? Yes β directly from the Apify dataset.
π Troubleshooting
- Fewer rows than expected β raise
maxResultsPerQuery, or refine the name. - A name returns an unexpected entity β it matched a similar registered name; search the exact registry ID.
- No rows for a name β try the entityβs exact legal name or its registry ID.
βοΈ Is it legal to scrape this data?
This actor queries public AI assistants and analyses their answers for brand mentions. Results can still contain personal data (e.g. a personβs name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apifyβs blog post on the legality of web scraping.
π€ Support & contact
- π Website: data.foxlabs.com.tr
- π§ Email: info@foxlabs.com.tr
- π Issues: open a ticket in the Actorβs Issues tab
- π§° More clean B2B data actors: Fox Labs on Apify
Changelog
0.1 β 2026-09-07
- Dropped empty-promise columns. Removed
competitorsMentioned, competitorsMentionedText, competitors, citationRatePct, sourceGap, sourceGapTextβ live AI-assistant answers (brand-mention monitoring) does not carry them, so they were shipped as always-null columns. Only fields this source actually fills are now emitted. - Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).
0.0
- Initial release: data from live AI-assistant answers (brand-mention monitoring) by name or registry ID.