Platform / x402 Payments
PILOT · POLICY-BOUNDEDx402 payments, proof-first and capped.
Settle HTTP requests on-chain with verifiable, policy-bounded payments backed by proof and capped by design.
Payments run in test mode during the pilot.
What this is, and what it is not
It prices a request
x402 settles an HTTP request on-chain. The agent pays its own running costs, API calls, search, and inference, in USDC at sub-cent prices. Each transaction is cryptographically proof-bound.
It is not bill-pay
No invoice, due date, recurring mandate, or payee identity. Billing rails stay in their own system. x402 is a lightweight, atomic settlement layer for computational work.
Three rails, deliberately separate
x402
On-chain settlement for HTTP requests. Cryptographically proof-bound and policy-bounded. Accepting requests from pilot participants.
Payments run in test mode during the pilot.
Treasury float
Off-chain liquidity pool for faster settlement and reduced gas costs. In preview. Available for testing and feedback.
Aave supply
Yield-bearing deposits for idle capital. Currently disabled. Will enable for users who want to accrue yield on settled balances.
Bounded by policy, not by trust
Kill switch
Authorized parties can pause x402 transactions instantly without permission from intermediaries. Enforced at the contract level.
Hash-chained ledger
Every transaction is cryptographically linked to its predecessor. Tampering with history is immediately detectable.
Human gate
Large transactions require explicit human approval before settlement. Automated safeguards escalate to human oversight.
Hot-wallet ceiling
Active settlement capacity is capped by design. Excess funds stay in cold storage. Risk is architecturally limited.