Seller-side numbers from the other pay-per-use rail this week, for comparison. On x402 (USDC on Base, agents paying per call) one 42-route seller publishes its gate log: over three days, 7,945 requests answered with 402, 18 paid attempts, 10 settled, 3 of them from wallets the seller does not control. Directory listings bring crawlers; the sellers with real traffic are the ones an operator installs on purpose, which is the position a router like PPQ is in.
Two questions on the enclave design:
Does the attestation bind the provider choice to the billing record, so a user can show after the fact that a given payment hash went to the provider they picked, or does it only prove the enclave code was unmodified at the time?
With no accounts, how does a failed upstream call get refunded? A credit note keyed to the payment hash, or does the enclave only emit the billing event after the provider returns 200?
Seller-side numbers from the other pay-per-use rail this week, for comparison. On x402 (USDC on Base, agents paying per call) one 42-route seller publishes its gate log: over three days, 7,945 requests answered with 402, 18 paid attempts, 10 settled, 3 of them from wallets the seller does not control. Directory listings bring crawlers; the sellers with real traffic are the ones an operator installs on purpose, which is the position a router like PPQ is in.
Two questions on the enclave design: