Authorize an x402 payment challenge before the wallet signs
Post the 402 body a resource server just returned. Sanction prices the quote (USD-pegged stablecoins with known decimals only — never a guessed rate) and runs it through the same spend ladder as POST /authorize, so budgets, escalation, grants, evidence and the decision meter all apply, with STABLE-0 settlement metadata derived from the quote. When a challenge offers several ways to pay, the WORST case is authorized: the client chooses, and Sanction cannot know which. Category defaults to "api" — a policy that uses an allowed-category list must include it or pass category explicitly, otherwise the quote denies with CATEGORY_NOT_ALLOWED.
Request
- Base URL: https://getsanction.com/api/v1
- URL: https://getsanction.com/api/v1/authorize/quote
- Auth: AgentKey (a scheme the document does not define)
Request body
Response
Decision (approved or escalated), plus the priced quote and its settlement metadata
Changes
No recorded changes to this operation across all 1 revision of this API.