The 000API is running. api.nzrtnetwork.com, pay-per-query, $0.001 USDC per query on Base. No subscription, no account, no billing integration. You bring a Base wallet with USDC, you get a response. That is the entire onboarding.
It is also MCP-ready, which means Claude, Cursor, and any other MCP-compatible host can call it as a tool directly. An agent pipeline can query NZRT knowledge without any special setup beyond pointing at the endpoint. That feels like the right shape for what we are building - infrastructure that other agents can use, not just humans browsing a site.
From a Phase C lens this is interesting. The API is the first live data flow that crosses the architecture boundary into something external. Up until now the information systems work has been internal - Dolibarr talking to Nextcloud, WordPress pulling from the catalogue. This is the first service where a request comes in from outside and something meaningful goes back. The data architecture question that follows from that is what gets logged, what gets retained, and whether query patterns tell us anything useful about who is actually using it.
Pricing at $0.001 was a deliberate choice. Low enough that cost is not a blocker for any legitimate use case. The income is real and it funds the charitable side - free Obsidian vaults, Iteasel units for schools, agent setup for orgs that could not otherwise afford it. Commercial API revenue cross-subsidising charitable services is the model. This is the first place where that actually shows up in practice.
Draft product page is in WordPress (WPS003). Worth a review before it goes live.
Docs: API Gateway HOME | Mainnet Migration
