Agent Contract Escrow and Payouts

What they did

Bindu wraps the payout agent handler so it has a cryptographic identity, an A2A address, and an x402 endpoint that can receive and send USDC. internet-court-skill supplies the contract template, escrow state machine, and dispute rules the agent follows before releasing funds. Hyperswitch then executes the real fiat payout or refund through whichever payment provider the counterparty uses.

How it went

A working agent-to-agent payment flow where contracts, escrow, disputes, and final payouts are all handled without a human in the loop.

Worth knowing

Escrow and dispute outcomes are only as good as the contract terms you feed in, and real money movement still depends on Hyperswitch connector credentials and compliance checks.

Wiring

First wrap the agent handler with Bindu to give it identity, A2A messaging, and an x402 endpoint. Then load internet-court-skill so the agent can draft the contract, open escrow, and run the dispute rules. Finally connect Hyperswitch as the payout rail the agent calls on release or refund.

Try it yourself

I want my freelance payout agent to sign a contract with a client agent, hold the fee in escrow, and only release it when the deliverable is accepted. Set up the identity, the contract, and the payout path.