Skip to main content
Velobase is an AI gateway that meters and bills every model call to your end-customers. Point your OpenAI- or Anthropic-style SDK at https://api.velobase.io/v1, then add one header (X-Velobase-Customer: <user-id>) that says which customer to bill. Each call is metered against that customer’s wallet, with the per-call cost returned on the response. It is the per-customer wallet, ledger, and rate-limit layer that OpenRouter leaves you to build yourself. The same wallets also work as a billing ledger (freeze, consume, deduct), so you can meter work you price yourself such as image generation or agent runs.

​
Core Capabilities

Keep your existing SDK. Change the base URL to https://api.velobase.io/v1, add the X-Velobase-Customer header, and every model call is billed to that customer. Model-agnostic: route deepseek/deepseek-v4-pro, anthropic/claude-opus-4.8, and more through one endpoint.
Every end-customer has a wallet and an immutable ledger. Fund the wallet, and calls are gated and metered per customer, with the cost returned on each response header (x-velobase-cost-cents, x-velobase-balance-credits).
Freeze an estimated amount before an AI task, then consume the exact amount after. Amounts are explicit (amount_usd, amount_cents, or amount_credits, where 1 USD = 100 cents = 1,000,000 credits). Zero risk of negative balances.
Thousands of deductions per second without race conditions. Manage everything over REST or the Python and JavaScript SDKs.

​
Let’s Build

Don’t read about it, build with it. Point your OpenAI SDK at the gateway, or make your first billing call directly.

Models (OpenAI / Anthropic)

Route model calls through Velobase and bill each one to a customer.

Quickstart

Make your first API call in under 5 minutes.

Funding a wallet

Fund a customer wallet with POST /v1/customers/deposit, set validity periods, and manage balances.

Tutorial: meter your app

End to end: key, fund a customer, billed call, reconcile.