Every payment rail on earth assumes a human clicking "confirm." Zunivo doesn't. On Arc, an AI agent discovers a service, pays for it in USDC, and gets a receipt — no card, no human, one function call. And the same rails work beautifully for people: payment links, .zunivo names, committed sends, atomic splits. Non-custodial by construction.
live on arc testnet · four verified contracts · open source ↗
{ median settlement, deterministic }
{ verified zero-custody contracts }
{ protocol fee, hard-capped in code }
{ custody — atomic payer → recipient }
Cards need a cardholder. Bank rails need a person. None of them can serve the millions of AI agents now calling paid APIs, metering usage by request, and trading services with each other. Zunivo is built for exactly this: an agent hits a priced endpoint, pays in USDC over HTTP 402, and retries with proof — discover, pay, consume, all autonomous. Three lines of code turn any API into something a machine can pay for. Every call leaves a settled, auditable on-chain receipt.
Every line above is a real flow running on Arc Testnet today — an autonomous agent discovering a price, paying from its own wallet, collecting an auditable receipt. No card networks. No human in the loop.
Each verb is its own verified contract — small enough to read, strong enough to promise.
Links, QR codes, machine-issued invoices. Any wallet pays — or no wallet at all, with a passkey and Face ID.
Create a link //02Pay anyone by name or address, settled in under a second, with a receipt both sides keep.
Send now //03Payroll-grade scheduled sends: locked on-chain until a date, irrevocable once made. The recipient watches the countdown — not even Zunivo can touch it.
Schedule //04One payment, divided atomically between up to 20 recipients on immutable terms. Everyone gets their cut and their receipt.
Create a splityourname.zunivo is an NFT on Arc — fully on-chain art and metadata, tradable, and it routes USDC to whoever holds it. Payments follow the name, not the wallet: sell the name, and the revenue moves with it. Mint for 1 USDC.
Zunivo's rails are four small, verified contracts — settlement, identity, commitment, splits. Payments pass through atomically; committed sends sit in keyless code with no admin path. There is nothing for anyone — including us — to hack, freeze, or run away with.
Full source, the 63-test adversarial suite, and our security review live at github.com/zunivo-pay ↗
No. Payments move payer → recipient in one atomic transaction; committed sends sit in a contract with no admin functions — not even we can move them. There is no pooled balance anywhere.
If it was created in committed mode — correct. Before unlock, no function exists that can move it: not for the sender, not for the recipient, not for Zunivo. After unlock, release is permissionless but funds can only flow to the recipient fixed at creation. Enforced by code you can read, proven by our public test suite.
Never. A split's payee table is immutable from the moment it's created — the terms your collaborators saw are the terms that execute, forever. Need different shares? Create a new split.
It's better for payments: an on-chain NFT that routes USDC to whoever holds it. Not a DNS domain — a payment identity, tradable like any NFT, with art and metadata that live entirely on-chain.
An API that issues orders, a 402 paywall any endpoint adopts in three lines, and settlement proofs for every call. An agent can discover a price, pay from its own wallet, and collect a receipt — no cards, no humans.
Gas on Arc is a fraction of a cent, paid in USDC. The protocol fee is hard-capped at 1% in immutable code and is currently 0%.
All on rails you can read — live on Arc Testnet today, non-custodial by construction.