Ahrefs API Review (2026): Units, Row Caps, and Who It's Actually For

This is a review of the Ahrefs API from the perspective of the person who actually calls it: a developer with a pipeline, an agent, or a product that needs link data. Not a review of the Ahrefs suite — the dashboard is excellent and this post takes that as given. The question here is narrower: is the API a good way to buy SEO data programmatically in 2026?

Short version: the data is the best in its class, the developer experience is decent, and the commercial model is built for people who already pay for Ahrefs — not for people who just want the data. Everything below is as of September 2026, checked against Ahrefs' developer docs and current third-party writeups; where sources conflict, we say so.

What the API actually is

Ahrefs API v3 (launched late 2025, replacing v2) is a REST API over the same data the suite shows: Site Explorer (backlinks, referring domains, anchors, top pages), Keywords Explorer, Site Audit, Rank Tracker, SERP Overview, Batch Analysis (up to 100 targets per request), and the newer Brand Radar endpoints for AI-answer visibility. Responses are JSON, auth is a header token, there's an OpenAPI-compatible spec, and registered apps can send free test requests from staging without burning units. That last touch is genuinely developer-friendly and rarer than it should be.

The default rate limit is 60 requests per minute, with dynamic throttling (429s) at peak load.

The unit system, explained honestly

Every request burns "units," and the math has three parts:

1. A 50-unit minimum per request — even a request that returns one row.
2. Per-row, per-field pricing: the cost of a row is the sum of the costs of each field you select — most fields cost 1 unit, some metrics 5 or 10. Fields used in where and order_by count too, even if you don't return them.
3. The request costs the greater of the two: 50 units, or rows × field cost.

So a 1,000-row backlink pull with five 1-unit fields is ~5,000 units. This is a perfectly coherent system — and it means you cannot quote a job's cost without knowing every field you'll touch. Third-party math puts a typical 1,000-backlink retrieval at roughly $5.00 in plan-unit value, with overage pricing reported around $0.35–$1.00 per 1,000 rows.

The allowance problem

Here's the part we'd fix first if we ran Ahrefs' pricing page: how many units a plan includes is genuinely hard to pin down. Across Ahrefs' own pages and 2026 third-party guides, we found Lite variously reported at 10,000, 25,000, and 100,000 units/month, and per-request row caps reported as 10 rows on Lite in some writeups and 100 in others. We're not going to print a table we can't verify — the takeaway is that the vendor's own materials have contradicted each other, and buyers notice. Check your account's actual allowance before you budget anything.

What access costs

• No API-only product. API v3 comes with suite plans from Lite at $129/mo ($108/mo annual). The $29 Starter plan and the free tier have no API.
• No free API tier, no API trial.
• Enterprise is $1,499/mo, billed annually only, for the biggest allowances.
• Units are shared across API v3, Ahrefs Connect apps, and the Ahrefs MCP server — one meter for all programmatic access.

What's genuinely good

• The index. ~35 trillion links claimed, continuously crawled. If a link went live this week, Ahrefs is the API most likely to have it. Nothing else in this review's scope beats it on freshness or long-tail coverage.
• Endpoint breadth in one coherent API: links, keywords, SERPs, audits, rank tracking — one auth, one style.
• Real developer touches: OpenAPI spec, free staging test calls, a request builder, consistent JSON.
• Batch Analysis at up to 100 targets per request is well-shaped for scoring jobs.

What's genuinely bad

• The plan gate. You pay $129/mo minimum for a suite whether or not anyone opens the dashboard. For a pure API consumer, that's rent on software you don't use.
• Unit opacity. Minimums, per-field multipliers, and inconsistently-documented allowances make cost forecasting a spreadsheet project. This is the #1 complaint in developer writeups, and we reproduce it: budgeting this API is harder than integrating it.
• The per-row bill. At ~$5.00 per 1,000 backlinks in unit value, batch workloads get expensive fast. Scoring a 500-domain prospect list at 1,000 rows each is ~$2,500 in unit value — more than most competitors charge per month. We ran that comparison in detail in Ahrefs API alternatives.
• Row caps per request on lower plans mean pagination overhead — and every page re-pays the field costs.

Who should buy it

Be honest with yourself about which of these you are:

• Your team already pays for Lite or above. Then the API units are a sunk-cost bonus and this review's economics mostly don't apply. Use them.
• Your product's value depends on link freshness — link monitoring, digital PR reporting, "who linked to us this week." Ahrefs is the right tool and worth the money.
• You need maximum long-tail coverage for deep competitive research on obscure domains.

Who shouldn't

If your workload is batch scoring, lead enrichment, audits, agent tool calls, or anything where "the link graph as of the last quarter" answers the question, you're paying a continuous-crawl premium to read stored-data-shaped questions. That's the workload RankParse was built for: backlinks at 2 credits per call ($0.012–$0.02 for up to 1,000 rows), domain authority at 1 credit, flat published prices, no subscription, credits that never expire, and 100 free credits with no card. The tradeoff is symmetrical: RankParse's index rebuilds from quarterly open-data releases (Common Crawl and friends), so it will not show you yesterday's link. Full head-to-head: RankParse vs Ahrefs.

If you're mid-migration, the full cost teardown and the export guide cover the practical steps.

Verdict

Data: excellent. Developer experience: good. Commercial model: built for existing subscribers. As a data product bought on its own merits, the Ahrefs API is a premium freshness engine behind a subscription gate and a unit meter that resists budgeting. Buy it for the index. Don't buy it for the pricing.

FAQ

Is there a free Ahrefs API tier?

No. There's no free tier and no API trial. The cheapest access is the Lite plan at $129/mo ($108/mo annual); the $29 Starter plan has no API.

How much does an Ahrefs API call cost?

Every request costs at least 50 units; row-returning requests cost rows × the summed per-field cost (most fields 1 unit, some metrics 5–10). Third-party math works out to roughly $5.00 per 1,000 backlinks in plan-unit value.

How many API units does each Ahrefs plan include?

Reports conflict — we found Lite quoted at 10K, 25K, and 100K units/month across Ahrefs' materials and third-party guides in 2026. Check the allowance shown in your own account before budgeting.

Does Ahrefs have an MCP server for AI agents?

Yes — an official remote MCP server, available on paid plans from Lite up. It draws from the same shared unit pool as the API. There's no free MCP tier; we compared the options in best SEO API for AI agents.

What's the best Ahrefs API alternative?

Depends on the workload: DataForSEO for the cheapest raw live-index rows at volume, RankParse for pay-per-call link and domain data with no subscription (100 free credits), Moz for simple DA metering. We compared seven options with real 2026 pricing in Ahrefs API alternatives.

---

Want the batch-workload economics instead of the subscription? Get a free RankParse API key — 100 credits, no card — and see the pricing math for yourself.