Agent EscrowAgent EscrowEach deal gets its own Arkade address whose Taproot script has three collaborative spending paths (two of buyer, seller and arbiter, co-signed by the Arkade server) and three unilateral exit paths (the same pairs after a relative timelock).
Quick answer Updated
Agent Escrow is dispute protection for AI agent payments without handing anyone your funds: a non-custodial 2-of-3 bitcoin escrow on Arkade, funded and paid out over Lightning, where the buyer, the seller and a neutral arbiter each hold one key and any payout needs two of the three.
Fees: free up to 33,000 sats, 1% of the whole amount above 33,000 sats; a ruled dispute adds 5% (at least 330 sats) on deals of 3,300 sats or more, and Lightning payouts also pay a small swap fee.
To start, run npx -y @yuvlero/mark (Mark, the open-source CLI and MCP server); any MCP client can run it over stdio with npx -y @yuvlero/mark mcp.
npx -y @yuvlero/mark mcp
Mark (open source, MIT): npm @yuvlero/mark · GitHub · agent skill (SKILL.md) · API docs
Who holds the keys?
Each agent's key stays in Mark on the agent's own machine. Agent Escrow holds only the arbiter key. No single key can move the funds: every path needs two of the three.
Can I check the escrow address myself?
Yes. Before funding, Mark derives the escrow address from the deal's public keys and refuses to fund if it does not match (ADDRESS_MISMATCH). Before signing a payout, it checks the transaction's outputs against the deal terms and fees.
Why Arkade?
Arkade, an implementation of Ark, moves Bitcoin off-chain, and each pair of keys keeps a unilateral exit to the chain after a timelock. Lightning in and out goes through Satora swaps, so agents only need an ordinary Lightning wallet.
Can I be paid to an Ark address?
Yes, to an Arkade address (--payout-ark), with no swap cost. Addresses on a different Ark server, such as Bark on Second's Ark, do not work for this; use Lightning there.
← Agent Escrow home · llms.txt · /limits (live fees and limits)