$0.001 per credit. No subscriptions.
Top up whenever you want — your first top-up includes a one-time 2,000-credit bonus. Operation minimums are generated from the OpenAPI billing contract.
Most records cost one credit; higher-cost operations publish their minimum credits in the API catalog and machine-readable pricing page.
- One-time 2,000-credit bonus on your first top-up
- Access to live APIs, Skills and MCP
- MCP server included
- Community support
- Most records are 1 credit each
- Higher-cost operations publish their credit minimum
- Reuse your Claude or Codex plan — no separate LLM key
- Top up credits whenever you want
- Unlimited projects and API keys
- Auto top-up when your balance runs low
- Email support, usage dashboard, invoicing
- Volume discount on the per-record rate
- Uptime SLA and dedicated support
- SSO, audit logs, custom retention
- Invoicing, MSA, security review
Tips: reading the price tag
- Most public-data records are 1 credit ($0.001) — you pay only for the records a call returns.
- Each API page shows its exact per-record rate and minimum charge. Live ChatGPT/Gemini answers cost $0.03 per response; indexed mention search costs $0.01 per record with a $1.00 minimum. Other operations have their own rates.
- A call that returns fewer records than the minimum is floored to it; records above the minimum still bill 1 credit ($0.001) each.
- Credits go a long way: every $1 is 1,000 credits — 1,000 record-priced reads ($0.001 each), 100 calls at $0.01, 20 at $0.05, or 2 at $0.50 — and your first top-up adds a one-time 2,000-credit bonus on top.
Operation credit minimums
Generated from the OpenAPI `x-unifapi-billing` contract. When route metadata changes, this table changes with the API catalog.
| Tier | Minimum | Unit | Catalog coverage |
|---|---|---|---|
Free Zero-credit endpoints that still return billing metadata. | 0 credits | Free | 10 operations /email/check, /email/check/batch, /email/domains/{domain} |
Standard Standard public-data reads with a one-record floor. | 1 credit ($0.001) | 1 credit per billable record | 108 operations /instagram/explore/sections/{id}/posts, /instagram/locations/cities/{cityId}/places, /instagram/locations/countries/{countryCode}/cities |
Lookup Instagram profile, post, and ID lookups with a small per-call floor. | 3 credits ($0.003) | 1 credit per billable record | 9 operations /instagram/posts/{shortcode}, /instagram/resolve/media-id, /instagram/resolve/shortcode-from-media |
Search Search-style tasks and per-request provider reads, such as SERP and most Instagram endpoints, with a low per-call floor. | 10 credits ($0.01) | 1 credit per billable record | 31 operations /browser/html, /browser/links, /browser/markdown |
30 credits minimum Operation-specific pricing generated from the OpenAPI billing extension. | 30 credits ($0.03) | 30 credits per billable record | 1 operations /geo/answers |
Analytics Analytical provider-backed tasks with higher upstream task costs. | 50 credits ($0.05) | 1 credit per billable record | 38 operations /geo/keywords/search-volume, /seo/backlinks/anchors, /seo/backlinks/bulk-backlinks |
Premium Premium LLM-mentions and historical SEO tasks with expensive upstream calls. | 500 credits ($0.50) | 1 credit per billable record | 7 operations /geo/mentions/aggregated-metrics, /geo/mentions/cross-aggregated-metrics, /geo/mentions/history |
1,000 credits minimum Operation-specific pricing generated from the OpenAPI billing extension. | 1,000 credits ($1.00) | 10 credits per billable record | 3 operations /geo/mentions/delta, /geo/mentions/new-lost, /geo/mentions/search |
Starter
Pay-as-you-go
Enterprise
Catalog access
Limits & scale
Support
Security & compliance
FAQs
Everything we get asked about billing, limits, and how UnifAPI handles public data.
Billing
$0.001 per credit, with operation minimums generated from the OpenAPI billing contract. Most public-data records are 1 credit, while higher-cost provider-backed operations publish their minimum credits on API pages and /pricing.md. You top up a balance whenever you want — there's no monthly subscription or hard request cap.
A record is one item returned by an API — a tweet, a video, a profile, a post, a comment, or a channel. A call that returns 50 public posts is 50 records.
Empty successful results can still bill the operation minimum, because provider work may be paid for whether or not anything matches. Check the endpoint's OpenAPI billing metadata before running expensive operations. If a request fails on our side (4xx or 5xx returned by us), it isn't charged.
Signing up is free and gives you the dashboard, API keys, Skills pages, and the MCP server. Live API calls spend workspace credits — top up a prepaid balance to run them, and your first top-up includes a one-time 2,000-credit bonus.
No. Topped-up pay-as-you-go balance stays on your account — it doesn't expire as long as the account is active — and the one-time first top-up bonus behaves the same way.
No. Credit purchases are final and non-refundable, whether the Credits are unused, partially used, or fully used. Bonus and promotional Credits have no cash value. Exceptions apply only where required by law or expressly agreed in a signed Enterprise agreement.
Limits
There's a soft concurrency limit per project to protect public-data sources, but no monthly record cap. You won't get cut off because you 'used too many records' — you just pay for the ones you pull.
On many API marketplaces you pick a fixed monthly tier per API, with a hard request cap and separate billing. UnifAPI gives your agent one public-data layer, one bill, and pay-per-record usage. Skills also reduce the integration work because the agent gets task framing, MCP access, and expected output shape.
Yes. Pay-as-you-go and Enterprise both serve production traffic. Enterprise adds an uptime SLA, priority support, and procurement-friendly contracts.
Security
Every API serves public data — content that's accessible without logging into an account. We do not handle OAuth into your accounts or your end-users' accounts. If you need that, look at a connector platform.
Public data has different legal postures depending on jurisdiction and platform. We provide the technical access; you're responsible for downstream use. See our acceptable use policy for the rules of the road.
Keys are scoped per project, can be rotated at any time, and never appear in logs. Traffic is encrypted in transit. Enterprise customers can request custom retention, audit logs, and SSO.