# Fund AI API Spend from a Stablecoin Treasury

> Markdown mirror of https://router.one/pay-ai-api-with-crypto for AI assistants and crawlers. Router One is an OpenAI-compatible LLM API gateway.
> Last updated: 2026-07-25

Finance tops up one Router One wallet in USDT or USDC. Engineering draws on that balance through budget-capped API keys instead of personal or corporate cards, and calls GPT, Claude, Gemini, DeepSeek, and other models through one OpenAI-compatible endpoint. Every top-up and every request lands in a history the team can reconcile.

## How a treasury-funded team runs model spend

This page covers the funding workflow. The rails themselves — supported chains, confirmation times, gas economics, and the current minimum top-up — live on one canonical page, /pay-with-crypto.

### Finance funds the wallet, not each developer

One transfer from the treasury wallet covers the whole team for the period. Nobody expenses a personal card, and nobody waits on a corporate card that does not clear for USD developer tools.

### Engineering draws on budget-capped keys

Each service, agent, environment, or client project gets its own API key with a maxSpend ceiling. The ceiling is the budget decision, enforced by the gateway instead of tracked in a spreadsheet.

### Spend stops at the cap, not at the invoice

A key that reaches its maxSpend returns HTTP 402 while the rest of the team keeps working. A retry loop in one job cannot quietly consume the quarter's budget.

### Reconciliation without provider portals

One transaction history lists top-ups alongside per-request charges with model, tokens, latency, status, and cost, so a finance review does not mean logging into several provider accounts.

## Where stablecoin funding fits best

### Teams already paid in stablecoins

If revenue and payroll already move in USDT or USDC, funding model usage from the same treasury removes an off-ramp step before engineering can ship.

### Distributed teams without a shared card

Contributors across several countries can all draw on one funded wallet through their own keys, without a single shared card number circulating in chat.

### Studios billing usage back to clients

Issue one key per client project, read that key's usage when you invoice, and build your own service on top of Router One with margins you set.

### Teams that budget by quarter

Fund once per period and split the balance across keys. Raising a cap is a dashboard change, not a new payment run.

## Clear limits

### Refunds follow one policy

Unused base credits may be refundable within 14 days according to the Refund Policy. Consumed credits, bonus credits, and payment-channel fees are not refundable except where required by law. Wallet balance cannot be withdrawn back to stablecoins and never expires.

### No wrong-chain recovery guarantee

Funds sent on an unsupported chain or token may be unrecoverable, which is standard for any on-chain deposit. Match the token and chain shown at checkout exactly.

### Compliance-aware billing

Router One frames stablecoin billing as a USDT/USDC payment option for global teams, not regulatory avoidance.

### Enterprise identity is separate

Self-serve top-ups are lightweight, while contracts, invoices, abuse reviews, or legal requests may require extra information.

## Treasury funding versus putting model spend on cards

| What a funded team needs | Router One |
| --- | --- |
| Fund model usage for a whole team at once | One stablecoin top-up into a shared USD wallet |
| Give each service its own limit | One API key per service with a maxSpend ceiling |
| Stop a runaway job before it bills | The key returns 402 at its cap; the rest of the wallet is untouched |
| Reconcile at the end of the period | Top-ups and per-request charges in one history |
| Onboard a developer without a card | Issue a key from the funded account |
| Keep the SDK the team already uses | OpenAI-compatible endpoint, one base-URL change |

## Use the funded balance from any OpenAI-compatible client

Finance funds the wallet once; each service gets its own key. The funding method does not change your SDK integration.

`.env`

```ts
# Router One uses the OpenAI-compatible Chat Completions API
OPENAI_BASE_URL=https://api.router.one/v1
OPENAI_API_KEY=sk-rk-your-router-one-key

# Claude Code — ANTHROPIC_API_KEY is not required
ANTHROPIC_BASE_URL=https://api.router.one
ANTHROPIC_AUTH_TOKEN=sk-rk-your-router-one-key
```

## FAQ

### Can a team fund AI API usage from a stablecoin treasury?

Yes. Top up one wallet with USDT or USDC. The balance is denominated in USD and every API key on the account draws from it.

### Does each developer need their own payment method?

No. Developers receive an API key. Only the account that funds the wallet touches a payment rail at all.

### Which networks and minimums apply?

Supported chains, confirmation times, gas economics, and the current minimum top-up are listed on the stablecoin top-up page at /pay-with-crypto.

### Do I need a credit card?

No credit card is required for stablecoin top-ups. A card or Alipay through one hosted checkout is available for teams that prefer that rail.

### Can I cap what a single service or client project spends?

Yes. Each API key carries its own maxSpend, rate limit, and token-per-minute ceiling, so one workload cannot spend another team's budget.

### Are unused balances refundable?

Unused base credits may be refundable within 14 days according to the Refund Policy. Consumed credits, bonus credits, and payment-channel fees are not refundable except where required by law. Wallet balance cannot be withdrawn back to stablecoins and never expires.

### Can I get an invoice?

Enterprise invoicing is available through sales. Self-serve wallet history is visible in the dashboard for reconciliation.

## See also

- Supported stablecoin networks: https://router.one/pay-with-crypto
- Stablecoin LLM billing: https://router.one/crypto-llm-api
- LLM API for AI agents: https://router.one/web3-ai-agents
- Alipay top-ups: https://router.one/alipay-llm-api
- LLM API without a US credit card: https://router.one/blog/llm-api-without-us-credit-card
- Pricing methodology: https://router.one/pricing-methodology
- Refund policy: https://router.one/refund
- Canonical page: https://router.one/pay-ai-api-with-crypto
- Models and per-model token rates: https://router.one/models (markdown: https://router.one/models.md)
- Pricing: https://router.one/pricing
- API docs (markdown): https://router.one/docs.md
- Company facts: https://router.one/facts/company.md