Comparison
Semrush API Pricing: Access, Units and Alternatives
Estimate Semrush API pricing with eligible plans, separate units, backlink report calculations and MCP access explained, plus alternatives for specific tasks.
By Abhi Bavishi, Updated , 11 min read
The dated Semrush Standard API reference describes an eligible paid subscription plus separately purchased API units. Confirm current access and purchase terms before budgeting. There is no reliable single “Semrush API price” to multiply by your request count. First establish which subscription unlocks the API, then price the units for the reports and rows you need. A general SEO subscription price is not proof of API entitlement.
Pricing reference: 17 October 2026. Vendor prices, access terms and usage rates below are previously recorded reference values, not freshly verified current offers. Confirm current plan eligibility and unit prices with Semrush's API access documentation and pricing page before purchasing. The workload calculations below are illustrative.
This guide covers direct Standard API budgeting first, then explains the different rules for Trends and MCP. For API design and feature assessment, read the Semrush API review. For the narrower backlink comparison, use RankParse vs Semrush.
Which access route are you buying?
“Semrush API” can mean several different products. Keep the entitlement and usage balance attached to the route you actually intend to use.
| Access route | What it provides | Access requirements | What to price separately |
|---|---|---|---|
| Standard API | Domain, keyword, backlink and project reports, depending on endpoint | Eligible subscription plus separately purchased API units | Subscription entitlement, report-unit rates and unit package |
| Trends API | Traffic and audience intelligence | Separate Trends access/product terms | Relevant Trends entitlement and usage |
| Official MCP server | Agent access to the tools enabled for the connected account | MCP-specific eligible plans and allowances | Included MCP units, renewal, extra units and AI-client/model costs |
The recorded Standard API access reference uses Business subscription wording. The pricing reference describes a newer lineup, with API integration on custom-priced Advanced/Enterprise offerings. A one-to-one mapping between those labels is not established.
That mismatch is a reason to ask Semrush which current SKU grants direct Standard API access. It is not a reason to attach the cheapest SEO plan's price to an API comparison. Before checkout, obtain confirmation that names the product, direct API entitlement, separate unit package and billing cadence.
Known versus quote-required budget worksheet
| Budget item | Previously recorded reference | What you still need |
|---|---|---|
| Standard API access | An eligible paid subscription is required | Current eligible SKU and subscription quote |
| Standard API usage | Units are purchased separately | Unit-pack price, size, validity and renewal terms |
| Backlink reports | Reference rates: 40 units per returned line for v3 and 45 for v4 | Confirm rate for your exact endpoint and fields |
| Historical organic keyword report | Example in access docs: 50 units per line, versus 10 live | Confirm report, date selection and current charging rules |
| Trends data | Its own access route | Trends quote and applicable limits |
| MCP allowance | Confirm independently of Standard API terms | Your current plan's eligibility, included usage, renewal and which tools can spend it |
A budget can be complete in units while still incomplete in dollars. Leave the dollar cell open until the unit quote is known. Also ask whether a package is shared with other integrations, so the balance you budget is actually available to this job.
Report type and API version change the meter
The Semrush developer documentation is the source for endpoint-specific pricing and limits. Do not apply a backlink rate to a keyword report or a historical-data rate to a live report.
| Report or API version | Charging basis, pricing reference above | Format and authentication | Integration constraint |
|---|---|---|---|
| Classic v3 backlink report | 40 units per returned line | Report-style text/CSV, API key in query | v3 backlink endpoints marked deprecated for new integrations |
| v4 backlink links | 45 units per returned line | JSON, Authorization: Apikey header | Select fields and confirm endpoint-specific result limits |
| Domain Organic Search Keywords, live | 10 units per returned line in the access-page example | Depends on report route | This rate belongs to this report, not all domain queries |
| Same keyword report, historical | 50 units per returned line in that example | Depends on report route | Historical selection can change the cost materially |
Set a result limit explicitly. A query that returns 100 rows and one that returns 1,000 rows do not have the same bill merely because each is one HTTP request. Check the chosen endpoint for maximum limits, filters, continuation support and error charging; row caps vary by report.
Worked backlink calculations
Assume 100 valid domains, successful responses, no retries and enough data for every requested row. The job asks for URL-level backlinks, not an authority score, traffic estimate or keyword report. These are conditional billing calculations using the reference rates, not measured outputs or evidence that vendors return identical links.
A bounded first sample: 100 rows per domain
100 domains × 100 returned rows = 10,000 rows
v3: 10,000 × 40 = 400,000 API units
v4: 10,000 × 45 = 450,000 API unitsThis small sample is a useful integration budget before requesting larger outputs. It still consumes units from a separate package for direct Standard API access.
A larger target: up to 1,000 rows per domain
100 domains × 1,000 returned rows = 100,000 rows
v3: 100,000 × 40 = 4,000,000 API units
v4: 100,000 × 45 = 4,500,000 API unitsThese totals assume the chosen endpoint and account support retrieving the target rows. If multiple requests are needed, use only documented continuation or non-overlapping query slices. We have not verified a complete-export procedure for every report version. If fewer rows are returned, recalculate the per-line charge from that output; add any other charge documented for the chosen report.
Do not multiply 4.5 million units by a price found in an undated third-party guide. The complete cash model is:
new access cost = eligible subscription + required unit-package purchase
job usage value = returned rows × applicable unit rate × quoted price per unitPackage sizes can make the purchase larger than the usage value. If you already hold an eligible subscription and enough uncommitted units, incremental cash outlay may be zero for this run, even though it consumes a paid balance.
The same requested row target on RankParse
For RankParse backlinks, assume one limit=1000, sort=recent call per domain with scoring disabled:
| Quantity | Calculation |
|---|---|
| Calls | 100 domains × 1 = 100 |
| Consumption | 100 × 2 = 200 credits |
| Usage value at base rate | 200 × $0.01 = $2 |
| With an unused welcome balance | 100 free credits cover 50 calls; 100 additional credits are needed |
| Example purchase | $10 buys 1,000 credits; after this job plus the welcome balance, 900 remain |
The $10 purchase is an example, not a claim about the minimum checkout. Other purchase sizes and larger-volume credit rates are described in credits and pricing. With score=true, each call costs 3 credits and this job consumes 300 credits.
The requested maximum is comparable; the datasets and resulting links are not identical. RankParse uses a periodic link-graph snapshot built from quarterly public-web releases. Check the active dataset date in the response-format documentation; do not assume a current-quarter release. sort=recent returns URL-level rows within that snapshot, not live discovery. Default importance-sorted output can contain aggregated referring-domain rows. The endpoint has a 1,000-row ceiling and no offset pagination, so it is unsuitable for an unrestricted complete-profile export.
MCP entitlements are a separate budget
Confirm current MCP eligibility, included usage, renewal and additional-unit terms through Semrush's developer documentation. Check which tools can spend each balance and whether Trends tools require separate data access. An MCP allowance does not establish direct Standard API access on the same terms.
A client or model subscription is another potential bill. Compare tool access, data usage and model costs separately. The SEO MCP pricing guide explains the full workflow budget.
Alternatives by the data you actually need
The cheapest provider for a backlink sample may not supply your traffic-intelligence or competitor-keyword workflow. The options below use the pricing reference above, with USD and billing cadence indicated. Check the linked official source before purchase.
| Task | Option and cost model | Limitation to resolve |
|---|---|---|
| Bounded backlink research and domain enrichment | RankParse pricing: prepaid credits, no subscription; $10 for 1,000 credits is an example purchase | Periodic link snapshot; no Semrush competitor keyword or traffic database |
| Keywords, SERPs and backlinks through separate API products | DataForSEO: reference $50 minimum top-up | Confirm any recurring or backlink-product fee and complete access cost; not equivalent Semrush reports |
| Broader SEO API coverage | SE Ranking Data API: pay-as-you-go wallet from $50, or an annual plan | Check endpoint charges and coverage before pricing the whole workflow |
| Moz Domain Authority and link data | Moz API: 50 free rows/month, then $20/month for 3,000 rows | Row allowances are monthly; proprietary DA is a different metric |
| Historic link research and Trust Flow | Majestic: full API plan $399.99/month, monthly billing | Link-focused data and its own unit system |
| Traffic and audience intelligence | Semrush Trends or another explicitly licensed traffic dataset | A backlink graph is not traffic analytics |
| Analytics for sites you control | Google Search Console, Bing/Yandex or Google Ads integrations, where authorized | Own-account data does not replace market-wide competitor intelligence |
Keep Semrush when its competitive keyword coverage, Trends data, historical reports or existing suite investment is the reason for the purchase. Compare alternatives when the actual requirement is a limited link or domain-data task. The Ahrefs API vs Semrush API comparison helps when the decision is between the two suites.
Before approving a budget
Record the current eligible subscription SKU, API product/version, reports, domains, rows and date ranges. Ask for a unit-package quote with its validity and renewal terms. Estimate retries and other consumers of the same balance. Then run a bounded sample and compare actual billed units and returned data with the worksheet before expanding.
If an example compares costs, require the same requested output size and distinguish an existing balance from a new purchase. If it compares capabilities, require the same question: a first-party Search Console report and a competitor-ranking report answer different questions even when both contain keywords.
FAQ
How much does Semrush API access cost?
The dated Standard API reference describes an eligible paid subscription plus separately purchased API units. A complete dollar price requires a current quote. Request the eligible SKU and package quote from Semrush rather than treating a general SEO plan price as the API price.
Does Business include units automatically?
The recorded Standard API access reference describes units as separately purchased. Confirm current direct API and MCP terms independently, including which route and balance your account has.
Is there a free Semrush API tier?
The referenced access options do not identify a general free Standard API tier. If your plan includes MCP units, that allowance does not establish free arbitrary API access.
Can I use RankParse instead of Semrush?
For supported backlink and domain-data tasks, evaluate it on a representative sample. RankParse does not reproduce Semrush's competitor keyword rankings, proprietary scores, traffic analytics or historical coverage.
What to build next
Choose one report and calculate its units before buying broad access. For a supported link-data sample, read the backlinks reference, review RankParse vs Semrush, and use the pricing page to distinguish consumed credits from a purchase. New accounts receive 100 free credits, enough for 50 ordinary backlink calls with scoring off.
Keep reading
Related posts
Comparison, 11 min read
Ahrefs API vs Semrush API: Pricing, Limits and Fit
Abhi Bavishi, Oct 18, 2026Comparison, 16 min read
Ahrefs vs Semrush for an AI-Assisted SEO Workflow
Abhi Bavishi, Oct 18, 2026Comparison, 12 min read
SEO MCP vs. browsing in Claude and ChatGPT: when to use each
Abhi Bavishi, Oct 18, 2026
Start free
Let your agent take the first pass.
100 free credits. No card. No seats.