Coding plan

Monthly Model API usage for your workspace, with two plan limits, optional credits after limits, and Standby for chat.

Your plan pays first for covered requests from your workspace, with a 5-hour limit and a weekly limit. Usage is counted at our standard per-token prices, with cached input at the cached price. Plan usage is not a credit deposit and does not roll over.

Choose a plan

	Starter	Pro	Team
Monthly price	$10	$29	$99
Approximate usage a month at our rates	$12	$35	$119
5-hour limit	$1.11	$3.23	$10.98
Weekly limit	$2.77	$8.08	$27.46
Standby daily amount	Up to $0.20	Up to $0.58	Up to $1.98

Shared by this workspace, not per member. Monthly usage is approximate: months hold different numbers of weekly resets.

Only an owner can buy a plan, with Subscribe at Settings > Coding plan. A workspace with partner pricing, a legacy subscription or a billing hold cannot subscribe. Secure checkout shows the renewal disclosure and asks you to accept the Terms of Service. If you were charged but the payment is not confirmed after 10 minutes, select Charged? Contact support.

Your coding plan automatically renews each month until canceled. Your payment method is charged at the start of each billing period.

How the limits work

Your 5-hour window starts with your first plan request, and the next request after it ends starts a new one. The weekly limit resets on a fixed schedule from activation. The plan pays while both have room.

If requests still running have reserved the rest of a plan limit, a new request waits up to 30 seconds, then gets a retryable 429 plan_window_busy instead of credits or Standby.

Manage your plan

Settings > Coding plan shows your limits, when they reset, and your plan. Only an owner can change it; members can view it. From a terminal, runinfra plan reads your plan. From code, GET /v1/usage returns its current limits. To connect a coding agent, see Set up with your coding agent.

See your plan usage

In Usage Analytics, Paid from shows what paid for each request. Plan and Standby requests charge nothing.

What happens at a limit

At a limit, keep full speed on credits (your choice: a cap, or no limit), then Standby, free and slower.

• An owner picks Keep full speed on credits or Use Standby only (free, slower) when subscribing, and can change it with Change on the At a limit tile at Settings > Coding plan.
• The credits cap defaults to the plan price and accepts $1 to $100,000, or No limit. A request whose maximum cost does not fit in the rest of the cap cannot use credits.
• With a cap, Most you can pay is the plan price plus the cap per billing period. Wallet and key limits still apply.

A stopped request gets 402 plan_limit_reached with its reset time and next step. See Plan limit errors and Spending controls.

Standby

Standby is best effort. It refills at midnight UTC, may be reduced or paused at any time, and is off while a plan payment is due or processing, or credits are owed. See Rate limits for its capacity limits.

What your plan covers

The plan covers these operations from every workspace key except keys marked Credits only. The Model Library lists the models served now.

Operation	Plan	Standby
/v1/chat/completions, /v1/messages, /v1/responses	Covered	When available
/v1/embeddings, /v1/rerank	Covered when those models are available	Not covered

Images and audio always stay pay as you go.

Credits only keys

An owner marks a key Credits only at Settings > API keys so it always pays from credits and skips the plan, Standby and the credits cap. Its wallet and key limits still apply, and the setting survives rotation.

What you can count on

• Requests that fail before returning output never use your plan.
• Client cancellations count usage, as in pay as you go.
• A request stays on the source that admitted it.
• Every response a plan decision applied to says what paid, in x-runinfra-funding.
• Metering changes come with written notice, and promotional rates are labeled temporary.
• Credits survive cancellation and keep their existing expiry dates.

Emails

Coding plan emails go to the billing contact with the owner copied, or to the owner alone. Plan limit emails follow the owner’s Product notifications switch at Settings > Notifications. All other plan emails always send.

Change, cancel, or delete

Upgrades take effect now with a prorated charge. New limits apply immediately, and usage already counted carries over. Downgrades take effect at the end of the current billing period.

An upgrade that needs payment action shows Upgrade unpaid and a Pay button. Your plan keeps its current tier until you pay, and stays on it if the deadline passes. Keep Pro, named for your current tier, undoes a scheduled downgrade.

Cancel anytime at Settings > Coding plan, in any plan state. Cancellation takes effect at the end of the current billing period, or immediately while a payment dispute is open. Until then, Keep plan undoes it, except after a payment dispute, even one decided in RunInfra’s favor. When your plan ends, your keys keep working with credits.

Account deletion ends the plan at once, with no refund of the current month. A renewal or an upgrade charged after you delete your account is refunded.

Payment issues

After a failed renewal, your plan can keep serving for up to 48 hours, or 7 days if it has had a paid renewal. Select Pay overdue amount at Settings > Coding plan before then.

A disputed plan payment pauses the plan and ends it at the period end. A bank inquiry, which only asks about a charge, does not. If the disputed card also bought credits, your account is frozen too, so credits cannot pay either. A dispute decided in RunInfra’s favor lifts the pause and the freeze, but the plan still ends at the period end, on its current tier. One decided for the cardholder ends it at once. Contact support.

See the account FAQ and Terms of Service, section 7 for the cancellation and refund rules.