How do we review AI visibility APIs, MCP servers and connectors?

Every guide on AI Visibility APIs answers the same questions about each vendor, so that access paths can be compared and checked by anyone. Last full check: 13 Nov 2026.

Which sources do we use?

  1. Vendor documentation first. API references, MCP documentation, help-center articles and pricing pages published by the vendor.
  2. Specifications second. Protocol and platform documentation such as the Model Context Protocol specification and Google's Looker Studio and BigQuery documentation.
  3. Research for context. Studies and reputable write-ups are cited with a numbered source when they inform a claim.

What do we check for every vendor?

FieldWhat we record
APIWhether a public REST API exists, its base URL and documented endpoint groups
MCP serverWhether one exists, its transport, which tools it exposes, read-only or write
AuthAPI keys, OAuth, scopes, per-project restrictions
Plan requiredThe lowest plan that includes the access path, as listed on the pricing page
LimitsPublished rate limits, quotas and whether API calls consume plan credits
Exports and connectorsCSV, scheduled exports, Looker Studio, BigQuery, webhooks

What do we not do?

  • We do not publish star ratings, scores or anonymous reviews.
  • We do not guess undocumented endpoints or limits; missing information is marked "not published".
  • We do not accept payment from vendors for placement.

How often are guides updated?

APIs, MCP servers and plan gating change quickly in this category. We re-check every guide at least monthly and whenever a vendor announces a change to its API, MCP server or pricing. The updated date is shown at the top of each guide.