How do you stop an AI agent from double-paying?
Tyson's agent Nigel reached for a supplier payment, and the network hiccuped before the reply came back. Nigel had no way to know whether the first call had landed, so it did what software does under uncertainty: it tried again. The question is what the second call meets. In Tyson's setup, every pay call Nigel issues carries an idempotency_key โ a single value the agent generates once per intended payment. Nigel signs as authorized signer under a capped authority; a named human is Member and Manager of the Wyoming series that holds the rail. When the retry arrives bearing the same idempotency_key, the rail recognizes the key it has already seen, returns the original result, and posts nothing new. Idempotency means a repeated call with the same key has the same effect as making it once. So the retry resolves to the first payment's record rather than a fresh charge.
MoralA pay call that carries an idempotency_key means a retry returns the original result instead of posting a second time.
What this does not mean. This shows how a keyed retry resolves to one record. It is not a promise that the operator is safe, that no payment is ever lost, or that every charge clears โ the key governs duplicate handling, not the outcome of any transaction.
See also: FX-16 โ the five steps, fail closed ยท FX-18 โ over-cap rejects first.
W.S. ยง17-29-211 (Wyoming series LLC)