▲ OpenAI-compatible API · Robinhood Chain

Know.Verify.Route.

Inference routing with verified transparency. Reach hundreds of models with one API key and one USDG balance, and get a signed receipt that proves who served each call and what it cost.

No blind trust. Trust through cryptographic proof.

Read the docs

Or try any model and its tools on one page →Read VEIL, the privacy protocol, and its open spec →

$Verify CAPublished at launch

Route #1042Simulated

model: llama-3.3-70b
provider: Quarry Compute
bond: 10,000 USDG ✓
canaries: pass 12 / 12
lane: TEE attested ✓
latency: 284 ms
tokens: 312
cost: 0.000061 USDG
receipt: ed25519 7c1e…a90b

Robinhood Chain · 4663Block · 76,503,652Block time · 0.10 sSettlement · USDGReceipts · Ed25519Robinhood Chain · 4663Block · reading…Settlement · USDGReceipts · Ed25519

GPT-6.1 Sol Pro$2.00 / 1M in◆GPT-6.1 Sol Pro (batch)$1.00 / 1M in◆GPT-6.1 Sol$2.00 / 1M in◆GPT-6.1 Sol (batch)$1.00 / 1M in◆Claude Sonnet 5.5$2.00 / 1M in◆Claude Sonnet 5.5 (batch)$1.00 / 1M in◆Perceptron Mk1.5$0.15 / 1M in◆Ember-1$3.00 / 1M in◆GLM 5.3 Prime$2.80 / 1M in◆Qwen3.8 Max Prime$4.00 / 1M in◆Aion 3.5 Mini$0.70 / 1M in◆Aion 3.5$3.00 / 1M in◆Solar Mini 4$0.05 / 1M in◆Command A+$0.30 / 1M in◆GPT-6 Luna Pro$0.10 / 1M in◆GPT-6 Luna Pro (batch)$0.05 / 1M in◆

Catalog◆Reading live models◆Know◆Verify◆Route◆

1key

One API key reaches every model in the live catalog.

Know

1USDG

One USDG balance on Robinhood Chain pays for all of it.

Settle

10kUSDG

Bond each provider posts before it may serve traffic.

Verify

4checks

Bond, canary, signed receipt and TEE attestation per call.

Proof

Protocol design values. Bonds and canaries go live with provider onboarding; see the roadmap.

Features / what a route proves

Every call should
arrive with proof.

Routing, settlement, verification and privacy in one layer. Keep your SDK and gain a receipt, a budget and evidence about who served you.

Verify Route

The verified routing layer

Hundreds of models, many providers, one route you can check. Know where a call went, what it cost and why it can be trusted.

Open API

Your client, unchanged

Keep the chat-completions shape your code already speaks. Swap the base URL and the key; streaming and tools behave as before.

USDG balance

One balance for every model

Fund once in USDG on Robinhood Chain and spend it on any model. Withdraw what you do not use.

Signed receipts

Proof that travels with the answer

Each response carries an Ed25519 receipt: model, provider, tokens, cost and hashes of the request and reply. Roots are anchored on Robinhood Chain so anyone can check them later.

Provider bonds

10,000 USDG at stake

A provider bonds 10k USDG before it serves live traffic. Broken promises cost money, on evidence.

Quality canaries

Tested around the clock

Automated canary prompts check every served model for swapped weights, quantization and empty replies.

TEE attestation

Privacy you can check

Private lanes only reach hosts whose enclave quote was verified minutes ago. The quote hash lands in your receipt.

Agent payments

HTTP 402 for agents

An agent with no account gets a price, pays from its wallet and retries with the payment proof.

Fallback routing

The request keeps moving

Filter by price, speed, context and data policy. A provider that fails health checks or canaries drops out of the pool, and the next verified one answers.

Virtual keys

A budget per workload

Every key carries its own model allowlist, rate limit and spend cap.

Open telemetry

Usage in your own tools

Export spans and usage records to the observability stack you already run.

Team controls

Shared, not shared-out

