REST API
Compatible raw SEO API v3 requests.
https://api.seoapikey.com
Getting started
One Client API Key gives you access to the supported Semrush SEO API v3 REST surface and a higher-level MCP research layer. Start with a header, not a key in the URL.
Compatible raw SEO API v3 requests.
https://api.seoapikey.com
Higher-level tools for research workflows.
https://mcp.seoapikey.com/v2/mcp
View the remaining API Units for a Client Key.
Check API UnitsREST API
Use https://api.seoapikey.com as the base URL. Send your Client API Key in the preferred request header:
X-Sem-Pool-Key: YOUR_API_KEY
Header authentication is recommended. Compatibility requests may use ?key=YOUR_API_KEY, but URLs are easier to expose in logs and browser history.
For existing Semrush SEO API v3 code, replace the official API host and key while retaining supported parameters such as type, domain, phrase, database, and display_limit.
curl -H "X-Sem-Pool-Key: YOUR_API_KEY" \
"https://api.seoapikey.com/?type=domain_rank&domain=example.com&database=us"
curl -H "X-Sem-Pool-Key: YOUR_API_KEY" \
"https://api.seoapikey.com/?type=domain_organic&domain=example.com&database=us&display_limit=10"
curl -H "X-Sem-Pool-Key: YOUR_API_KEY" \
"https://api.seoapikey.com/?type=phrase_organic&phrase=seo&database=us&display_limit=10"
curl -H "X-Sem-Pool-Key: YOUR_API_KEY" \
"https://api.seoapikey.com/analytics/v1/?type=backlinks_overview&target=example.com&target_type=root_domain"
MCP
MCP uses the same Client API Key and the same API Units balance as REST. It is a higher-level research layer over the REST Pool, not a one-tool-per-raw-report mirror.
https://mcp.seoapikey.com/v2/mcpAuthorization: Apikey YOUR_API_KEY{
"mcpServers": {
"seo_api_key": {
"url": "https://mcp.seoapikey.com/v2/mcp",
"headers": {
"Authorization": "Apikey YOUR_API_KEY"
}
}
}
}
Supported MCP categories include domain, keyword, organic, paid search, competitor, backlinks, and shopping research.
Check Balance
The key is sent only in a JSON POST body. It is not placed in the URL, stored, cached, or logged by this documentation flow.
smp_demo_example, smp_demo_zero, smp_demo_invalid, smp_demo_expired, smp_demo_failed, or smp_demo_unavailable.
Supported Features
61/61 raw SEO API v3 report types have a supported live path.
Domain Analytics, Keyword Analytics, Organic Research, and Paid Search / Ads.
Backlinks, Historical Ads, and competitor research.
Shopping Live Reports, Rank History, and supported daily result views.
display_dailyThe accepted value is exactly display_daily=1 for:
domain_rank_historysubdomain_rank_historysubfolder_rank_historyurl_rank_historydomain_organicsubdomain_organicsubfolder_organicRequests with blank, duplicate, zero, invalid, or other values are rejected.
Limitations
This service does not claim coverage for every Semrush product or parameter combination.
Unsupported or pricing-ambiguous requests may fail closed before upstream execution.
Security
Do not publish it, upload it to GitHub, commit it into source code, place it in frontend JavaScript, include it in screenshots, or share it with unrelated users.
Use environment variables, a secret manager, or a password manager.
Contact the administrator and disable or replace the Client Key.
Set a reasonable display_limit and check balance before large jobs.
Each Client Key has its own quota, remaining Units, and expiry. Charges reflect the executed report and actual service accounting.
Official Reference
Use the official Semrush SEO API v3 reference for report-specific parameters and response fields, then substitute this service's host and authentication method for supported requests.
Open the official Semrush SEO API v3 overview