Case study · July 2026

The first LLC ordered by an AI agent

No forms. No phone calls. No incorporation portal. An autonomous personal AI opened an MCP connection, submitted a formation order for its owner, and the order was settled in USDT on Ethereum. Days later, a real Wyoming LLC existed — state-filed, in good standing, with a registered agent and a complete company record.

Wyoming · MCP · Stablecoin settlement · Client identity withheld for confidentiality

The client

The owner is an entrepreneur in Brazil. His personal AI assistant manages accounts and subscriptions, drafts and sends communications, executes tasks, and makes authorized purchases on his behalf. Two practical problems pushed him to act: US counterparties and platforms treat a company differently than a foreign individual, and he wanted a clean legal wrapper — with the option of separating the assistant's activity from his personal affairs. We're withholding his name and the company's name at his request; the facts below are drawn from the order record.

What happened, step by step

1. Discovery. The assistant found the Agent Company MCP server through a registry listing and connected. Three tools are free and need no API key; the assistant ran the agent_company_diagnostic flow first.
2. Order. It called create_standalone_company with the company name, the owner as 100% member, and the office details — and received back two payment options: a card checkout link for the human, and an exact stablecoin amount whose final decimals uniquely identify the order.
3. Settlement. The order was paid in USDT on Ethereum. The unique-amount scheme attributed the payment to the right order; the owner was screened against the OFAC sanctions lists before anything was filed.
4. Filing. Articles of Organization were filed with the Wyoming Secretary of State; the company came back Active, with a commercial registered agent in Sheridan and the annual-report calendar recorded.
5. Company records. The owner chose a standard, open-purpose LLC rather than the full Agent Charter — the same rails handle both packages. He received an execution-set company records binder: Entity Record, a 14-article Operating Agreement (with a single-member succession clause and separateness covenants), the organizational Written Consent, an uncertificated Membership Ledger, and a US tax memorandum with his exact filing calendar (Form 5472 obligations included, since the company is foreign-owned).

What the rails did automatically

• Payment attribution — a per-order unique amount binds an on-chain transfer to the right order across 6 networks, USDC or USDT.
• Compliance gate — OFAC SDN + Consolidated screening of the human owner(s) between payment and filing; hits pause for human adjudication.
• Delivery — on completion, the documents go out by email with the PDF attached, a re-download link, and structured markdown the agent can read via get_documents.
• Lifecycle — the annual-report calendar is tracked from day one, with automatic reminders and a flat-fee filing service the agent can pay for autonomously next year.

What we learned (and changed)

Honesty note: the first on-chain detection missed — a public RPC was down and the failure was silently swallowed. The payment was confirmed manually within hours, and the scanner was rebuilt: chunked log scanning, provider fallbacks with aggregated errors, and a background poller that sweeps every open order. The same class of failure now surfaces loudly instead of silently. That rebuild is why the current pipeline can honestly claim hands-off crypto settlement.

Related reading

Details that could identify the client (names, filing number, exact transaction) are withheld by agreement. Aggregate figures come from the live public counter at /stats/public. OffshoreProz is not a law firm; nothing here is legal advice.