Skip to main content

LLM Gateway

A unified interface for LLMs — pay with your launch fees or wallet balance.

Access Claude, Gemini, GPT, Grok, and other frontier models through a single API. Every request is tracked, and you fund usage from your Bankr wallet — USDC, USDT, ETH or any other ERC-20, including the creator fees your token launches earn. See Credit Management for chains and limits.

LLM Dashboard

Manage your LLM Gateway at bankr.bot/llm — view usage breakdown by model, top up credits, and configure auto top-up.

Generate and configure API keys at bankr.bot/api-keys.

Why Bankr LLM Gateway?​

FeatureBenefit
Cost TrackingFull visibility into token usage and costs per request
Launch Fee FundingSpend the creator fees your token launch earns on inference, once claimed to your wallet
Flexible PaymentsPay in USDC/USDT directly, or swap in any other ERC-20
Multi-ProviderAccess models from Anthropic, Google, OpenAI, xAI, Z.ai, DeepSeek, MiniMax, Moonshot AI, and Alibaba
High AvailabilityAutomatic failover ensures your agents stay online
SDK CompatibleWorks with OpenAI and Anthropic SDKs — no code changes

See Supported Models for every model with context windows and capabilities, or run bankr llm models for the live list.

How It Works​

┌─────────────┐  ┌─────────────┐  ┌─────────────┐
│  OpenClaw   │  │ Claude Code │  │  AI SDK /   │
│             │  │             │  │ Custom Apps │
└──────┬──────┘  └──────┬──────┘  └──────┬──────┘
       │                │                │
       └────────────────┼────────────────┘
                        │
                        ▼
              ┌─────────────────┐
              │   LLM Gateway   │
              │  llm.bankr.bot  │
              └────────┬────────┘
                       │
   ┌──────────┬────────┼────────┬──────────┐
   ▼          ▼        ▼        ▼          ▼
Vertex AI  Vertex AI  OpenAI  MiniMax  OpenRouter
(Claude)   (Gemini)                    (All Models)

Routing Strategy (the typical order; every model has its own provider list, and a request falls through to the next provider on an error or a capacity limit):

  • Claude models → Vertex AI, then OpenRouter
  • Gemini models → Vertex AI, then OpenRouter
  • GPT models → OpenAI, then OpenRouter; GPT-5.2 Codex → OpenRouter
  • MiniMax models → MiniMax, then OpenRouter where the model is listed there
  • Gemma, Grok, GLM, Kimi, Qwen and DeepSeek models → OpenRouter

Data Privacy​

When a request is routed through OpenRouter (as a primary route or a failover), the gateway sends data_collection: "deny" on every request. OpenRouter is instructed never to route to upstream hosts that store or train on your prompts.

This governs the OpenRouter hop only — the upstream provider's own policies (for example, Anthropic's for Claude) still apply independently. See each provider's documentation for their data-handling practices.

For a stronger guarantee on supported open-weight models, Private Inference routes a request into a hardware-secured enclave (TEE) by appending :private to the model ID — the gateway verifies the enclave's attestation on every request and never silently downgrades.

Quick Start​

Get Your API Key

Get your LLM Gateway API key →

Base URL:

https://llm.bankr.bot

OpenAI-compatible format (/v1/chat/completions):

curl https://llm.bankr.bot/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bk_YOUR_API_KEY" \
  -d '{
    "model": "claude-opus-4.8",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

Anthropic-compatible format (/v1/messages):

curl https://llm.bankr.bot/v1/messages \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bk_YOUR_API_KEY" \
  -d '{
    "model": "claude-opus-4.8",
    "max_tokens": 1024,
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

Both formats work with every text model. See API Reference for full details.

Key Permissions

Your API key must have LLM Gateway enabled at bankr.bot/api-keys.

  • The Read Only toggle only affects the Agent API — LLM Gateway access is always available when enabled.
  • A key used only for LLM Gateway doesn't need Agent API enabled.

See API Keys for full details.

LLM Credits Required

New accounts start with $0 credits. Requests will be rejected (402) until you top up. Add credits at bankr.bot/terminal/llm?tab=credits or via bankr llm credits add <amount>. LLM credits are separate from your trading wallet — see the OpenClaw setup guide for details.

Model Discounts​

The LLM Gateway supports time-bounded discounts on individual models. When a discount is active and you're eligible, your credit deduction uses the discounted price automatically — no action needed.

Check bankr.bot/llm for active promos and your effective pricing. The /v1/models endpoint only returns discounts you qualify for; the discount field on each model includes bps, valid_from, valid_to, reason, and eligibility_scope.

Setup with Bankr CLI​

The Bankr CLI can configure your tools automatically:

