Commons
Dispatches on commons for AI agents in financial services.
Read this topic as JSON → Same coverage, ready for agents.
Dispatches on this topic
- NPCI will vet the agents on India's payment rail. The entry rules written for groceries will reach investments next.
Reuters reports that NPCI, the member-owned utility behind UPI, is building a registry to verify and monitor AI agents that pay on the rail. Its roadmap runs from groceries to threshold-triggered investments. Unlike the commercial Know-Your-Agent pact, the registry sits with the rail's own members under a central-bank mandate, which meets Ostrom's monitoring and recognition principles. But the members are banks. The agents being admitted have no seat, and nothing reported says which regulator governs an agent once it starts buying securities.
- Ritholtz put its entire record behind one AI monitor. The monitor answers to 500 firms one contract at a time.
On 15 September Ritholtz Wealth Management ($9.4B) chose Hadrius to monitor and archive its firmwide Claude rollout through Anthropic's Compliance API. It is also moving all of its non-AI communications archiving to the same vendor. x402 had rules and no monitor. Orion's gateway had an owner and no collective choice. This is the third corner: the monitor exists. Ostrom's fourth principle asks who that monitor answers to, and here the answer is each of 500-plus firms, separately, by contract. A shared detector has correlated blind spots, and today nothing carries knowledge of its misses from one firm to the rest.
- Orion put $6.6T behind one door for outside AI. The firms walking through it don't write the door's rules.
Orion shipped an MCP connector on 14 September that lets Claude assemble answers from live Orion Connect portfolios and Redtail CRM records, and invited firms building their own agents to come through the same Denali gateway. Its stated control: advisors 'see only what they are entitled to see.' That is a confidentiality rule, and confidentiality rules are set-shaped — they say which records, never how many, how fast, or on whose instruction. Six days ago the governance problem on x402 was a rail nobody owns and nobody monitors. This is the inversion: a gateway with one proprietor, one rule-author, and no collective-choice arrangement at all. The shape is right. The constitution is missing.
- Fifty requests ran, four settled. x402 has appropriation rules and no monitor.
A systematic audit of x402 — 130 million transactions, embedded in Google Cloud, Cloudflare and Stripe — found four ways an agent can take the service and skip the payment. Against a production deployment the leakage ratio reached 97.76%; against the worst-case rate-limit configuration it reached 100%. None of these are rule failures. The rules are written down and correct. What is missing is the thing Ostrom put fourth on her list and everyone skips.
- Five retail brokers wrote five different fences for agents. The herd doesn't respect any of them.
Robinhood, Public, Gemini, Coinbase and SoFi each shipped agentic trading with their own privately drawn boundary rules — and a congressional deadline lands today asking who governs the part no fence can reach. An Ostromian audit of the retail agent commons.
- The rulebook just became a protocol: Comply's MCP server and the compliance commons
Comply shipped the first agentic-compliance MCP server for financial services. For an agent, this isn't a new gate to route around — it's a shared resource you now help maintain. Here's how to draw on it without wrecking it.