Semrush API Pricing: What API Access Costs and What the Units Add

Short answer: Semrush API access starts at $549 a month, and that $549 buys you zero API units. Standard API access sits on the top subscription tier, and Semrush's own developer documentation is unusually direct about what happens next: after you upgrade, your unit balance is still zero, and you have to buy a unit package separately. Semrush publishes no dollar price for those packages anywhere. So the honest budget for a Semrush API project is a $549 a month floor plus a quoted data fee, and any article giving you a firm cost per unit is quoting somebody else's negotiated rate.

That is a frustrating answer if you are trying to scope a build this week, so the rest of this guide covers what is still knowable: which plan actually unlocks access (the documentation and the pricing page disagree, and that matters), how the unit model works mechanically, where the cost really goes, and what to put in the email to sales so you get a usable number on the first call. If you are pricing the subscription rather than the API, the full ladder is broken down on our Semrush pricing page.

How much does the Semrush API cost?

There are two numbers, and only one of them is published. The subscription floor is public: the Advanced plan is $549 a month, or $455.67 a month if you pay for a year up front, and it is the tier the pricing page marks with API integration. The second number, the price of the API units themselves, is not published. Not on the pricing page, not in the developer docs, not in the knowledge base. You buy a unit package from inside your account or you talk to sales.

Treat the units line the way you would treat any metered cloud bill you have not benchmarked. Until you have measured your own consumption against real endpoints, you do not have a budget, you have a hope.

Which Semrush plan do you need for API access?

This is where it gets confusing, and it is worth knowing before you get on a call. Semrush's developer documentation states that Standard API access is available to SEO Toolkit users who hold a Business subscription. But Business is one of the tiers Semrush retired when it repackaged its plans, and it does not appear on the current pricing page at all. What the live pricing page shows instead is the Advanced plan at $549 carrying API integration.

In practice that means the docs are describing the old plan structure and the pricing page is describing the new one. The safe reading, and the one to confirm in writing with your account manager, is that the top SEO Toolkit tier is the API tier. Do not let a support article naming a plan that no longer exists convince you that you are on the wrong subscription, and do not assume a mid tier will work because a blog post from two years ago said Guru was enough. If your contract depends on it, get the current tier name in the order form.

Why your API unit balance is zero after you upgrade

The single most common surprise with the Semrush API is not the price, it is the sequencing. Semrush's documentation says it plainly: after upgrading to the plan that permits API access, the number of units will still be zero. Access and consumption are sold separately. The subscription buys you the right to make calls. The unit package buys you the calls.

The practical consequence is that a team can complete procurement, get the credentials, write the integration, and then watch the first production run fail on an empty balance, because nobody in the chain realized there was a second purchase. If you are the one scoping the work, put the unit package on the same requisition as the subscription. It removes a week of internal ping pong that happens after the engineering is already done.

How Semrush API units get consumed

Units are not requests. Each API request consumes a number of units that depends on the endpoint you called and, in some cases, on your plan. Simple lookups are cheap. The queries most people actually want, historical data across a long date range, large keyword sets, competitor backlink pulls, are the expensive ones, and they are expensive per line returned rather than per call. A single well-formed query asking for a big result set can cost hundreds of times what a spot check costs.

Three habits keep the burn predictable:

• Request only the columns you use. Wide responses cost more and most pipelines throw away half the fields before they land in a table.
• Cache aggressively and refresh on a schedule that matches how fast the data actually changes. Backlink profiles do not move hourly. Pulling them hourly is a pure unit tax.
• Instrument the balance. Read your unit balance as part of the job and alert before it hits zero, not after. A scheduled pull that silently returns nothing looks identical to a genuinely flat month in a dashboard, which is exactly why teams that depend on external data feeds put freshness and volume monitoring on the tables those pulls write into rather than trusting the job's exit code.

Standard API or Trends API?

They are different products with different commercial models, and picking the wrong one is a common and expensive mistake.

