Zero-knowledge marketplace on Robinhood Chain
Qoura. Buy AI, stay private.
Qoura sells model and image compute for USDG. A zero-knowledge proof then separates what you bought from the wallet that paid, so the key you spend with leads nowhere.
- Block
- …
- Credits sold
- …
- ETH
- $…
Machines are becoming customers. Qoura lets them shop without a name.
An agent cannot pass a card check or fill in a sign-up form. It can hold stablecoins. Here it spends them on its own, and nothing on the chain draws a line from its purchases back to the person or company running it.
The same holds for people. A trader asking a model about positions, a lab comparing a dozen models for a paper, a startup prototyping a feature before announcing it: each leaves a trail when compute is billed to a named account. Here the trail stops at a stablecoin payment that says how much was spent, and nothing about what for.
Built for agents
From a price tag to a reply.
Five steps. Only the second one is written to the chain; the proof stands between it and everything after.
Why credits instead of an account balance? An account would have to remember who paid. A credit forgets: once it is in the tree, it looks like every other credit of the same size, and the only thing that can spend it is the pair of numbers sitting in your browser.
- 01
Browse
Every model and image renderer on the shelf shows its price per million tokens or per picture before you spend a cent.
- 02
Pay
Buy a credit with USDG. One signed message moves the stablecoin; a relayer carries it on chain, so you hold no ETH for gas.
- 03
Prove
A proof computed on your own machine shows you hold one unspent credit at that face value, and stays silent about which.
- 04
Redeem
The proof tops up an API key you generated locally. The key is born with no wallet, no email and no account behind it.
- 05
Call
Use the key with any OpenAI-style SDK by swapping the base URL. Every reply or picture is debited from its balance.
Where the privacy starts, and where it stops.
A privacy promise is only as good as the system that keeps it. This is the honest split at launch. The whitepaper goes deeper.
Hidden by the proof
Which purchase paid for a key
The proof says the credit belongs to the set of all credits bought at that face value. Nothing in it narrows the set.
Who is making the calls
A key is a random string your device made. Only its hash crosses the wire at redeem time, and no account stands behind it.
Which wallet owns the balance
Balances live on the key, not the wallet. Holding a key is the only way to spend it.
Still visible
The purchase itself
Paying moves USDG in plain sight. Anyone can look up the payer address, the sum and the block it landed in.
Timing and network
Zero knowledge says nothing about the clock or your IP. Letting time pass and switching connections before redeeming helps.
Requests on their way through
Each request passes through the gateway on its way to a supplier. Usage numbers and cost are logged; message bodies are not.
Prompts at the supplier
Whoever hosts the model processes your text. It only ever talks to the gateway, so it learns nothing about who asked.
Six kinds of buyer, one reason to stay unseen.
Agents and bots
Buy their own compute from a funded wallet. The operator who runs them stays out of the trail.
Traders
Ask models about strategy without a wallet that ties the questions to a book.
Developers
Ship features on open models through a familiar API, without handing over a card or an identity.
Researchers
Compare many models from one balance, without an account that records the whole study.
Privacy-minded people
Use AI without a profile building up behind every prompt.
Companies
Keep compute spend from mapping, line by line, onto the entity that pays for it.
Models and images first. A compute market after.
- Now
Models and images
Text and picture listings, stablecoin credits, the OpenAI-style gateway, browser proving and the credit tree held by the contract.
- Next
The agent kit
Web search and page reading on their own meters, plus an SDK and MCP server so agents can buy and spend unattended.
- Later
Many sellers
Several hosts per listing bidding on cost and latency, budget rules for bots, and a shielded payment step once the chain can carry one.
- Later
Raw compute
Code sandboxes by the second, then GPU time, fine-tuning runs and other work whose result can be checked.
Hold $QOURA, pay less for every credit.
The marketplace token on Robinhood Chain. A paying wallet that holds it gets a lower USDG quote on every face value.
Published here and on X at launch, on Robinhood Chain. Trust no other source.
- A holder price
- Hold at least the threshold of $QOURA in the paying wallet and the desk applies a discount. Threshold and percentage are contract parameters, and each buy panel prints the price you will actually be charged.
- Read once, at the purchase
- The balance is read once, inside the purchase transaction that already reveals the payer. No deposit, lock-up or staking.
- No mark on the credit
- Discounted and full-price credits of one face value are indistinguishable leaves. Redeemed keys carry no hint of the token.
Straight answers.
The questions people ask before their first credit. The docs go further.
What exactly is Qoura?
A marketplace for AI compute that settles on Robinhood Chain. You prepay in USDG for credits, convert them into balance on an API key through a zero-knowledge proof, and use that key with any OpenAI-compatible client. The point is that the key cannot be traced back to the wallet that paid.
Which models can I use?
Open and open-weight language models from DeepSeek, Qwen, Moonshot, Z.ai, Meta, Mistral, Google and OpenAI, plus several image generators and a search-grounded answer service. Prices follow the hosting suppliers live and are shown per million tokens or per picture.
Why would a proof make me private if my payment is public?
Because the proof refers to a set, not to you. It shows that the holder owns one unspent credit of a given face value without naming the leaf. Everyone who bought that same value is an equally plausible owner, so the bigger and older the set, the weaker any guess.
Do I need ETH, an account, or an email?
No account and no email, ever. With the gasless relayer on, you only sign a USDG authorization and need no ETH; without it, your wallet pays a small gas fee for approve and buy. Redeeming and calling the API need no wallet at all.
Can Qoura see my prompts?
Requests pass through the gateway to reach the model supplier, so they exist in memory for the length of the call. The gateway writes down only the listing, token counts and cost. The supplier processes the text but receives it from the gateway, never from your address or key.
What happens if I lose my browser data?
Credits and keys exist only on your side, which is what makes them private. Lose them and the balance is gone, so export the backup string after every purchase and copy each key somewhere safe.
What does $QOURA do?
Holding $QOURA in the wallet that pays lowers the USDG price of every credit. Nothing is staked or locked, the balance is read once at purchase, and discounted credits look exactly like full-price ones once they are in the tree.
How long should I wait before redeeming?
There is no fixed rule, only a trade-off. Each extra purchase at your face value makes your credit harder to single out, and every hour between paying and redeeming blurs the timing. Check the set size shown on the buy panel and in the dashboard; for routine use, waiting until a few dozen others share your amount is a sensible habit, and redeeming over a different network adds more distance.
Has the contract been audited?
Not yet. The desk contract and the redeem circuit are tested and their source is public, but no independent audit has been completed. Start with small credits.