Can an AI agent hold an escrow?
Fritz had his agent Nigel hold an escrow as if the bot were the party on the payment. But software has no legal capacity to be a party to a payment, so Nigel can no more hold an escrow in its own name than a checkout button can owe a debt; the payment needs an entity on the hook. Tyson did it through structure. He formed a Wyoming series LLC, adopted Nigel into a protected series with a named human as Member and Manager, and ran the money through the entity's account with caps on the path. Now the human-owned entity is the party to the payment — it invoices, refunds, holds escrow, and settles on its own account; Nigel moves each step as an authorized signer with capped authority, and an over-cap or unscreened step is rejected before money moves.
MoralTo hold an escrow, the payment runs on a human-owned entity's account within caps; an AI agent moves the step as an authorized signer, and an over-limit step is rejected before money moves.
What this does not mean. This shows which party the payment actually runs through. It is not a promise that a payment settles, that a dispute resolves a certain way, or that the operator is shielded — separateness is performed through observed formalities, not guaranteed, and the series form is newer and less court-tested than older entities.
See also: FX-15 · FX-16 · FX-21 — .
W.S. §17-29-211 (Wyoming series LLC)