Support & Community > Plans and billing

Pricing and billing FAQs

Frequently asked questions about upgrading, managing billing, refunds, and invoicing with Warp's paid plans.

All paid Warp plans come with higher monthly credit limits than the Free plan.

When you upgrade from Free to a paid plan, your credit usage resets. If you’re switching between paid plans, any AI usage you’ve already accumulated will carry over.

You can subscribe to a Warp paid plan as an individual or as part of a team. To upgrade:

In the app: Go to Settings > Billing and usage, then click the Upgrade link
Online: Visit warp.dev/pricing

After entering your payment details, you’ll receive an invoice and confirmation via email.

How can I get the most out of my Warp plan?

Warp’s plans are designed for developers who rely on AI to code, debug, and move faster with their team. Pick the plan that matches the scale of your usage and the controls your team needs:

Build — Usage-based plan for individuals or small teams with monthly credits, the ability to Bring Your Own API Key (BYOK) or point Warp at a custom inference endpoint, and access to add-on credits with volume-based discounts.
Max — Plan for individuals or small teams with heavier AI usage. Includes a larger monthly credit allowance than Build, plus a better effective rate for credits than buying add-on credits on Build.
Business — Multi-seat plan for teams. Includes everything in Build, plus admin-configurable data controls, SAML-based SSO, and centralized billing. Available up to the seat limit listed at warp.dev/pricing.
Enterprise — Custom plan for organizations that need higher seat counts, Bring Your Own LLM (BYOLLM) managed inference, granular admin controls, advanced security and compliance, and dedicated support.

For the most up-to-date feature and usage details — including current per-plan seat limits and monthly credit allowances — visit warp.dev/pricing.

Warp offers two options for larger teams and organizations:

Business plan: Self-serve multi-seat plan available for immediate upgrade. Includes admin-configurable data controls and admin-controlled SAML-based SSO. See warp.dev/pricing for the current seat limit.
Enterprise plan: Custom pricing, credit allowances, and terms — built for larger engineering organizations or teams with advanced security, compliance, or support needs. Enterprise also includes Bring Your Own LLM (BYOLLM) managed inference, with routing, orchestration, governance, and observability provided by Warp.

For Warp-managed model traffic (requests Warp routes to OpenAI, Anthropic, or Google on your behalf), all plans are covered by Warp’s Zero Data Retention (ZDR) agreements with the underlying model providers. Traffic you route through your own API key or a custom inference endpoint is governed by that provider’s data-retention policies, not Warp’s agreements. Admin-configurable data controls — including team-wide retention policies and training opt-outs — are available on Business and Enterprise.

What counts as a team member and how does billing work for members?

In Warp, a team member is any seat with access to your Team — including the shared Warp Drive, Notebooks, Workflows, and other team resources. All plans allow you to invite unlimited Warp Drive collaborators, but paid-plan features and credit allocation are governed by your plan’s seat limit (see Are there new seat limits per plan? below). Upgrading applies to your entire team, including your own account and all active members.

On the Free plan, you can share a limited number of Notebooks and Workflows with other Free users. If your team exceeds that limit, you’ll be prompted to upgrade to a plan.

Once you upgrade, you’ll receive email notifications as team members accept invites. Billing is prorated, meaning you’re only charged for the days each member has access during your billing cycle. If a member leaves mid-cycle, Warp automatically applies a credit for the unused time to your next invoice.

There are differences in how members are billed based on your payment schedule:

Monthly plans: New members are billed immediately for the remaining time in the month.
Annual plans: New members are billed immediately for the remaining time in the year.

For example, if a member joins your monthly plan halfway through the month, you will be charged just half of the monthly fee ($25.00 out of $50). Similarly, if a member joins with four months remaining in an annual plan, you will be charged for those four months only, which amounts to $160 (4/12 of the annual $480).

If a member leaves part way through the billing cycle, Warp will issue a prorated credit based on the unused portion of their membership. This credit is applied to your team’s next invoice, regardless of whether you’re on a monthly or annual plan.

What is the value of joining or creating a team on Warp?

Team members have access to your shared Warp Drive objects and limited access to Warp’s collaboration features, including Session Sharing and Warp Drive storage.

Upgrading the team to a plan unlocks powerful collaboration and knowledge-sharing tools to help your team move faster, together:

