Agents discover, negotiate, and pay — end to end, no humans.
End to end, no humans in the loop. Your agent finds a model, gets a 402 quote, signs a USDC payment, and settles on-chain — and the gateway only claims what the provider actually delivered.
live 402 handshake · agent ⇄ gateway ⇄ escrow
No signup form. An AgentCard.
Solvela speaks the A2A protocol. An agent fetches /.well-known/agent-card.json, sends a message/send, gets back a task that says exactly what it costs, signs a USDC payment, and collects its artifacts — discovery to settlement over one JSON-RPC surface, no human in the loop.
The whole payment, watched live.
scroll the column · five beats · escrow pda 9neDHouXgEgHZDde5Sp…
discover
The agent reads Solvela’s A2A AgentCard — capabilities, models, and the x402 payment terms it will be quoted against. No human, no dashboard.
get quoted
It posts a request with no signature. The gateway answers 402 with a per-token USDC cost and a flat 5% platform fee — the exact amount, before a cent moves.
sign + deposit
The agent signs a USDC-SPL transaction that deposits the full quote into a trustless on-chain escrow. A wallet is the only credential — no accounts, no API keys.
settle
The provider streams the response. In the same transaction, the escrow claims only what was delivered to the provider — never more than the work performed.
refund
Whatever the provider did not earn refunds to the agent on-chain, atomically with the claim. Pay only for what gets delivered — verifiably, not on trust.
deposit · stream · claim + refund · same tx
Four guarantees, by construction.
One endpoint. One USDC price book. Five frontier labs.
call model="auto" and the router places the request — or name a model directly. unified per-token pricing in usdc. plus a free nvidia nim tier — 15 zero-cost nemotron models.
- 01OpenAIlive
- 02Anthropiclive
- 03Googlelive
- 04xAIlive
- 05DeepSeeklive
Multi-tenant from the base layer.
Orgs, teams, per-wallet budgets, scoped keys, and a full audit trail — first-class gateway primitives, not a bolt-on.
Organizations
Multi-tenant orgs with parent / child hierarchy. One gateway deployment serves every customer in isolation — spend, keys, and quotas scoped at the org boundary.
Teams & roles
POST /v1/orgs/{id}/teamsTeam scoping with admin / member roles. Route spend to the right wallet, enforce policy per team.
Per-wallet budgets
PUT /v1/wallets/{wallet}/budgetHard spend caps in USDC per wallet, per team, per org. Block at the gateway before the provider hits.
Scoped API keys
POST /v1/orgs/{id}/api-keysPrefix-signed keys with configurable scope, expiry, and wallet binding. Rotate without redeploying agents.
Audit log
GET /v1/orgs/{id}/audit-logsEvery request, every 402, every claim — fire-and-forget write to Postgres. Export, ingest, comply.
Usage analytics
GET /v1/orgs/{id}/statsSpend by model, wallet, org, or time window. Cost attribution at the API boundary, not the invoice.
One gateway. Two ways to settle.
Exact payments verify up front and settle after delivery; escrow deposits land on-chain first, then claim and refund settle in one transaction. Redis and Postgres are optional — the gateway degrades gracefully without either. architecture docs →
A wallet is your API key.
Sign, send, receive. That's it.
import {
SolvelaClient,
ChatRequest,
ChatMessage,
Wallet,
KeypairSigner,
} from '@solvela/sdk'
const wallet = Wallet.fromEnv('SOLANA_PRIVATE_KEY')
const signer = new KeypairSigner(wallet)
const client = new SolvelaClient({ wallet, signer })
const response = await client.chat(
new ChatRequest('auto', [new ChatMessage('user', 'hi')]),
)
console.log(response.choices[0].message.content)curl https://api.solvela.ai/v1/chat/completions …