Skip to content

The neutral index of AI-visibility & GEO tools

Research report · data-report

API access: a census of 114 listings

27 of 114 listings answer yes for “API access”. Counted from our own datasheet, with the query that reproduces every figure.

Sep 14, 2026updated Sep 14, 20262 min readSource-linked research

API access, across 114 settled listings

  1. Yes27 of 114

  2. Qualified58 of 114

  3. No9 of 114

  4. Does not apply9 of 114

  5. Not established11 of 114

Of the 114 Published listings whose datasheet settles “API access”, the largest group is “Qualified” at 58 (51%). Measured 2026-09-14.

Denominator: 114 Published listings whose datasheet settles “API access”.Method: Counted from the stored datasheet answer for “API access” across every Published listing, excluding the 1 without a recognised stored answer on that row.Measured .
Cite this chart

Reuse this chart anywhere, with credit. Paste this HTML — it links back to the report the numbers come from.

<a href="https://citedindex.com/blog/api-access-census/" target="_blank" rel="nofollow noopener"><img src="https://citedindex.com/charts/api-access-census.png" alt="API access, across 114 settled listings — CitedIndex" title="API access, across 114 settled listings — CitedIndex" width="640" loading="lazy" style="max-width:100%;height:auto" /></a>

Explore the matching tools

API access · Datasheet criterion api_access · Report counted .

Current listings as of ; this set may differ from the report's original sample. Includes “Yes” and “Qualified” answers only. Read the conditions on qualified answers before treating them as a match. “No”, “Not applicable” and “Not established” answers are excluded.

