Work in progress

Work in progress: we are building this site ahead of MainNet. Details will change.

This site is still being built

ZooBC is building in the open. What you see here is current and honest, but it is not finished: read it as where we are today, not as a final statement.

Between now and MainNet, things will change: wording, structure, images, and figures. Some pages are placeholders.

The wider ZooBC ecosystem arrives in stages. The wallet, the explorer, and the community channels each come online as MainNet approaches, and this site grows alongside them.

If something reads wrong, looks broken, or seems misleading, tell us. Feedback now is worth more to us than a polished launch later.

Additional languages will be enabled after the site is complete.

ZOOBC / API REFERENCE

ZooBC Gateway API

ZooBC Gateway API documentation, including proxy, status, allowlist, release, and CORS endpoints.

Choose a network

Each gateway documents the routes it really serves. The reference is generated from the running binary, not written alongside it.

TestNetzoobc.network
Open the API reference
MainNetzoobc.net
Open the API reference

MainNet opens 14 February 2027

01 / ONE BASE URL

Everything under /api/v1

The whole chain API lives under /api/v1 on any gateway, same origin as its reference page. No CORS to negotiate, no key to obtain, no rate plan.

curl -s https://zoobc.network/api/v1/blockchain/status returns the height, the confirmed height and the latest block. That is the shortest useful call and a good first check that a gateway is alive.

02 / READS AND WRITES

They go to different places

A GET is proxied to an archival node, which holds the deep history: blocks, transactions and accounts as of any height. A POST is proxied straight to a full node, never to archival, because submitting a transaction needs a mempool.

That split matters more than it sounds. An archival node is a read-only history service and used to answer POST with a 404, which is why broadcasting through a gateway once did not work. The developer guide covers the routing and the allowlist in full.

03 / FOR PROGRAMS

Reading it without a browser

A machine-readable guide to the same API is published by the gateway at agents.md, with a discovery file at llms.txt and a dependency-free Python reference at zoobc-agent-example.py.

Those are served next to the chain deliberately: a guide that tells a program how to spend money should come from the same origin as the API it describes.