One key. One quota. Every API.
A month is a single pooled budget of weighted units, and every one of the 99 public operations draws on it. The per-1,000-unit rate is printed beside each plan so you never have to work it out yourself.
And you only pay for calls we actually ran: a request we reject before running it, a throttled call, an idempotent replay and a cache hit all cost zero units.
Start free. Scale when you ship.
One subscription, one shared quota across every API — SERP, social, dev data, finance, and more. Proxies are included at a flat, predictable price. See how that compares to Apify, Bright Data and ScraperAPI.
No card, no expiry, no overage
Everything you need to prototype and ship a side project.
- 1,000 weighted units / month
- Every public API through one key
- Usage analytics on every key (p50 / p95 / p99)
- Interactive playground + 8-language snippets
- Community support
USD 0.29 per 1,000 units
For a launched side project with real, growing usage.
- 100,000 weighted units / month
- 25 operations · 5 products
- 3 hosted functions
- 14-day free trial
USD 0.198 per 1,000 units
For teams running APIs in production with real traffic.
- 500,000 weighted units / month
- 100 operations · 25 products
- 15 hosted functions
- 300 requests / minute
USD 0.0998 per 1,000 units
High-volume workloads on one predictable bill.
- 5,000,000 weighted units / month
- 1,000 operations · 1,000 products
- Unlimited hosted functions
- 1,000 requests / minute
What a call costs
Your quota is measured in units, not requests, so heavy work is priced honestly instead of hidden behind a fair-use clause. Most calls spend 1; nothing spends more than 20.
- 1Most operationsA direct read: developer data, finance, news, weather, public profiles. More operations cost one unit than any other price.
- 2–6Parse & extractA real processing step on top of the fetch — PDF text, image OCR, page-to-Markdown, Reddit and Maps reads.
- 10Audio transcriptionGPU transcription, charged per call rather than per minute of audio.
- 15Social via residential IPsInstagram, TikTok and LinkedIn reads. The residential proxies they need are what make them costly.
- 20Browser renderingA real headless Chromium tab loading the page: screenshots and HTML-to-PDF.
The free tier is 1,000 weighted units a month — no card. In practice that is:
- 1,000developer, finance or weather reads
- 333web pages turned into clean Markdown
- 3,320Google Maps places
- 50full-page screenshots
Any mix of them, from one pooled budget — not four separate allowances.
Maps, priced per place
USD 29 of Starter buys 333,320 Google Maps places — about USD 0.087 per 1,000. A Maps search costs 6 units and returns up to 20 places, and we charge for the search, not for the rows. Fewer results still cost the same 6 units, so the figure is a ceiling on price, not a floor on volume.
Stated for Maps alone. Social reads run on residential IPs whose per-call bandwidth we have not measured yet, so they stay priced per call with no per-record claim attached.
Questions people actually ask.
What is a weighted unit?
A unit is what one call costs, and not every call costs the same. A plain read — developer data, finance, weather, a public profile — spends 1. The heaviest operations, a real headless browser rendering a page to an image or a PDF, spend 20. Every operation publishes its weight on its catalog page and in the OpenAPI document, so you can price a workload before you build it.
Do I need a credit card to start?
No. The Free tier is 1,000 weighted units a month, permanently, with no payment method on file. A card is only required if you start a 14-day trial on a paid tier, because a trial goes through checkout: the card is validated with a zero-amount authorisation and charged only when the trial converts.
How much does a free trial include?
A trial on a paid tier runs for 14 days and includes 10% of that tier's monthly units for the whole trial — 10,000 units on Starter. It ends when either limit is reached, whichever comes first, and an organization can trial once.
What happens when I run out of units?
Calls return 429 with the error code QUOTA_EXCEEDED, and the quota refills at the start of the next UTC month. There is no surprise overage charge: the ceiling is a hard stop rather than a spend alert that arrives after the money is gone. Every response also carries your remaining balance in a header, so you can see it coming.
Am I charged for calls that fail?
You only pay for calls we actually ran. A request we reject before running it — a missing required field, a malformed body, an unknown operation, a key we do not accept — costs zero units, and so does a throttled call, a retry replayed from an Idempotency-Key, and a response served from cache. The exception is an error the operation itself returns: reaching it means it ran, so that call is billed at its weight.
Is the quota per API or shared?
Shared. One key calls every public operation, and one monthly budget covers all of them, pooled across every key in your organization. There is no per-API subscription to hold and nothing to move between allowances when your traffic shifts from one source to another.
Are proxies charged separately?
No. Datacenter and residential egress are included in the unit price of the operations that need them, so there is no bandwidth meter and no per-GB line. You can supply your own exit IPs per call if you need consistency across a chain of requests.
What does it cost per 1,000 units?
USD 0.29 on Starter at USD 29 a month, falling on the higher tiers. The rate is printed beside every plan price so you never have to derive it, and it is computed from the same catalog the gateway meters against.
Can an AI agent use my key?
Yes. Operations are exposed as MCP tools. The hosted server authorizes over OAuth 2.1 with PKCE so no key is written to a config file, and serves every public operation; the published stdio server runs on your own machine with your own key and catches up in its next release. Tool calls are metered on exactly the same quota as an HTTP request.
How we compare, honestly.
One page per competitor, each written against their own published pricing — and each saying where they are the better choice.
- upAPI vs ApifyOne meter instead of seven, and a price you can read before the call.
- upAPI vs Bright DataProxy infrastructure you do not have to become a customer of.
- upAPI vs ScraperAPIA catalog of operations, not a credit balance against one endpoint.
- upAPI vs SerperKeep the price sensibility, lose the single-purpose ceiling.
- upAPI vs ApyHubThe same one-subscription idea, pointed at the expensive work.
- upAPI vs RapidAPIA catalog one team maintains, priced in one place.
- upAPI vs ScrapingBeeNamed operations with a published weight, not a credit meter on every page.
- upAPI vs FirecrawlNamed lookups on one key, for when you are not crawling a whole site.
- upAPI vs ScreenshotOneA screenshot as one call among several, not the whole product.
Ship your first call in under a minute.
Grab a free key, open the playground, and call any of 99 APIs through one gateway.