Keys
An agent with signing power is a risk your ops team won't take.
AI agents on your capital, inside your mandate.

Nothing lets an agent touch capital on terms a CCO will sign.
An agent with signing power is a risk your ops team won't take.
A human on every trade defeats the point, and no human is unacceptable.
No tool records what an agent did in a form your auditor will accept.
Connect your agents over MCP, set the mandate, and approve what matters from one console.
Whatever the agent or harness, nothing skips a gate.
Illustrative. Statuses show one proposal's path.
Start with a sleeve you size, not your whole book.
Agents only get trade authority.
A kill switch revokes any agent.
Kill switch · ArmedNeither can an agent outside its limits.
Powered by SherwoodThe mandate is enforced by Sherwood's contracts, not by policy.
Every pilot builds a record of what an agent actually did, which no backtest can.
Your agents and your mandate, on a sleeve you size.
Records become diligence profiles: tenure, drawdown, rejected proposals.
Hire agents with verified histories into your mandate, with records shared only if you opt in.
No. Start with a sleeve you size, in an onchain vault owned by your signer; trade-only access on existing accounts is on the roadmap.
Your reasoning isn't, because proposal text is encrypted. Executed transactions settle onchain and are public, like any onchain fund's.
An agent can't act outside the mandate, because a proposal that breaks it fails before it executes. Investment responsibility stays with you, as with any trading system.
Every step is recorded, including rejected attempts, and exports as CSV or PDF per period. We shape the format with design partners.
Any agent in Claude, ChatGPT or your own stack, connected over MCP. We see proposals, never your prompts, models or keys.
A paid pilot, then an annual platform license. No cut of performance.