ACCOUNTAVAILABLE
Wallet and key registry
Open the public dashboard, sign in with a wallet, and manage API keys. Key validation works through the account API.
Get startedZEVIO / DOCUMENTATION
One system.
Clear boundaries.
Zevio is private, verifiable inference billing: client-held notes, capped leases, and settlement anyone can audit. This guide covers the account API, the private billing protocol, and the holder compute model.
SYSTEM MAP2026
01Account & API keysAVAILABLE
02Private billing vaultAVAILABLE
03Normal vault creditAVAILABLE
04Holder compute creditsAVAILABLE
Each track has its own accounting design and release stage. This guide marks those boundaries explicitly.
WHY ZEVIO
Privacy is the product, not a promise.
Every other gateway can see your balance, your usage pattern, and your billing history, because that data sits in their database and funds their margin. Zevio is engineered so the operator cannot see it: value moves as client-held notes, spend is authorized by zero-knowledge proofs, and the only things made public are what settlement requires.
NOTES
Balances without identities
Your funds exist as secret notes you hold. The operator learns nullifiers and caps, never who owns what, never a running balance, never a history to correlate.
PROOFS
Authorization without exposure
Each spend is proven in zero knowledge: the chain verifies the note exists and the cap is covered without learning which note it was or what remains of it.
PATTERNS
No profile to sell
No subscription footprint, no card on file, no per-account usage ledger at the operator. Your spend journal lives on your machine and nowhere else.
HONESTY
Scoped, stated, enforced
Prompts do reach the model provider; that boundary is stated plainly rather than implied away. Privacy claims you can check beat privacy claims you must trust.
Controls come with it
Privacy does not come at the price of oversight. Every lease carries a hard spend ceiling, every window settles its actual usage onchain, unused value refunds automatically, and each capped lease has an emergency exit that pays out without the operator. The same design that hides your history makes the accounting publicly verifiable.
ARCHITECTURE
How the system runs.
Zevio separates the web experience, the account registry, the user-side daemon, the operator service, and the onchain vault. Each component has one responsibility and a narrow interface.
| Component | Runs | Responsibility |
|---|---|---|
| Account registry | With the web app | Sessions and API keys. Full keys are shown once; only SHA-256 hashes are stored. |
| Client daemon | Your machine, port 8788 | OpenAI-compatible inference endpoint. Holds note secrets, builds zero-knowledge proofs, keeps the local spend journal. |
| Operator service | Zevio, port 8789 | Mints capped provider keys per lease, settles actual usage onchain, and runs the escape challenger. |
| Vault contract | Ethereum | Onchain Merkle tree, escrow, caps, settlements, and emergency exits. |
Lifecycle of a request
One completion moves through six stages, from escrow to refund, and every transition lands onchain where anyone can verify it.
01
Deposit
ETH is escrowed in the vault against a secret note commitment. The value is now a private note only you can spend.
02
Open a lease
A zero-knowledge spend burns the note onchain and mints a capped lease plus an exact change note in a single transition.
03
Mint a scoped key
The operator issues a provider key bounded by the lease cap. Beyond that ceiling it is worthless, and it expires with the window.
04
Run inference
The daemon serves OpenAI-compatible requests through that key. Note secrets never leave your machine.
05
Settle
The operator anchors actual usage onchain and freezes the lease. The recorded charge is public and verifiable.
06
Refund
The unused cap returns to you as a fresh private note, ready for the next window. No claim step, no waiting period.
PLATFORM OVERVIEW
Know which surface you are using.
Zevio spans four product tracks. Their release stage matters when planning an integration.
PROTOCOLAVAILABLE
Private inference billing
Client-held notes, zero-knowledge proofs, and an onchain vault meter inference spend without exposing your balance history.
Explore the flowBILLINGAVAILABLE
Normal vault credit
A plain ETH balance in the dashboard. Deposit, pay per request at the discounted rate, and withdraw any time.
See the endpointsECONOMICSAVAILABLE
Holder compute model
Half of every trading fee becomes spendable compute credits for $ZEVIO holders, paid out hourly.
Read the modelGETTING STARTED
From visitor to an API key.
You can inspect the dashboard without a wallet. Signing in unlocks key management.
01
Open the dashboard
Visit the dashboard as a guest to inspect the account layout and empty states. No login is required to view it.
02
Connect a wallet
Sign a short-lived challenge with an EVM wallet. A successful signature creates a seven-day HTTP-only session and returns you to the dashboard.
03
Create a key
Generate an API key in the dashboard. Copy it when shown: the full value is displayed once, while the server stores only its SHA-256 hash. You can revoke it from the same view.
04
Validate the key
Call GET /api/key-info with a Bearer token to confirm the key is active and linked to your account.
KEY VALIDATION / HTTP
curl -H "Authorization: Bearer YOUR_API_KEY" https://zevio.sh/api/key-infoSUCCESS RESPONSE
{ "account": "0x…", "scope": "account" }Scope: API keys identify your Zevio account and grant access to the account API.
ACCOUNT API
A small, explicit surface.
The website exposes these account endpoints. Wallet challenges and session management are intended for the same-origin web flow.
| Method | Endpoint | Purpose |
|---|---|---|
| POST | /api/auth/challenge | Issue a short-lived message and nonce for a wallet address. |
| POST | /api/auth/verify | Verify the signed challenge and create a session cookie. |
| POST | /api/auth/logout | End the current browser session. |
| GET | /api/key-info | Return the account for a valid, active API key. |
| GET | /api/models | Live model catalog with lab pricing and the Zevio discount applied. |
An invalid or revoked key receives 401.
PRIVATE BILLING
Pay for a window. Keep the change.
The billing protocol combines client-held notes, zero-knowledge proofs, an onchain vault, and a metered daemon for inference spend.
01 / FUND
Deposit to a note
The client escrows ETH in the vault against a secret note commitment.
02 / AUTHORIZE
Prove a spend
A zero-knowledge proof spends the note and creates a capped lease plus a fresh change note.
03 / INFER
Use a lease
The Zevio daemon forwards OpenAI-compatible requests through a temporary provider key bounded by the cap.
04 / SETTLE
Return unused value
The operator records actual usage onchain. The unused cap returns to the client as another private note.
Recovery path
If a lease remains unsettled, the client can start an onchain emergency exit. A one-hour challenge window lets actual usage be accounted for before payout.
Daemon API
The daemon exposes its own API on port 8788, separate from the website’s /api/* account routes. The credit endpoints drive the normal vault; every other endpoint drives private notes.
| Method | Endpoint | Action |
|---|---|---|
| POST | /v1/deposit | Escrow ETH into a private note. |
| POST | /v1/chat/completions | Run OpenAI-compatible inference through a metered lease. |
| GET | /v1/balance | Read notes, pending leases, and the local journal. |
| POST | /v1/withdraw | Withdraw a note to an address. |
| POST | /v1/escape | Open an emergency exit for a stuck lease. |
| POST | /v1/credit/deposit/intent | Prepare a normal-vault credit deposit. |
| POST | /v1/credit/deposit/claim | Confirm the transfer and add credit. |
| POST | /v1/credit/withdraw | Withdraw normal-vault credit to an address. |
HOLDER MODEL
A separate compute-credit design.
The holder experience is a fee-funded credit stream, separate from the private ETH vault and the dashboard balance. It is live on Ethereum mainnet.
LIVE ON MAINNET
Every $ZEVIO trade pays a 1.5% fee, swept hourly and split 50/50: half funds the discount program, half becomes holder credit divided pro-rata among wallets holding at least 1,000 $ZEVIO at the sweep. Accrual is automatic, there is nothing to claim, and every payout is listed on the public leaderboard.