Paying for AI compute stopped being the hard problem on July 14, when Visa, Mastercard, and the Linux Foundation put their names on x402.
We're partnering with
@0G_labs because the harder problem, proving the compute you paid for actually ran, still needed solving.
0G doesn't just claim its compute is trustworthy, it lets you pick how much proof you need. On the private tier, a provider has to deploy the model on TEE hardware, Intel TDX on the CPU side with H100 or H200 GPUs in confidential computing mode. The enclave signs the response and the attestation is fixed at deployment, so you can check the enclave measurement and the model hash rather than take anyone's word for it. Route a request to Claude or GPT-5.6 instead, and 0G is upfront about the difference: authenticated delivery through the same enclave-secured broker, not in-chip execution, because 0G doesn't hold those weights and isn't going to pretend otherwise.
Cluster sits on top as the orchestration and settlement layer, same as always, but the decision it's making here is different: not which privacy mode a step needs, but which verification tier is worth paying for. A cheap answer routes wherever is fastest. A number that ends up in a financial report routes to 0G's fully attested models, and the x402 payment on Base only clears once the attestation checks out, not before.