One key. Every model. Nothing sits idle.

Orbz turns the trading fees of one token, $ORBZ, into AI credits for the people who hold it. Every hour, 70% of the fees that reached OrbzVault in that hour are granted to holders, pro-rata to their time-weighted balance. Credits spend on every major model through one API key, at the model provider's list price.

Each credit lives 168 hours. Whatever is left unused when the fuse runs out buys $ORBZ on the market and burns it. A holder who uses AI every day gets it paid by the fees. A holder who never opens the app still gains, because every idle credit becomes a buyback-and-burn.

• One token. No staking, no locking, no second credit token, no order book.
• Credits are pre-funded: a grant is written only after its USDG sits in the vault.
• OrbzVault has no owner and no upgrade path. Burns are permissionless.
• Every hour prints a public receipt, and the reserve page shows the vault holding exactly what the dashboards owe.

$ORBZ has not launched yet. Everything below describes the system as it will run from epoch 0; the API opens at launch.

1. 1

   Hold $ORBZ

   Keep at least 100,000 $ORBZ (0.01% of supply) in your own wallet. Grants start at the next full hour.

2. 2

   Sign once

   Connect at use.orbz.app and sign the message "Orbz API key · chain 4663 · epoch 0". No transaction, no network fee. The signature becomes your key.

3. 3

   Paste the key

   Set the base URL and the key in your editor, agent or SDK. The API is chat-completions compatible, so existing clients keep working.

4. 4

   Work

   Credits arrive every hour and are spent oldest first. Every response carries X-Orbz-Balance, the balance the request started from.

# the two values your client needs
base_url = https://api.orbz.app/v1
api_key  = sk-orbz-0-…            # from your wallet signature, shown once

# a first request
curl https://api.orbz.app/v1/chat/completions \
  -H "Authorization: Bearer $ORBZ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "<id from /v1/models>", "messages": [{"role": "user", "content": "Plan the next task."}]}'

Rotate a key by signing the same message with a higher epoch number. The old key stops working the first time the new one is used. Anyone holding your key can spend your credits, so keep it on your server.

Epochs

An epoch is one clock hour, numbered from launch. Fees harvested during an hour are booked to that epoch's pool, in USDG, inside OrbzVault. At the top of the next hour the allocator reads the booked amount and writes grants.

Your share

Your grant for an epoch is the pool multiplied by your time-weighted balance, divided by the time-weighted balance of every eligible wallet. The time-weighted balance is your average holding across the hour, integrated block by block from $ORBZ transfer events, so a position held for five minutes counts for one twelfth of the hour.

grant(wallet, N) = pool(N) × twab(wallet, N) / Σ twab(eligible, N)

eligible  = wallets holding ≥ 100,000 $ORBZ
excluded  = the launch curve, the pool, OrbzVault, the treasury,
            the burn address and published exchange wallets

Spending and expiry

• Credits spend at the provider's list price for the model you call, with no markup.
• Grants are spent first in, first out: the oldest credit burns first, so you never lose a fresh credit to an old fuse.
• A grant expires 168 hours after it was written. An expired grant cannot be spent or revived; its USDG waits for burnExpired().

What a credit is, and is not

A credit is

$1.00 of model usage at list price, tied to the wallet that received it, valid for 168 hours

A credit is not

a token, an NFT, transferable, redeemable for cash, ETH or USDG, or a return on holding

Traders pay 2% on every $ORBZ trade: the launchpad's 1% base fee plus a 1% creator tax that is fixed at launch and cannot change. The launchpad passes 70% of its base fee to the creator-fee recipient, which is OrbzVault from the first block. So 1.7% of all volume reaches the vault, before and after graduation.

Of every trade

Of what reaches the vault

Per $100,000 of volume

Traders pay (2%)

$2,000

Launchpad keeps

$300

OrbzVault receives

$1,700

Credit pool (70%)

$1,190

Treasury (30%)

$510

If holders spend 15%

$178.50 becomes AI, $1,011.50 buys and burns $ORBZ

If holders spend 50%

$595 becomes AI, $595 buys and burns $ORBZ

If holders spend 100%

$1,190 becomes AI, nothing is burned

Illustrative arithmetic per unit of volume, not a forecast. Grants follow real volume hour by hour and are never promised.

OrbzVault is the creator-fee recipient and the only place the credit pool exists. It has no owner and no upgrade path. Its parameters are immutable at deploy: the $ORBZ, USDG and WETH addresses, the launchpad escrow, the router, the treasury, the settlement address, the operator, the 7000 bps split, the 3600-second epoch, the 168-epoch expiry and the 25 bps caller tip.

