Bank account
$ 1,986,315.42
An account in your business name, to receive and send money by bank transfer.
- Local and international transfers
- Sub-accounts for teams, projects and agents
One business account for your money and your AI. Hold cash and stablecoins, spend by card, and call leading text, image and video models. Every call and every agent payment is metered and paid from your balance in real time. No new vendor contracts. No separate AI bills.
iTabb starts as a business account. Money arrives by bank transfer or as stablecoins, and leaves by transfer, by card or as a model call. It is all the same balance.
Bank account
$ 1,986,315.42
An account in your business name, to receive and send money by bank transfer.
Stablecoins
500,000.00 USDC
Hold stablecoins next to cash, and convert either way when you need to.
Cards
14 active
Virtual and physical cards for people and for agents, each with its own limit.
Together $2,486,315.42, the balance that every model call and agent payment draws on.
Every charge is a line item showing the model or payee, the team or agent, and the usage: tokens, seconds of video, or an agent's payment. Finance no longer logs in to each vendor's dashboard to export invoices, and there are no foreign card charges to reconcile.
| Date | Type | Counterparty or model | Usage | Amount (USD) | Balance (USD) |
|---|
iTabb already holds the contracts with model providers and settles with them for you. Turn on AI access and every connected model is ready.
Usually takes weeks, and starts over with every new provider.
Live the same day.
Most work does not need the most expensive model, and some work should never be sent to a cheap one. Set the model to auto and iTabb reads each task, picks the model that fits, and shows what it chose and why.
Routed to
DeepSeek
Short inputs and a fixed set of labels. A light model matches the flagship on this kind of work.
"model": "auto" returns "routed_to": "deepseek"Access to models is the easy part. These are the things that make the bill smaller and the service dependable.
When a provider slows down or goes offline, calls move to an equivalent model. Your teams and agents keep working.
Context you send again and again is cached and billed at a fraction of the price. The saving is shown on each call.
Work that can wait until morning runs overnight at a lower rate, with the same models and the same statement.
Upload a sample of real work and compare models on quality, cost and speed before you move a workload.
Card numbers, ID numbers and other personal data can be masked before a prompt leaves your account.
Each month, see which workloads could move to a cheaper model without losing quality, and what that would save.
Agents call models and pay for the tools, data and suppliers they need from a sub-account you fund. Each one works inside a mandate you set: how much it can spend, who it can pay, and when a person has to approve.
Agents use the same API as your teams, or connect over MCP to call models, check their remaining budget and request payments as tools.
Pay-per-request APIs settle over x402 in the moment. Suppliers and invoices are paid by bank transfer, card or stablecoin, each with a signed mandate the payee can verify.
Anything over the limit, or to a payee that is not on the list, waits for a named approver. Pause or revoke an agent at any time.
No monthly fee, no minimum spend, nothing prepaid to a vendor. Your funds stay in your iTabb account until a call actually uses them.
Budgets, permissions and usage live in your iTabb dashboard, managed the same way you already approve payments.
Give each team or project its own budget. When it runs out, calls stop without touching anyone else's funds.
Notify the owner and finance when the balance or monthly spend crosses a threshold you set.
Each API key is tied to a team, project or agent and a list of allowed models. Revoke it at any time.
See tokens, video seconds and agent payments by model, team and project, and export it to your finance system.
Spend across every model and every agent is combined into a single monthly invoice.
Prompts and outputs are never used to train models. You decide how long logs are kept.
The API follows the request format of the major SDKs, so migrating means changing one URL. Every response includes the amount charged and your balance afterwards, so an agent always knows what it has left.
api.itabb.ai/v1/chat/completions, video at /videos, agent payments at /agent/paymentsmcp.itabb.ai"model": "auto" and the response names the model chosen in routed_to402 when funds run low, naming the budget that is shortcurl https://api.itabb.ai/v1/chat/completions \ -H "Authorization: Bearer $ITABB_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "model": "claude-sonnet", "messages": [ { "role": "user", "content": "List the payment terms in this contract" } ] }'
{
"id": "chatcmpl_7Hq2xV",
"model": "claude-sonnet",
"usage": {
"input_tokens": 3120,
"output_tokens": 486
},
"billing": {
"charged": "0.02",
"currency": "USD",
"balance_after": "2486315.42",
"sub_account": "R&D"
}
}One account for cash, stablecoins, cards and AI. Book a demo and we will set it up around how your team works.