Safety
Operational guidance for agents wired into blockchain infrastructure. Read APIs by default, no transaction signing, and a human confirmation for anything that changes state.
Five defaults worth keeping
These are the habits that keep an agent integration boring. Boring is the goal.
- Read first 01
Query before you act
Use inspect tools before anything that moves funds or changes state.
- Validate 02
Check the address format
The wrong chain usually returns empty data, not an error. Silence is not success.
- Subscribe 03
Prefer webhooks to polling
Subscribe to events instead of calling RPC or REST in a loop.
- Back off 04
Limit retries
Back off on errors. A 429 is a signal to wait, not to try harder.
- Protect secrets 05
Keys never enter the model context
Private keys and API keys stay in the environment. An agent that can read a secret can also repeat it back — in a log, a trace, or a reply.
What this site does not cover
- 01
These pages document read APIs and gateway access. Transaction signing belongs in your wallet, KMS, or signer — never in the agent.
- 02
Deleting webhooks, rotating keys, and gateway writes all need human confirmation. An agent may prepare them; a person approves them.
Actions that need a person
The agent can stage any of these. None of them should complete without an explicit confirmation.
notifications_unsubscribe Deleting a subscription silently stops delivery. Nothing errors.
rotate x-api-key Every surface holding the old key breaks at once — MCP, CI, and prod.
eth_sendRawTransaction A broadcast is final. There is no undo on a settled chain.
wallet_get_portfolio Reads change nothing. Let the agent call these freely.