> ## Documentation Index > Fetch the complete documentation index at: https://runinfra.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Pricing and credits > One workspace balance, credits worth a dollar each, a minimum top-up of 5 US dollars, monthly coding plans for the same workspace keys, and Model APIs token costs and rate limits. One balance per workspace. One credit is one US dollar. Pay as you go and a coding plan are two ways to fund requests from the same workspace keys. | | Pay as you go | Coding plan | | - | - | - | | Payment | Add credits when you need them | Monthly payment for covered usage | | Meter | Published per-token rates for Model APIs | The same per-token rates, with a 5-hour limit and a weekly limit | | At a plan limit | Not applicable | Credits if chosen, with a cap or no limit, then Standby for chat, then a 402 | | Everything else | Credits fund images, audio and other billable work | These always stay pay as you go | See [Coding plan](/docs/introduction/coding-plan) for tiers, coverage, Standby and cancellation. Manage your plan at [**Settings > Coding plan**](https://runinfra.ai/settings/plan). ## Pay-as-you-go credits | | | | - | - | | What a credit is worth | \$1, everywhere | | Free on signup | \$1, once per account, never expires | | Minimum top-up | \$5 | | Maximum per top-up | \$1,000,000 | | Where you add funds | [Settings > Billing](https://runinfra.ai/settings/cost#credits) | | How you pay | Card | | Seats | No per-seat fees, on any workspace | ## What a token costs Priced **per model**, not by size band. When rates are published for a model, its page in the [Model Library](https://runinfra.ai/inference-api) lists the input, cached input, and output rates per one million tokens. If that published price set has no separate cached input rate, cached input bills at the standard input rate, and the page says so. An unpublished fact is left absent rather than filled with a placeholder. Model APIs work on every account, whatever you have spent. ### Partner pricing RunInfra arranges Model API prices per account and per model. You see your agreed prices while signed in. They apply automatically when you call a covered model with your account's API key. **Partner pricing** at [**Settings > Billing**](https://runinfra.ai/settings/cost#partner-pricing) lists each covered model with your price beside the list price. The section is hidden for accounts without arranged prices. `GET /v1/models` returns your account's prices when called with its API key. The response's `usage.cost` reflects that price. Partner pricing is not self-serve. [Contact us](https://runinfra.ai/contact). ## Rate limits Three limits govern Model API requests for your account: 1. **Requests per minute, per API key.** The default is 10,000 before your first credit purchase and 50,000 after it. Enterprise plans default to 200,000. Provider partners have a provider-grade rate. Each key follows your workspace default. A key that already has a custom limit keeps it, clamped to the workspace maximum. 2. **Tokens per minute, per model.** Credit purchases and net coding plan payments contribute to your token tier. Each model keeps its own default if it is higher than the tier's minimum. 3. **Concurrent requests, per model, on pay as you go.** Your share is a quarter of the model's capacity before your first purchase and most of it after. These shares apply only while a model is busy. With spare capacity, your account can exceed its share. See **Rate limits** at [**Settings > Billing**](https://runinfra.ai/settings/cost) for your current limits and token tier. The per-model table and the token tiers are under **All limits and tiers**. Each model's published concurrency allowance is available on `GET /v1/models` as `max_concurrent_requests_per_api_key`. The credit milestones below describe pay-as-you-go standing. While a coding plan serves covered requests, Pro and Team have a temporary floor of at least 20 million tokens per minute per model. Standby has separate capacity limits. See [Rate limits](/docs/api-reference/rate-limits#coding-plans-and-standby). ### How to raise your token budget | Tier | Lifetime credit purchases | Tokens per minute, per model | | - | - | - | | Model defaults | Less than \$50 | Each model's own default | | At least 20M | \$50 to less than \$200 | At least 20 million, or the model's higher default | | No practical limit | \$200 or more | No practical limit | | Enterprise | By arrangement | No practical limit | A top-up raises your token tier as soon as payment settles. Your tier never goes down, even as you spend your balance. Promotional credit does not count. Your first credit purchase, from \$5, unlocks paid standing with a higher request rate and busy-model concurrency share, before you reach either token milestone. ## Adding funds * **One-time top-ups** from \$5 to \$1,000,000 at [Settings > Billing](https://runinfra.ai/settings/cost#credits). Type any whole-dollar amount in that range. The field opens at \$20 unless the page that sent you specifies the amount you need. RunInfra opens secure checkout, which collects your card and billing address, offers an optional VAT or tax ID field for business purchases, and shows the exact charge before you confirm. Every purchase issues an invoice carrying those details. * **Auto recharge** is off until you turn it on at [Settings > Billing](https://runinfra.ai/settings/cost#auto-recharge). If no card is saved, turning it on first runs one top-up through checkout that saves your card. After that, when your balance falls below your threshold, RunInfra charges the saved card, up to a monthly ceiling you set. * **Billing details**: the owner selects **Manage billing details** at the top of [Settings > Billing](https://runinfra.ai/settings/cost) to open the billing portal. There you can edit the company name, billing address, and tax IDs that appear on your invoices, manage saved cards, and browse every finalized invoice. The owner sets one **Billing contact** at [Settings > Account](https://runinfra.ai/settings/workspace#billing-contact). Purchase receipts, balance and spend alerts, payment issues, plan changes and account holds go to that address, with the owner copied. The invoice for a purchase follows the payment account, and this setting cannot move it. Clear it to send those notices to the owner alone. | Auto recharge setting | Starting value | Range | | - | - | - | | Threshold | \$10 | \$1 to \$1,000,000 | | Recharge amount | \$50 | \$10 to \$1,000,000 | | Monthly ceiling | \$500 | \$10 to \$10,000,000 | A card decline that requires your action pauses auto recharge and flags it for attention. Temporary declines can retry after a six-hour backoff. Turning auto recharge off stops new attempts, but an attempt already in progress may still complete. Credit is added when the payment confirms, never before, and an automatic recharge counts toward lifetime purchases exactly like a manual top-up. **Credit checkout does not take promotion codes,** and a reload cannot charge you twice. Credits are stored value, so a discount would reduce the credits you receive by exactly what it takes off the price. The attempt you started is identified for as long as it is open, so a refresh, a back button, or a return from a bank verification screen resumes that payment instead of creating a second one. ## Spending controls **Credits fund pay-as-you-go work.** A coding plan's **Cap per billing period** limits only credits spent after a plan limit, not other pay-as-you-go work. Set an optional monthly spending limit per API key at [**Settings > API keys**](https://runinfra.ai/settings/api-keys). Pay-as-you-go requests on that key return `402 spend_limit_reached` once its settled spend reaches the limit. See [Authentication](/docs/api-reference/authentication). To bound automatic charges, use the auto recharge monthly ceiling. ## At zero balance A serving coding plan can cover eligible requests at zero credit balance. These credit rules apply to pay-as-you-go work: * Calls to the Model APIs return `402 Payment Required` and are not billed. See [Errors](/docs/api-reference/errors). * If a settlement drives the balance below zero, the workspace pauses new billable work. Your next top-up offsets the negative amount first. * A screen that cannot read your balance says so and offers a retry. It never renders a zero it did not read. ## Details you may need Balance from a top-up lasts one year from purchase, manual and automatic alike. The \$1 signup grant never expires. Whatever expires soonest is spent first, so a top-up is never stranded behind funds that expire later. A small number of workspaces hold one from before credit subscriptions were retired, and nothing about those changes: it keeps granting its monthly balance, which expires at the end of each billing period. Its invoices are listed under **Invoices** on [Settings > Billing](https://runinfra.ai/settings/cost), alongside the invoices credit purchases now produce. New legacy credit subscriptions cannot be started. Coding plans are a separate product and do not grant a monthly credit balance. To move a legacy workspace onto credits, [contact support](https://runinfra.ai/contact); that switch is not self-serve today. Enterprise is arranged with RunInfra, not unlocked by a purchase. It has no practical token limit, a provider-grade request rate, and the same concurrency share as the top paid tier. [Contact us](https://runinfra.ai/contact). Make your first API call. Short answers about keys, funds, and workspaces.