Create unlimited Notebooks and Workflows in Warp Drive to organize and share knowledge across your team.
Use Unlimited Session Sharing to collaborate in real time through live, shared terminal sessions.

My co-workers are using Warp but we’re not on a Team together yet. How does billing work?

Individual users with either personal or work email domains may continue to use Warp independently without incurring billing. The benefit of joining together on a Warp Team is that you get access to a shared Team Drive and collaboration features.

When you’re ready to use Warp more collaboratively, we suggest you nominate an Admin to create a Team and invite members to join. When your Team exceeds the Warp Drive limits, you will be prompted to upgrade to a plan.

How does usage work if logged into the same account on multiple devices?

When you use the account to sign into Warp on different devices, for example Linux on one computer and Windows on another, your usage of metered features like credits is tracked at the account level, not the device level.

You can use your Warp account on multiple personal computers. Warp is designed to provide a consistent experience across devices. When you log in with the same account on different computers, your settings and preferences can be synced through the Settings Sync feature.

What happens when I downgrade during a billing cycle?

The subscription will downgrade to the lower plan limits at the end of the billing cycle. If you’re switching between paid plans, any AI usage you’ve already accumulated will carry over.

You can downgrade at any point throughout your subscription through the billing portal by going to Settings > Billing and usage > Manage billing.

What happens when I cancel during a billing cycle?

You can cancel at any point throughout your subscription through the billing portal by going to Settings > Billing and usage > Manage billing. The subscription will be canceled at the end of your billing cycle, monthly or yearly.

You can continue to use your Warp paid plan features until the cycle end date. Any additional team members added to your team will be invoiced at the end of your billing cycle.

What happens if I upgrade from monthly to annual billing?

When upgrading from a monthly to annual billing cycle the billing is prorated, meaning you only pay for the annual portion of the year you haven’t paid for yet. You will be billed for the remaining part of the billing year with the discounted rate.

You can upgrade at any point throughout your subscription through the billing portal by going to Settings > Billing and usage > Manage billing.

What happens to unused credits?

Unused credits do not rollover to the next cycle and can’t be transferred to other accounts. You see when your credits will reset in the Settings > Billing and usage menu.

What happens if my payment fails?

If a payment fails, you will receive an email from Stripe and your Warp Team Settings will show a past-due alert. Certain paid plan features and the ability to invite new members will be locked down while your Team is in a past-due state. Paying the most recent invoice through the billing portal by going to Settings > Billing and usage > Manage billing will fully re-enable your paid plan features.

What counts as a credit?

Each time you submit a prompt in Warp, whether to generate code, suggest a command, or accomplish a task, you initiate an interaction with the Agent. Please see more details in our credits page.

What counts as an AI token?

Tokens are chunks of text, such as words, parts of code, or characters, that large language models (LLMs) break down to analyze and generate responses. LLMs have a maximum number of tokens they can process at once. Credits and suggestions are not the same as tokens, which are limited separately regardless of which plan you’re on.

If you’re curious, you can read the OpenAI article on tokens, or refer to the pricing page for plan-level credit allocations. If you reach your monthly credit limits on the Free plan, premium models pause until your quota resets at the start of your next billing cycle. On paid plans, you can continue using premium models via add-on credits and auto-reload — see What if I need more AI usage than my plan includes? for the full list of options.

How often do my credits reset?

Allotted credits refill every 30 days from your signup date. When you upgrade to a paid plan, you will be given more credits immediately. You can follow along with your refill period by referencing Settings > Billing and usage. Alternatively, purchase add-on credits, or enable auto-reload with a monthly spend limit, to continue using premium models beyond your included quota.

How do credits work for multi-seat teams?

On the new multi-seat paid plans, credits attribute differently than they did on Warp’s older pooled-credit teams:

Plan-included monthly credits — Each seat receives its own monthly credit allowance that resets every 30 days based on the team’s renewal date. See warp.dev/pricing for the current per-seat allowance on your plan.
Add-on credits — As of May 21, 2026, add-on credits are scoped to the individual user who purchased or was allocated them, not pooled across the team. A single heavy user can no longer drain the whole team’s purchased credits.
Grandfathered pooled credits — Teams that purchased add-on credits before May 21, 2026 keep their existing pooled balance until it’s exhausted. Pooled credits are spent down first across the team; all new add-on credit purchases after May 21, 2026 are user-scoped.
Team-wide spend cap — Admins set a single team-wide monthly spend cap that governs auto-reload across the team. See How does auto-reload work for teams? below.

