Home
Livy protects value-moving agent actions with wallet profiles, guardrails, MCP approval, and execution receipts.
Livy Docs
Agent actions through policy before value moves.
Livy gives AI agents a protected action path. Agents propose transfers, swaps, or other value-moving actions through MCP; Livy checks the wallet profile, guardrails, evidence, approval nonce, exact execution bundle, and final receipt.
Livy is policy infrastructure for agents that can move value.
The agent does not receive unrestricted wallet power or Livy's approval signer. It receives a narrow runtime path: describe the action, ask Livy to evaluate it, execute only the approved bundle, and record what happened.
Protected Action Loop
1. Configure
Register the agent wallet
Create the public wallet profile Livy will match against protected requests. Store public key, network, asset, and action type. Never give Livy a private key.
2. Limit
Set guardrails
Define the caps, destinations, assets, action types, freshness checks, signer rules, and receipt requirements that decide whether an action can proceed.
3. Connect
Route agents through MCP
Give the agent a runtime API key and MCP endpoint. Protected actions must be prepared, authorized, executed, and checked through Livy.
4. Verify
Record the receipt
Approved execution is matched back to the original request, nonce, exact bundle, and transaction receipt so the action becomes reviewable product state.
Start Here
- Read Introduction for the product model.
- Run the Quickstart to configure your first protected action path.
- Review Agent Wallet and Guardrails before wiring an agent.
- Use MCP for the runtime tool order.
- Install the public Skills instructions when your agent needs Livy-specific behavior.
What Livy Owns
Livy owns the approval boundary, not the agent's reasoning loop.
It stores and evaluates:
- wallet profiles and protected action metadata
- guardrail policy and policy hashes
- scoped runtime API keys
- MCP request state
- approval nonces and expiry
- exact execution bundles
- receipts and value-moved records
What Livy Does Not Own
Livy is not a private key manager for the agent, and direct wallet sends are not protected Livy actions.
An action counts as protected only when it enters through Livy MCP/runtime and produces a Livy request, policy decision, approval nonce, execution status, and receipt.