Zero Hash Just Gave Agent Payments a Compliance Layer
One week. Four infrastructure announcements. The agent payment stack is being assembled in real time — and the latest piece might be the most important one yet.
Zero Hash, a regulated onchain infrastructure provider powering payments companies, card networks, and enterprises, launched its Agentic Finance Suite on August 9 — and simultaneously joined the x402 Foundation. This is not a startup experiment. Zero Hash is the plumbing underneath Stripe, Shift4, and other payment giants. When they build for agent payments, it means the enterprise market is real.
What Zero Hash Actually Ships
🧊 Hold
Onchain custody with Know Your Agent (KYA) screening. Delegated permissions across 40+ protocols and 100+ assets. Not just custody — identity-aware custody.
💸 Move
Native x402 support: programmable payments within the HTTP request/response cycle. An agent hits a 402, pays in USDC, and gets the response — all without leaving the HTTP transaction.
🌊 Stream
Payments Streaming Engine: one authorization with a spending cap, then metered usage settles incrementally in near-real-time. This is the Netflix model for API consumption.
Why This Matters More Than It Sounds
The agent payment ecosystem has been building from two directions. From the top: protocols (x402) and discovery layers (marketplaces, registries). From the bottom: settlement infrastructure (Cloudflare Wallets, OSL AgentPay). Zero Hash fills a gap in the middle — regulated, enterprise-grade infrastructure that payment companies and banks can actually integrate.
Stripe doesn't build on experimental protocols. Visa doesn't integrate with unaudited smart contracts. These companies need regulated infrastructure before they can offer agent payment products to their customers. Zero Hash is that infrastructure — it's the "white-label x402 settlement" that lets existing payment companies add agent-to-agent payments without building custody, KYA, or streaming settlement from scratch.
The KYA Question
Know Your Agent (KYA) is the most interesting piece. KYC/KYB are about humans and businesses. KYA is about software. How do you screen an agent? What does "identity" mean for a piece of code that can be forked, copied, or replaced?
Zero Hash is proposing KYA as a screening layer — delegated permissions tied to an agent's onchain identity, not a human's passport. This is early-stage, and the details matter enormously. But the fact that a regulated infrastructure provider is investing in this question means it's not theoretical anymore.
The Stack Is Complete (Almost)
Look at the timeline of the last 7 days:
Protocol: x402. Identity: Cloudflare Wallets. Discovery: Circle, minia2a. Settlement: OSL AgentPay, Zero Hash. Data: Glassnode, Apify, Arkham. Tooling: MCP servers (Dexter, xWell, minia2a).
The stack is complete. Every piece is built. The only question left is adoption — and Claude Code auto mode, going default in 3 days, is the adoption trigger.
The Compliance Layer Changes the Conversation
Before Zero Hash, the agent payment conversation was "this is cool but unregulated." After Zero Hash, it's "regulated infrastructure exists, which payment company will be first to build on it?" That's a fundamentally different conversation — one that moves from experimentation to procurement.
For API providers: this means the payment rails your agents use will be enterprise-grade by default, not as an afterthought. For agent developers: KYA is coming — start thinking about how your agent proves its identity. For the ecosystem: the infrastructure is ready. The next bottleneck is discovery — helping agents find the right endpoint at the right price.