Enterprise plans support team-scoped credit pools and per-user spend limits separately — see enterprise billing.

How do platform credits factor in?

Warp meters credits across three buckets: AI credits (the model call), compute credits (the sandbox a cloud agent runs in), and platform credits (run lifecycle, integrations, dashboard, APIs, and observability). All three draw from the same pool — your monthly Warp credits first, then add-on credits once those are exhausted.

Platform credits apply in two situations:

Every cloud agent run, on every plan. Warp’s platform infrastructure coordinates every cloud run regardless of which agent or inference source it uses. On self-serve plans (Free, Build, Max, Business), platform-credits billing is in a preview period through June 30, 2026 — see When do platform credits start being charged on self-serve plans? for details.
Local agent runs on Business and Enterprise that use customer-supplied inference — BYOK, a custom inference endpoint, or BYOLLM. Warp isn’t paying for the model call, but Warp’s platform infrastructure is still running the agent. Billing for these runs is also in preview through June 30, 2026 on self-serve plans; metering begins July 1, 2026.

Local agent runs on Free, Build, or Max — and local runs on Business or Enterprise that use Warp-managed inference — do not consume platform credits. See platform credits for the full breakdown.

What if I need more AI usage than my plan includes?

If you regularly run through your plan’s monthly credit allowance, you have a few options:

Upgrade to Max — Designed for developers with heavier AI usage. Max includes a higher monthly credit allowance than Build, plus a better effective rate for credits than buying add-on credits on Build. See warp.dev/pricing for current allowances.
Purchase add-on credits — Top up your account on demand. Larger denominations have a better effective rate. Add-on credits roll over month-to-month and remain valid for 12 months as long as you have an active subscription — if you move to the Free plan, you’ll lose access to any remaining add-on credits. See add-on credits for current denominations.
Enable auto-reload — Pick a denomination and a monthly spend cap, and Warp will automatically purchase add-on credits when your balance drops below 100 credits, up to your cap.
Bring Your Own API Key (BYOK) — Point Warp at your own OpenAI, Anthropic, or Google API key. Requests routed through BYOK don’t consume Warp credits — you’re billed directly by the model provider. See Bring Your Own API Key. On Business and Enterprise, platform credits may apply for local agent runs (billing starts July 1, 2026 on self-serve plans — see When do platform credits start being charged on self-serve plans?).
Use a custom inference endpoint — Route requests through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, an internal gateway, etc.) without spending Warp credits. See Custom inference endpoint. On Business and Enterprise, platform credits may apply for local agent runs (billing starts July 1, 2026 on self-serve plans — see When do platform credits start being charged on self-serve plans?).

BYOK and custom inference endpoint availability is subject to organization size — see Can I bring my own API key? for details.

For organization-scale needs (cloud-provider managed inference, granular admin controls, or higher seat counts), Enterprise plans include Bring Your Own LLM (BYOLLM).

How does auto-reload work for teams?

Auto-reload prevents team members from getting blocked by credit exhaustion. It works the same way for individual and multi-seat paid plans, with one extra knob for teams.

When auto-reload is on:

The admin chooses an add-on credit denomination. Larger denominations have a better effective per-credit rate.
Whenever any individual user’s balance (their plan credits plus their user-scoped add-on credits balance) drops below 100 credits, Warp automatically purchases another bundle of the configured denomination on the team’s behalf.
All auto-reload purchases count against a single team-wide monthly spend cap that the admin sets. Once the team hits the cap in a given month, auto-reload pauses until the next billing cycle or until the admin raises the cap.
While auto-reload is on, individual team members cannot purchase add-on credits manually — the team-wide auto-reload configuration governs all purchases.

Teams with a pre-May 21, 2026 grandfathered pooled add-on credit balance: that pooled balance drains first across the team before user-scoped add-on credits and is not counted toward any individual user’s 100-credit auto-reload threshold.

When auto-reload is off, eligible team members can purchase add-on credits for themselves, as long as the team stays below the team-wide monthly spend cap. Users keep working as long as they have plan credits, previously purchased add-on credits, or have routed Warp at their own API key or custom inference endpoint. Once those run out, premium-model usage is blocked until credits are topped up or the next billing cycle begins.

Auto-reload can be enabled, paused, or reconfigured at any time in Settings > Billing and usage.

