The API is in private beta and is enabled per organization. If every request
returns
403 with the message “The ZeroGen API is not enabled for this
organization.”, contact ZeroGen to join the beta.What you can do
With the API, you can:- List the models your organization can run, each with the JSON Schema that its requests follow.
- Quote a generation before you start it.
- Create a generation in one call, wait for it to finish, read it, list your generations, and cancel one.
- Upload files, or pass
httpsURLs as inputs. - Read your key’s own access, and your organization’s balance and monthly limits.
- Rehearse all of it with a test key, on placeholder media, at no charge.
Base URL
Send every request to the following base URL over HTTPS:Content-Type: application/json. A request
body can be up to 128 KiB.
Conventions
- Field names are camelCase.
- Money is an integer number of micro-USD, in fields whose names end in
MicroUsd. One US dollar is 1,000,000 micro-USD. For details, see Billing. - Timestamps are RFC 3339 strings in UTC, such as
2026-10-21T17:04:05.000Z. - Every response carries a
Request-Idheader, such asreq_8d0f3c2b9a7e4f6d8c1b2a3e4f5d6c7b. Include it when you contact ZeroGen about a request. - Every error uses one envelope. For details, see Errors.
Versioning
Changes within/v1 are additive: new endpoints, new optional request fields,
and new response fields, error codes, and enum values. Breaking changes go to a
new version. Write clients that ignore response fields they don’t know and that
handle unknown enum values and error codes.
Next steps
Quickstart
Create your first generation and wait for its result.
Authentication
Create an API key and choose its scopes.
Test keys
Rehearse requests and failures at no charge.
Errors
Handle the error envelope and its stable codes.