Ahrefs API Pricing: Plans, Units and Real Costs

The dated Ahrefs reference lists API access from Lite at $129/month, with usage charged in API units. Its recorded request caps are 100 rows for Lite, 250 for Standard and 500 for Advanced; confirm current eligibility and limits before buying. The subscription price alone does not tell you what a job costs: you also need your direct API allowance, selected fields, returned rows and any extra-unit quote.

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 Ahrefs pricing and its API documentation before purchasing. Prices below are USD with the billing cadence shown; workload calculations are illustrative.

If you already pay for Ahrefs, the useful question is how much of your allowance a pipeline consumes. If you are buying access for the first time, include the subscription and the extra-unit purchase separately. This guide models both. For vendor selection, use the Ahrefs API alternatives comparison; for implementation differences, see RankParse vs Ahrefs.

What you pay for, by plan

Sources: Ahrefs pricing and subscription-plan help, using the pricing reference above.

The dated reference describes monthly API allowances on eligible plans. Do not use an Ahrefs Connect integration allowance as the direct API budget. Confirm the direct allowance for your plan in your account. A number labelled “integration units” on a plan page needs its own entitlement check.

The recorded terms describe a monthly reset for plan units and three billing months of validity for eligible additional pay-as-you-go API units. Confirm both terms for your account. That differs from RankParse's non-expiring credit balance. Also distinguish API rows from dashboard export rows: an export allowance is not a direct API allowance.

The referenced plans do not list a standalone API-only subscription. Starter and free accounts do not list general API access. The dated API reference describes free test queries against designated test targets, which help develop an integration but do not provide free arbitrary-domain research.

How an Ahrefs request consumes units

The previously recorded usage model has three parts. Confirm these rules for your endpoint in the Ahrefs API docs before using the calculations as a budget:

1. Each request has a 50-unit minimum.
2. Row cost is the sum of the billable field costs. Many fields cost 1 unit; some metrics cost 5 or 10.
3. Fields used for filtering or sorting can count even when omitted from the returned output.

For a row-returning request, the planning formula is:

request units = max(50, returned rows × total billable field cost per row)
job units = sum(request units for every billable request)

A one-row request whose fields sum to 5 units still costs 50 units. A full 100-row response with five 1-unit billable fields costs 500 units. Selecting fewer fields matters on the second request; on the first, the minimum dominates.

A row cap controls how much a request can return. It does not establish a complete export method. Before planning multiple pages, check that the specific endpoint supports a way to retrieve distinct result slices. Repeating the same capped request can return the same rows while spending more units.

Two illustrative workloads across 100 domains

The following worksheet is conditional arithmetic using those reference charging rules. These jobs were not executed. Assume 100 valid domains, successful calls, no retries, and enough source data for the requested output. The authority and backlink jobs are separate, not a bundle.

Workload A: one authority lookup per domain

Assume one individual Ahrefs Domain Rating lookup per domain and a total field cost below the 50-unit minimum. This deliberately models individual lookups, rather than assuming that a Batch Analysis endpoint has identical billing.

At RankParse's base rate, 100 credits have a $1 consumption value. A new account can consume the welcome credits without a purchase. An existing funded account spends from its balance; it does not receive another free allowance for this job.

These scores are different metrics. Ahrefs DR and RankParse's authority score use different data and calculations. Equal request counts make the billing comparison useful, but a score threshold of 50 cannot be migrated by keeping the same number.

Workload B: up to 1,000 backlink rows per domain

The target is 100,000 URL-level backlink rows across 100 domains. For Ahrefs, assume five 1-unit billable fields per row in total, including any charged filtering or sorting fields. Assume full result slices and an endpoint-supported way to obtain non-overlapping slices. If that retrieval method is unavailable, this is a capacity calculation, not a runnable export recipe.

Every modeled Ahrefs slice exceeds the 50-unit minimum. Larger request caps reduce the request count here; they do not reduce the row-and-field total. An extra expensive metric, paid filter field, retry or partially filled page changes the calculation.

