Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.velobase.io/llms.txt

Use this file to discover all available pages before exploring further.

​
What is Velobase?

Velobase is an open-source, high-performance billing ledger designed for AI applications. When you build AI apps, billing is hard because you don’t know the exact cost upfront (e.g., streaming LLM output). Velobase solves this by acting as a high-speed “credit bank” for your application.
Using an AI coding agent? Install the MCP server to let your agent write the integration for you — no manual setup needed.

​
How it works

1

Get an API key

Sign in at velobase.io/dashboard and generate an API key under Project Settings → API Keys.
2

Deposit credits

Call POST /v1/billing/deposit with a customer_id and an amount. Velobase creates the customer automatically if they don’t exist yet.
3

Charge for AI work

Use direct deduction for fixed-price tasks, or the freeze → consume flow for LLM calls where cost is only known after generation.
4

Track every transaction

Every operation is recorded in an immutable ledger. Query balances and audit charges in real time.

Get started in 5 minutes

Make your first API call — deposit credits and charge a customer end to end.

​
Key features

Credit Deposits

Wallet categories, validity windows, and auto-provisioning for customer balances.

Direct Deduction

Charge immediately when the cost is known upfront — image generation, fixed-price APIs.

Staged Deduction

Freeze a budget, then settle the actual cost — LLM inference, async tasks.

Immutable Ledger

Every balance change is recorded permanently with full audit trail.

​
Billing flows

Direct Deduction

Fixed cost known upfront

Freeze → Consume

Variable cost settled after

Deposits

Top up customer wallets

​
Why Velobase?

Stripe is built for subscription and invoice workflows. AI workloads need sub-second credit operations with atomic freeze-and-settle semantics. Velobase handles thousands of concurrent operations per second with zero race conditions and no negative balances.
When you freeze credits, Velobase atomically reserves them from the available balance. No other request can spend those credits while they’re frozen. After the task completes, settle the actual cost and any unused credits are returned automatically.
Every billing operation is idempotent. Retry with the same transaction_id and Velobase returns the original result without double-charging.
Yes. The direct deduction flow works for any fixed-price operation — game currencies, API rate credits, marketplace points, or anything you model as credits.

​
Explore

Quickstart

First API call in under 5 minutes

API Reference

Complete endpoint reference

MCP Server

AI coding agent integration

Dashboard

Manage customers, keys, and ledger

Idempotency

Prevent double charges

Error Handling

Error codes reference

Website

velobase.io

Dashboard

Console

GitHub

Source & issues