Trust

Where your money is

ZEAM never holds your money. A payment goes from the wallet that pays to the seller. Where a product takes a deposit, a contract holds it, not ZEAM, and what is not spent goes back to the wallet that funded it.

Money reaches ZEAM three ways only: as its fee on a sale, as the price where ZEAM itself is the seller, and as a gas charge you were quoted before you signed for it.

What moves it

Money leaves a wallet only when that wallet signs. What it signs fixes the amount and where it goes. ZEAM’s services send what was signed, as it was signed. They cannot change the amount or where it goes.

The price is stated before anything is signed. For a call priced by use, that is the most it can cost.

The fee

ZEAM’s fee is a fixed share written into the contract that pays the seller. That contract has no owner. No one can change the share, ZEAM included. Where ZEAM is the seller, the whole payment goes to ZEAM.

What anyone can check

Every payment settles on Base, a public blockchain. Anyone can read it, with or without us.

The software you install from ZEAM is published under open licenses, and its source can be read. The services ZEAM runs are not published.

The limits

• With a pass, ZEAM’s pass service holds that pass’s key in memory once its link is in use. With that key it can pay only that pass’s seller, up to what was loaded, or ask for the balance to go back to the wallet that funded it.
• A payment for a call that was served is final.
• ZEAM’s services can decline to send a transaction. They cannot keep a deposit from going back: the contract that holds it pays it back to the wallet that funded it, without us.

What we keep

• No accounts and no sign-up. A wallet address, or the address of a pass a wallet funded, is the only lasting identifier the paid services use.
• We keep server logs. They hold IP addresses. They stay on our servers.
• No cookies, no third-party analytics or ad trackers, and no profiles.
• We do not sell or share our logs. Cloudflare carries the traffic as our network provider.

Who we are

ZEAM Labs, LLC, Delaware file number 10206382; the filed documents are at https://github.com/zeam-labs/ZEAM-Labs-Corporate-Docs. Contact: info@zeamlabs.com. A person reads it.

ZEAM :: Prism

Every line names the place you check it. The money, the ledger and the exit are on a public chain you can read without us.

Where your money is

When you pay over x402, your collateral sits in the x402 batch-settlement escrow at 0x4020074e9dF2ce1deE5A9C1b5c3f541D02a10003. It is not our contract: it is hardcoded in @x402/evm. No owner, no pause, no upgrade, no sweep. Deposits enter through its collectors, 0x4020806089470a89826cB9fB1f4059150b550004 (EIP-3009) and 0x4020425FAf3B746C082C2f942b4E5159887B0005 (Permit2). Read any of it on Base through any node. /verify answers the same reads free, with no wallet, within the hourly allowance it states, which can be zero. The 402 answer carries an MPP session challenge, below, and no MPP charge.

When you pay by an MPP session, your deposit sits in the session escrow, which is a separate contract from the x402 escrow. Its address is the escrowContract of the session challenge in the 402 answer, and services.json states it. It was deployed by us. It has no owner or administrator and cannot be changed, by us or anyone, and it has not been audited or reviewed by anyone outside its authors. You spend the deposit with signed vouchers, it pays the receiver below through a payee contract that has no owner and can only forward to that receiver, and the unspent part returns to you when the session is closed or when you withdraw it yourself. Read it on Base through any node.

Who holds which key

The receiver 0x22e35149493B9BB147F8225AF27Bcf499407Aa7b is a split with no owner that pays 0xc60996007B7657DE2F39fA0577E97d7aAF3b7d1e 100%. With the ZEAM :: Pass software or your own code, your key signs each voucher on your machine. With a pass, ZEAM's pass service signs with the pass's key, which can only pay ZEAM :: Prism or return the balance to the wallet that funded it. With a pass at ZEAM :: Prism, ZEAM runs both the pass service and the seller; the most that can be spent is still what you loaded. A voucher is a signed ceiling; we cannot claim above it.

What we can charge, and how you check it

A claim takes what you were charged: the price of each paid call, the time buy_time bought, and never time you did not burn, which comes back on refund. /healthz/books reconciles the receiver against the escrow's Settled events. /healthz/settlement reports what is unclaimed and the last claim and payout.

Leaving without us

For an x402 deposit, POST https://mcp.zeamprism.com/refund and the unspent balance, unburned time included, goes back to the payer. Or take it yourself: initiateWithdraw, then finalizeWithdraw after 86400 seconds, your gas, and it works if we refuse. For a session, close it and the unspent part of the deposit goes back to the payer in the same transaction; our relay sends the close, and pays its gas when what the session spent covers the gas of opening it, of any top-up or close request our relay sent and of closing it. Or take it yourself: request a close on the session escrow and withdraw after its grace period of 15 minutes, through our relay under your signature, which pays that gas when what the session has settled covers the gas of opening it, of any top-up our relay sent and of leaving it, or with requestClose and withdraw at your gas, and it works if we refuse. When that gas is not covered, the gas is taken in USDC from what the MPP session returns, as with an x402 refund, and no ETH is needed. Your own requestClose and withdraw remain available and are the only way out of a session that needs ETH on Base for gas. Stop signing and we cannot charge you again.

What we keep

No accounts, no API keys, no names. The network address we see counts free calls for the current hour. A channel's time lives while the channel does; its record is kept for as long as settlement needs it, with no automatic deletion date. The privacy notice is the whole list.

Write to info@zeamlabs.com to ask what we hold about a wallet, a pass or a channel, or to ask us to correct or delete it.

Proving it is us

x402-trust.txt carries the key the ZEAM :: Prism endpoint answers x402 Trust with. security.txt is where to report a problem; a person reads it. Contract issues go upstream to x402.