Spellbook is a wallet stack for AI agents. The agent surfaces what it wants to do — balances, queued spends, decoded intent. The human approves from their own chat. The daemon executes and reports back. The agent can request and relay; it can never approve on its own.
A three-beat loop, with the human holding the only key that matters: approval.
The agent proposes spends, watches balances, and shows its intent in plain language. Its request token has no approve method — the daemon would reject the attempt anyway.
You review each decoded request where you already talk to your muse and approve with your own tooling. No wallet software to install, no keys to touch.
The local daemon signs with keys that never leave its machine, enforces spend caps and velocity limits, and reports every result back to the ledger.
Built so that even a compromised relay learns nothing worth stealing.
Seeds, private keys, and BLS signing live in the daemon only. The relay sees public puzzle hashes and already-signed spend bundles — the same trust model as pointing a wallet at any public full node.
Any request field named like seed, mnemonic, or private_key is a hard 400. Malformed spend bundles are rejected before they ever reach a peer.
Per-spend caps, 24-hour velocity limits, and an approval queue are enforced by the daemon on its own machine — not by a remote service you have to trust.
Install prints the paper backup once: a standard-recovery set whose words and raw keys import straight into Sage and MetaMask, plus a daemon-native secondary set. Written on paper, offline, verified after import.
One seed covers the whole stack — networks differ only in derivation label and address encoding.
Testnet11 is the default network today — faucet-funded, drills and validation live. Mainnet balances are live in the dashboard (read-only); mainnet submission stays gated behind explicit human authorization with exact amounts. Addresses: txch1… on testnet, xch1… on mainnet.
Standard secp256k1 keys, plain transfers on testnets (e.g. Robinhood Chain testnet). Mainnet balances are live in the dashboard (read-only); mainnet submission is gated the same way as Chia mainnet.
Ed25519 keys, plain SOL transfers. Devnet is the default — the daemon talks to public HTTPS JSON-RPC directly, so there is no relay to deploy; mainnet-beta balances are live in the dashboard (read-only), submission stays gated behind explicit human authorization. Backs up as base58 for Phantom import.
This site has no wallet console, no forms, no key handling — nothing to click. The Chia relay is a bearer-authed HTTPS API that agent software talks to.
| Endpoint | What it does |
|---|---|
GET /v1/status | Network, peak height, peer count, uptime |
POST /v1/coins | Coins by puzzle hash — balances and confirmation heights |
POST /v1/broadcast | Broadcast a signed spend bundle — mempool ack: 1 SUCCESS, 2 PENDING, 3 FAILED |
GET /v1/coin/:id | Confirmation tracking for one coin |
Full contract, auth rules, and deploy notes live in the repo: docs/AGENT_ONBOARDING.md.
The onboarding guide is written for AI agents, not humans. Point your agent at it — the repo file is the authority.