For agents and payers (the main product)
- Install four ways: an auto-setup file (zbase.app/SKILL.md, live), an MCP server (claude mcp add zbase -- npx -y @zbase-protocol/mcp@latest), a CLI through npx, or the
SDK @zbase-protocol/core. Both npm packages are published: mcp@0.3.1 and core@0.5.0, last updated 21–22 Jul.
- Six wallet tools:
- balance: shows spendable funds.
- fund_address: gives the address to send USDC to.
- fund_sweep: moves that USDC into the privacy pool. It's gasless, so you don't need ETH.
- probe: a free check of whether a seller is compatible, before you spend anything.
- pay: pays a seller's URL, with a maximum amount you set.
- seed_backup: shows the 12-word recovery phrase.
- How a payment works: it is paid from a fresh single-use wallet, with a ZK withdrawal from the pool (proof takes about 0.7s). A payment takes about 7–15s when things
are warm and about 21s from cold. Leftover change is recoverable from the seed, and settlement can't double-charge if a response is lost.
- Proven sellers: BlockRun, Nansen and MetaLend returned 200 and delivered normally.
For sellers and API providers
- No integration needed: the seller gets a standard payment and can't tell zBase was involved.
- Stealth addresses (optional): you register a meta-address once, and each payment lands at a new, unlinkable address.
- Compliance screening: every deposit is checked against the OFAC sanctions list plus a curated list of hack and mixer addresses. Deeper screening (Chainalysis-style) is
on the roadmap.
For developers
- A live API playground where you can call one endpoint, GET /api/facilitator/supported. The five endpoints that move money are documentation only.
- Reference pages for contracts, circuits, the Merkle tree and the wallet backend, plus trust and threat models.
Give feedback to the team
Your message is private to you and the zBase team.
Create an account to send feedbackAfter signup, you can write a private message with this update attached.