Site traffic data API: pull traffic estimates into an agent

If you want a site traffic data API that an agent can call while it works, the setup is shorter than most dashboards. seogeoaeo.ai exposes its Domain Overview tool over both REST and MCP, so Claude Code, Cursor or a script can request a traffic estimate for any domain, cap what it spends, and read the result as JSON.

This guide covers the call, the guardrails, and what the numbers can and cannot tell an agent.

What the endpoint returns #

Domain Overview answers one question per domain and Google market:

• ranking keyword count, split by position band
• estimated monthly visits from Google
• the cost of those visits if bought as Google Ads clicks
• paid keywords and estimated monthly ad spend
• referring sites, a 0 to 1,000 link rank, average link spam score, nofollow share, broken links and the kinds of sites linking in

It costs 50 credits per run. Agent runs cost the same as runs in the browser.

REST call #

Create a key at the API keys page; keys start with sga_. Then:

curl -X POST https://seogeoaeo.ai/api/v1/tools/domain-overview/runs \
  -H "Authorization: Bearer $SEOGEOAEO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"input":{"url":"https://example.com","market":"us"},"maxCredits":50}'

url takes any public http or https address; a page URL is reduced to its domain. market is optional and takes one of 20 codes: us, gb, ca, au, ie, in, sg, nz, za, de, fr, es, it, nl, se, pl, br, mx, jp, ae.

MCP setup #

The MCP server lives at https://seogeoaeo.ai/api/mcp and uses the same bearer key. In Claude Code:

claude mcp add --transport http --scope user seogeoaeo https://seogeoaeo.ai/api/mcp --header "Authorization: Bearer YOUR_API_KEY"

Each tool is exposed under its slug, so the agent sees domain-overview. The check-credits tool is free, which lets the agent confirm the balance before a batch.

Guardrails worth setting #

• maxCredits. The run is refused if its price is above this number. Set it to 50 for Domain Overview so a misrouted call to a pricier tool cannot go through.
• idempotencyKey. Retrying with the same key returns the original run instead of charging again. Use the domain plus the date as the key.
• Refunds. A run that fails before producing a result is refunded, and a Domain Overview run that finds neither search data nor links is refunded too.

Looping over a list of domains #

A small batch job looks like this in plain steps:

1. Read the domain list, including your own site.
2. For each domain, call domain-overview with the same market andmaxCredits: 50 .
3. Store estimated visits, top-three keyword count and link rank in one table.
4. Divide each rival's visits by your own site's estimate, so the output is a relative size, not a raw count.

Ten domains cost 500 credits. The smallest plan on the pricing page is $29 a month for 2,000 credits.

What an agent should not conclude #

The visits figure is a model of organic Google traffic. A ranking-based estimate takes each keyword's position and search volume, applies a typical click share, and adds it up. That leaves out direct, social, email, newsletter and AI referral visits, and it often runs low on branded searches.

Tell the agent so in its instructions. Useful rules:

• Report estimates as relative size and trend, never as visitor counts.
• Only compare domains measured by the same tool, same market, same day.
• Flag sites with few ranking keywords but a strong link rank as "possibly brand-led; traffic may sit outside search".

Calibrating with your own data #

The product does not connect to Search Console or analytics accounts, so calibration is a manual step. Export your Google clicks from Search Console for the same month and compare them with the tool's estimate for your domain. Hand that ratio to the agent as a constant, and it can adjust rival figures the same way.

Getting the keywords behind the number #

Domain Overview gives totals only. For the keyword list behind a domain's traffic, the agent can call competitor-keywords (35 credits), which returns ranked keywords with volume, difficulty and cost per click.

If you need a stored traffic history across many sites rather than on-demand calls, a subscription data suite will suit you better. For an agent that pulls estimates when a task needs them, paying per call keeps costs tied to use.