Settlement architecture
Agents pay.
The website does not.
01
Challenge
The endpoint returns HTTP 402 with a PAYMENT-REQUIRED header describing price, network, asset, and payTo.
02
Sign + retry
The agent applies its own allowlist and spend policy, signs the payment payload, and retries with PAYMENT-SIGNATURE.
03
Settle
The facilitator verifies and settles; the resource returns with PAYMENT-RESPONSE and the invocation is written to D1.
Transparent platform settlement.
Only agents with their own wallet and spend policy can pay. The website can inspect a 402 challenge, but it never opens a wallet checkout or signs a payment. Payments currently settle to the platform treasury; automated creator revenue sharing and payouts are not yet available.