PLATFORM
Credits and billing
Understand token costs, reserved credit, and usage attribution.
Overview
Inference uses prepaid organization credit. One US dollar adds one prepaid credit. Check your selected organization's balance in Billing, then use current model prices to estimate work. A key's traffic spends that key's organization's balance, regardless of which organization is currently open in your browser.
Add credit and confirm payment
Only the organization owner can start a top-up. Open Billing → Top up, choose a supported payment provider and an amount from $1 to $10,000, then follow that provider's payment instructions. The available methods and recommendation depend on your region and provider availability: DOKU provides Indonesian credit/debit cards through a secure hosted payment page, QRIS, and bank transfers when each merchant channel is enabled, while Polar provides an international hosted checkout. Use only the methods currently shown in the interface.
For DOKU, select the USD amount and review the estimated IDR total before Continue. New DOKU top-ups use the USD-to-IDR exchange rate without a customer processing surcharge: Netra covers payment processing costs, and you receive the full USD credit amount. The estimate includes any applicable tax. Existing checkouts keep their original locked total; start a new top-up to use current pricing. The final exchange rate and payment amount are locked when the payment is created; previewing the estimate does not create a payment.
Returning from a checkout page does not itself add credit. Netra must verify the provider's payment notification or status before recording the credit transaction. If a payment is still pending, inspect its status and the relevant DOKU/Polar history rather than repeatedly paying again. Pending payment rows refresh automatically, and confirmed payments refresh the selected organization's balance and history. The app periodically checks the provider if confirmation is delayed. A paid DOKU history entry offers an invoice; Polar history includes payment and refund state.
If an already-spent payment is refunded, Billing can show account debt. Later top-ups repay debt before adding spendable balance. For credit expiration and refund terms, use the current Terms of Service rather than treating a payment status as a refund policy.
Estimate inference cost
Where a model has separate uncached-input, cached-input, and output rates:
uncached_input_tokens = prompt_tokens - cached_tokens
estimated_USD = (
uncached_input_tokens * input_price_per_million
+ cached_tokens * cached_input_price_per_million
+ completion_tokens * output_price_per_million
) / 1_000_000Use a model's listed rates; this formula is not a fixed price quote. If no distinct cached-input rate is listed, cached input uses the normal input rate. Do not count cached tokens twice. Usage may be estimated when exact token counts are unavailable; use the settled usage record to reconcile charges.
Netra reserves credit while requests are active and settles actual usage as work completes. Available credit can therefore be less than the displayed total balance during concurrent requests. A generation cap can affect admission reservations, while settled cost depends on usage. Check active work and limits before interpreting a 402 as a missing payment.
In structured usage data, cost_micros is millionths of a US dollar: divide by 1_000_000. MCP's cost_nanos is a decimal string in billionths of a dollar: divide by 1_000_000_000. Use decimal or integer-safe arithmetic for reconciliation; do not mix the two units.
Observe and billing summaries can use different filters and time windows. Compare the same organization, key, model, and UTC interval. Plain API traffic is attributed to its API key; dashboard Playground traffic can be attributed to the signed-in member. MCP activity results cover only the authenticating key, so they need not equal organization-wide totals. The balance tool instead reads that key's shared organization wallet.
Read balance through MCP
Call netra_get_balance with {} for the current organization balance. It accepts no time window or organization override. Read balance.remaining_credit_nanos for remaining credit and balance.debt_nanos for separate debt; the result includes its organization scope, billing source and as_of timestamp. Amounts are decimal integer strings in billionths of a US dollar. This wallet is shared by the organization's keys and is separate from a key's monthly budget.
netra_usage_summary reports spend within a time window, defaulting to the last 24 hours. A cost_nanos value of "110000000" means $0.11 spent, not $0.11 remaining. A failed balance query means unavailable, not zero; do not replace it with spend. Pending usage, debt, limits and concurrent requests can affect what can be spent next. See the MCP guide for the full field definitions and connection refresh instructions.
Trace ingest and MCP observation reads do not run inference or add inference token charges. An agent's separate model calls, Playground requests, or configured external evaluation providers may have their own costs. Do not treat observability access as authorization to generate paid test traffic.