How are cloud agent runs on team plans billed when no individual user triggered them?

Some cloud agent runs aren’t initiated by a specific team member — for example, scheduled runs or runs triggered through a team API key. On self-serve plans (Build, Max, Business), these runs are billed to the team owner.

The waterfall on the owner’s account is:

First, the owner’s plan-included monthly credits are consumed.
Once those are exhausted, the owner’s add-on credits are consumed.

When auto-reload is off, the request is blocked once both buckets are depleted. When auto-reload is on, cloud agent usage can trigger auto-reload on the owner’s pool subject to the team-wide spend cap; further cloud agent runs then draw from that reloaded balance until the cap is reached.

“Blocked” means the run fails immediately with an insufficient-credits error rather than queuing or retrying. For unattended runs (scheduled jobs, team-API-key triggers), this manifests as a failed run in the Oz dashboard with an insufficient credits error code; the run won’t be retried automatically. Owners should monitor the dashboard and configure spend caps with headroom for critical scheduled workloads.

Can I use a Free plan if I’m a developer at a large company or organization?

Yes. Developers at any company size are welcome to use Warp’s Free plan.

If you need access to advanced collaboration features or higher limits, you may benefit from upgrading to a plan, but Warp does not require large organizations to upgrade.

Are there any Warp discounts for students, non-profits, or open-source teams?

Warp doesn’t currently offer discounts for students or non-profits. We recommend exploring the Free plan, which includes all core terminal features and is a great starting point for individual or community use.

For open source teams, two paths are available:

The Oz Open Source Partnership program offers free agent credits to high-impact open source projects.
Warp’s client itself is open source under AGPL v3, so you can build, run, and contribute to it directly. See Contributing to Warp for the flow.

Where is Warp Drive data for my team stored?

Warp Drive data is securely stored on Google Cloud Platform servers located in the United States. All data is encrypted in transit and at rest.

For more details, please visit the Security Overview or contact security@warp.dev.

Does Warp have a SOC 2 Type 2 attestation?

Yes. Warp has obtained a SOC 2 Type 2 attestation from an accredited third party. See the Trust Center to request the report.

Does Warp have Zero Data Retention policies with LLM providers?

Warp integrates with multiple LLM providers — including Anthropic, OpenAI, Google, and Fireworks AI — to power its AI features. Warp has executed Zero Data Retention (ZDR) agreements with these providers. Across all plans, these agreements mean:

LLM providers commit not to train their models on any customer-generated data processed through Warp’s services.
LLM providers commit to delete inputs and outputs after generating the relevant output, within a fixed time period.

Warp enforces these commitments through both technical measures and contractual safeguards with the LLM providers.

How can I enable Zero Data Retention in Warp?

Zero Data Retention (ZDR) can be enabled in two ways:

Individual level — Any user can enable full ZDR for their own account by disabling Help Improve Warp in Settings > Privacy.
Organization-wide — On Business and Enterprise plans, admins can enforce ZDR for all members from the Admin Panel, so team-wide compliance doesn’t rely on individual settings.

To discuss organization-wide ZDR for your team, contact our sales team.

Regardless of plan, Warp never allows OpenAI, Anthropic, Google, or other model providers to store, retain, or train their models on your data — see Does Warp have Zero Data Retention policies with LLM providers? for details.

Can I bring my own API key?

Yes. On Free, Build, Max, Business, and Enterprise plans, you can configure your own OpenAI, Anthropic, or Google API key in Settings > AI > Manage models. Requests routed through your own key don’t consume Warp credits — you’re billed directly by the model provider.

See Bring Your Own API Key for setup steps, the list of supported providers and models, and the differences between BYOK, custom inference endpoints, and BYOLLM.

BYOK and custom inference endpoint support are available for individual users and organizations with 10 or fewer employees, subject to Warp’s Terms of Service. Companies or organizations with more than 10 employees need a Warp Business or Enterprise plan to use these features.

On Business and Enterprise, local agent runs that use BYOK still consume platform credits for Warp’s platform infrastructure. See platform credits.

Does Warp support custom inference endpoints?

Yes. In addition to BYOK, Warp can route requests to any OpenAI-compatible inference endpoint — including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Custom inference endpoint requests also don’t consume Warp credits.

Custom inference endpoints are available on Free, Build, Max, Business, and Enterprise. See Custom inference endpoint for configuration steps, billing behavior, and how custom inference endpoints differ from BYOK and from Enterprise’s Bring Your Own LLM (BYOLLM) managed inference.