Roles and budgets for everyone building on the same workspace.

Public registry

Every measurement on record

Attested endpoints and their software changes kept in a public log.

Know the model · Verify the provider · Route the call

Read how each check works →

Route types

One request.
Four routes.

The same request body can take an open lane, an attested private lane, a verified-only lane or an agent's pay-per-call lane. Pick it with a model suffix, a header or a key policy.

Explore models

chat/completions

const res = await vr.chat.completions.create({
  model: "meta-llama/llama-3.3-70b-instruct",
  messages,
  provider: { sort: "price", allow_fallbacks: true },
});

res.route.provider;     // who answered
res.usage.cost;         // what it cost, in USDG
res.receipt.sig;        // Ed25519 over the whole call

01 Know

catalog, price, provider

02 Verify

bond, canary, attestation

03 Route

served, signed, anchored

The Flow

Three checks.
One request.

Point your client at the router and keep your code. Every call passes through Know, Verify and Route, and comes back with the proof of each.

Step 01 · Know
Pick a model.
Search the live catalog, compare prices and context, then send the request shape you already use.
model · provider{} · budget
Step 02 · Verify
Check the provider.
Before a call is routed, the provider's bond, canary record and, on private lanes, its enclave quote are checked.
bond ≥ 10k · canary ✓ · tee ✓
Step 03 · Route
Keep the receipt.
The best verified provider answers. Usage, cost and hashes come back signed, and roots are anchored on-chain.
ed25519 · merkle · 4663

Verify / bonds and canaries

Trust is posted,
not promised.

Providers lock money behind what they claim to serve. Canary prompts test every model they host, and each result is kept as evidence before any penalty is proposed.

Provider bonds
10,000 USDG per provider, posted on Robinhood Chain. Reliability has a price, and failures leave a trail.
Quality canaries
Automated tests compare the declared weights, quantization and quality, with a dispute window before any slash.

Evidence log · illustrationprov_4c19 · hourly

09:00:02passweights fingerprint · llama-3.3-70bfp8 = fp8
09:00:05passexact-answer canary set12 / 12
09:00:09passempty-reply rate · 24h0.03%
09:00:14warnp50 latency drift · 1h+19%
09:00:31passreceipt root anchored0x2d7a…c4e1
09:01:06failweights fingerprint · qwen3-32bbf16 ≠ int4
09:01:06failcanary replies mismatched3 of 3
09:01:08openslash proposal · 25% of bond72h dispute

Provider bond10,000 USDG

At stake in dispute2,500 USDG

01
Evidence
02
Proposal
03
72h dispute
04
Slash or refund

POST /api/v1/keys · example4 / 8 on

{
  "name": "research-agent",
  "limit": 300,
  "limit_reset": "monthly",
  "rpm": 600,
  "tpm": 400000,
  "allowed_models": ["qwen/qwen3-32b", "deepseek/deepseek-r1"],
  "verify": null,
  "lane": "standard",
  "team": null,
  "expires_at": null
}

Gateway / policy per key

Every control on.
Any control off.

Policy belongs to the key, not your code. Require verified providers, force the attested lane, cap the spend, and switch off whatever you do not need.

Bring your own workflow
Keep your SDK, name your providers, set fallbacks. Caching and guardrails are opt-in.
Built for autonomous agents
Virtual keys, spend caps and rate limits draw a boundary around each workload.

Privacy / TEE attestation

Private lanes,
proven by hardware.

An attested request goes only to a host whose enclave evidence was checked minutes ago. If the evidence is missing or stale, the request fails closed instead of falling back.

Attested private lane
Only freshly attested TEE hosts qualify. The quote hash is written into the receipt.
Declared data policy
Read each provider's data policy before routing, and see which parts are proven and which are only declared.

See what the router has verified about a provider

Private lane · examplefail-closed

Request :attested

Quote verified

Route selected

Receipt signed

request: pending
tee: pending
nonce: pending
quote: pending
freshness: pending
data policy: pending
receipt: pending

Verifying attestation…

Case study / an audited agent

