REST API
An SEO API for all your AI visibility data. REST, JSON and OpenAPI.
AutoSEO exposes its data over a versioned REST API: projects, prompts, AI answers, metrics, competitors, sources, keywords, rank trackers, audits, reports and tasks. Authenticate with scoped API keys or OAuth 2.1 and generate clients from the OpenAPI spec.
Why it matters
Your data belongs in your stack, not only in a dashboard.
AI visibility and SEO data is most useful when it reaches the tools you already use: BI dashboards, data warehouses, client portals and internal automations. The REST API makes the numbers in AutoSEO available to all of them.
- 01
Own your reporting
Pull metrics and time series into your BI tool, warehouse or spreadsheets on your own schedule and in your own format.
- 02
Automate the routine
Create projects, add prompts, start site audits or rank checks from scripts and pipelines instead of clicking through the app.
- 03
Built on open standards
An OpenAPI spec, JSON responses and bearer tokens mean any language, HTTP client or code generator can talk to AutoSEO.
- Key scopes
- 4
- Read, write, spend, export
- Requests per minute
- 120
- Default limit per key
- Answers per export page
- 5,000
- As JSON or CSV
- Self-hosted
- $0
- API included, MIT licensed
What you can do
What the API covers, from any language.
AI visibility metrics
Visibility, mention rate, citation rate and position as totals or time series, filtered by engine, tag and period.
Prompts and answers
List and create prompts, read single AI answers with their citations, and pull competitors, sources and query fan-outs.
SEO research and tracking
Keyword research, SERPs, domain and backlink data, saved keywords, rank trackers and local SEO — all with the same keys.
Audits and crawlability
Start and stop site audits, read issues, pages and Lighthouse results, compare runs and export them as CSV or JSON.
Reports and tasks
Create, share and generate reports, and read, update or comment on optimization tasks.
Bulk export
Export every prompt with its metrics and every AI answer in a period as JSON or CSV, up to 5,000 answers per page.
How it works
From API key to first request in three steps.
- 1 Step 1
Create a scoped API key
Under Settings → API & MCP, create a key with the scopes you need and optionally limit it to specific projects. The key is shown once.
- 2 Step 2
Read the OpenAPI spec
The spec is served at /api/v1/openapi.json on your AutoSEO URL, and the docs live under Settings → API & MCP.
- 3 Step 3
Send your first request
Pass the key as a bearer token. Every response uses the same JSON envelope with a request ID, and usage shows up in your API settings.
FAQ
Frequently asked questions
Does AutoSEO have an API?
Yes. AutoSEO includes a versioned REST API at /api/v1 with an OpenAPI specification, self-hosted and in AutoSEO Cloud. It covers projects, prompts, AI answers and metrics, SEO research, rank tracking, site audits, analytics, reports and tasks.
How do I authenticate with the AutoSEO API?
Create an API key under Settings → API & MCP and send it as a bearer token in the Authorization header. Apps can use OAuth 2.1 with PKCE instead. Keys and tokens are stored only as hashes and can be revoked at any time.
What are API key scopes?
Scopes limit what a key can do. Read covers projects, metrics, competitors, sources, tasks and reports; write lets it create projects, prompts and tags; spend allows anything that costs money, such as DataForSEO research or AI generation; export allows bulk exports. Your role permissions still apply on top.
Is there an OpenAPI specification?
Yes. AutoSEO serves its OpenAPI spec at /api/v1/openapi.json. Import it into Postman, Insomnia or a code generator to get a typed client in your language.
Are there rate limits?
Yes. Each API key or OAuth token is limited to 120 requests per minute by default; when you self-host, admins can change the limit in the admin panel. Failed authentication attempts are rate-limited per IP.
Can I export all AI answers through the API?
Yes. The export endpoint returns all prompts with their metrics and one row per AI answer in the chosen period, as JSON or CSV. It's paginated with up to 5,000 answers per page and can include the full answer text.
Should I use the REST API or the MCP server?
Use the REST API for scripts, integrations and dashboards that need predictable JSON. Use the MCP server when an AI agent such as Claude Code, Codex or Cursor should work with your data. Both use the same API keys and scopes.
Does the API cost extra?
No. The REST API is part of the open-source AutoSEO app and included in every AutoSEO Cloud workspace for $50 per month. Endpoints that call DataForSEO or AI providers need the spend scope; when you self-host, those providers bill you directly, and in Cloud they count toward the $10 of included usage.
Related features
Works better together. One platform, one dataset.
- MCP serverConnect Claude, ChatGPT, Cursor or Codex to your data with 100+ MCP tools.
- AI SEO agentChat with your SEO and AI visibility data on your own Claude Code or Codex.
- Report builderBranded client reports with live data, 11 templates, PPTX/PDF export and share links.
- AI visibility trackingTrack how often 16 AI engines mention and cite your brand, every day.
Put your AI visibility data to work
Start with an AutoSEO Cloud workspace for $50/month, or self-host the open-source edition for free.