Skip to content

Billing & Budgets

KeyMaker usage is billed monthly to the billing code your sponsor registered. Sponsors decide how their budget is split across team members, and for each member, how much goes to API budget versus chat balance. Those two behave very differently at billing time.

API budgetChat balance
Used forProgrammatic access with your API key (Claude Code, Codex, scripts)Chat in campusGenAI, using your team’s wallet
What it isA spending capA one-time transfer of funds
What gets billedOnly what’s actually used, monthlyThe full amount transferred, at month end, even if only partly spent
Unspent fundsCarry overStay with the member, who can keep using them
Can it be reversed?Sponsor can lower the capNo — once transferred, it can’t be moved back. Contact us if a transfer was made in error.
Adding moreThe Sponsor raises the capThe Sponsor funds another transfer

In practice: allocating API budget is low-risk, because you only pay for what’s used. Keep chat balances small and add more as needed.

A member doesn’t need to use the API at all. If someone only needs more chat credit, a sponsor can give them a chat balance and little or no API budget. Joining a team currently issues an API key either way.

  • Usage and cost are tracked per team. If you belong to more than one team, each team’s usage is billed to that team’s billing code.

  • Usage is billed monthly to the billing code on file.

  • Members see their own spend in the KeyMaker portal. Sponsors and administrators see team and institutional usage in the admin portal.

  • Your institution’s finance administrator routes the bill to the billing code.

  • By default, 100% of your budget is allocated to you as the sponsor. Lower your own budget with Edit Budget before you give any to a member.
  • Allocate per member on the Team Members tab, and choose how much of each member’s allocation goes to API budget and how much to chat balance.

The best estimate comes from real usage. Have members run a representative piece of their workload on a trial key, then check what it cost.

As a rough guide to monthly API spend:

Usage patternTypical monthly cost
Testing and trying things outWell under $100
Typical research coding support, selective with expensive modelsUp to about $100
Moderate ongoing developmentLow hundreds of dollars
Heavy multi-agent workflows using frontier modelsCan reach thousands of dollars

Programmatic workflows can consume far more than interactive use — a single script can make thousands of calls.

When an API budget runs out, requests made with that key return an error until more funds are allocated.

  • Team members: ask your sponsor to increase your allocation.
  • Sponsors: select Request Budget Top-Up on your team’s Overview tab. The request goes to an administrator for approval, and timing varies.

Check your spend regularly so you can ask for more before you run out.


Your interface may look slightly different depending on your institution’s deployment.