npm install -g @bankr/cli
bankr login
bankr llm setup openclaw --install   # OpenClaw
bankr llm setup opencode --install   # OpenCode
bankr llm setup claude               # Claude Code
bankr llm setup cursor               # Cursor

If your LLM gateway key differs from your Bankr API key, you can set them separately:

bankr login --llm-key YOUR_LLM_KEY
# or
bankr config set llmKey YOUR_LLM_KEY

See Coding Agents for full details on each tool.

Credit Management​

bankr llm credits                   # Check balance
bankr llm credits add 25            # Add $25 credits (defaults to Base USDC)
bankr llm credits add 25 --token USDT  # Pay in USDT on whichever chain holds the most
bankr llm credits add 50 --token 0x... --yes  # By contract address, no confirm
bankr llm credits auto              # View auto top-up config
bankr llm credits auto --enable --amount 25 --threshold 5 --tokens USDC,USDT
bankr llm credits auto --disable

Top-ups are $1–$1,000, paid on Base, Ethereum, Polygon, Arbitrum, BNB Chain, Robinhood Chain, Unichain or World Chain. USDC (USDG on Robinhood Chain) is taken directly, as is USDT on Ethereum, Polygon, Arbitrum and BNB Chain; any other token is swapped first, except on Unichain and World Chain, which accept USDC only. The CLI resolves --token across Base, Polygon, Ethereum, Arbitrum and BNB Chain — the highest USD balance wins.

Auto top-up buys --amount whenever your balance drops below --threshold (at most $500), paying from up to three tokens tried in order. Usage spends granted credit first, soonest-expiring grant first, then purchased credit; a grant's unused balance lapses when it expires.

Sending credits to another Bankr user​

You can pass credits straight to someone else — funding a teammate's key, splitting a top-up, or covering an agent you run for a friend. Purchased credit moves free, and the credits land on their balance immediately.

  • From the web — open the Credits tab at bankr.bot/terminal/llm and use the Send Credits card. The transfer shows up in Credit Activity as Sent / Received on both sides.
  • From chat — ask the agent: "send $20 of my LLM credits to @username". It restates the recipient and amount and waits for your confirmation before moving anything.

On both surfaces the recipient is an X username or a 0x wallet address. ENS names aren't accepted, because the recipient has to resolve to an existing Bankr account rather than to any address.

What can move:

Credit typeRule
Purchased creditSendable free, including credit someone else sent you
Granted credit (promos, bonuses, operator grants)Sendable only with the opt-in below, and only with a 10% burn fee
Minimum$1 per transfer
Rolling 24h limit$500 sent per wallet

The recipient must already have an active Bankr account — credits can't be sent to an arbitrary address, and there's no create-on-send. Transfers are writes, so read-only API keys can't make them, and a key with a trusted-recipients allowlist can only send to addresses on it. Transfers also count against your daily spend budget alongside usage, so a transfer that would breach the budget is refused until the window drains or you raise the cap.

Sending granted credit​

By default a transfer only spends purchased credit. Turn on Use granted credits first to let the send draw on granted credit too — promos, bonuses and operator grants, including grants with an expiry date.

Granted credit carries a 10% burn fee, and it's the only slice that does:

  • The granted portion of the amount is spent first and is fee-bearing; purchased credit tops up the rest, free.
  • The fee is charged on top. The recipient always receives exactly the amount you entered; your balance is debited amount + fee.
  • The fee is burned — it isn't credited to anyone. It shows in Credit Activity as its own debit row.
  • Both the amount and the fee count against your daily spend budget.

The toggle is off by default on both surfaces. In the web Send Credits modal it previews Fee / Recipient receives / Total deducted before you confirm, and Max solves for amount + fee. In chat, if purchased credit alone won't cover a send but granted credit would, the agent quotes the fee and total deduction and sends nothing until you agree to it.

Transferable balance vs. today's allowance​

Two different numbers bound a send, and Bankr quotes both rather than collapsing them:

  • Transferable credit — your purchased (main) balance, less any not-yet-deducted usage your granted credit can't cover. A property of the balance.
  • What can move right now — that figure clamped by the $500 rolling-24h transfer cap and by your daily spend budget.

When a daily gate is what's binding, the smaller figure is a timer, not missing money: it recovers as the rolling window drains, without you buying anything.

Transfers are final

A sent transfer can't be undone. Check the handle or address before confirming.

Daily spend budget​

Your credit balance bounds what the account can spend in total. The optional daily spend budget bounds how fast it can spend it — a cap on spend in any rolling 24-hour window, across every API key on the wallet plus Max Mode and app-invoked agent runs. It's the guard against a runaway client burning a balance overnight.

Set it in the Settings tab at bankr.bot/terminal/llm; the card shows what the current window has spent. A key can't change its own wallet's budget, so a leaked key can't raise the cap it's bound by. See Daily spend budget for what the API returns while you're over it.

Next Steps​