RankParse's 200 credits have a $2 consumption value at $0.01/credit. With an unused 100-credit welcome balance, 100 additional credits are needed. Check current checkout terms for the purchase needed to cover those remaining credits. For a concrete purchase example, buying 1,000 credits for $10 leaves 900 credits after this job when the welcome balance is also applied. Money purchased and credits consumed are different quantities.

The RankParse charge stays 2 credits when a response contains fewer than 1,000 rows, including an empty result. Adding score=true raises it to 3 credits per call: this workload would then consume 300 credits. Neither API guarantees that every domain has 1,000 matching rows.

What the worksheet cannot tell you

It cannot convert Ahrefs units into dollars without the account's usable allowance and current additional-unit terms. Use:

extra units needed = max(0, job units - remaining direct API allowance)
new-customer cash outlay = subscription charge + required extra-unit purchase
existing-customer incremental outlay = required extra-unit purchase

An extra-unit pack may exceed the precise deficit. Include its purchase size and validity in your budget. Dividing the subscription by a guessed allowance produces an apparent per-call price that the evidence does not support.

When the Ahrefs subscription is justified

Ahrefs offers a continuously crawled proprietary link index, historical research and API coverage beyond backlink rows, including keyword and other suite data. Index updates do not guarantee when any particular new or lost link will be discovered.

Keep Ahrefs when recent-link discovery, proprietary DR, historical continuity or the wider suite is central to the work. An existing subscription also changes the economics: compare additional units against the cost of another provider, rather than charging the entire subscription to one small script.

RankParse is worth evaluating for bounded backlink research and domain enrichment when a periodic link-graph snapshot meets the requirement. The graph is built from quarterly public-web releases; check the active dataset date rather than assuming a current-quarter release. Its data page and response-format documentation explain the freshness trade-off. It does not provide Ahrefs DR, a matching index, complete backlink exports beyond its result limit, or a market-wide competitor keyword database.

Try the supported output before migrating

This SDK example shows a request shape; it is not a recorded test result:

import os
from rankparse import RankParseClient

with RankParseClient(api_key=os.environ["RANKPARSE_API_KEY"]) as client:
    result = client.backlinks("stripe.com", limit=1000, sort="recent")

print(result["total"])  # rows returned, not the domain's complete link count
backlinks = result["data"]

sort="recent" returns URL-level rows from the stored snapshot. It does not make the data live. With the default importance sort, some responses can contain aggregated referring-domain rows. There is no offset pagination on this endpoint. Check the backlinks response contract before deciding that the output meets your application's needs.

FAQ

Is the Ahrefs API free?

The dated reference lists general API access on eligible paid subscriptions from Lite, with free queries limited to designated test targets. Confirm current access terms; a test facility does not establish a general free API tier.

Are API units the same as Ahrefs dashboard credits?

Do not assume they are interchangeable. Direct API usage, Ahrefs Connect integrations and dashboard/export allowances have different labels and limits. Budget against the direct API allowance shown for your account.

Can I buy extra Ahrefs API units?

The recorded terms describe additional pay-as-you-go units for eligible usage with three billing months of validity. Confirm current eligibility, price, pack size and renewal behavior in your account before relying on them.

Does MCP avoid the API subscription and row limits?

Confirm current MCP eligibility, row caps, included usage and renewal separately from direct API access. A different connection protocol does not establish a separate free data allowance. Check the official entitlement and see our SEO MCP comparison.

Are 100 RankParse credits enough for 100 backlink requests?

No. They cover 100 successful 1-credit authority lookups, 50 ordinary 2-credit backlink calls, or 33 scored 3-credit calls with 1 credit left. Other endpoints have their own charges.

What to build next

Write down your domain count, output rows, required fields and acceptable data age before choosing a provider. Compare the resulting budget with the alternatives worksheet, then test a small representative domain set through backlinks or domain authority. The pricing page shows RankParse's purchase options; sign up for 100 free credits if the documented scope fits.