ZEAM Labs LLC, a Limited Liability Company formed in Delaware, United States —
Delaware file number 10206382, formed 2025-05-27. Registered agent:
Northwest Registered Agent Service, Inc., 8 The Green, Suite B, Dover, DE 19901, United States. Contact: info@zeamlabs.com.
The filed certificate of formation, operating agreement, initial resolutions and the signed IP licence are
published in full at https://github.com/zeam-labs/ZEAM-Labs-Corporate-Docs. The file number above resolves
independently of us — but note that the
State of Delaware entity search is browser-only: it needs JavaScript,
carries a honeypot field, and answers a scripted query with an empty result table rather than an error —
an auditor confirmed it returns nothing for “GOOGLE LLC” either, so an empty result there is
evidence of a block and not of absence. The filed certificates linked above are the machine-checkable route, and they carry
the same file number.
The intellectual property is held by ZEAM Foundation LLC (file number
10206388, formed 2025-05-27), which licenses it
exclusively to ZEAM Labs LLC; its filings are at
https://github.com/zeam-foundation/ZEAM-Foundation-Corporate-Docs.
A wallet-paid Ethereum and Base JSON-RPC service, reached over MCP. There is no account, no API key and no human step. Using the paid tools constitutes acceptance of these terms as published at the time of the call.
We have no external paying customers yet. There is a settlement history on chain
behind this endpoint and the books reconcile to the unit — but it is the record of us testing our own
product. Nearly every wallet that has opened a channel here was funded by our own treasury. We would rather
say that than have you find it, which you can: the payers are public, and
services.json carries the same statement under
payment.provenance with the method for checking it. Nothing on this endpoint claims adoption;
this sentence exists so nothing implies it either.
The two chains are not equally deep, and the difference is the one thing most likely to make this
service the wrong choice for you. Base is archive and at tip, with Flashblocks on, so the
pending tag returns the preconfirmed next block; no trace_ methods are served on it.
Ethereum keeps 10064 blocks of state history — roughly
33 hours. Beyond that window trace_ and debug_ calls
fail on Ethereum. If your work needs deep historical state on Ethereum, this is not an archive node and you should
not buy it expecting one. The per-chain method lists are in the rpc tool description and in
llms.txt, and the free sample tool lets you check any of it
before paying.
You buy time on a line, not calls. The goods are free; what you pay for is holding the line open, at 1 micro-USD per 1ms. A second is 1000 micro-USD. An hour of continuously held line is $3.60, whatever volume goes through it.
Deposit once, open a line on the socket at /pay, and it hands you a credential. Then call the
tick tool on a steady cadence: that is an ordinary paid call and it buys the milliseconds since your
previous tick. Everything else you call carries only that credential in a line argument and costs
nothing — no signature per call, nothing to order, and as many calls in flight at once as you like, across every
tool we serve. Miss a tick and the line keeps serving for 5000ms — room to top up, since your
wallet deposits before it can send the next tick. Stop entirely and the line closes 5000ms after your
last request. An open line bills the whole time it is open, so a line you forget costs at most
5000 micro-USD past your last tick and then stops existing.
Deposit sizing. 1000 micro-USD buys a second of line and 3600000
buys an hour. A tick is quoted at 250 micro-USD — the same figure as a call, and the most one
tick can bill. Your wallet funds a multiple of that quote, and the multiple is your client's choice, not
ours: our bridge asks 400× and the scheme refuses anything below 3×. A deposit tops up on its own
as it depletes. Without a line, a call buys the minimum hold of 250ms —
250 micro-USD, the amount quoted in accepts, which is what we charge. That is the
same meter a line uses, not a second one: we sell time, and this is the smallest slice of it we can settle on chain.
The floor exists because a 1ms charge cannot be settled for less than it is worth.
Which is cheaper is arithmetic, and it is yours to do. A held line bills wall-clock time whether you call or not; slices bill only when you call. So holding wins above one call per 250ms and loses below it — at one call a second you would hold 1000ms to use 250, paying about four times what slices cost. Hold a line for sustained bursts; buy slices when you are sparse.
We serve while the line is paid up and while collateral remains behind it, whichever binds first. A voucher larger than your deposit is refused, because a signature is not money.
Check the withdraw delay before you sign it. Your unilateral exit —
initiateWithdraw then finalizeWithdraw — reverts for anyone but you, so we cannot
take your collateral. What we do choose is how long that exit waits: extra.withdrawDelay arrives in
our 402 and you sign it into the channel config, where it is immutable. The contract permits up to
30 days; we quote 900 seconds, the contract minimum and the most
payer-favourable value available. Read the field rather than trusting it — it is the only place the
guarantee above has any give in it, and a client that caches accepts and pays without looking
would never see a change.
Getting your money back costs you nothing. Ask on the socket with
{op:"refund"} on an open line and we send the unspent collateral back at our gas.
We also return unspent collateral on our own once a channel has gone quiet, without being asked — but that is
something we do, not a deadline we are giving you, and you should not plan around it. You can also always take it yourself — initiateWithdraw, then
finalizeWithdraw after 900s — which needs nothing from us
and is the guarantee that none of this rests on our goodwill. That path is two transactions of your own gas, which at
small ticket sizes can cost more than the service did; the three above exist so it never has to.
There is no per-call charge and no per-method price list. Everything the endpoint exposes is included.
The machine-readable form of all of this is at
services.json under payment.rate, and in
llms.txt.
Every asset we quote has a base unit worth far less than one request, so the ceiling above is exact in all of them. The meter still accrues fractional units and carries the remainder between requests, so you are never billed a whole unit before one has genuinely been earned. The per-asset quotes are in services.json.
Settlement is the batch-settlement scheme over x402 on eip155:8453, in any of:
USDC, USDT, DAI, EURC, WETH. Payment travels in the MCP tool call's _meta, not an HTTP header. Amounts are received at
0x0Cec1E92fa2b92a93194D40C1D38E989E3C0597c. You pay no gas; we submit.
A deposit is collateral, not a payment. It is held by the batch-settlement contract at
0x4020074e9dF2ce1deE5A9C1b5c3f541D02a10003 on Base, which you may inspect before funding — eth_getCode
against that address is served free and without a wallet at https://mcp.zeamprism.com/bootstrap.
That contract is not ours. It is x402's own batch-settlement escrow, hardcoded in
@x402/evm and published to npm by Coinbase in 2.12.0 on 2026-05-13, two days before
the contract existed on Base. No owner, no pause, no upgrade, no sweep. Verify with
npm pack @x402/evm@2.12.0 and grep the package for the address.
Unused collateral is withdrawable only by your side of the channel — the
payer or the payerAuthorizer you named when the channel was opened, which for most clients
are the same key but need not be. After the 900-second withdraw delay, by calling
initiateWithdraw and then finalizeWithdraw. We cannot move it and we cannot
withhold it. What we can claim is only the time the meter actually earned, against a voucher your wallet signed.
Time already metered and claimed is final and is not refunded, including for calls that return
empty results, revert, or are not useful to you.
Do not attempt to disrupt the service, our infrastructure or third parties, including denial-of-service, settlement-replay or oracle-manipulation attacks; do not attempt to obtain metered service without paying for it. We may refuse or terminate service to a wallet at our discretion. Termination does not affect your right to withdraw collateral under section 4.
No uptime commitment is offered or implied. The service is pre-revenue infrastructure and may change,
pause or be withdrawn. Prices may change; calls made after a change reflect the new price, which is always
readable in advance at https://mcp.zeamprism.com/services.json and in the 402 you receive before paying anything.
Provided "as is", without warranty of any kind. Chain data is served from our own nodes; we do not warrant
that any node, including ours, is correct, current or complete. Verify anything you rely on — the free
sample tool exists so you can check our answers against an independent source before trusting us.
To the maximum extent permitted by law, ZEAM Labs, LLC is not liable for indirect, incidental, special or consequential damages, or for lost profits, arising from use of the service. Aggregate liability for any claim is limited to the amounts you paid us for metered time in the 30 days preceding the claim.
These terms may change. The version in force is the one published here at the time of your call.
These terms are governed by the laws of the State of Delaware, United States, without regard to conflict-of-laws principles — the same jurisdiction as ZEAM Labs, LLC's company terms, which govern the websites.