Coding plan

Coding plans are retired; your plan stays active until its paid period ends and won’t renew. Eligible workspaces receive never-expiring credits worth one month of the plan now, as soon as the plan’s end is scheduled, so keys keep working on credits. Workspaces with a live plan at retirement get 20% extra on top-ups for 12 months, unless partner pricing applies. Want a refund instead? Contact support.

​

Current plan limits

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. A plan qualifies unless its payment was refunded, reversed or disputed. Plans that ended before 2026-11-03 at 00:00 UTC receive no retirement credit. Shared by this workspace, not per member. These limits apply until your plan ends. Monthly usage is approximate: months hold different numbers of weekly resets. Pro and Team workspaces keep at least 20 million tokens per minute per model after the plan ends, including any higher existing limit.

​

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 when your plan ends. Only an owner can change its credits-after-limits setting; members can view it. You cannot buy, keep, resume, upgrade or downgrade a plan. Installed CLIs still run runinfra plan, which shows your plan until it ends. From code, GET /v1/usage returns the 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.

• Until the plan ends, an owner can change Keep full speed on credits or Use Standby only (free, slower) 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. 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.
• Existing credits keep their expiry dates. Retirement credits never expire.

​

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.

​

Cancel or delete

Your plan already ends at its paid period end and won’t renew. There is nothing to cancel for a normal plan. While a payment dispute is open, an owner can select Cancel now at Settings > Coding plan to end it at once. A cancellation cannot be undone. 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.

​

Refunds

You can ask support for a full refund of your latest monthly plan payment instead. Your plan then ends at once, and any unspent retirement credit is removed. A payment dispute removes it too. A bank inquiry alone changes nothing. A coding plan that never starts serving is refunded in full.

​

Payment issues

If a renewal failed before retirement, 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. That failed payment can still be collected automatically until your period ends; contact support to cancel it. A disputed plan payment pauses the plan, ends it at the period end and removes any unspent retirement credit. A bank inquiry alone changes nothing. If the disputed card also bought credits, your account is frozen too, so credits cannot pay either. A dispute decided in RightNow Inference’s favor lifts the pause and the freeze, but the plan still ends at the period end, on its current tier, and the retirement credit is not restored. 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.