/pricing
Meter the tokens,never the team.
Credits map directly to model usage — reserved on request, committed on response, released on failure. Bring your own provider key and pay nothing on top. Add teammates without adding a line to the bill.
- 100 API credits / month
- 100 API credits / month
- Every model behind one endpoint
- Community support
- 10,000 API credits / month
- 10,000 API credits / month
- BYOK passthrough — your keys, zero markup
- Per-key spending caps
- Email support
/pricing#math
The math on one call
A 12-credit hold goes down before the first token streams. The model produces 8 credits of tokens — so 8 commit, 4 come straight back. Fail mid-stream and all 12 return. The ceiling is the worst case, never the price.
nara meter --explain --last-call
reserve12.00 crhold at the catalog ceiling
commit− 8.00 crtokens the model produced
release+ 4.00 crrefunded on response
you paid 8.00 cr — never the ceiling
/pricing#why
/pricing#meter
What a credit buys
No seats, no per-model invoices, no per-provider accounts. One meter, four rules.
Token-aware metering
Every call reserves, commits, and releases. Billing is floored at the catalog rate and capped at the reservation — you pay for the tokens the model actually produced, never a flat per-request fee.
BYOK passthrough
Bring your own provider key and requests route through it at cost — credits stop counting entirely. Zero markup, and your key never leaves the gateway's encrypted vault.
No seat pricing
Mint as many API keys as you want on any plan. Name, scope, and cap each one independently — the meter follows credits consumed, not people on the account.
Organization plans
One pooled credit balance for the whole team, one invoice, one audit trail. Add and remove members freely — the pool doesn't care how many hands are on it.
/pricing#faq
Fine print, short.
Everything the meter does with your credits, stated plainly. Still unsure? The ledger in your dashboard shows every reserve, commit, and release.
What exactly is a credit?
A credit is the metering unit for model usage. Every call reserves credits at the model's catalog ceiling, commits only what the produced tokens actually cost, and releases the rest back to your balance.
What happens when a request fails?
The full reservation is released. You are only ever charged on a committed response — the ledger books reserve, commit, and release as separate auditable entries, so a retry can never double-charge.
How does BYOK pricing work?
Bring your own provider key and requests route through it at cost, with zero markup — your NARA credits stop counting entirely for those calls. Keys are stored in an encrypted vault and never leave the gateway.
Do you charge per seat?
Never. Mint as many API keys as you want on any plan and cap each one independently. The meter follows credits consumed, not people on the account.
How do organization plans bill?
One pooled credit balance shared across the whole team, one invoice, one audit trail. Add or remove members freely — the pool doesn't care how many hands are on it.
Do I need a card to start?
No. The free tier includes 100 API credits every month — enough to try every model behind the gateway before you pay anything.