From one call
to a checked receipt.

An example agent workflow: a research agent that must prove to its operator which model answered, what it cost and that the host was attested.

The workflow

Your request stays the same.
Your evidence gets a paper trail.

The agent calls a model through Verify Route with a verified-only key. The router checks the provider's bond and canaries, routes the call, signs the receipt and anchors it. The operator checks the signature in a browser, without asking anyone.

Read the case study

Illustrative receipt

Verify Routegen-2027114

model: llama-3.3-70b
provider: attested host
tokens: 142 in · 88 out
bond: 10,000 USDG
canary: pass · 24h
settlement: USDG
anchor: chain 4663
cost: 0.00004112 USDG

sig ed25519 · 9Qx4b…Tz0= · key 7f21ac03

Roadmap / build status

Know first.
Then prove it.

Stage one runs on this site today. The verification stages ship in order, and nothing below is live until it says so. No release dates are promised.

01 Live

Know

Live model catalog, wallet sign-in on Robinhood Chain, USDG balance reading and the public docs.

02 Building

Verify

Signed receipts, a browser receipt checker, canary suites and the public evidence log.

03 Next

Bond

Provider bonds of 10k USDG on Robinhood Chain, disputes with a 72-hour window, first bonded providers.

04 Planned

Attest

TEE-attested private lanes, the VEIL protocol, blind credits and the attested endpoint registry.

Token launch on Robinhood Chain, then provider bonds open to the first operators.

About Verify Route

Know the model.
Verify the provider.
Route the call.

Verify Route is an inference router on Robinhood Chain. The familiar API gets you in the door. What keeps you is evidence: bonded providers, tested models, signed receipts and attested hardware.

An answer is only as good as your ability to check where it came from.

Which provider served it? Was that the model they claimed? What did it cost? Could anyone else read the prompt? Routing, USDG settlement, receipts and attestation checks answer those questions in the router, with bonds and anchors on Robinhood Chain.

Read the documentation

Built for developers

The shape you know.
The proof you lacked.

Keep your request shape. Point the client at /api/v1 and use a Verify Route key. Streaming, tools, structured output and provider preferences behave as expected.

Try the console API documentation

Quickstart · node

// Two lines change: the base URL and the key.
const client = new OpenAI({
  baseURL: process.env.VERIFYROUTE_BASE_URL, // "https://verifyroute.tech/api/v1"
  apiKey: process.env.VERIFYROUTE_API_KEY,   // "vr-live-…"
});

const answer = await client.chat.completions.create({
  model: "meta-llama/llama-3.3-70b-instruct",
  messages: [{ role: "user", content: "Hello, Verify Route." }],
});

answer.receipt; // signed, itemized, checkable

Know.Verify.Route.

Every call shouldarrive with proof.

The verified routing layer

Your client, unchanged

One balance for every model

Proof that travels with the answer

10,000 USDG at stake

Tested around the clock

Privacy you can check

HTTP 402 for agents

The request keeps moving

A budget per workload

Usage in your own tools

Shared, not shared-out

Every measurement on record

One request.Four routes.

Three checks.One request.

Pick a model.

Check the provider.

Keep the receipt.

Trust is posted,not promised.

Provider bonds

Quality canaries

Every control on.Any control off.

Bring your own workflow

Built for autonomous agents

Private lanes,proven by hardware.

Attested private lane

Declared data policy

From one callto a checked receipt.

Your request stays the same.Your evidence gets a paper trail.

Know first.Then prove it.

Know

Verify

Bond

Attest

Know the model.Verify the provider.Route the call.

The shape you know.The proof you lacked.

Every call should
arrive with proof.

One request.
Four routes.

Three checks.
One request.

Trust is posted,
not promised.

Every control on.
Any control off.

Private lanes,
proven by hardware.

From one call
to a checked receipt.

Your request stays the same.
Your evidence gets a paper trail.

Know first.
Then prove it.

Know the model.
Verify the provider.
Route the call.

The shape you know.
The proof you lacked.