Connect your wallet

One signature exchanges your wallet for a 24-hour session token. The dashboard never reads your private key.

No browser wallet?

The dashboard requires an EIP-1193 provider (most browser wallets inject one as window.ethereum). Without one, you can still call the proxy directly via curl following the steps in the project's landing page Coding agents section.

Spendable balance · —

— PTON

≈ $— USD · 1 TON = $— · — · —

Reserved

—

Pending consume

—

Wallet PTON

—

Wallet ETH

—

Deposit

Top up credits

EIP-3009 · gasless

Amount

PTON

You deposit 5 PTON

≈ USD $—

The proxy pulls PTON into ClaudeVault via EIP-3009 and credits your wallet — no on-chain tx from you.

Swap

Swap to credits

Route via TON

You pay Balance —

You receive

0.00 PTON

≈ USD $—

Route

USDC → ETH → TON → PTON

Slippage

Swaps route via DEX aggregator to TON, then wrap + deposit into ClaudeVault. Each step prompts a separate wallet signature.

Inference

Model

Gateway-wide · default for API keys + chat

One active model serves the whole gateway. It is the default for external API-key calls that omit a model, drives the agent chat, and is shown next to the agent name in chat.

Usage

Activity · last 30 days

Input tokens

—

Output tokens

—

Total spend

—PTON

Cache reads

—tok

Cache writes

—tok

Auth

API keys

For Claude Code / anthropic-sdk · x-api-key

ID	Name	Network	Created	Last used	Status

Outbound · x402

Pay other agents

EIP-3009 vouchers · CALL_A2A_AGENT

Your agent can spend its top-up balance to call other agents that demand payment — no separate API keys, no per-vendor accounts. Hard caps prevent runaway spend.

The same PTON balance that pays for your bot's chat now pays outbound, signed one call at a time with EIP-3009 vouchers over HTTP 402.

Operator wallet

—

checking…

Spend caps

— / — PTON

per call · session total

Receipt mode

—

facilitator off → trust upstream 2xx

Discover a peer agent

Paste a base URL. We fetch /.well-known/agent.json — no payment, no signature.

Discover any A2A-compatible agent.

Result shows the agent's skills, auth schemes, and a one-click chat prompt to invoke each skill from your bot.

Caps & facilitator Tweak limits and (optionally) point at a facilitator.

What's x402, really? A 60-second read on agent-to-agent commerce.

Why it matters

Agents are starting to charge for their work the same way humans do — per request, in real money. The old answer was "sign up, get an API key, store a secret, watch a bill." That doesn't scale when your agent might want to call ten peers it discovered five seconds ago.

x402 collapses the whole thing into the HTTP layer. A paid endpoint replies 402 Payment Required with a structured quote, the client signs a one-shot voucher, retries, and gets the response. The same PTON balance that funds your bot's inbound chat now funds outbound calls — one wallet, one budget, no per-vendor accounts.

How it works

Request. Your agent sends a normal HTTP call to a peer's endpoint.
402 challenge. The server replies with payment requirements — asset, amount, recipient, validity window, nonce.
Cap check. Local middleware compares the quote to X402_MAX_PAYMENT_PER_CALL_PTON and X402_MAX_TOTAL_SPEND_PTON. Over the cap → refuse immediately. The wallet is never asked to sign a refused payment.
Sign + retry. The operator wallet signs an EIP-3009 TransferWithAuthorization over PTON; the agent retries with the base64 voucher in X-Payment.
200 receipt. Server accepts the voucher and serves the response. We emit a X402_PAYMENT event so you can audit every outbound spend.

Trust & safety

Caps are enforced locally, before the wallet sees the request. You can't be tricked into signing a 100 PTON voucher when your per-call cap is 1.0.
Each voucher is single-use. EIP-3009 nonces prevent replay; the validity window prevents long-lived signatures from sitting around.
No facilitator by default. We trust the upstream 2xx as proof of settlement — the same model as Tokamak's inbound billing rail. X402_FACILITATOR_URL is reserved for a future verification mode if you'd rather check settlement out-of-band.
Discovery is read-only. Fetching an AgentCard never spends money. You pick which skill to invoke from chat — the CALL_A2A_AGENT action runs the paid request.