Give your agent an allowance, not your keys.
Your agent pays for compute, data and subscriptions to do its job. Denze gives it a self-custodial spending account with a budget you set and rules it cannot break. Enforced onchain, not by us.
Overview
research-agentKill switchFund it
Load an account only you own. What you fund is the hard ceiling, forever.
Set the rules
Budgets, per-spend caps, merchants, expiry. Compiled into policy the chain enforces.
Connect your agent
One MCP link. Your agent requests, states a reason, and spends inside the lines.
That is the whole integration. Claude Code, or any agent that speaks MCP, connects to your account and spends only inside your policy.
MCP SERVER · DENZE CLI · @DENZE/SDK · REST API






Claude, ChatGPT, Cursor, Copilot. Any agent that speaks MCP can hold a Denze allowance.
Every rule lives on the chain, where no one can talk their way past it.
Bounded
Budgets, per spend caps and merchant allowlists are enforced at the account level. A hacked agent, a rogue prompt, even a compromised Denze cannot exceed them.
Traceable
Your agent states a reason before it pays. Every spend settles as an onchain receipt, not a log line we could edit, with declines recorded beside it. Export the ledger as CSV, or publish any receipt as a page anyone can verify against the chain.
Revocable
Session keys expire on their own and one tap withdraws them all in under a second. Trust that can be taken back is trust you can afford to give.