Model metadata
The four fields that define a registered model's behavior and cost.
When you register a model the platform doesn't know in advance, you provide four values. Two govern what fits in a call; two govern how much it costs.
Catalog models come with these values already filled in. You only enter them manually when adding your own model or a new variant.
The fields
| Field | Unit | What it determines |
|---|---|---|
Max Input Tokens | tokens | The size of the context window, adding up prompt, history and retrieved passages. |
Max Output Tokens | tokens | The ceiling for a single answer. |
Input cost | USD per token | The price of each token sent to the model. |
Output cost | USD per token | The price of each token returned by the model. |
The two cost fields are entered per token, not per thousand. A model that charges US$ 0.15 per million input tokens has an Input cost of 0.00000015.
The effect of each one
Max Input Tokens is the practical limit on how much knowledge fits in an answer. An Agent with many attached Collections and long conversations hits it before anything else.
Max Output Tokens cuts the answer off when it grows too long. Answers cut off mid-sentence are usually this field, not the model.
The two cost fields don't change any behavior. They feed the consumption calculation and quota enforcement.
A wrong price here produces wrong reports and quotas across the whole organization, with no warning. Consumption keeps being counted; only the amount is wrong. Too low delays the block; too high blocks too early.
Where these values show up later
- Observability uses the costs to convert tokens into money.
- Quotas uses the same costs to decide when to block a scope.
- The Agent form uses
Max Output Tokensas the ceiling for the field of the same name, under Advanced options.
Next steps
- See the consumption calculated from these values in Observability.
- Understand how to choose between models in Providers and models.