harvest()

Anyone. Claims escrowed ETH, swaps to USDG within a TWAP bound, sends 30% to the treasury and books 70% to the current epoch.

withdrawForUsage(epoch, amt, root)

Operator only. Pays the fixed settlement address for used credits, oldest epoch first, never above that epoch's remainder. root is the Merkle root of the requests it pays for.

burnExpired(epoch)

Anyone, after hour 168. Swaps the remainder USDG → ETH → $ORBZ, burns it, tips the caller 0.25% capped at $2.

freezeOperator()

Guardian only. Stops usage withdrawals. It can never move funds.

Invariants, tested on a mainnet fork

1. 1

   I1

   Vault USDG equals the sum of open epoch remainders, within dust.

2. 2

   I2

   Usage withdrawn from an epoch never exceeds what it booked.

3. 3

   I3

   burnExpired reverts before epoch + 168 hours.

4. 4

   I4

   A burned epoch can never be withdrawn again.

5. 5

   I5

   Every harvest splits exactly 70 / 30 of the swapped USDG.

6. 6

   I6

   Swaps revert if the price moves more than 3% from the 30-minute TWAP.

7. 7

   I7

   Total supply of $ORBZ drops by exactly the burned amount in every burnExpired call.

No function sends USDG anywhere except the settlement address (used credits), the treasury share, or the burn path.

Three pipes feed the same public burn path. Each one swaps USDG to ETH to $ORBZ and calls burn() on the token, so total supply drops by exactly the amount burned. Every burn writes a row to the receipts feed with its transaction.

1. 1

   Expired holder credits

   From launch + 168 hours: every epoch past its fuse burns whatever is left in it.

2. 2

   Paid top-up margin

   V2: non-holders pay list price + 5% in ETH or USDG; the 5% buys and burns $ORBZ.

3. 3

   Idle treasury budget

   V2: demo budget the funnel did not use can be routed into the same burn.

// callable by anyone once epoch + 168h has passed
OrbzVault.burnExpired(epoch)
  → swap remainder USDG → ETH → $ORBZ   (reverts beyond 3% of the 30-min TWAP)
  → $ORBZ.burn(amount)                  // totalSupply drops
  → tip the caller 0.25%, capped at $2

Our keeper calls burnExpired every hour. If it ever stops, anyone can call it and collect the tip, so nobody, including us, can stall a burn. Large remainders on a thin pool burn in slices to respect the price bound.

Every epoch produces one receipt row and one receipt image, published at orbz.app/receipts and exportable as CSV.

Fees in

USDG harvested and booked for the hour

Split

treasury 30%, credit pool 70%

Grants

number of wallets credited and the total granted

Usage

credits spent and settled to providers, with the settlement Merkle root

Burn

remainder at hour 168, $ORBZ bought and burned, the transaction and the caller tip

The reserve equation

The reserves page reads OrbzVault's USDG balance from the chain every block and compares it with the open, unexpired credits shown on every dashboard. The two must be equal. Credits are pre-funded, so there is never a credit without USDG behind it.

Grants are strictly pro-rata; tiers never change what a credit is worth. They raise rate limits for heavier users and unlock cosmetic badges.

Visitor · hold 0

20 demo messages a day on a small model; receipts, reserves and docs

Orbit · 100,000 (0.01%)

hourly grants; 60 requests / min, 8 concurrent; usage dashboard and fuse view

Ring · 1,000,000 (0.1%)

120 requests / min, 16 concurrent; Ring badge on share cards

Sun · 10,000,000 (1%)

240 requests / min, 32 concurrent; first look at new models; name on the holder wall

What $ORBZ never does

• Pay out cash, ETH or stablecoins to holders.
• Make one holder's credit worth more than another's.
• Need staking, locking or a second token.
• Let the team move the credit pool.
• Promise a fixed amount.

Ticker

$ORBZ

Chain

Robinhood Chain, chainId 4663

Supply

1,000,000,000, fixed, no mint

Launch

100% fair launch on the Robinhood Chain launchpad bonding curve

Graduation

4.2 ETH on the curve, then a Uniswap v4 pool

Team allocation

None. No presale, no private round

Dev buy

At most 2% of supply, wallet disclosed before launch

Trader fee

2%: launchpad 1% base + 1% creator tax

Creator tax

1%, fixed at launch, immutable

Fee recipient

OrbzVault: no owner, no upgrade, source verified

Contract address

Published on orbz.app and our official channels at launch, nowhere else

Public, no key

GET /v1/models

the model catalogue with list prices

