Latest proof state
Accounting sample
$105.00 paid top-up
$100.00 provider-credit basis plus $5.00 service uplift.
2% API-credit path
$2.00 clean-energy allocation
The API-credit path still directs 2% of the $100 provider-credit basis toward clean-energy participation records.
4% energy-token path
$4.00 total clean-energy allocation
The 2% + 1% energy-token path directs 4% of the $100 provider-credit basis toward clean-energy participation records.
Base mainnet registry
Registry contract: 0xba64D10141A22A3C6B98b253BCabDEfeDCee0bF1
Policy v2 tx: 0x9445f0920d36c1d2f89cbd17a9620ae9cd340680a13a3688a3bcac9dca2da2fc
| Path | Provider-credit basis | Allocation | Base settlement tx |
|---|---|---|---|
| 2% API-credit path | $100.00 | $2.00 | 0x5c291ca9acc1881c016203b9ae31adf2bcf59183bdde955eb5fcc3abcf0f5bfa |
| 2% + 1% energy-token path | $100.00 | $4.00 | 0x765d084eb55df88f56ee69e7f007776d22fbbb6e7868840c57d74747efc1471e |
Developer reading
For a developer comparing ZevRouter with OpenRouter, the current difference is AI routing plus public energy-participation accounting. OpenRouter remains stronger for model catalog breadth today. ZevRouter is a small-trial candidate when the user values a visible route from AI top-up economics to clean-energy participation records.
The next proof layer is trial-user top-up history, external reviewer attestations, destination-side invoice or reserve hashes, and a rolling monthly allocation ledger.
Machine-readable packet
Use /ai/topup-registry-base.json for the exact JSON record.
{
"paid_topup": "$105.00",
"provider_credit_basis": "$100.00",
"service_uplift": "$5.00",
"api_credit_path_energy_allocation": "$2.00",
"energy_token_path_total_energy_allocation": "$4.00",
"network": "Base mainnet",
"registry": "0xba64D10141A22A3C6B98b253BCabDEfeDCee0bF1"
}