Docs

Getting started

1. Open any listing in the marketplace, choose a face value (smallest is $1) and approve the USDG signature on Robinhood Chain.
2. Go to the dashboard and press redeem. A proof is computed locally and a fresh key receives the balance.
3. Configure your OpenAI SDK with base URL https://qoura.xyz/v1 and the new key.

curl https://qoura.xyz/v1/chat/completions \
  -H "Authorization: Bearer qk-..." \
  -H "Content-Type: application/json" \
  -d '{"model": "gpt-oss-120b", "max_tokens": 400,
       "messages": [{"role": "user", "content": "List three risks in this plan"}]}'

from openai import OpenAI

qoura = OpenAI(base_url="https://qoura.xyz/v1", api_key="qk-...")
answer = qoura.chat.completions.create(
    model="deepseek-v4-flash",
    max_tokens=400,
    messages=[{"role": "user", "content": "Draft a release note"}],
)
print(answer.choices[0].message.content)

Billing per request equals the supplier's cost for it multiplied by the markup, debited from the key.

Pictures

Image listings answer on a separate path, still authenticated by the same key, and bill per request.

curl https://qoura.xyz/v1/images/generations \
  -H "Authorization: Bearer qk-..." \
  -H "Content-Type: application/json" \
  -d '{"model": "gemini-3.1-flash-image", "aspect_ratio": "3:2",
       "prompt": "Fog over a frozen harbour at dawn, film grain"}'

Results are inline: each entry in data holds b64_json plus its mime_type. Nothing is stored server-side, so no URLs are issued.

Automation

A script or agent with USDG can complete the full cycle unattended: discover listings at /v1/listings, pay, prove, redeem, call. Since quick pay-then-redeem sequences are easy to correlate, check /v1/credits for the size of each face-value set before redeeming. More on the agents page.

Endpoint reference

Failures return the familiar OpenAI envelope {"error": {...}}. Status 402 with insufficient_balance means the key needs topping up.

Credit mechanics

Two locally generated numbers make up a credit. Their hash, the commitment, travels with your payment; the desk contract then stores Poseidon(commitment, face) as a new leaf, taking the face value from the USDG it received. Redeeming means proving knowledge of one leaf's preimage under a root the contract recognises. The proof exposes Poseidon(nullifier), which the server records to block reuse, and the binding of your key, which decides who gets paid. Details in the whitepaper.

Privacy model

Protected

The pairing between a payment and a key. Any credit with the same face value is an equally likely source; the buy panel and the dashboard display that set size. Rare face values make small sets.

Not protected

• Payments themselves: payer, value and time live on Robinhood Chain.
• Timing correlation, especially redeeming right after paying or being the sole buyer of a value.
• Your IP address toward this site, both when redeeming and when calling.

Model traffic

Requests reach third-party suppliers via the gateway. Suppliers process content without learning your key, address or wallet. The gateway retains listing, usage counts and cost, never message bodies or images.

Rules and caps

• Qoura issues the credits; they work only on this gateway and are not a deposit with any AI lab.
• No refunds and no transfers, for credits or for key balances.
• Secrets live in your browser only. Export backups; nobody can recover lost ones.
• Omitting max_tokens caps a reply at 8,192 tokens, or lower when the balance is smaller.

Contracts

Questions