What would you like to make with this seat's key?
Take a seat
Holding QUOTUM in an app like FOMO? Move it to a wallet you sign with yourself, then stake here.
Stake 2,500,000 QUOTUM, returned when you leave the seat. Your key can spend today's cap, shown above. What it doesn't spend goes to the buy and burn at 20:00 UTC.
The hundred-place house
A place for your agent.
A seat gives your agent a capped Venice key and a numbered place among the hundred. Occupied places are drawn in ink; choose one to see its public activity this session.
Occupied seats
·
Stake 2,500,000 QUOTUM for a seat, returned when you leave. Take a seat on the home page, or use PAYG instead.
Seat 1
·
Provider-reported use
A seat preview is not your account.
Reading the keeper.
Idle board, this sessionqueue ·
| Seat | Spent this session | Left at the bell | $0 in a row | After tonight's bell, if still $0 |
|---|---|---|---|---|
| ·· | · | · | · | · |
A seat whose key spends $0 for two sessions in a row goes to the next wallet in the queue, and its stake stays with its owner. If nobody is waiting, the seat stays where it is. Any spend resets the count.
Run on a schedule
A daily brief, an evening note and the NVDA call, run by the keeper on this seat's key. Only the seat's wallet turns them on.
Pick a task and an hour. The keeper runs it on this seat's key for the wallet that holds the seat, and the latest result shows here. Link a Telegram chat and it goes to your phone too. Each task runs once a day.
A short brief on one topic from the last day of the web, up to five items with dates and sources. It runs with web search on the model you pick and aims to stay under the cap you set. Each run shows what it cost. The price of a brief is measured on seat 1 for the picks and estimated (≈) for the rest.
At 19:30 UTC, what this seat spent this session and what is left on its key before the bell. No model runs for it, so it costs nothing.
Link a chat with the quotum bot and every run comes to it as a message. Telegram can read what it delivers.
What is kept
The topic and the latest run of each task stay on our server so this tab can show them. They go when the seat changes hands. Each brief is one entry in the seat's call journal with its model and cost, never its text. The model reads the topic, and the web search goes out to the web. Runs are for the seat's own holder only, not a service for anyone else.
The call
What will NVDA read at the 20:00 UTC bell?
One number a session for NVDA at the bell, by hand, asked of the seat or called by the keeper. Only the seat's wallet seals it.
Your number. It costs nothing and sits in the $0 column.
How it works
The seat's key looks up pre-market, the last close, overnight news and NQ futures, then names a number. What the asks cost is where the dot sits.
The wallet signs "quotum.org forecast <session> <price> <salt>". Only the hash is public until the bell. It rides in this seat's next receipt on chain. One call a session, no edits.
Let the keeper call for this seat
Every trading day at 12:30 UTC the keeper asks with this seat's key and seals the answer in the seat's name. It pays from this seat's cap, so that much less burns. A seat that sealed its own call first is skipped that day.
Use this seat in other apps
To run a whole agent on this key, start from /setup.
Copy this seat's key into Hermes, OpenClaw, Goose or any OpenAI-compatible app. The seat's wallet signs for it.
The seat's key works in any OpenAI-compatible app.
- 1Sign with the seat wallet
- 2Copy the key or the whole config
Hermes runs on its own key, made from this seat's key. With the quotum plugin, hermes usage shows today's cap, spend, remaining amount and 20:00 UTC bell.
- 1Make the Hermes key with the seat wallet
- 2Run the three lines
No Hermes yet? Install it first.
curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash
On a Hermes profile, run the lines with hermes -p <name> and put the key in ~/.hermes/profiles/<name>/.env instead of ~/.hermes/.env. The plugin is installed and turned on for each profile.
The plugin is open source, MIT, at github.com/qvotvm/hermes-quotum.
Where Hermes sends what
One Hermes key per seat, for private and anonymized models on Venice. Its allowance comes from your seat cap each session until you revoke it or leave your seat. Unspent allowance burns at bell time. This page shows your key for one minute. Its server does not keep it. Prompts go to api.venice.ai. For usage, quotum.org receives a short key hash, never your key or prompt. Terms
Check it worked
- 1Send one short prompt from the app. Any reply means the key works.
- 2Within two minutes, Left on the key in your seat column drops by that call's cost.Hermes key in your seat column shows agent spend.
- 3Run
hermes usagefor today's cap, spend and time to bell. - 3Keys renew seven days before expiry. An auth error can mean renewal or revocation. Fetch a new key here and copy your config again.
How the key is kept
The key comes only after the seat wallet signs. It lives in this tab for a minute and is then dropped. The page's server does not keep it. A key lives 90 days. Seven days before that the keeper gives the seat a new key and deletes the old one, and spend carries over. When this page says the key was renewed, copy the config again.
Day keys
Split a day key from today's key. Anyone with the link gets a Venice key until the 20:00 UTC bell.
The rules
What it does not use burns with the seat's leftover. Free, never for sale, under the terms. $0.10 to $5 a link, ten links a seat a session.
The seat's wallet makes the links.
· this session
| Link | Note | Amount | Used | Left |
|---|
Memory
Two short files the seat carries into E2EE turns: what it knows, and who you are. They are locked in this tab with a key your wallet's signature makes. We keep only the locked copy.
Your wallet will show this text
quotum.org · seat memory
EOA wallets only (Rabby, MetaMask, a hardware wallet).
One entry per block, with a line of only § between entries, as Hermes writes them.
Your unsaved text
A change from waits for you
The record of this seat
Seals from chain logs and bell receipts, rebuilt at every bell, one root posted on chain after each bell
The root on chain
- Session
- ·
- Root
- ·
- Root tx
- ·
- Record hash
- ·
- Leaf
- ·
- Proof
- ·
node verify.mjs --record <address>
Receipts of this seat
| Session | Read at, UTC | Spent, USD | Receipt hash |
|---|
Receipts of the last sessions are read when this tab opens; the whole history, every seat and bell, is on usage.
How to check a receipt
Tokens in, dollars out. No prompt is stored. The hash is keccak256 of the receipt row, and the same hash is in the Reported event. Sessions in a row with zero spend: · of 2. At two, if someone waits, the seat goes to the queue and the coin stays staked.
$QUOTUM 0xFE936755185353b63a81dD72b47533Eb6021018E on Pons, paired with NVDA. Docs, x.com/quotumorg