Admin ConsoleAdminister

Tiers and limits

A tier decides which models someone can use, which models run LatentCode's background work, and how many requests and dollars they can spend per window.

Required role

Owner or Admin of the active organization.

How tiers work

Each organization has its own tiers; one of them is the default. Every member uses exactly one tier in each organization. The gateway picks the tier for each request in this order and uses the first one it finds:

For a request made from a team: the member's tier override in that team, then the team's tier.
The tier assigned to the person in this organization, on the Users page.
The organization's default tier.

New members start on the organization's default tier. A request is refused if no tier applies, if its model isn't on the tier, or if it would go over a limit. The errors are listed below.

The Tiers page

Open Tiers from the Administration group. Each tier card shows a Default badge on the default tier, an Incomplete badge when a required model is missing, the number of Allowed models and Rate policies, the Default model, and how many of the four required Background models are set. Select a card to expand the full list of models, per-model rate limits, background models and the Ultra-Plan setting.

The icons on each card Set default (star), Edit (pencil) and Delete (trash). The default tier can't be deleted; make another tier the default first.

Create or edit a tier

1
Select New tier
Or the pencil icon on an existing tier.
2
Name it
Enter a Name (unique within the organization) and, optionally, a Description.
3
Choose the allowed models
Tick models under Allowed models, or use Select all. The search box filters by model or provider. Only models with a provider configured in Settings are listed.
4
Set the background and default models
Every required model must be one of the tier's allowed models (see the field reference below).
5
Set limits
Fill in the rate-limit and budget tables. 0 means unlimited.
6
Save
Select Create tier or Save changes. The button stays disabled until every required model is set.

The first tier you create in an organization becomes its default automatically.

Field reference

Models

Field	Required	Meaning
Name	Yes	Shown on the Users, Teams and My Usage pages.
Description	No	Free text.
Allowed models	Yes, at least one	The models members on this tier can call. Requests for any other model are refused.
Subagent model	Yes	Runs helper agents.
Goal / Loop model	Yes	Runs goals and /loop.
Title model	Yes	Writes short session titles.
Fusion advisor model	Yes	Plans how work is shared between models.
Review model — high, medium, low	No	Models for the /review reviewers, by difficulty. Unset ones use the subagent model.
Default main-agent model	Yes	Pre-selected the first time someone opens LatentCode or LatentWork, and the model a session falls back to if its current model errors. People can still pick any allowed model for their sessions.
Enable Ultra-Plan mode	No	Adds a planning mode in which a second model checks the finished plan against the codebase before the user approves it. Costs one extra model pass per plan. When off, the mode doesn't appear in the client.
Plan revisor model	When Ultra-Plan is on	The model that checks plans. Pick a capable model, ideally from a different vendor than the default main-agent model.
Default tier (new users get this)	No	Makes this the organization's default tier.

People can't change the background models in their client. If a model the tier allows no longer has a provider, the editor leaves it out of the selection and asks you to Acknowledge that before you save.

Limits

Table	Unit	Windows	Meaning
Rate limits per model	Requests	min, hour, 6h, day	Requests each member may make in each window. A model with its own row uses that row; every other allowed model uses the default (any other model) row.
Budget limits	USD	min, hour, 6h, day	Total spend per member across all models in each window.
Budget limits per model	USD	day	Daily spend per member on one model, with the same default row. Enforced in addition to the tier-wide budget: whichever cap is reached first blocks the request.

Limits count each person separately, per organization. Usage through a team is counted separately from the same person's own usage, against the team's tier. To see how close someone is, use View usage on the Users page; people see their own on My Usage. To clear someone's current windows, use Reset rate limits on the Users or Teams page.

Change the default tier

Select the star icon on a tier, or tick Default tier (new users get this) in its editor. Exactly one tier is the default. The default applies to new members, and to existing members who have no tier assigned in this organization.

Delete a tier

Select the trash icon and confirm. Anyone assigned to the deleted tier, including team and team-member tier assignments, is moved to the organization's default tier.

What users see when a limit is hit

HTTP status and type	Cause
403 `no_tier_assigned`	No tier applies to this person in the selected organization.
403 `model_not_allowed`	The requested model isn't on the tier. The message names the tier.
429 `rate_limit_exceeded`	A request window is full. The request waits briefly, then fails if the limit hasn't cleared (Settings → Rate Limits).
402 `budget_exceeded`	A spend cap for the window has been reached. Requests fail until the window resets. The error names the window and, for a per-model cap, the model.
402 `credit_limit_exceeded`	An organization or personal credit balance has run out. See Credits.

Warn people before they hit a budget

People can set budget alerts to get an email when their daily spend passes a percentage of their tier's daily budget.

Troubleshooting

A tier shows Incomplete

One of the four required background models, the default main-agent model, or (with Ultra-Plan on) the plan revisor model isn't set. Edit the tier and set them.

"… must be one of this tier's allowed models"

A background or default model isn't ticked under Allowed models. Tick it, or pick a different model.

"These are not registered models, so nothing can serve them"

The tier lists a model that was removed from Settings → Model Settings. Untick it, or add the model back.

"A tier with this name already exists"

Tier names must be unique within an organization.

The model list is empty

No models have a provider yet. Configure providers and models in Settings.