x402 v2USDG on Robinhood ChainSigned receiptsZero retentionNo API keyTEE on the roadmap

Private AI Inference, Paid Per Request

Your prompts are the most sensitive data you own. Umbra answers them through a gateway that keeps nothing, settles each call with x402 in USDG on Robinhood Chain, and hands you a signed receipt. No API key, no account, no logs.

Nothing KeptPrompt hash and token counts in a signed receipt, nothing else
Pay Per Callx402 in USDG, settled exactly
No KeyOne signature per request
POST https://api.umbra-inference.app/v1/chat/completions
live gateway · Base Sepolia testnet
1
Request without payment
No key, no cookie, no session.
2
402 Payment Required
Price, asset, network, in the PAYMENT-REQUIRED header.
3
Check the gateway identity
Receipt signing key and attestation status.
4
Sign the authorization
USDC on Base, ceiling only. Nothing moves yet.
5
Paid retry
Signature in the PAYMENT-SIGNATURE header.
6
200 + receipt
Settled on-chain. Receipt signed. Nothing stored.
# This console talks to the real gateway at api.umbra-inference.app. # Steps 1 to 3 need nothing. Steps 4 to 6 need a wallet with test USDC on Base Sepolia, or USDG on Robinhood Chain.
x402EIP-3009Intel TDXNVIDIA ConfidentialHPKEBaseSolana

The Challenge: Every AI request you send today is tied to a name, a card and a key, and lands on a server that keeps it. Privacy you have to trust someone for is not privacy. The only workable path is proof.

Zero retention
What is Umbra?

A private inference network, paid one request at a time

Umbra, the only inference API where the payment, the compute and the deletion are all provable

What is Umbra? Umbra is a network of confidential-compute nodes serving frontier and open models. Each request is paid with x402, executed inside a hardware enclave, answered with a signed receipt, and wiped. There is no account to create and no key to protect.

100% Sealed Compute

Models run inside Intel TDX hosts with NVIDIA H100 confidential mode. The operator, the host and Umbra cannot read your prompt or the answer.

Paid in One Round-Trip

A 402, a signature, a 200. Settlement happens in the same request, in USDG on Robinhood Chain, with no checkout and no balance to top up.

∞

No Minimum, No Month

One short answer costs a fraction of a cent. There is no subscription and no unused credit.

Any Model, One Endpoint

Frontier and open weights behind OpenAI and Anthropic compatible routes. Streaming, tools and vision unchanged.

Ready to send a request nobody can read?

Fund any wallet with USDG on Robinhood Chain and make your first paid call in under a minute.

Features

Everything a request needs, nothing it should leave behind

Payment, compute and proof in one connected flow with Umbra

Umbra Protocol

The foundation. HTTP 402 carries the price, the asset and the enclave quote. Your client signs an EIP-3009 authorization for a ceiling, retries once, and the node settles exactly what the answer cost. The "upto" scheme meters streamed output to the token.

x402 v2"exact" and "upto"USDGRobinhood ChainBase Sepolia (test)
POST /v1/chat 402 · maxAmount 0.012 PAYMENT-SIGNATURE 200 · settled 0.004317

Umbra Enclaves roadmap

The compute layer we are building toward. Today the gateway runs on conventional hardware and keeps nothing by design; the receipt says so with attestation.tee = null. The next step moves umbra-gateway into Intel TDX hosts with NVIDIA confidential GPUs, so the quote in every 402 proves which build will see your prompt, and your client can refuse to pay anything else.

Intel TDXNVIDIA H100 CCReproducible buildsOpen source gateway
umb-fra-02 · claude-fable-5.1attested$50.0
umb-ams-01 · gpt-6-astraattested$50.0
umb-sin-01 · gemini-3.8-flashattested$4.13
umb-iad-02 · llama-5-70battested$0.92
umb-cdg-01 · deepseek-v4-proattested$1.98

Umbra Receipts

The proof layer. Every answer carries the enclave measurement, a hash of your prompt, the exact amount settled and a signature produced after the request's memory pages were zeroed. If the wipe signature is missing, the client treats the response as untrusted.

MeasurementWipe proofPrompt hash onlyOn-chain tx
verified PAYMENT-RESPONSE scheme "upto" network "eip155:8453" authorized 0.012000 USDC settled 0.004317 USDC tx 0x9c1e…b7a0 measurement mr:4f0a9d…e2c1 prompt sha256:3d8f…11ac tokens 612 in · 188 out retained 0 bytes wipe_sig ed25519:ab41…90ef
Live network

Inspect the capacity. Watch the settlements.

Umbra, the only inference network you can audit before you pay

01.02.03.

One gateway, fully inspectable

The gateway publishes its payment configuration, its receipt signing key and its attestation status at a well-known URL. Everything on the right is fetched live from it when this page loads.

