Skip to content

doc: clarify auth webhook maxPrice scope #4019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rickstaa merged 2 commits into from
Aug 12, 2026
+1 −1
Merged

doc: clarify auth webhook maxPrice scope #4019

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e0a2633
doc: clarify auth webhook maxPrice scope
rickstaa Aug 12, 2026
b4a53f6
Merge branch 'master' into docs/remote-signer-auth-webhook-maxprice-s…
rickstaa Aug 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion doc/remote-signer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,7 +183,7 @@ a HTTP 481.
- `-maxPricePerCapability` (optional, capability/model pricing config)
- `-maxTicketEV`, `-maxTotalEV`, etc.
- **Request maximum** A client requesting a payment can also specify a `maxPrice` taken from the discovery pricing, or put in their own max (in wei). This ensures that the discovery price and actual price do not drift too much. It is recommended that clients add a ~1.2% buffer to the discovery price which should cover roughly 95% of hourly ETH-USD price moves. The format follows that of the discovery pricing scheme.
- **Auth webhook** The auth webhook can also return a `maxPrice` in the same format as the discovery price.
- **Auth webhook** The auth webhook can also return a `maxPrice` in the same format as the discovery price. It is checked only when the webhook actually fires (see [Auth webhook expiry caching](#auth-webhook-expiry-caching)) and is not retained across cached requests.
- **Selection behavior**: if an orchestrator’s price is above the signer’s configured limits, the signer rejects the payment request (HTTP 481) and the gateway will retry with a different orchestrator session.
- **LV2V session price is fixed**: Live Video-to-Video (LV2V) jobs treat price as fixed for the lifetime of the session, captured at session initialization time.

Expand Down
Loading