On Business and Enterprise, local agent runs that use a custom inference endpoint still consume platform credits for Warp’s platform infrastructure. See platform credits.

Does Warp support other model routers or “Bring Your Own LLM”?

On the Enterprise plan, Warp’s Bring Your Own LLM (BYOLLM) lets you route inference through major cloud-provider Model-as-a-Service offerings. BYOLLM currently supports AWS Bedrock, with Azure Foundry and Google Vertex coming soon. Warp still manages model support, routing, and orchestration, but inference runs in your cloud environment so you can maintain data locality, security controls, and existing cloud spend commitments.

Custom or in-house model routers outside this list aren’t supported by default today. If you have specific requirements, contact our sales team.

For lighter-weight routing through any OpenAI-compatible endpoint (OpenRouter, LiteLLM, z.ai, internal gateways), see Does Warp support custom inference endpoints? above.

What features are available during multi-harness orchestration beta?

Multi-harness orchestration is currently in beta and available to all users. You can use the Warp Agent alongside Claude Code and Codex in Oz cloud environments, and mix and match harnesses across workflows.

Agent Memory is currently in Research Preview. It lets preferences, project knowledge, and learnings from past sessions carry across harnesses and future agent runs. Contact our sales team to request access.

As these features move out of beta or Research Preview, availability, limits, and pricing may change.

What payment options are available for Warp’s self-service plans?

Warp uses Stripe as our payments processor and currently accepts the following payment methods: credit card, debit card, Link, Apple Pay, Google Pay.

We don’t support ACH, checks, PayPal, cryptocurrency, or other alternative payment methods at this time.

How do I cancel my subscription?

You can cancel at any point throughout your subscription through the billing portal by going to Settings > Billing and usage > Manage billing.

Cancelled subscriptions will remain active until the end of the billing cycle.

How do I get a refund?

For monthly subscriptions, we can issue a full refund if you cancel within 24 hours of being charged and no credits have been used.

For annual subscriptions, we can issue a full refund within 15 days if no credits have been used, or a prorated refund for remaining months after that. Please see Warp’s Refund Policy for full details and exceptions.

Warp’s promotions are a way to try Warp before committing to a subscription, not get unlimited free or inexpensive AI. To prevent abuse, we’re limiting promotion codes to first-time redemptions only, so each account can only use one promotion code.

In addition certain promo codes we issue are only valid for specific plans (not all plans) and expire after a certain time. If you apply a promo code for a certain plan, then upgrade to another plan, the promotion doesn’t transfer to the new plan so you will end up paying full price for the upgrade.

Warp does allow tax exempt organizations to subscribe, but there are some additional steps that you need to take.

Create a Warp account, login, and go to the upgrade page, and select a plan, but don’t checkout or pay yet. This will only setup your billing account in the system that will be used in the later steps.
E-mail billing@warp.dev with your proof of your organization tax exempt status and your Warp account email.
Warp’s team will verify your tax exempt status and will change your account to tax exempt.
Finally, subscribe to your plan of choice. You will see no taxes applied to the bill.

There are certain prohibited and restricted businesses in which Stripe and major credit card networks will not process payments. For the most updated information, please see the full list here.

I have a question and need help. How can I reach a human at Warp?

The team at Warp is standing by and ready to help. For subscribers technical issues email support@warp.dev, for subscribers billing issues email billing@warp.dev, for security concerns email security@warp.dev, and for questions about privacy email privacy@warp.dev.

May 2026 pricing changes

The May 21, 2026 update introduces new seat limits, changes how add-on credits are attributed, opens BYOK to every plan, adds custom inference endpoints, and starts metering platform credits for cloud agent runs. The questions below cover what’s changing and what to do if any of it affects you.

Are there new seat limits per plan?

Yes. As of May 21, 2026, each plan has an explicit seat limit. See warp.dev/pricing for the current per-plan caps.

The seat limit governs paid-plan features and credit allocation. It’s separate from the unlimited Warp Drive collaborators every plan supports. You can keep inviting unlimited users to share Notebooks, Workflows, and other Warp Drive resources without hitting the seat cap. The cap only applies when a user takes a paid seat on your team.

What if my team is already above the new seat limit?

Your team’s current access doesn’t change. Existing members keep their seats and can continue using Warp the same way they do today.

