Loading
Loading
Not sure which plan to pick? Use the Pricing Calculator to find the right plan for your usage, or learn how the calculator works before you buy.
Best suited for anyone who needs a one-time credit top-up.
Best suited for anyone who wants the lowest cost per credit.
Best suited for anyone who wants flexible, month-to-month access.
For small teams getting started with shared billing.
For large teams that need custom scale and support.
Cards are accepted at checkout, along with these wallets and local methods where they are available.
Find the right API plan in seconds
Enter your monthly API request volume across any endpoint - get an instant plan recommendation with exact cost per 1,000 requests on every tier.
A credit is what an API request costs. Credits come as One-Off Credits or Subscription Credits. The amount deducted per request varies by API: some cost more, some cost less.
You can see that amount in the X-AF-Credits-Cost response header. On asynchronous APIs it may not be the final cost, because the work finishes after the first response. Exact costs are on the Pricing Calculator.
One-Off Credits are a one-time purchase. They stay in the account until they are used: they do not expire, there is no deadline, and unused One-Off Credits carry over. Subscription Credits are recurring, billed monthly or yearly. On both monthly and yearly billing, Subscription Credits reset every month; unused Subscription Credits do not carry over.
| Feature | One-Off Credits | Subscription Credits |
|---|---|---|
| How you buy | One-Off CreditsOnce | Subscription CreditsRecurring, monthly or yearly |
| Credits | One-Off CreditsStay until used; no expiry; unused credits carry over | Subscription CreditsReset every month; unused credits do not carry over |
| Extra credits if you run out | One-Off CreditsNot available | Subscription CreditsSurcharge, if the plan includes it |
No. APIFreaks is one plan, one bill, every API. Nothing is gated. The same credits work across every API and every feature. That is true on every plan, including the free One-Off Credits that come with a new account.
If Subscription Credits run out mid-plan, upgrade the Subscription Credits plan from the account dashboard, either manually or by enabling Auto Upgrade so the plan upgrades automatically when usage hits the threshold set for credits used on the current plan.
On plans that include Surcharge, it could be left enabled so extra credits keep requests going. Those extra credits are billed at the end of the cycle. That extra cost is a cue to move to a larger plan, not a reason to stay on the current one.
A mid-cycle upgrade or downgrade is prorated. The remaining charge depends on how far the cycle has already run and how many Subscription Credits have already been used. On a downgrade, unused value is applied to the next plan rather than refunded.
From the account dashboard, go to the Subscription Credits card and click Cancel. Then choose Deactivate At Next Period or Deactivate Now.
Deactivate At Next Period keeps the subscription active through the billing cycle already paid for. Requests keep running until that cycle ends, with no further charges. It can be resumed from the dashboard before the cycle ends.
Deactivate Now ends the subscription immediately. Remaining Subscription Credits on that plan stop at that point, with no further charges.
An Organization is shared billing. All members in the Organization share one credit pool and one bill. One-Off Credits and Subscription Credits are bought for the Organization, not for each member. The Organization fee is separate from the credit plan the Organization uses.
Both can be used on the same account. Subscription Credits are used first. Once those run out, One-Off Credits are used next.
The account dashboard shows your balance. You can also check it from your own code with the Credits Usage API.
Credits used for a request are restored when the API returns an error status (4xx or 5xx). A request that is withdrawn after it has already been issued keeps those credits applied, because the call was already accepted.
Surcharge is extra credits used after Subscription Credits run out, on plans that include it. It is enabled by default, and can be disabled. The rate and cap depend on the plan. Usage is billed separately on the next renewal. Using Surcharge is a cue that the current plan no longer covers typical usage; the intended next step is to upgrade, manually or with Auto Upgrade.
Auto Upgrade moves you to a larger plan automatically when your credits usage hits a threshold you choose. It is disabled by default.
You can pick one of these options:
Subscription Credits options (80%, 90%, 100%) upgrade the plan while you still have Subscription Credits left. Surcharge-credit options (50%, 70%, 80%, 90%) wait until surcharge has already started, then upgrade once that share of the surcharge pool is used.
No. Both only apply to Subscription Credits. With One-Off Credits, once they are gone, you can buy more whenever you want.
When you need to look up many items at once. One bulk call replaces a long sequence of single requests, so your code opens fewer network connections and spends less time waiting on round trips. Credits are still counted per item.
Bulk endpoints use the same credits as calling each item on its own. Credits are counted per item, not per request. If one domain check costs 18 credits, ten domains cost 180 credits whether you send ten calls or one bulk call.
Credits apply only to items that return a successful result. If you check 50 domains and 3 come back invalid, credits are used for the 47 that succeeded.
Concurrency is how many requests can run at the same time. Only a handful of APIs have a concurrency limit; the rest do not. The plan sets that number on:
See the Concurrency Limits page for what each plan allows.
The extra requests are rejected. Requests within the concurrency limit go through; anything beyond it returns an error. Most APIs are not capped this way. It applies only here:
See the Concurrency Limits page for what each plan allows.
See the Organization & Teams page for roles, seats, permissions, and how shared billing works.