API Reference
The RankRush REST API - base URL, authentication, JSON responses, and the available operations.
The REST API returns the same visibility and audit data as the dashboard, as JSON. It’s included on every paid plan, alongside the CLI and MCP server.
Base URL
https://api.rankrush.ai/v1Authentication
Pass your API key (prefixed rr_live_) as a bearer token on every request. See API Keys to create one.
curl https://api.rankrush.ai/v1/visibility \
-H "Authorization: Bearer <your-api-key>"Every response is JSON, so it drops straight into scripts, BI tools, dashboards, and agents.
Operations
The API exposes the same operations as the CLI - each CLI command wraps an endpoint and selects a business by name:
| Operation | CLI command | Returns |
|---|---|---|
| Visibility | rankrush visibility-check | Per-engine citations, mentions, and share-of-voice |
| Audit | rankrush audit-run | Audit nodes scored 0-100 with recommended fixes |
| Keywords | rankrush keywords-list | Tracked keywords for a business |
| Profiles | rankrush profiles-list | The businesses on your account |
| Blog topics | rankrush blog-topics-list | AEO content topics for a business |
The full machine-readable contract - every api-key operation with its request/response schemas and error shapes - is published as an OpenAPI 3.1 document: openapi.json (YAML). Import it into Postman/Insomnia, generate a client, or hand it to an AI agent. Direct REST is rolling out; today the MCP server and CLI are the fastest integration paths. A rendered per-endpoint reference is coming.
Rate limits & errors
Requests are rate-limited per key and return standard HTTP status codes; error bodies are JSON with a message. The CLI is the quickest way to explore responses before you wire up the raw API.