One fee, stated up front
No plans, no seats, no minimums. Usage debits each provider's own metered price. Our entire margin is 5.5%, charged once, when you add credits. Sign-up comes with $5 to spend. That's the whole page — everything below is just the receipts.
$5 seeded at sign-up
Balance starts at $5.00 with a key already minted — no card, no call with sales. Across the catalog that's thousands of real requests before you spend a cent.
Usage at the provider's price
What Serper, Firecrawl or ElevenLabs metered for the call is what leaves your balance. The number you benchmarked against is the number you pay.
5.5%, only on top-ups
Added on top at checkout and itemized on the Stripe receipt: $100 of credits charges $105.50, and the full $100 lands in your balance. Nothing monthly, nothing per request.
Checkout math, pre-computed
Same rounding the checkout uses — the figure here is the figure your card sees.
Whole dollars, $10–$5,000 per purchase.
- Lands in your balance
- $25.00
- Service fee (5.5%)
- $1.38
- Card is charged
- $26.38
| Credits bought | Fee (5.5%) | Card charged | Balance receives |
|---|---|---|---|
| $10 | $0.55 | $10.55 | $10.00 |
| $25 | $1.38 | $26.38 | $25.00 |
| $100 | $5.50 | $105.50 | $100.00 |
| $1,000 | $55.00 | $1,055.00 | $1,000.00 |
What the free $5 covers
Computed from measured cost-per-call in our benchmark runs, not from list prices.
≈16,000
Google SERP queries via Serper — measured at $0.0003 per call, ranked #1 of 4 on the SERP board.
≈2,300
Clean page scrapes via Firecrawl — measured at $0.0021 per successful scrape, #1 of 10 on the Scrape board.
≈5,000
Rendered screenshots via Firecrawl — measured at $0.001 per call, #1 of 8 on the Screenshot board.
Same prices, one account
| Direct, provider by provider | Through NativePort | |
|---|---|---|
| Sign-ups | One onboarding per provider — up to 31 | One |
| Secrets in your agent | Up to 31 keys within its reach | One — upstream keys injected server-side |
| Invoices | Up to 31 plans and billing cycles | One dollar balance |
| Per-call price | The provider's metered rate | The identical metered rate |
| Idle providers | Often a plan floor or expiring plan credits | $0 — unused means unbilled |
| Our cut | — | 5.5% at top-up, full stop |
Weighing this against another gateway instead? Read the NativePort vs. OpenRouter or NativePort vs. Eden AI breakdown.
Why the fee lives at top-up
So the rankings stay clean
We publish head-to-head scores for every provider we carry. If margin hid inside per-call prices, pricier routes would pay us more and every ranking would deserve your suspicion. A flat fee at top-up earns the same 5.5% whether you route to the #1 provider or the #8 — the leaderboards have no stake in your choice.
So every number is auditable
The fee is a visible line at checkout and on the receipt; each request's exact provider cost sits in your ledger; and credits are plain dollars — no points currency with an exchange rate to hide arithmetic in.
So there's nothing else to find
The 5.5% funds payment processing, the ledger and receipts, server-side custody of two dozen upstream keys, provider monitoring, and the benchmark fleet itself. It is the entire business model.
Asked and answered
Does a request cost more through the gateway?
No. A call debits exactly what the provider metered for it — the same amount you'd pay them directly. Per-call prices carry no markup; our margin lives entirely in the top-up fee.
Where does the 5.5% fee apply?
Only when credits are purchased, including auto-top-ups. It rides on top of the amount: buying $100 of credits charges your card $105.50 and puts the full $100.00 in your balance, with the fee itemized on the Stripe receipt. It never touches individual requests or the free $5 starting credit.
Can I try it without a card?
Yes. First sign-in seeds your balance with $5.00 and mints your first API key automatically. A card only enters the picture when you decide to top up.
What are the top-up limits?
Whole dollars, $10 minimum and $5,000 maximum per purchase. Auto-top-up recharges at the same 5.5% — there is no separate rate.
What happens at zero balance?
Every request answers HTTP 402 until credits are added. Turn on auto-top-up in the dashboard if an agent should never stall mid-run.
Is this safe for an unattended agent?
That's the design center. Failure is deterministic (402, never a silently degraded response), auto-top-up keeps long runs funded, every request is individually debited in an auditable ledger, and upstream provider keys stay server-side — your agent's only secret is its NativePort key.
Can I see what a call will cost before making it?
Provider pages publish measured cost per successful call next to quality and latency, per-endpoint prices live in the docs, and after the fact the ledger shows the exact debit for every request.
Do credits expire? Are they refundable?
Credits are plain dollars in your balance — no monthly cycle sweeps them away. They're non-refundable except where the law requires it; the Terms of Service carry the current policy.