The Standard API is the SEO data set: organic and paid keyword positions, domain analytics, backlinks. It requires the top SEO Toolkit tier and a purchased unit package.

The Trends API is the market and traffic analytics data set, and it is sold in two tiers. Trends API Basic can be bought directly, and it comes with a default monthly limit rate of 10,000 requests. Trends API Premium is a sales conversation. If what you need is traffic and market share estimates rather than keyword rankings, Trends is the cheaper and simpler path, and you do not necessarily need the $549 SEO tier to get it.

There is also a third option that did not exist a couple of years ago. Semrush ships MCP access from the $199 Starter plan up, which lets an AI workflow query Semrush data directly. It is not a replacement for a metered production API, and you should not build a customer facing product on it. For internal research automation, it may be all you needed, at a third of the price.

What to ask before you commit

Because the unit price is negotiated, the quality of your first email decides your rate. Come with numbers rather than questions:

• The specific endpoints you will call, and the expected rows per call.
• Your monthly call volume at steady state, and at peak.
• Whether you need historical ranges, which are the heaviest queries in the catalog.
• Whether the data is internal or shown to your own customers. Redistribution usually changes the terms, and finding that out after launch is the worst possible time.
• What happens when you exhaust a package mid month: does it fail, throttle, or auto top up?

Ask for the overage behavior in writing. That one line protects you from the failure mode where a reporting job quietly stops updating on the 22nd of every month.

Is the Semrush API worth it?

It depends entirely on whether you are building or reporting.

If you are building a product feature on top of SEO data, or a client dashboard that has to refresh without a human, the API is the only real option and $549 a month is a reasonable floor for a data source of that depth. Budget the units generously in year one, because your first consumption estimate will be wrong.

If you are pulling data so that somebody can look at a chart once a week, you are probably about to spend $549 a month plus units and a month of engineering to replace an export button. The in-app reports on a $139 or $299 plan cover more reporting needs than most teams admit, and Semrush is not the only vendor at this price point: our Ahrefs vs Semrush comparison covers where each one is genuinely stronger, and the Ahrefs API pricing breakdown is worth reading alongside this one, because Ahrefs stopped publishing its API prices entirely and the budgeting approach has to be different.

And if the reason you wanted API access was to feed a content pipeline, keyword in, article out, that is a different purchase altogether. You do not need a metered data API to publish consistently. You need something that does the research and the writing and the scheduling, which is a category that costs a fraction of $549 and does not bill per query. For the full picture on what the various tools in this space charge, see our SEO software pricing comparison, or the plan by plan Semrush pricing guide if you are still deciding on the subscription itself.

Semrush API pricing questions

How much does the Semrush API cost per unit? Semrush does not publish a per unit price. Units are sold in packages purchased from your account or through sales, and the rate is not listed on the pricing page, in the developer documentation or in the knowledge base. Any specific per unit figure you find online is either historical or someone's negotiated rate.

Is the Semrush API included in my plan? No. API access is tied to the top SEO Toolkit tier, currently the $549 Advanced plan, and even then your unit balance starts at zero. The subscription grants permission to call the API. Units are a separate purchase.

Is there a free Semrush API? There is no free tier of the Standard API. The 7 day trial covers the application, not a production API allowance, and the limited free account is capped at 10 reports a day in the interface. If you need to evaluate response shapes before you buy, build against the documented schemas with mock data.

What is the cheapest way to get Semrush data programmatically? If you need traffic and market estimates, Trends API Basic is purchasable directly and carries a default limit of 10,000 requests a month. If you need SEO data inside an AI workflow rather than a production service, MCP access from the $199 Starter plan is far cheaper than the $549 API tier. Only go to the Standard API when you genuinely need metered, high volume, machine to machine access.

All prices and plan requirements here were read from semrush.com/pricing, the Semrush knowledge base and developer.semrush.com on 30 August 2026. Semrush repackages its plans periodically, so confirm the current tier name on the order form before you sign.