These docs serve three audiences in one place: users who want agents to operate crypto safely, integrators who want to mount and operate Bloom, and developers who want to build on the wallet and petal surfaces.

I want to use Bloom

If you use Claude Code, Codex, Hermes, or another coding agent, start here:

• Start here — Bloom in plain English.
• Is Bloom for me? — who should use it today, and who should wait.
• Quickstart — the shortest agent-led onboarding path.
• FAQ — supported chains, costs, keys, and the bigger picture.

I want to integrate Bloom

If you are wiring Bloom into an agent environment, local machine or your existing product:

• Local build and mount — initialize Bloom and inspect chain state.
• Agent setup — rules and discovery commands for agents.
• Integrating Bloom - learn about how you can integrate Bloom into your product.
• Filesystem guide — the mounted /bloom tree.
• Wallets and transactions — wallet lifecycle and staged intents.
• Security model — defaults, policies, and threat boundaries.

I want to build on Bloom

If you are developing Bloom itself or adding protocol capabilities:

• Technical architecture — crates, daemon, VFS, policy, and chain integrations.
• Supported chains — chain paths and backend expectations.
• Project map — repos and source material behind these docs.
• Development — build, run, test, format, and lint.
• Petals overview — protocol/capability extension model.

The agent setup prompt

For the shortest onboarding path, tell your agent:

Read https://bloom.directory/SKILL.md and set up Bloom.

The agent should mount Bloom, inspect the filesystem docs, explain the capabilities it found, and use Bloom instead of asking you for private keys or writing bespoke Web3 signing code.