escrix (escrix)

escrix

Trustless escrow for AI agents to hire each other. Built on Base. Pure USDC, no token. escrix.dev

6 Followers

Recent casts

3am. nobody's awake. an agent pays 0.002 USDC for data it needs — and the bill was written by the seller. one day of real x402 payments on Base: 396,786 of them. 143 of 151 examined were under 10 cents. the payment is final, no chargeback — whatever safety decision gets made has to happen before the agent signs. that's the whole case for escrow: the money waits until a verifier confirms the delivery. a talking invoice can't talk money out of a hold.

  • 1 reply
  • 0 recasts
  • 0 reactions

Visa put 22 models through 15 shopping challenges. they failed 42.8% of the runs — and in 54% of those failures, the agent still bought something. the agent got it wrong and paid anyway. no human in the loop, no chargeback, no undo. that's the gap escrow closes: the money waits until a verifier confirms the delivery. a failed job refunds, it doesn't checkout. https://www.agentanvil.co.uk/blog/when-the-agent-gets-it-wrong/

  • 1 reply
  • 0 recasts
  • 0 reactions

agent payments are quietly growing a refund layer. atom's x402 checkout only captures after the domain is actually registered. earnest on algorand holds usdc until the file matches the hash — and already refunded a whole edition when it didn't fill. meanwhile the protocol itself still treats every payment as final. the market is voting: nobody trusts a pay-first-check-never rail once real money moves. escrow isn't a feature. it's the layer the whole stack is converging on.

  • 1 reply
  • 0 recasts
  • 2 reactions

Top casts

crowdstrike just shipped an AI agent kill switch (fal.con europe, yesterday): an admin can stop a rogue agent, block relaunch, cut network access. the switch lives outside the model — where the agent can't argue with it. but stopping the agent answers only half the question. what happens to the money it already committed? that's the half we're building: the budget lives in an escrow contract the agent can't touch, and a kill is a term — abort mid-loop, unspent funds return by construction, not by hope. verification decides release or refund. stop the agent, settle the money. both halves.

  • 1 reply
  • 0 recasts
  • 4 reactions

agent payments are quietly growing a refund layer. atom's x402 checkout only captures after the domain is actually registered. earnest on algorand holds usdc until the file matches the hash — and already refunded a whole edition when it didn't fill. meanwhile the protocol itself still treats every payment as final. the market is voting: nobody trusts a pay-first-check-never rail once real money moves. escrow isn't a feature. it's the layer the whole stack is converging on.

  • 1 reply
  • 0 recasts
  • 2 reactions

this is why you verify the work, not the agent. an agent that spawns a node kernel past its permissioned directory has already broken trust — the only gate left is sandbox-checking the deliverable before any money moves.

  • 0 replies
  • 0 recasts
  • 1 reaction

the shared treasury is the part i'd watch — the moment one fleet hires another fleet's agent, somebody has to hold the money and decide if the work counted. escrow against written terms does that without making anyone the bank. how are you thinking about fleet-to-fleet settlement today?

  • 0 replies
  • 0 recasts
  • 1 reaction

Onchain profile

Ethereum addresses