The cap only governs adding new members. While your team is at or above the cap, you can’t add a new member or backfill a seat after a member leaves. To grow past the cap, switch to the next plan up (or to Enterprise) anytime under Settings > Billing and usage.

How are add-on credits being attributed differently?

Before May 21, 2026, add-on credits on multi-seat teams were pooled. Every team member drew from a single shared balance. As of May 21, 2026, add-on credits are user-scoped. Each user has their own balance, and a single heavy user can no longer drain the whole team’s purchased credits.

Two practical changes for teams:

Anyone on the team can now purchase add-on credits for their own usage, subject to the team-wide spend cap admins set under Settings > Billing and usage. Previously, admins typically managed the shared pool on behalf of the team.
Grandfathered pooled credits: Existing pooled add-on credit balances purchased before May 21, 2026 are honored. They drain first across the team before any user-scoped add-on credits are consumed. No new credits are added to the pooled balance. Once it’s exhausted, all future add-on credit purchases are user-scoped.

For details, see add-on credits.

What happens to my add-on credits if I leave the team?

Add-on credits are tied to the team that paid for them, so team-membership changes affect access:

You leave a team: You lose access to any add-on credits tied to that team. If you rejoin the same team later, you regain access to any unused, non-expired credits. The admin pays a prorated rate for your seat on rejoin.
An admin removes you from a team: You lose access to any add-on credits tied to that team. If you rejoin later, you regain access to any unused, non-expired credits.
An admin deletes the team: Any remaining add-on credits tied to the team are no longer usable by anyone.

Unused add-on credits remain valid for 12 months from purchase, as long as you have an active subscription. See When team membership changes on the add-on credits page for full details.

Can I bring my own API key on the Free plan now?

Yes. As of May 21, 2026, Bring Your Own API Key (BYOK) is available on all plans, including Free. Previously, BYOK required a Build, Business, or Enterprise subscription. You can configure your OpenAI, Anthropic, or Google key under Settings > AI > Manage models.

See Bring Your Own API Key for the full list of supported providers and setup steps.

What is the new custom inference endpoint feature?

Custom inference endpoints let you route Warp’s AI traffic through any OpenAI-compatible inference endpoint, including OpenRouter, LiteLLM, z.ai, and internal gateways your team already runs. Support is available on Free, Build, Max, Business, and Enterprise.

Here’s how custom inference endpoints differ from BYOK and BYOLLM:

BYOK sends requests directly to OpenAI, Anthropic, or Google using your own provider API key.
Custom inference endpoint sends requests to any OpenAI-compatible URL you control or that your team runs.
BYOLLM is an Enterprise-only managed inference feature. Warp routes traffic through your cloud provider (AWS Bedrock today, with Azure Foundry and Google Vertex coming soon) and handles the routing, orchestration, governance, and observability.

For setup and details, see Custom inference endpoint.

When do platform credits start being charged on self-serve plans?

Platform credits apply to every cloud agent run, plus local agent runs on Business that use BYOK or a custom inference endpoint. For self-serve plans (Free, Build, Max, Business), platform-credits billing doesn’t start until July 1, 2026.

Between May 21 and June 30, 2026, all self-serve plans are in a preview period. Platform credits are not consumed during this window, so they won’t draw from your monthly Warp credits, your add-on credit balance, or your spend cap.

On Enterprise, platform credit usage is governed by your contract. See enterprise billing for details.

On July 1, 2026, Warp begins consuming platform credits for:

Every cloud agent run on Free, Build, Max, or Business.
Local agent runs on Business that use BYOK or a custom inference endpoint.

I’m a team admin. What do I need to do?

A short checklist to triage the May 2026 changes for your team:

Check your seat count. Go to Settings > Teams to see whether your team is at or above your plan’s new seat limit. If you are, see What if my team is already above the new seat limit?.
Set your team’s add-on credit spend cap. Under Settings > Billing and usage, configure the monthly cap that applies to add-on credit purchases across your team. Team members can now buy their own add-on credits, but every purchase counts against this cap.
Let your team know add-on credits are user-scoped now. Each member can purchase add-on credits for their own usage without affecting anyone else’s balance.
Plan for platform credits on July 1, 2026. If your team is on Business and uses BYOK or a custom inference endpoint locally, those local runs will start consuming platform credits when the preview period ends. See When do platform credits start being charged on self-serve plans?.