How avesapi.com Is Priced and Which Plan Fits Your Request Volume
Updated
avesapi.com uses a pay-per-request model rather than a recurring subscription. Every request returns a live result and costs 1 credit, so the plan you choose is simply a prepaid block of requests. Based on the published pricing, there are four tiers: a free test tier with 1K requests, Starter at $50 for 25K requests, Premium at $125 for 100K requests, and Professional at $500 for 500K requests. All tiers include GEO-targeted search and JSON or HTML export. If your volume exceeds the Professional tier, the site directs you to its pricing page for larger search limits.
The pricing model in plain terms
The key mechanic is that you are not buying a monthly subscription — you are buying a pool of requests. The site states it uses pay-per-request pricing and that you "only pay upon successful requests," which means failed requests are not billed. There is no monthly recurrence, so credits do not expire on a subscription clock in the way a SaaS plan would.
Two consequences follow from this:
- Cost scales linearly with volume. At the published tiers, the effective cost per request drops as you buy larger blocks (see the table below).
- You are not locked into a renewal. If you run a burst of rank-tracking jobs and then go quiet, you are not paying for idle months.
The site also notes it "currently doesn't support priorities" — every request is treated the same and returns a real-time result. There is no premium queue to buy into.
Plan comparison
| Plan | Price | Requests included | Effective cost per request | Best for |
|---|---|---|---|---|
| Free Test | $0 | 1K | — | Evaluating output format and accuracy before committing |
| Starter | $50 | 25K | ~$0.002 | Small rank trackers, side projects, low-frequency keyword sets |
| Premium | $125 | 100K | ~$0.00125 | Growing SEO tools with regular daily tracking |
| Professional | $500 | 500K | ~$0.001 | High-volume platforms tracking large keyword sets frequently |
| Custom | Not published | Above 500K | Contact required | Enterprise-scale or bulk search needs |
All four published tiers list the same feature set: GEO-targeted search, JSON or HTML export, and always-live results. The only variable is request volume, so the decision is purely about how many requests you will consume.
Estimating your request volume
Because pricing is per request, the practical question is how many requests your workflow generates. A few common patterns:
- Rank tracking: one request per keyword per location per device per check. Tracking 500 keywords daily across one country and one device is roughly 500 requests/day, or about 15K/month — comfortably inside Starter.
- Multi-location tracking: the same 500 keywords across 10 cities is 5,000 requests/day, or ~150K/month — that pushes you into Premium.
- SEO tool with end users: if each user triggers searches on demand, volume can spike unpredictably. The pay-per-request model handles this without a plan upgrade, but you should size your credit purchase to your peak month, not your average.
The site supports geo-specific requests via UULE, country, and/or city parameters, so each location variant counts as its own request. Factor that multiplier in before picking a tier.
Choosing between tiers
- Pick Free Test first if you have not yet validated that the JSON or HTML output fits your pipeline. It costs nothing and answers the format question directly.
- Pick Starter if your monthly volume is under ~25K requests — typical for a single-site rank tracker or an early-stage tool.
- Pick Premium if you track multiple locations or run a tool with a modest active user base, landing in the 25K–100K range.
- Pick Professional if you are running a production SEO platform with large keyword sets or frequent refresh intervals, up to 500K requests.
- Ask for custom pricing if you expect to exceed 500K requests, since the published tiers stop there.
What the pricing does not tell you
The published page does not specify credit expiry, refund terms, or whether unused requests roll over. It also does not list payment platforms. Before buying a large block, confirm these details directly — particularly expiry, since a 500K-request purchase is only economical if you can consume it within whatever window applies.
The site does state that you only pay for successful requests, which is the most useful cost-control guarantee on the page: if a scrape fails, it should not consume a credit.