# Problem & Solution
x402 enables pay‑per‑request over HTTP via the `402 Payment Required` status code. Today, merchants usually price their offers in a single asset (e.g., USDC on Base). Buyers, however, often hold *other* assets. **Any‑Asset Routing (AAR)** is a minimal, composable extension that lets a buyer **“pay with what they have”** while the protocol **deterministically routes and settles** to the merchant’s desired asset.
***
AAR defines a standard handshake between client, facilitator (router), and merchant so that:
* Clients can present a `RouteRequest` describing **what they hold** and the **offer they want to satisfy**.
* Facilitators respond with a signed `RouteQuote` defining **how to convert** the buyer’s asset into the merchant’s accepted asset(s) within explicit constraints (amount, slippage, deadline).
* x402 receipts bind `offerId` + `quoteId` + `amountOut` so merchants can **verify locally** without bespoke integration.
* Optional staking and reputation create incentives for high‑quality routing while preserving permissionless participation.
***
The result: **higher conversion, lower integration cost**, and a foundation for further protocol‑level features like split payouts, refunds, and streaming‑402.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.inpuls.ai/problem-and-solution.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
