Use Cases

1. SEO Team: Track AI Visibility Like SERP Rank

Context: You run weekly organic performance reviews. You track GSC clicks, Ahrefs keyword rankings, and traffic by page. Your VP asks how the brand is doing in AI search. You have no answer.

The pain: Every rank tracking tool you use is built for Google's blue links. None of them tell you whether ChatGPT mentions your brand when someone asks a high-intent question in your category. You're reporting on a shrinking slice of how buyers discover products.

The job: Add visibility_pct per engine to your weekly organic report, the same way you report on average position in GSC. Know whether your brand is gaining or losing ground in AI answers week over week.

How to do it with the AEO API:

1. Call GET /v1/aeo/visibility/by-brand?brand_id=YOUR_ID&from=2026-04-03&to=2026-04-10 to pull last week's visibility scores per engine.
2. Call the same endpoint for the prior week (from=2026-03-27&to=2026-04-03) to compute delta.
3. Use GET /v1/aeo/visibility/by-engine?brand_id=YOUR_ID to break down which engines are driving citation vs. which are ignoring you.
4. Pipe the results into your existing Looker or Google Sheets report.

The visibility_pct field is directly chartable: it's a 0–100 number, computed daily, comparable across time periods. No normalization needed.

2. Agency: Power Client AEO Dashboards

Context: You have 10–30 clients who want to understand their AI visibility. Some are SaaS companies tracking brand mentions. Some are e-commerce brands tracking product category queries. All of them expect you to have the data.

The pain: You can't run custom AI scrapers per client. BrightData contracts require enterprise agreements. Maintaining scrapers across 4 separate AI UIs — each with different interfaces, rate limits, and answer formats — is a full engineering team's worth of work. Per-engine LLM analysis adds another layer of infrastructure you don't want to own.

The job: Issue one API key per client workspace. Call the AEO API endpoints on their behalf. Render branded AEO dashboards in your reporting tool. Your clients see professional AI visibility data. You don't manage any scraping infrastructure.

How to do it with the AEO API:

• GET /v1/aeo/prompts — list all tracked prompts for the client, with aggregated visibility stats
• GET /v1/aeo/visibility/by-engine?brand_id=X — engine breakdown for client dashboard
• GET /v1/aeo/citations?brand_id=X — which sources are cited alongside the client's brand
• GET /v1/aeo/visibility/timeline?brand_id=X&days=30 — 30-day trend chart data

All responses use a consistent envelope format. Authentication is per API key — one key per client organization means clean data isolation with no extra configuration.

3. Platform Team: Build AEO Alerting

Context: You're building a competitive intelligence product, or an internal growth tool. You need near-real-time awareness of what's happening in your AI category — not a weekly summary, not a dashboard someone has to remember to check.

The pain: You need programmatic access to cited domain data. You need to know when a competitor that wasn't in the AI answers last week starts appearing consistently this week. You need this to flow into your existing alerting infrastructure — Slack, PagerDuty, a custom webhook — not into another SaaS dashboard.

The job: Daily sync of all cited domains for your tracked prompts. Diff against the previous day. Alert if a new competitor domain appears above a citation threshold.

How to do it with the AEO API:

# Step 1: Pull all domains cited alongside your brand in the last 24 hours
curl "https://api.reddgrow.ai/v1/aeo/sources/domains?brand_id=42&from=2026-04-09&to=2026-04-10&limit=100" \
  -H "x-api-key: rg_YOUR_KEY"

# Step 2: Compare to your previous snapshot (stored in your DB)
# Step 3: If new domain with citation_count > threshold → alert

Use GET /v1/aeo/sources/detail?scope=domain&target=competitor.com to drill into specific pages on a new competitor domain that are getting cited. Use GET /v1/aeo/runs/{scan_result_id} to read the full AI answer that generated the citation.

The API is designed to be polled. Rate limits are 60 requests/minute and 1,000 requests/hour — sufficient for daily batch syncs across hundreds of prompts.