Everything for managing your account, credentials, and usage in one place - your organization and projects, API keys, authentication, usage and logs, and billing.
Everything for managing your account, credentials, and usage in one place - your organization and projects, API keys, authentication, usage and logs, and billing. Sign in at the ZeroGPU dashboard.
An organization is your top-level container - your team or company. A project scopes the workloads you’re running; use separate projects for dev, staging, and production. Each project is isolated: its own API keys, its own usage, its own logs.
Organization
Project
Use
my-company
production
Live traffic
my-company
staging
Pre-release testing
my-company
development
Local experiments
Switch between projects, create new projects, or create new organizations from the navigation dropdown.
Always separate dev from production. A leaked dev key should never be able to touch your production traffic.
Create, rotate, and revoke the credentials your requests authenticate with. Issue a separate key per environment.Keys follow a one-way lifecycle and use the zgpu- prefix:
Created (shown once) -> Active -> Revoked (permanent)
Action
What happens
Create
A new key is generated and shown once, in full
View
See masked keys and their creation dates
Revoke
The key is disabled immediately; it cannot be undone
Rules of thumb:
One key per environment - dev, staging, and production each get their own.
Rotate on a schedule - create the new key, deploy it, then revoke the old one.
Revoke immediately if exposed - don’t wait.
The full key is only displayed once, at creation. Copy it then and store it securely - if you lose it, revoke it and create a new one.
Every request needs two headers: x-api-key (your API key) and x-project-id (the project the request runs in). A 401 means a bad API key; a 403 means a bad project ID.
API keys belong in server-side code only - never in frontend JavaScript, mobile apps, or version control. To call from a browser or mobile client, proxy the request through a server you control. See Production patterns.
Usage shows token counts, request volume, and latency trends. Logs show every request with its model, status, latency, and timestamp.
Usage
Real-time trends for the active project - spot cost spikes and latency regressions before they hit your bill.
Logs
The full request history - inspect, filter, and audit individual calls.
Usage metric
What it tells you
Total requests
How many API calls you’ve made
Average response time
How fast the API is responding
Input tokens
Tokens you’re sending to models
Output tokens
Tokens the models are generating
Log field
Example
Model
The model that handled the request
Status
200, 400, 401, 403, 420, 429, 5xx
Latency
Time from request to response
Timestamp
When the request was made
Use both together: Usage shows the trend, Logs show the individual requests behind it. See a spike in Usage, then filter Logs to find the requests that caused it.
Usage-based pricing per million input and output tokens, priced by model - just like frontier APIs. Each model is priced on capability, latency, and compute cost.ZeroGPU is pay as you go: API usage draws down a prepaid credit balance, with no reserved capacity or minimums.
On the Billing page
What it does
Credit balance
Your prepaid balance; API usage is paid from it
Add to credit balance
Add funds with a saved or new payment method
Auto recharge
Optionally top up the balance automatically when it runs low
Payment methods
Add, change, or remove the cards used for credit and auto recharge
Billing history
Review past transactions and their status
Compare per-model rates in the Model Catalog, and estimate spend for your expected volume with the cost calculator.