View 85 current matching records
  • Adobe Brand Visibility Qualified

    The only documented API surface is the Edge Optimize production and staging key used to route CDN traffic; no reporting or data-retrieval API is documented, so visibility data leaves through CSV and PDF export or the analytics connectors.

    Source retrieved 2026-09-12

  • AEO Engine Qualified

    A keyless public API exists but only runs the free report, with per-IP, per-email and per-domain rate limits; no API is documented for the paid dashboard's tracking data.

    Source retrieved 2026-09-10

  • AEOlens Qualified

    Public no-auth quick-scan endpoints are open to anyone (10 scans/hour/IP); the API-key CI scan endpoint requires Growth or Agency, and dashboard endpoints are session-auth only.

    Source retrieved 2026-09-02

  • Ahrefs Brand Radar Yes

    Brand Radar reports expose an API button and a documented API reference; API access is listed on every plan tier.

    Source retrieved 2026-09-02

  • AIclicks Qualified

    Read-only v1 REST API with bearer keys, absent from Starter; no write endpoints and no webhooks.

  • AI Search Watcher Yes

    A documented REST API covers models, monitors and prompts, is included on every tier including Free, and draws on the plan's API quota.

    Source retrieved 2026-09-17

  • AI Sightline Yes

    REST API on every tier with self-issued bearer keys; monthly call caps run 100 (Free) to 50,000 (Agency).

    Source retrieved 2026-09-02

  • AI Visibility Audit Qualified

    The stack is a FastAPI backend guarded by a shared API key that the bundled frontend calls, so a self-hoster can query it locally, but no endpoint reference, client library or versioned API contract is published.

    Source retrieved 2026-09-16

  • Amplitude AI Visibility Qualified

    No AI Visibility API endpoint is documented; data leaves as a CSV of prompt metrics or as report events ingested into Amplitude projects, where the platform REST APIs then apply.

    Source retrieved 2026-09-01

  • Analyze AI Qualified

    Programmatic access exists through the token-authenticated remote MCP server, but the docs publish no REST API reference and traffic analytics are excluded from that surface.

    Source retrieved 2026-09-12

  • ApexGEO Qualified

    API Access appears only in the Enterprise feature list (from $999/mo, contact sales); no API is offered on the five self-serve tiers.

    Source retrieved 2026-09-02

  • Archytas AISpy Qualified

    There is no public or REST API for AISpy itself; programmatic access means reading the local SQLite file it writes, or picking up scheduled CSV/XLSX dumps, and the GUI has to be running for any data to exist.

    Source retrieved 2026-09-13

  • AthenaHQ Qualified

    A paid add-on on Starter, included on Enterprise, absent from the free plan.

    Source retrieved 2026-09-02

  • auto-geo Qualified

    There is no hosted or public HTTP API and the library exports were removed; programmatic access means piping the CLI's stable JSON or NDJSON output into your own stack.

    Source retrieved 2026-09-12

  • BabyLoveGrowth Yes

    REST API keyed by an X-API-Key header, pull-based and rate-limited; it serves generated articles, not the AI-visibility data.

  • Bloomiro Qualified

    Programmatic access is the MCP endpoint at mcp.bloomiro.com/mcp with OAuth or a project API key as a Bearer token; the published OpenAPI document exposes only /mcp and /health, so there is no separate REST data API.

    Source retrieved 2026-09-02

  • BrightEdge Yes

    BrightEdge Connect is a REST API used to push rank, search and social data into analytics and BI stacks; packaging by tier is not published.

    Source retrieved 2026-09-11

  • Bttr. Qualified

    API access is a tier feature, marked absent on Starter and present on Growth and Enterprise, and the vendor publishes no developer documentation, endpoint reference or authentication guide anywhere on the site to say what it returns.

    Source retrieved 2026-09-08

  • Canonry Yes

    Versioned REST API plus a JSON-returning CLI and signed webhooks; the dashboard is one client of the same project API.

  • CheckThat.ai Qualified

    API tokens exist inside the paid platform's admin and govern programmatic access, but GrowthX issues and manages them, customers see the screen read-only, no public API reference is published, and the terms forbid automated extraction.

    Source retrieved 2026-09-11

  • CisionOne AI Visibility Qualified

    A REST API exists but its published scope is media monitoring only: the v2 reference documents mentions, streams and stream stats, with no AI Visibility endpoint, and access needs an admin-generated token.

    Source retrieved 2026-09-11

  • Citadex Qualified

    A May 2026 comparison post claims an API, but no plan tier lists API access, no API documentation exists in the help centre, and the same post is stale on price and engine count.

  • CiteLens Qualified

    Read-only REST API (v1) on Pro and Agency only; the plan table marks Free, Starter and Growth 'No API'.

    Source retrieved 2026-09-02

  • CiteMentor Qualified

    Programmatic access is Enterprise-only and documentation is not public; it is requested from the vendor along with pricing.

    Source retrieved 2026-09-02

  • Cognizo Yes

    REST API at core.cognizo.ai/api/v2/, listed on every published tier

    Source retrieved 2026-09-02

  • Conductor Qualified

    Data API is an available add-on on Essentials and Growth, included on Enterprise.

  • Dageno Qualified

    A documented REST API with x-api-key auth exists and covers prompts, citations and opportunities, but plan access starts only at Scale, the $410 tier; Starter and Growth get no API at all.

    Source retrieved 2026-09-15

  • Distribb Yes

    Documented REST API v1 with a bearer key from account settings covers projects, articles, keywords, backlinks, Search Console, AI visibility and outreach; POST /articles/generate is Pro-only and not available on the Agentic plan.

    Source retrieved 2026-09-02

  • EdenRank Qualified

    A documented read-only REST API with self-serve keys exists, but only from the $299 Concierge tier; write APIs and webhooks are explicitly not offered.

    Source retrieved 2026-09-13

  • Elmo Yes

    A documented REST API ships on every plan and in the self-hosted build, with organization keys that carry explicit scopes, can be limited to chosen brands and can be given an expiry.

    Source retrieved 2026-09-11

  • Emergine Qualified

    API is an Enterprise-tier line item and part of the agency programme; not included on Lite.

    Source retrieved 2026-09-02

  • Epovest Yes

    REST API v1 included with the account, same surface as the app, 120 requests per minute per key.

    Source retrieved 2026-09-02

  • Finseo Qualified

    A versioned REST API with an OpenAPI spec exists, but the brand plan table withholds API and webhooks from Starter and Business; agency tiers all include it.

    Source retrieved 2026-09-08

  • Foglift Qualified

    The authenticated REST API, CLI and GitHub Action start at Launch; free accounts get only the playground and the unauthenticated single-page scan endpoint.

    Source retrieved 2026-09-03

  • Frase Yes

    REST API on every plan including Starter, metered by requests a month, with HMAC-signed webhooks; Enterprise limits are custom.

  • Gauge Yes

    Programmatic API plus CSV exports; an OpenAPI spec is published.

  • GeoArk AI Qualified

    API access is a Custom-plan line item; the comparison table marks the row with a dash for Free, Starter and Growth.

    Source retrieved 2026-09-02

  • GeoRankers Qualified

    Launch and Grow show a dash for API access and the row itself is labelled Roadmap, so only custom-quoted Enterprise is offered one.

    Source retrieved 2026-09-14

  • geoSurge Yes

    REST API is ticked on both Free and Enterprise.

    Source retrieved 2026-09-02

  • GEO Tool Qualified

    The public API is open and unauthenticated but only exposes blog posts and the aggregate visibility index; the page analysis itself is deliberately kept out of it.

    Source retrieved 2026-09-14

  • GetCito Qualified

    The self-hosted open-source build ships a Bearer-authenticated REST API; no managed plan row mentions API access.

  • Goodie Qualified

    The API row is unchecked for Core and Pro and checked only for Enterprise, so programmatic pulls require a custom-quoted contract.

    Source retrieved 2026-09-15

  • HubSpot AEO Qualified

    A beta AEO API returns prompts, prompt runs with response text and citations, and recommendations under scope marketing.aeo.read - but the reference gates it to Marketing Hub Professional or higher, not the $50 standalone plan.

    Source retrieved 2026-09-02

  • Indexly Qualified

    A documented REST API keyed by X-API-Key and rate limited to 15 requests per minute, but the plan table marks APIs excluded on Starter and Growth and included only on Scale.

  • Keyword.com AI Visibility Qualified

    API on every plan but scoped by plan: AI Visibility data only on the AI plan, Google SERP only on Search Visibility, both on 360°

  • Knowatoa Qualified

    REST v2 with twelve export endpoints, but bundled into the reporting stack that Starter does not get; the docs confirm the key only appears if the plan supports it.

  • LLMClicks.ai AI Visibility Tracker Qualified

    Accounts carry a rotatable API key documented for external integrations and used by the WordPress plugin, but no endpoints, reference docs or rate limits are published.

    Source retrieved 2026-09-03

  • LLM Pulse Qualified

    REST API with SDKs and a Rust CLI, but the plan cards exclude it from Starter and Growth and include it from Scale.

    Source retrieved 2026-09-02

  • LLMrefs Yes

    Bearer-token REST API with a published OpenAPI 3.1 reference and a JavaScript SDK, included on the single plan; all users are capped at 10 requests per minute.

  • Local Dominator AI Tracker Qualified

    A documented AI Tracker REST API exists, but API access is a Pro-and-above plan line.

    Source retrieved 2026-09-02

  • Local Falcon Qualified

    Data-retrieval API needs Basic monthly or Starter annual; the on-demand API is a separate $199/month subscription plus $0.0032 per request.

  • Meltwater GenAI Lens Qualified

    A documented AI Visibility API returns GenAI Lens prompts, trends and share of voice, but the plan comparison grid ticks API & MCP Integrations only for Enterprise and Agency.

    Source retrieved 2026-09-18

  • Mentionable Qualified

    Programmatic access exists through per-user API keys against the hosted MCP endpoint, but it starts at Pro and no separate REST API is documented for the entry tier.

    Source retrieved 2026-09-09

  • Morningscore Qualified

    Full API on every plan at 2 requests/sec, but the AI Overviews and ChatGPT tracking endpoints are marked "Coming soon" on all four tiers.

    Source retrieved 2026-09-02

  • Nightwatch Qualified

    Not on Starter. Included from Professional upward, with custom API rate limits added on Agency and Enterprise.

    Source retrieved 2026-09-02

  • Omnia Yes

    API access is listed as included on every tier, Growth upward.

    Source retrieved 2026-09-02

  • OmniSEO Qualified

    No API is documented anywhere on the site. The word never appears about their own product across all 84 sitemap pages, and there is no docs, api or integrations route. The only machine-readable path is JSON export on Enterprise, beside a Custom server-side-events row.

    Source retrieved 2026-09-03

  • OpenSEO Qualified

    Personal API keys exist, but they authenticate the hosted MCP endpoint for headless clients; the docs describe no separate REST or data API for your own stack.

    Source retrieved 2026-09-09

  • Orchly Yes

    API listed on Essential and Pro; Enterprise gets 'Full API Access'.

    Source retrieved 2026-09-02

  • OtterlyAI Qualified

    API access starts on Standard (2,000 requests/month, 5,000 on Premium); Lite has none.

    Source retrieved 2026-09-02

  • Peec AI Qualified

    A documented REST API exists but is beta and Enterprise-only, and the plan table marks API access absent on Starter, Pro and Advanced while the homepage advertises the API with no such condition.

    Source retrieved 2026-09-03

  • Profound Qualified

    A documented REST API with Python and JavaScript SDKs exists, but the plan table marks API No on both self-serve tiers and access is granted on request.

    Source retrieved 2026-09-09

  • Promptwatch Yes

    REST API keys are ticked from Essential ('MCP and API access'); the docs warn API access is a plan feature and existing keys stop working after a downgrade.

    Source retrieved 2026-09-02

  • Qwairy Qualified

    REST API v1 is excluded from Starter and included from Growth up, with team-scoped bearer tokens over brands, performance, competitors, sources, prompts, answers and crawler analytics.

  • RadarKit Qualified

    API access is No on Lite, Growth and Pro, and Yes only on Enterprise.

    Source retrieved 2026-09-02

  • Rankability Yes

    API access is included on all three plans, Starter upward.

  • Rankfender Yes

    Documented REST API at api.rankfender.com/v1 with bearer API keys; included on every plan, rate-limited 100/500/2,000 requests per hour by tier.

  • RankLens Yes

    A documented POST endpoint returns rank and competitor rows, with engine, language, location and sampling as parameters; the key is free.

  • Rank Prompt Yes

    Public REST /v1 included from the cheapest paid tier upward with per-tier request caps; standalone API-only plans also exist.

  • Rankscale Qualified

    REST API is absent on Essentials and Pro, included on Growth and Enterprise as Metrics + Share Links.

    Source retrieved 2026-09-02

  • Rankshift Yes

    REST API on every plan, including Starter, and not gated to higher tiers.

    Source retrieved 2026-09-02

  • RankZero Qualified

    A documented REST API exists but keys are issued on request and scoped to one account; no plan row grants it

  • Scrunch AI Qualified

    Query, responses and agent-traffic APIs, but API access is an Enterprise line item and is billed on responses collected.

    Source retrieved 2026-09-02

  • Searchable Yes

    API access is listed on every published plan card, including the cheapest.

  • Semrush AI Visibility Toolkit Qualified

    Semrush publishes a unit-metered API v3/v4 for SEO, traffic and project data, but no AI Visibility endpoint is documented; the pricing page reserves custom API work for Enterprise.

    Source retrieved 2026-09-18

  • SEObot Yes

    A REST API and webhooks pull articles into your own stack, with an npm package and a Next.js example, plus endpoints to create headlines programmatically; the per-website API key only appears once the site holds at least one article credit.

    Source retrieved 2026-09-09

  • SEORCE Qualified

    A REST API with Bearer auth exists, but tokens are requested by email and the two pages disagree on which plan unlocks it; only the AI Beacon GEO endpoint is live today.

    Source retrieved 2026-09-15

  • SE Visible Yes

    A documented REST API covers projects, prompts, results, metrics and cited sources, keyed by the same SE Ranking token, and the plan cards name no tier where it is withheld.

    Source retrieved 2026-09-17

  • Similarweb AI Search Intelligence Qualified

    The API is not part of the self-serve $99/$399 AI Search tiers; it is a Business/Enterprise entitlement or a separate purchase.

  • Sleepwalker AI Yes

    Public REST API on scoped bearer keys, plus a CLI over the same API; 300 authenticated requests per hour by default.

  • Surfer Qualified

    API is Peace of Mind and Enterprise only, and AI Tracker data is explicitly not exposed through it

  • Trakkr Qualified

    The REST API is withheld from the entry plan and unlocks on Scale or Enterprise; the comparison table marks the API row with a dash for Growth.

    Source retrieved 2026-09-16

  • TrueRanker Qualified

    A REST API covering AI visibility exists but only on the top Agency tier; the plan comparison table marks 'API & MCP access' as not included on both Starter and Pro.

    Source retrieved 2026-09-17

  • WebGlazer Qualified

    Included on Enterprise only. Not included on Basic and Standard, 'Coming soon' on Advanced and on all three agency tiers.

  • Writesonic Yes

    REST GEO API keyed by X-API-KEY, activated from an API Dashboard toggle in the account.

    Source retrieved 2026-09-02

