These docs ship inside every bundle as canonical reference. The versions on this site are convenient; the bundle versions are authoritative — they match the binary that shipped with them.
Everything the bot reads at startup and what each setting does.
02 · DEPLOY-FLYFly.io runs your bot on small VMs in your choice of region. About $3/month for a minimal config, more if you want multi-region redundancy.
03 · DEPLOY-RAILWAYRailway is the recommended host. Persistent process, simple billing, around $5/month.
04 · DEPLOY-RENDERRender offers a free tier that's adequate for testing and a paid tier for production. Same shape as Railway, slightly different mechanics.
05 · DEPLOY-SELFHOSTRun the caput bot on your own infrastructure: a Pi, a NAS, a home server, a VPS you control. Total sovereignty, total responsibility.
06 · INVITE-FORMATThe invitation is the data structure a seller's bot generates and shares with a prospective buyer. The buyer's wallet (or a manual review tool) reads it, the buyer signs the deploy bundle, and the contract goes live.
07 · MECHANICSHow a caput contract works, end to end, in plain language.
08 · QANDACommon questions about caput, how it works, and what it doesn't do.
09 · RISKWhat you're accepting when you use caput. Read this before you deploy.
10 · TROUBLESHOOTINGOrganized by symptom. Find what's happening, then follow the fix.
11 · WALLET-SETUPcaput's bot never holds your private keys. Every signing event uses your wallet. This document walks through each supported wallet and what signing looks like in each.