{"slug": "site-traffic-data-api-pull-traffic-estimates-into-an-agent", "title": "Site traffic data API: pull traffic estimates into an agent", "summary": "Seogeoaeo.ai has exposed its Domain Overview traffic-estimate tool over both REST and MCP, letting agents such as Claude Code and Cursor request estimated monthly Google visits, ranking keyword counts and link metrics for any domain at 50 credits per run. The API accepts a bearer key prefixed `sga_`, supports 20 market codes, and offers `maxCredits` and `idempotencyKey` guardrails, with failed runs and runs returning no search data or links refunded; the smallest plan is $29 a month for 2,000 credits. The company cautions that visit figures model organic Google traffic only, excluding direct, social, email and AI referral visits, so agents should report relative size rather than visitor counts.", "body_md": "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.\n\nThis guide covers the call, the guardrails, and what the numbers can and cannot tell an agent.\n\n## What the endpoint returns\n\n[Domain Overview](https://seogeoaeo.ai/tools/domain-overview) answers one question per domain and Google market:\n\n- ranking keyword count, split by position band\n- estimated monthly visits from Google\n- the cost of those visits if bought as Google Ads clicks\n- paid keywords and estimated monthly ad spend\n- referring sites, a 0 to 1,000 link rank, average link spam score, nofollow share, broken links and the kinds of sites linking in\n\nIt costs 50 credits per run. Agent runs cost the same as runs in the browser.\n\n## REST call\n\nCreate a key at the [API keys page](https://seogeoaeo.ai/api-keys); keys start with `sga_`. Then:\n\n```\ncurl -X POST https://seogeoaeo.ai/api/v1/tools/domain-overview/runs \\\n  -H \"Authorization: Bearer $SEOGEOAEO_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\"input\":{\"url\":\"https://example.com\",\"market\":\"us\"},\"maxCredits\":50}'\n```\n\n`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.\n\n## MCP setup\n\nThe MCP server lives at `https://seogeoaeo.ai/api/mcp` and uses the same bearer key. In Claude Code:\n\n```\nclaude mcp add --transport http --scope user seogeoaeo https://seogeoaeo.ai/api/mcp --header \"Authorization: Bearer YOUR_API_KEY\"\n```\n\nEach 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.\n\n## Guardrails worth setting\n\n- **`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.\n- **`idempotencyKey`.** Retrying with the same key returns the original run instead of charging again. Use the domain plus the date as the key.\n- **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.\n\n## Looping over a list of domains\n\nA small batch job looks like this in plain steps:\n\n1. Read the domain list, including your own site.\n2. For each domain, call `domain-overview` with the same market and`maxCredits: 50` .\n3. Store estimated visits, top-three keyword count and link rank in one table.\n4. Divide each rival's visits by your own site's estimate, so the output is a relative size, not a raw count.\n\nTen domains cost 500 credits. The smallest plan on the [pricing page](https://seogeoaeo.ai/pricing) is $29 a month for 2,000 credits.\n\n## What an agent should not conclude\n\nThe 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.\n\nTell the agent so in its instructions. Useful rules:\n\n- Report estimates as relative size and trend, never as visitor counts.\n- Only compare domains measured by the same tool, same market, same day.\n- Flag sites with few ranking keywords but a strong link rank as \"possibly brand-led; traffic may sit outside search\".\n\n## Calibrating with your own data\n\nThe 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.\n\n## Getting the keywords behind the number\n\nDomain 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.\n\nIf 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.", "url": "https://wpnews.pro/news/site-traffic-data-api-pull-traffic-estimates-into-an-agent", "canonical_source": "https://usageatlas.com/guides/other/site-traffic-data-api-for-agents", "published_at": "2026-10-26 05:19:07+00:00", "updated_at": "2026-10-26 07:41:28.291743+00:00", "lang": "en", "topics": ["ai-agents", "ai-tools", "agent-protocols", "ai-search"], "entities": ["seogeoaeo.ai", "Domain Overview", "Claude Code", "Cursor"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/site-traffic-data-api-pull-traffic-estimates-into-an-agent", "markdown": "https://wpnews.pro/news/site-traffic-data-api-pull-traffic-estimates-into-an-agent.md", "text": "https://wpnews.pro/news/site-traffic-data-api-pull-traffic-estimates-into-an-agent.txt", "jsonld": "https://wpnews.pro/news/site-traffic-data-api-pull-traffic-estimates-into-an-agent.jsonld"}}