FAQ · B2B pilot
The five questions every pilot prospect asks before submitting the intake form — privacy, double-counting, methodology, auditability, and pilot pricing — answered in 2-4 short sentences each, with outbound links to the deeper /docs, /verify, and /pilot surfaces.
Carbon AI returns a receipt — it never logs the prompt, the response, or any identifier for the calling user. Only the four inputs you pass (model, region, tokens, client_id) and the carbon math they imply enter Tao's systems, and the receipt hash is a one-way function over that disclosure core.
See the full AI Transparency Policy for the data-handling, retention, and sub-processor posture.
Every receipt carries a receipt.hash — a sha256 of its disclosure core — so the same inference can never be attributed twice. The backing CDR capacity is locked to a named project (e.g. TAO-UKR-HEMP-MRV-2026) and retired atomically per receipt, not pooled and re-split.
See /verify for the live attestation audit UI — every receipt hash resolves to its project ID and retirement date.
The kg_co2e_estimated on a receipt is market-based Scope 2 over the daily interval the request landed in: 0.3 kWh × PUE 1.6 ≈ 0.48 kWh × grid intensity. It's not the GPU's nameplate draw, and it's not a Scope 3 LCA — it's the disclosure figure a CSRD auditor will recognise.
The exact math, the per-region grid-intensity table, and the versioned methodology object are documented in the API Docs under GET /api/v1/inference/attest.
Every receipt response includes a receipt.verifyUrl at /verify/<hash>. Hit the URL, paste the hash, and the page re-derives the sha256 from the same disclosure shape the API used — so a downstream auditor can independently re-prove the receipt without trusting Tao's UI.
See /verify for the live attestation audit UI — paste a hash or scan the receipt's QR.
Pilot partners get a quota tied to expected monthly inference volume and the EU-region unit cost, billed as a monthly EUR figure with the verified-CDR line item called out separately. The pilot is 90 days and converts into an annual plan, a per-receipt plan, or the loop closes — there is no auto-renewal in the pilot.
Send the volume, region, and use case via the pilot intake form; we respond within one business day with a pilot key, quota, and integration window.