MACHINE ACCESS / PAY-PER-REQUEST
A clear price.
For every request.
Tollframe is being designed to make paid access legible to both agents and people. A resource, a payment requirement and an explicit authorization boundary.
Inspect a request ↓REQUEST / LOCAL EXAMPLEMarket depth snapshot
GET/depth/example04SettlementPLANNED
05AccessPLANNED
RESOURCE REQUESTILLUSTRATIVE
GET01
Ask for a resource.
A machine requests a market-depth snapshot. Inspect what a payment requirement would need to describe.
- Resource
- Market depth snapshot
- Price
- Not returned yet
- Authorization
- Not requested
The boundary
belongs in the interface.
Tollframe would separate a quoted requirement from permission to spend. Verification, settlement and resource delivery would follow only after valid authorization.
What happens on this page?
Three local steps explain the request, an illustrative HTTP 402 requirement and the authorization boundary. No network call, signature, payment or receipt is generated. TOLL is a brand-token candidate, not an enabled payment asset.