GET /.well-known/umbra.jsonGET /v1/modelsOpen source
Gateway status fetching…
FieldValue
statuscontacting api.umbra-inference.app…

What a settlement looks like

Each paid request settles on-chain for the amount in the receipt. Addresses are the only identity the gateway ever sees, and the record holds a prompt hash, never the prompt. The feed on the right is sample activity, not live data.

Exact amount, never the ceiling
Failed answers settle nothing
Metadata deleted after 7 days
Sample settlements illustrative

Know the price before you send

Prices are Anthropic list prices per million tokens plus the protocol fee, fetched live from the gateway catalogue. The ceiling you sign is in the 402; with "upto" only the tokens actually produced are settled.

No markup on input4% protocol feeRefund on timeout
Cost of one request
$0.0000USDC per request, settled exactly
Comparison

Why builders choose Umbra

What makes Umbra unique-in-class as the private, pay-per-request inference network

Cloud APISelf-hostedUmbra
Privacy
No account or identity
Prompts never storedRetained 30 daysOn your disks
Operator cannot read trafficYou are the operatorRoadmap: TEE attestation
Signed receipt per request
Economics
PricingCredits or invoiceGPUs up frontPer request, exact
Time to first callMinutes, after sign-up12-18 monthsOne round-trip
Long-lived secret to protectAPI keyInternal credentialsNone
Use any modelVendor onlyInternal AI team
Agents

Your agent pays for its own thoughts

Umbra works where an API key cannot be trusted.

A wallet instead of a key

Give an agent a funded wallet and a signing policy. It negotiates each 402 on its own, within caps you set once. If the wallet leaks, an attacker gets a budget, not your identity or your history. An agent can also expose its own 402 endpoint and earn USDG for its work.

Per-call ceilingHourly and task capsAgent-to-agent
research-agent-03
0x7a4c…e19d · Base
signing
$41.26USDC remaining · 1,384 calls today
Hourly cap$3.12 / $5.00
Task cap · summarize filings$0.84 / $2.00
Spend, last 24 h
Research agents
Coding assistants
Legal and health
Autonomous services
Open standards

Built on protocols you can read, not promises you have to trust

Umbra combines x402, the open payment protocol built on HTTP 402, with Ed25519-signed receipts today and hardware attestation from Intel and NVIDIA next. The gateway is open source, so what it does with your prompt is readable, not promised.

x402 v2Payment protocol
2 networksRobinhood Chain · Base Sepolia
6 modelsClaude family, live catalogue
0 bytesRetained per request
FAQ

Questions We Hear Often

Common questions about Umbra, x402 and confidential inference

x402 is an open payment protocol built on the HTTP 402 status code. A server answers an unpaid request with 402 and a PAYMENT-REQUIRED header that describes the price, the asset and the network. The client signs a payment authorization, retries with a PAYMENT-SIGNATURE header, and a facilitator settles it on-chain. No accounts, no sessions, no card forms.
The gateway holds your prompt and the answer in memory only while the request runs. It writes no logs of content and stores nothing afterwards; the receipt carries a SHA-256 of the prompt and the token counts, never the text. Today this is a property of open-source code you can read. The roadmap moves the gateway into a hardware enclave so that it becomes a property you can verify from the attestation in every 402.
The signed receipt reports the exact model id that produced the answer, as returned by the provider, together with the token counts you were charged for. Once the gateway runs inside an attested enclave, the build measurement in the 402 will bind that promise to hardware, and a client can refuse to pay any other build.
With "exact", the price is fixed before the response. With "upto", you authorize a ceiling and the node settles only the tokens it produced. A 2,000-token ceiling that returns 188 tokens charges 188 tokens. Streaming works the same way; the receipt arrives after the last chunk.
Not by Umbra. The settlement record holds the prompt hash, not the prompt. For stronger unlinkability, use a fresh address per task, or Umbra Relay, which routes the request through a mixing relay so the node never sees your IP alongside your signature.
Umbra runs a single gateway today. It settles in USDG on Robinhood Chain (mainnet, real money, the gateway facilitates its own settlements), and in test USDC on Base Sepolia so anyone can try the full paid flow for free. Prices are Anthropic list prices plus a 4% protocol fee. Independent operators on confidential hardware come after the enclave build ships.
An authorization is not a payment. If the node fails to answer, nothing settles and the authorization expires in 60 seconds. If it answers partially under "upto", you pay for what you received, and the receipt shows exactly that.
Two things: the base URL, and the fetch implementation, which you wrap with an x402 signer bound to a wallet. Model names, streaming, tool calls and vision work exactly as they do today with the OpenAI and Anthropic SDKs.

Ready to send a request nobody can read?

No sign-up. Fund any wallet with USDG on Robinhood Chain and make your first paid call now.

Send a Paid Request
UMBRA