Skip to main content
GET
Use the GENGEN pricing API to retrieve the customer price catalog in a single request. Each model includes its individual pricing specifications, so you can display the rate for the applicable resolution, input type, or billing unit.

Request

Without authentication, this endpoint returns standard customer prices. To get the prices configured for your billing accounts, send your GENGEN API key in the Authorization: Bearer <GENGEN_API_KEY> header. No request body or query parameters are needed. This free request returns the full catalog without pagination and requires no positive balance. It does not reserve funds or create a generation task.
string
Optional. In Try it, enter Bearer YOUR_GENGEN_API_KEY to request your billing accounts’ prices. Include the Bearer prefix. Leave this field empty to request standard customer prices.
Accounts with a public-price display policy receive standard customer prices and the same response fields as an anonymous request, even with a valid API key. Their configured billing rates still apply to generation requests.
To include your billing accounts’ prices:

Response

HTTP 200 returns a JSON object. The example shows two models with illustrative prices. Fetch the endpoint for current values.

Using the prices

For time-priced video tasks, retrieve the successful task by ID and match usage.priceRowId to a price row for the same model. For a per-second rate, multiply usage.billableSeconds by priceUsd. A Wan 3.0 task can return:
MiniMax H3 uses three terms. Multiply billableOutputSeconds by the priceRowId rate, inputVideoDurationSeconds by the referenceVideoPriceRowId rate, and billableReferenceImageCount by the referenceImagePriceRowId rate, then add the results. BytePlus video enhancement uses a per-minute rate: multiply outputDurationSeconds / 60 by the priceRowId rate. To reproduce a historical charge, use the rates effective for that task and paying account. A later catalog request returns current prices. The account-specific rules below apply when billingScope is present. Accounts with a public-price display policy receive standard rates without payer catalogs.
  • A configured account price replaces the standard price for that specification, including when the account price is zero. Those rows omit originalPriceUsd and discountPercent; all other rows keep their standard pricing and discounts.
  • An authenticated request resolves the accounts that can pay for your API calls. models uses the preferred paying account’s prices. Shared-wallet members see the wallet owner’s prices here, including that account’s inherited public rates.
  • Shared-wallet members also receive their personal prices in fallbacks. A generation that falls back to personal payment uses those rates. The catalog follows billing priority even when a wallet has no available balance, since a free specification can still use that wallet. The actual payer is determined when the generation reserves funds, using its required amount and applicable credits. This catalog does not predict that decision.
  • A model can have several rates. Match the applicable basis and unit; do not use the first row as a universal price for that model.
  • 1M tokens means one million tokens. For a per-1,000-token display, divide priceUsd by 1,000 and label the converted unit accordingly.
  • Unit prices are not fixed quotes for a complete generation. A request can incur several usage components, and final charges depend on actual billable usage.
  • Hidden or retired models are excluded. Inclusion in this list does not replace the endpoint’s generation availability, input, or account checks.
  • Responses use Cache-Control: no-store. Fetch again when you need an updated catalog; generatedAt does not guarantee that a previously fetched price still applies.
  • The JavaScript example is for a server environment. Browser cross-origin access is restricted to the GENGEN documentation origin; call from your backend when integrating this endpoint into another website.
An invalid or malformed key returns HTTP 401. A revoked or expired key returns HTTP 403. If key validation fails because the service is unavailable, the endpoint returns HTTP 500; if pricing cannot be loaded, it returns HTTP 503. Retry service errors later. Do not treat an error response or a missing price as a zero price.