Providers

AI Gateway Custom Pricing

Applies to
Gatewayruntime for API, AI, and MCP gateways
Hosting
Managed EdgeManaged DedicatedSelf-Hosted

The AI Gateway prices every request from Zuplo's model catalog, which lists each vendor's published per-token prices. If you've negotiated different rates with a vendor—a committed-use discount, an enterprise contract, or credits—set those prices on the provider so the gateway uses what you actually pay.

A price you set applies everywhere the gateway computes cost:

Prices apply to new requests within about a minute of saving. Setting a price doesn't redeploy your gateway.

What you can price

You can set a price for any rate the catalog lists for a model on a built-in provider:

RateWhat it prices
InputPrompt tokens
OutputGenerated tokens
Cache readInput tokens served from the provider's prompt cache
Cache write (5 minute)Input tokens written to a cache entry that lasts five minutes
Cache write (1 hour)Input tokens written to a cache entry that lasts one hour

Models that charge more above a prompt-size threshold also have long-context rates. Those keep Zuplo's list prices.

A rate the catalog doesn't list for a model, such as a 1-hour cache write on a model without one, can't be priced.

How prices apply

Prices belong to a provider, not to your whole project. Two providers for the same vendor can carry different prices: for example, anthropic and anthropic-2 with API keys under two different contracts. The gateway prices each request at the rates of the provider named in its model reference, so anthropic-2/claude-sonnet-5 uses the prices on anthropic-2.

For each rate, the gateway uses your price when you've set one and Zuplo's list price otherwise. A rate you leave unset follows the list price, including future changes to it. Set only the rates your contract changes.

Deleting a provider deletes its prices. A provider you create later with the same name starts at list prices.

Custom providers don't use the catalog. You enter their per-token costs on each model when you add it, so there's no list price to override.

OpenRouter

OpenRouter reports the cost of each request itself, and the gateway records that figure instead of computing one from prices. A price you set on an OpenRouter provider applies only to a request whose response carries no cost.

Set prices in the portal

Setting prices requires the same Edit permission as managing providers.

  1. Open Settings → AI Providers in your AI Gateway project in the Zuplo Portal.

  2. Click Edit next to a built-in provider.

  3. In Available Models, find the model and enter your price in a price cell. Prices are per 1M tokens. An empty cell shows Zuplo's list price as its placeholder; leave it empty to use the list price.

    A model with at least one price of your own shows a Custom price badge. To return every rate on that model to list prices, click Reset. The change takes effect when you save.

  4. Click Save.

Import or export prices

To set many prices at once, or to keep them in a spreadsheet, use the Import / Export menu beside Available Models when you edit a built-in provider. The file can be CSV or JSON. Prices in the file are in dollars per 1M tokens, the same unit as the price cells.

  • Export CSV and Export JSON download the provider's models with their prices. An exported file is a ready template for an import.
  • Import reads a CSV or JSON file and fills in the price cells. Review the summary above the table, then click Save to apply the prices. Nothing changes until you save.

A file has one row per model, with these columns:

ColumnWhat it sets
modelThe model name. Required.
input_per_1mInput price
output_per_1mOutput price
cache_read_per_1mCache read price
cache_write_per_1mCache write (5 minute) price
cache_write_1h_per_1mCache write (1 hour) price

Only model is required. An empty cell leaves that price unchanged, so a file can carry just the prices you want to change. For example, this file sets the input and output prices for one model and the cache read price for another:

Code
model,input_per_1m,output_per_1m,cache_read_per_1m,cache_write_per_1m,cache_write_1h_per_1m claude-sonnet-5,2.4,12,,, claude-haiku-5-5,,,0.08,,

The same prices as JSON:

JSONCode
[ { "model": "claude-sonnet-5", "input_per_1m": 2.4, "output_per_1m": 12 }, { "model": "claude-haiku-5-5", "cache_read_per_1m": 0.08 } ]

A price that matches Zuplo's list price leaves the cell empty, so it keeps following the list price. A model you haven't selected under Available Models is selected for you when the file gives it a price, because only a model the provider serves is billed at a price.

The portal rejects the whole file, and changes nothing, if it has a column it doesn't recognize, a price that isn't a number of 0 or more, or the same model twice. The message names the line or entry to fix. A model the provider doesn't offer, or a price for a rate the model doesn't have, is left out, and the summary lists what was skipped.

Last modified on