SEO APIOne key for the SEO data you need

Send one line to your AI and it signs in and connects by itself. Domain, traffic and more SEO data behind one key, one credit balance and one JSON format.

Read https://seo-api.org/agent.md and set up SEO API for me.

Works with Claude Code, Cursor, Codex, Windsurf and other AI tools that can browse the web

  1. 1Copy the prompt
  2. 2Sign in via the link your AI sends
  3. 3Your AI starts querying
10 free credits on sign-up

Every endpoint in the catalog

Each API has its own reference page with parameters, response fields, errors and MCP and CLI usage. New APIs show up in this catalog as soon as they ship, on the same key and the same balance.

View the full catalog →

Domain & traffic

  • Domain data1 credit per call

    GET /api/v1/domain

    Registration date, domain age, registrar, monthly traffic, ranks and traffic sources for one domain.

Site monitoring

  • Sitemap changes3 domains free, then 2 credits/day each

    GET /api/v1/sitemap/changes

    Watch any site's sitemap and get the pages it added or removed each day.

Account

  • GET /api/v1/credits

    Remaining credits on the account that owns the API key. Never costs a credit.

Need other SEO data?

Tell us which SEO data you want next and we will prioritise it.

Email us →

Stop stitching SEO tools together

Most SEO workflows pull from several services with separate keys, separate bills and separate response formats. We replace that with one integration.

One key, one balance

Every endpoint uses the same API key and draws from the same credit balance. Create as many keys as you need for projects, scripts and teammates.

One response format

Every call returns the same ok / data envelope, millisecond timestamps and stable error codes, so your parsing code is written once.

Pay only for data

You are charged only when an API returns data. Calls that are still collecting, have no data or fail cost nothing.

Built for AI agents

A remote MCP server exposes every API as a tool, so Claude, Cursor and your own agents query live SEO data instead of guessing numbers.

Works from the terminal

The CLI prints readable summaries or raw JSON and can wait for data that is still being collected.

New APIs, same integration

When a new endpoint ships it uses the same auth, billing and format. Your existing key and code keep working.

Call the SEO API from code, agents or the terminal

All three channels use the same API key, the same credit balance and the same response format, so you can prototype in the terminal and ship the exact same call in production.

Plain HTTPS GET endpoints with Bearer auth. Works from any language, serverless function or spreadsheet script.

REST API docs →
shell
curl "https://seo-api.org/api/v1/domain?domain=example.com" \
  -H "Authorization: Bearer YOUR_API_KEY"

What teams build with these APIs

SEO data feeds almost every growth workflow. These are the ones we see most often.

Vet domains and link targets

Check how old a domain is and whether it gets real traffic before you buy it, pitch a guest post or accept a backlink.

Research competitors and markets

Pull traffic and traffic-source data for a list of competitors and see who wins on organic search, paid search or AI assistants.

Enrich CRMs, directories and lists

Add SEO data to every row of a CRM, a startup directory or a link list so your team can sort by real size and authority.

Give AI agents real SEO data

Research agents hallucinate traffic numbers. Connected over MCP, they call a tool and cite what it returns.

Simple credit pricing for every API

Credits are the only unit across every API. Each endpoint lists its price in the catalog, and you are never charged for a call that returns no data.

Price per API

10free credits to start
  • 10 free credits when you sign in with Google
  • Each API lists its price in the catalog
  • Calls that return no data are free
  • Unlimited API keys, all sharing one balance

Need more credits? Email support@seo-api.org

SEO API questions

Short answers about the catalog, billing and the three ways to call the API.

What is the SEO API?

It is a single API for SEO data. Instead of signing up for a separate service for each kind of data, you use one API key, one credit balance and one JSON format for every endpoint in the catalog, over REST, MCP or the command line.

Which APIs are available today?

The catalog currently has domain data (registration date, domain age, registrar, expiry, monthly traffic, ranks and traffic sources), sitemap monitoring (pages a site added or removed each day) and a credit balance endpoint. The API catalog page always lists what is live, and every API has its own reference page.

How does pricing work?

Every account starts with 10 free credits. Each API lists its price in the catalog, and you pay only when a call returns data. To keep the free tier fair, sign-up credits go to personal email accounts such as Gmail or Outlook, once per network every 24 hours.

Can AI agents call these APIs?

Yes. There is a remote MCP server over Streamable HTTP. Add it to Claude Code, Claude Desktop, Cursor, Windsurf or any client that supports Streamable HTTP, pass your API key in the Authorization header, and every API in the catalog becomes a tool.

Is there a command-line tool?

Run npx @seo-api/cli login with your key once, then call any endpoint from your terminal. Add --json to pipe the raw response into jq or a script, or --wait to keep polling until data that is still being collected is ready.

How many API keys can I create?

As many as you need. Create one per project, script or teammate in the dashboard, rename or copy them at any time, and revoke any key instantly. All keys on an account share the same credit balance.

Can I request a new API?

Yes. Email us with the SEO data you need next. New endpoints use the same key, billing and response format, so they work with your existing integration from day one.

Where does the data come from?

Each API documents its sources on its reference page. Domain data combines registry RDAP and WHOIS records with third-party traffic panel estimates, which are best for comparing sites and spotting trends rather than matching a site's own analytics.