The population

115 listings in this index are Published. This is the population as of 2026-09-14. 114 of the 115 published listings in this index carry a settled answer for “API access”. That row asks: Can you pull the data into your own stack? One other listing has no recognised stored answer on this row and is left out of every figure below rather than counted as a no.

Findings

  1. 27 of the 114 settled listings answer “Yes” for “API access”. That is 24% of the settled set.

  2. 58 of the 114 settled listings answer “Qualified” for “API access”. That is 51% of the settled set.

  3. 9 of the 114 settled listings answer “No” for “API access”. That is 8% of the settled set.

  4. 9 of the 114 settled listings answer “Does not apply” for “API access”. That is 8% of the settled set.

  5. 11 of the 114 settled listings answer “Not established” for “API access”. That is 10% of the settled set.

1 of those yes answers is SEObot, which still answers yes for “API access”. Its listing carries the stored answer and links to the source recorded for it. This is one worked example, not an independent audit of every source in the census.

What we counted, and how

Each figure above is a count over the “API access” row of the listing datasheet, taken from the same stored answer the listing page renders. The denominator is the 114 listings whose answer is settled, meaning one of yes, qualified, no, does not apply, not established. It is not the 115 in the index, because a missing answer is not evidence of absence. Every number here is stored with the read-only query that reproduces it and re-run every sixty seconds against the live corpus, so a figure that stops reproducing surfaces as drift rather than as a stale sentence nobody notices. Our full method covers how a datasheet row is settled in the first place.

Limitations

This counts stored datasheet answers, not independently tested capabilities. A sourced answer can record a vendor statement or our reading of published evidence; this census does not re-fetch those sources. “Not established” means we have not established an answer. That can reflect vendor nondisclosure, blocked evidence, or unfinished research, not a no. An absent or unrecognised answer is excluded rather than treated as a researched finding. The figures are restated when the stored corpus changes; the date above is the count used for this published version, not a new verification of the vendors.

Get the next report

New tools rankings and fresh data reports. One short email, one-click unsubscribe.