Billing and Credits
How credits work and what costs what across the platform.
What costs what
| Activity | How it's billed |
|---|---|
| Inference calls (API) | Per token, varies by model |
| Eval judge calls | Per token (these are full LLM inferences) |
| Training compute | Per GPU-hour — H100 at $4/GPU/hr, H200 at $5/GPU/hr. Built-in recipes run 8 GPUs on a single node ($32/hr or $40/hr per node) |
Dedicated deployments currently run under a preview gate: every plan is capped at one active deployment, and per-hour deployment billing is not yet enabled. Storage (training datasets, model artifacts, trace dataset exports) is not metered.
Credits
Your account has a credit balance. All platform activity draws from this balance. Make sure you have sufficient credits before launching training runs or deploying models — both will fail if credits run out.
Checking your usage
View your current balance and usage breakdown in the Inference.net dashboard.