Can I pay for LLM API credits with USDT?

Yes. Router One supports crypto top-ups with USDT on supported networks, credited into a USD wallet balance.

Yes. Router One supports USDC top-ups on supported networks including Base and other listed chains.

Do AI agents get separate API keys?

Yes. Create separate API keys per agent, bot, team, or environment, then track and limit usage independently.

Can I set a hard budget cap before an agent spends?

Yes. Give the agent its own API key and set maxSpend on that key so a runaway retry loop cannot consume the whole wallet.

Does Router One store prompts or completions?

No. Router One does not retain request or response bodies. It stores metadata needed for billing, routing, and observability.

Is Router One an OpenRouter alternative for stablecoin-paying teams?

Yes. Router One is OpenAI-compatible and adds stablecoin top-ups, China-friendly routing, budget caps, and request traces.

LLM API gateway

LLM API Gateway with Stablecoin Billing

Router One is an LLM API gateway: one OpenAI-compatible endpoint for GPT, Claude, Gemini, DeepSeek, and more. For teams whose treasury already runs on stablecoins, you can top up the wallet with USDT/USDC alongside Stripe, WeChat Pay, and Alipay — and the AI side stays the same: budget caps, per-request traces, model/provider/token/latency/cost on every call.

Start with an API key Stablecoin top-up details

Base URL: https://api.router.one/v1
API surface: OpenAI-compatible Chat Completions
Payments: USDT/USDC, Stripe, WeChat Pay, Alipay
Controls: API keys, budget caps, usage traces

Why teams choose Router One

Stablecoin-friendly billing

Top up with USDT or USDC on supported networks when your team already manages treasury in stablecoins. The wallet balance is denominated in USD; the AI side is unchanged.

One API key for major LLMs

Route GPT, Claude, Gemini, DeepSeek, Mistral, and Llama through one OpenAI-compatible gateway instead of juggling provider accounts.

Per-key caps for agents and bots

Create separate API keys for agents, scripts, and teams, then set maxSpend on each key.

Cost and latency observability

Every request records model, provider, token counts, status, latency, and cost so agent spend is visible instead of surprising.

Common use cases

Router One is the LLM inference layer. If you're working with blockchain data, plug in your data provider (Moralis, The Graph, Dune, Alchemy, QuickNode, Etherscan, or your own indexer) — Router One does not fetch chain data itself.

Onchain analyst agents

Summarize wallet activity, protocol usage, governance events, and risk signals from your own indexed data.

DAO and community assistants

Turn proposals, forum threads, Discord logs, and treasury updates into concise briefings for contributors.

Smart contract coding workflows

Use Claude Code or Codex CLI through Router One while reviewing Solidity, tests, audits, and deployment scripts.

Telegram and Discord research bots

Build assistants that answer market and protocol questions without giving financial advice or promising trading returns.

Trust boundaries

Not an agent runtime

Router One does not orchestrate tools, wallets, workflows, or blockchain transactions. Your app or framework owns agent logic.

No prompt or completion storage

Request and response bodies are processed in real time and not retained. Billing and observability use metadata only.

Transparent wallet billing

Wallet balance is denominated in USD after top-up. Model usage deducts at posted rates from the models page.

Compliance-aware wording

Stablecoin billing is for teams that prefer USDT/USDC workflows. It is not permission to bypass laws, sanctions, or upstream model-provider terms.

Why Web3 teams use Router One instead of card-only AI billing

Need	Router One
Pay with stablecoins	USDT/USDC top-ups
Use normal SDKs	OpenAI-compatible API
Separate agent spend	API keys per agent, team, or environment
Stop runaway bots	Hard budget caps
Reconcile usage	Request traces and transaction history
Avoid prompt storage concern	No prompt or completion body retention

OpenAI SDK quickstart

Swap the base URL and keep your existing OpenAI-compatible client. Agent frameworks can use the same endpoint with per-agent API keys.

web3-agent.ts

import OpenAI from "openai";


const client = new OpenAI({
  baseURL: "https://api.router.one/v1",
  apiKey: process.env.ROUTER_ONE_API_KEY,
});


const result = await client.chat.completions.create({
  model: "auto",
  messages: [{ role: "user", content: "Summarize this wallet activity." }],
});

FAQ

Can I pay for LLM API credits with USDT?: Yes. Router One supports crypto top-ups with USDT on supported networks, credited into a USD wallet balance.
Can I pay with USDC?: Yes. Router One supports USDC top-ups on supported networks including Base and other listed chains.
Do AI agents get separate API keys?: Yes. Create separate API keys per agent, bot, team, or environment, then track and limit usage independently.
Can I set a hard budget cap before an agent spends?: Yes. Give the agent its own API key and set maxSpend on that key so a runaway retry loop cannot consume the whole wallet.
Does Router One store prompts or completions?: No. Router One does not retain request or response bodies. It stores metadata needed for billing, routing, and observability.
Is Router One an OpenRouter alternative for stablecoin-paying teams?: Yes. Router One is OpenAI-compatible and adds stablecoin top-ups, China-friendly routing, budget caps, and request traces.

Top up with USDT/USDC and call 40+ models in minutes

Start with an API key