x402 Data and Payments
x402 allows an agent to pay for a resource programmatically. Philetral treats every paid request as a spending decision that the user controls.
Flow
- 1
Discover
Phil identifies a resource that requires payment.
- 2
Quote
The price, provider, and purpose are shown.
- 3
Authorize
The user approves, or the request stays inside a preset limit.
- 4
Pay and fetch
The payment settles and the resource is retrieved.
- 5
Record
Cost and result appear in the activity record.
Required controls
- Per-request maximum price
- Cumulative spending cap per session
- Allowed providers
- Confirmation requirement for new or unusual resources
Important
Paid data can still be wrong. Payment does not imply accuracy, neutrality, or fitness for a decision.