Trigger
An agent receives an HTTP 402 payment requirement for a paid API or tool.05
x402 agent payments
Authorize the purchase before the agent signs.
An x402 rail tells the agent how to pay. Featherlane AI decides whether this agent should pay this amount, to this endpoint, for this task, right now.
What breaks
Parallel discovery, duplicate retries, merchant drift, or a runaway tool loop consumes the session budget without a reliable pre-spend decision.Control point
Normalize the payment requirement, verify the grant, reserve session budget, and return a signable decision only when every boundary passes.01402 requirement
→02Authorize + reserve
→03Agent signs
→04Commit receipt
How it works
- 01Propose
Submit the exact payment requirement
The runtime sends amount, payee, network, asset, resource, purpose, principal, and session budget before signing anything.
- 02Authorize
Check grant and standing policy
Featherlane AI compares the request with the allowed host, resource, network, asset, counterparty, amount, and task scope.
- 03Reserve
Hold budget across concurrent calls
An action-bound reservation prevents parallel requests or stale balance reads from spending the same remaining budget twice.
- 04Settle
Commit only the authorized payment
The settlement proof must match the normalized requirement. Commit closes the reservation and creates the execution receipt.