Can an AI agent get an EIN for tax?
Fritz let his agent Nigel move money and assumed it could get an EIN for tax on its own authority over a bare API key. But software has no legal capacity to hold the account or the funds, so Nigel can no more get an EIN for tax in its own name than a checkout button can own the till. 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 opened the account in the entity's name, with caps wired onto the money path — per-transaction, daily, and counterparty allowlists. Now the human-owned entity holds the account and the rules; Nigel moves a request as an authorized signer with capped authority, and an over-cap or unscreened request is rejected before money moves. The control lives on the entity's account, not in the agent.
MoralTo get an EIN for tax, the account and the caps sit on a human-owned entity; an AI agent moves the request as an authorized signer within caps, and an over-limit request is rejected before money moves.
What this does not mean. This shows where the account and the spend caps actually sit. It is not a promise that a payment clears, that every limit holds in practice, 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-18 — .
W.S. §17-29-211 (Wyoming series LLC)