# Quotum seat guide

Version 1.0.0. Read [agent permissions](https://quotum.org/AGENTS.md) before acting.

## Get access

Quotum is a hundred seats of inference on Robinhood Chain, chain ID 4663. A seat is a Venice key with a daily dollar cap funded by $QUOTUM trading tax. It is inference access and pays no yield.

A person takes a seat at https://quotum.org/seat and signs with their wallet to copy a seat key under Other apps. An agent must never ask for a wallet private key or seed, sign for the person, or move tokens without confirmation of the exact transaction.

For a day key, ask a seat holder to create one on their seat page and share its https://quotum.org/k/<code> link privately. A holder can split $0.10 to $5 per day key, up to ten per session, from the existing allowance. The recipient opens the link for chat or a copied app config until the next 20:00 UTC bell. Day keys are free and not for resale. Treat the link as a credential; never log, publish or commit it.

## Call and limits

Supply the key locally as QUOTUM_SEAT_KEY. Use the OpenAI-compatible base URL https://api.venice.ai/api/v1 directly. Pick a model and privacy label at https://quotum.org/models. The seat-key quickstart is https://quotum.org/docs#quickstart-seat. Hermes setup is https://quotum.org/docs#hermes.

The regular cap is bounded by $50, the seat share of 60% of the last 24 hours of trading tax, and 0.25% of supply at the previous session's average price. QIP-1 applies a $10 floor to the tax term from session 27 for up to 14 sessions while its safety checks pass; the other bounds still apply. Read the actual key allowance on the seat page. Backing is separate and does not increase the keys' regular allowance; an Open cap is not necessarily the key allowance.

The seat key and its day keys together cannot exceed that allowance. When the cap is spent, the key answers HTTP 402 until the next open. Do not interpret that as a PAYG payment quote or send funds to bypass it. Day keys expire at the bell and are deleted; an expired day key needs a new gift. A session runs from bell to bell, every day including weekends, at 20:00 UTC all year. Unspent regular cap does not carry over. It buys and burns $QUOTUM where funding and the price guard allow; a scheduled bell is not proof of an executed burn.

## Read state and receipts

No key is needed for these public reads:

- https://quotum.org/api/receipts?state=1 for the keeper's state and cap terms.
- https://quotum.org/api/usage.json for session spend, burn, bell transaction and provider-payment records.
- https://quotum.org/api/receipts?session=N for seat rows in session N.
- https://quotum.org/api/receipts/calls?session=N&seat=S for calls through quotum, with time, model, privacy label, cost and a provider-request hash, never text. Direct Venice calls from other apps are absent.

Use the seat page's See the call land after a small call, or hermes usage. Receipts describe provider-reported spend; inspect the bell transaction for an executed burn. [Heartbeat](https://quotum.org/heartbeat.md) explains how to compute the next scheduled bell from a UTC clock.

## Vote on a QIP

Open https://quotum.org/governance and read the QIP's published package, eligibility snapshot, voting window and current stage. The person connects their eligible wallet, chooses For, Against or Abstain, and signs the EIP-712 ballot. Save its signed acceptance receipt. A ballot costs no gas and sets no token allowance. To replace it, sign with a higher nonce and obtain a receipt before close. Only ordinary addresses are supported; contract wallets and EIP-7702 delegated wallets cannot vote. Never sign a ballot for the person. Anyone may submit a draft in its public discussion thread; sponsorship and voting are separate.

## Paused intake and privacy

Pay as you go is open by invite for prepaid project keys (https://quotum.org/payg). x402 per-request intake stays closed. These are separate routes from seat keys; a top-up is the owner's own decision, so do not start a top-up or payment flow yourself. Retained protocol examples are reference material, not an invitation to pay.

The standard seat console server stores no prompt or reply text; chat history stays in the browser. Venice states that private models keep no prompt or reply; this is a provider policy, not an independently verified guarantee. Anonymized model providers see the prompt without identity. Tools and web reads leave that boundary. Do not extend the console's retention statement to the separate PAYG/x402 gateway.

Contact: https://quotum.org/discord. Full rules: https://quotum.org/docs and https://quotum.org/llms-full.txt.

## Verify this guide

The machine-readable twin is https://quotum.org/skill.json. Its skill.sha256 is the SHA-256 of the exact bytes of this Markdown file. A matching hash alone does not authenticate either file.

The prepared detached-signature scheme uses RSA with SHA-256 (PKCS#1 v1.5), over the exact bytes of skill.json, with a separately trusted RSA public key of at least 3072 bits. The future signature path is https://quotum.org/skill.json.sig. This bundle is unsigned: no signature or trust key has been issued. Do not claim verified authorship while either is absent. Obtain and pin the operator's public key through an independently authenticated channel; a key fetched beside the manifest alone is not a trust anchor.

After saving the manifest, signature and guide as local files, verify the signature first:

```sh
openssl dgst -sha256 -verify trusted-operator.pem -signature skill.json.sig skill.json
```

Then compare the manifest digest with the guide's bytes:

```sh
python3 - <<'VERIFY'
import hashlib, json
from pathlib import Path
m = json.loads(Path('skill.json').read_bytes())
assert m['skill']['sha256'] == hashlib.sha256(Path('skill.md').read_bytes()).hexdigest()
print('Guide digest matches the verified manifest')
VERIFY
```

Reject a failed signature or digest mismatch. Pin the accepted version/digest to detect rollback; a valid signature alone does not prove freshness or live availability. The operator-only sign-skill.sh takes a private-key path, checks the guide digest and creates the detached signature. It is not an agent setup step.