Question 1

How does pay-as-you-go billing work?

Accepted Answer

Every API call costs a fixed number of credits, set per endpoint. You top up a credit balance whenever you want — there's no monthly subscription, no minimum spend, and no hard request cap. When your balance runs low you can configure auto top-up, or simply add credits manually.

Question 2

What's in the Free tier?

Accepted Answer

A monthly credit grant that refreshes on the same date every cycle. No card is required and you get access to every API in the catalog plus the MCP server. It's a real tier, not a 14-day trial.

Question 3

Why credits instead of dollars per call?

Accepted Answer

Credits decouple pricing from individual endpoint costs. Some endpoints are cheap to serve, others are expensive — credits let us price each one fairly without forcing you to think about it. Each endpoint's credit cost is listed in the catalog.

Question 4

Do unused credits expire?

Accepted Answer

Free-tier credits refresh monthly and do not roll over. Topped-up credits on the Pay-as-you-go plan stay on your balance — they don't expire as long as the account is active.

Question 5

Can I get a refund?

Accepted Answer

Unused topped-up credits can be refunded within 30 days of purchase. Reach out to support and we'll handle it.

Question 6

Are there rate limits?

Accepted Answer

There's a soft concurrency limit per project to protect upstream sources, but no monthly request cap. You won't get cut off because you 'used too many calls' — you just pay for the ones you make.

Question 7

How does this compare to subscribing on RapidAPI?

Accepted Answer

On RapidAPI you typically pick a fixed monthly tier per API, with a hard request cap and overage at punishing rates. UnifAPI gives you one key for every API in our catalog, one bill, and you pay only for the calls you actually make — no tiered ceilings.

Question 8

Can I use this in production?

Accepted Answer

Yes. Pay-as-you-go and Enterprise both serve production traffic. Enterprise adds an uptime SLA, priority support, and procurement-friendly contracts.

Question 9

Where does your data come from?

Accepted Answer

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.

Question 10

Is the data legally usable?

Accepted Answer

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.

Question 11

How do you handle our API keys and traffic?

Accepted Answer

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.

Pay per call. No subscriptions.

Free

Catalog access

Limits & scale

Support

Security & compliance

FAQs

Billing

Limits

Security