Skip to main content

​
Pricing

Velobase is an AI gateway first: point your OpenAI or Anthropic SDK at https://api.velobase.io/v1 and bill every model call to an end-customer’s wallet with the X-Velobase-Customer: <user-id> header. It is also a billing ledger (freeze, consume, deduct) for work you price yourself. Velobase charges based on ledger transactions: only successful Deduct and Consume operations count. Deposits, freezes, unfreezes, and wallet queries are always free. Model gateway calls are settled against the end-customer wallet and reported back to you per request via the X-Velobase-Cost-Credits, X-Velobase-Cost-Usd, and X-Velobase-Balance-Credits response headers.
New to the gateway? See the Quickstart to route your first model call and deposit funds to a customer wallet. This page covers what Velobase bills you for using the platform.

​
What counts as a transaction?

Only two operation types are billable:
  • Deduct: a direct, one-step deduction from a customer’s wallet.
  • Consume: the second step of a staged deduction (freeze then consume).
Everything else is free: Each model gateway call (POST /v1/chat/completions, POST /v1/messages) settles its real token cost against the customer wallet and counts as one billable settlement, just like a Consume.

​
Units

Every amount field in the API is a positive integer number of credits. The conversion is fixed: 1 credit = 1 micro-USD, so 1 USD = 1,000,000 credits. There is no cents unit anywhere in the API, and unit-suffixed fields such as amount_usd, amount_cents, or amount_credits are rejected with an error.

​
Plans

​
Pro tiers

Pro plans come in five tiers. Pick the volume that fits, and scale up or down at any time. Upgrades take effect immediately and are pro-rated. Downgrades take effect at the next billing period.

​
Free plan limits

The Free plan allows up to 50,000 ledger transactions per month. Once the limit is reached, Deduct and Consume API calls return HTTP 429:
Deposits, freezes, unfreezes, and wallet queries continue to work normally.

​
Billing cycle

  • Each organization has a single billing subscription.
  • The billing period is calendar-monthly from the date of subscription creation.
  • Usage is tracked per organization across all projects. The dashboard shows a per-project breakdown under Usage.
  • Pro overage is billed at the end of each cycle.

​
Tracking your usage

The project dashboard nav is: Overview, Models, Customers, Keys, Usage, Settings. The Usage section shows your billable ledger transactions and model gateway calls; you can also pull the same data programmatically from GET /v1/usage. If you build with the Velobase JavaScript SDK, pin a version:

​
Enterprise

For custom transaction volumes, annual invoicing, dedicated support, SSO/SAML, or custom billing rules, contact sales@velobase.io.