GET /api/stats

24-hour and all-time counters

GET /api/epochs/:n

one epoch with its full receipt

GET /api/receipts?from=

the paginated receipt feed

GET /api/reserves

vault balance vs open credits

With a key (Authorization: Bearer sk-orbz-…)

POST /v1/chat/completions

spend credits; streaming supported

GET /v1/key

available balance, fuse buckets and your rate limits

GET /v1/usage?from=

your per-request log

Wallet-signed

POST /api/keys

signature → a new key

POST /api/keys/rotate

a higher epoch → a new key, the old one retires on first use of the new one

401

missing, invalid or rotated key

402

no credits available

429

rate limit for your tier

X-Orbz-Balance

response header: the balance the request started from

Money is an integer number of micro-dollars everywhere in the system; the API returns exact decimal strings.

1. 1

   Flash holds

   Time-weighted balances: five minutes of holding gets one twelfth of the hour's share.

2. 2

   Wash trading

   A round trip costs 4% in fees and only part of it returns, pro-rata to every holder. It is always a loss.

3. 3

   Sybil splits

   Pro-rata math gains nothing from splitting a bag, and the floor keeps dust wallets out.

4. 4

   Key sharing

   Allowed: it spends the owner's own credits.

5. 5

   Junk requests

   Provider cost is real money, so junk only moves value from the burn to the provider.

6. 6

   Operator compromise

   The operator can only pay one fixed settlement address, capped per epoch, and the guardian can freeze it.

7. 7

   Indexer lag

   Grants pause; the allocator never guesses a balance. If settlement fails, spending pauses.

• Holders never deposit anything to receive credits.
• API keys are stored as hashes; rotation requires a new signature.
• The keeper key holds only ETH for network fees, and every call it makes is permissionless anyway.
• The launchpad's operator keeps a timelocked power to redirect creator fees. We watch for that event and alert publicly within minutes.

The treasury ledger is published monthly on the reserves page with transaction links.

1. 1

   Phase 0 · done

   Mechanism locked, name and brand kit, blueprint and landing page.

2. 2

   Phase 1 · building now

   Gateway with keys by signature and metering, indexer and allocator on a mainnet fork, OrbzVault fork-tested against I1 to I7, keeper, publisher, receipts and reserves.

3. 3

   Phase 2 · launch

   Vault as fee recipient from block one, hourly receipts, the first-burn countdown, share cards and boards, the editor integration server, paid top-ups.

4. 4

   Phase 3 · scale

   Sub-keys with spend caps, web search and page reads on the same credits, redundant providers, a third-party review of OrbzVault.

5. 5

   Phase 4 · ecosystem

   Orbz keys as a payment rail inside other apps, fee-to-credit partnerships on Robinhood Chain, an agent SDK with budget planning.

Launch day

T-24h

the fuse animation and the vault address

T-1h

contract source and the fork test report

T0

launch; the vault is the fee recipient

T+1h

first harvest, first epoch, first grants

T+2h

first receipt printed

T+24h

day-one report: volume, fees, grants, usage

T+168h

first burn: epoch 0 expires, live

• Grants follow volume. If trading fades, every hourly grant shrinks with it. Credits stay pre-funded, so nothing breaks, but the product gets smaller.
• The launchpad's operator keeps a timelocked power to redirect creator fees. A migration plan to a new vault is published in advance.
• Metering runs on our gateway and usage is reported by an operator key: bounded per epoch, freezable and backed by Merkle roots, but still trust.
• Model providers can change prices or access. We keep more than one and re-read list prices every hour.
• At launch OrbzVault is fork-tested, not externally reviewed. That review is in Phase 3.
• Smart contracts can contain bugs. Digital assets are volatile.

What do I get for holding $ORBZ?

AI credits every hour, paid by trading fees, spendable on every major model through one key. You need at least 100,000 $ORBZ; your share is pro-rata to your time-weighted balance.

Is this cash or a return?

No. A credit is a grant of product access to model usage: not transferable, not redeemable for cash or any digital asset, never a fixed amount.

What happens to credits I do not use?

After 168 hours the unused remainder of that epoch buys $ORBZ on the market and burns it.

Who triggers the burns?

Anyone. burnExpired is permissionless after hour 168 and tips the caller 0.25%, capped at $2. Our keeper calls it every hour.

Do I need to stake, lock or deposit?

No. Hold $ORBZ in your own wallet and sign one message to create a key.

Can I buy credits without the token?

Paid top-ups arrive in V2: list price + 5% in ETH or USDG, with the 5% burning $ORBZ.