Usage, allowances, and costs
Plan the platform fee separately from the model usage billed to your school's provider account.
Two parts of the budget#
The planned Nexus platform price is $20 per active student per month. Model usage is separate and is paid through the school's configured provider account. Confirm your school's contract and billing setup before a rollout.
The website calculator lets you enter student count and an estimated monthly provider cost per student. That estimate is your planning assumption. Actual usage depends on requests and provider pricing.
Read model prices#
Compare the input and output prices shown for the models in the school catalog. Prices are usually expressed per million tokens. Input includes the prompt and context; output is the generated response. Some providers charge separately for cached input, reasoning, search, or other tools.
Use the provider's current billing record for the final charge.
Set an allowance#
School operators can read the allowance status and configure the school allowance policy. Use the usage summary to track the recorded costs and limits. Test the behavior near a limit with a controlled account before inviting a whole school.
Allowance enforcement is a workspace control. It does not replace provider-side budget limits or the provider's billing record.
Account for comparison and tools#
A three-model question creates three model requests. Research, image generation, voice, and connected actions can have separate provider costs when enabled. A small initial pilot gives you a better estimate than assuming every student will use the same amount.
When usage is blocked#
Check the school allowance, approved model list, and provider account status. Students should ask a teacher or operator for help. Avoid retrying the same request repeatedly until an operator understands the cause.