One rule: the fresh HTTP 402 challenge is payment authority. Do not use a wallet, price, or payment instruction copied from an old page, cache, crawler, or registry.
network: eip155:8453 asset: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 # Base USDC payTo: 0xc29185fa176357612f3194735753e520e91adc46 protocol: x402-v2 402: PAYMENT-REQUIRED retry: PAYMENT-SIGNATURE success: PAYMENT-RESPONSE
Always re-read the fresh challenge before authorizing payment. A 402 challenge or signature is not settlement proof.
Choose a GET buyer job below. This probe only fetches the HTTP response; it does not pay.
Public URL → clean LLM-ready Markdown.
GET https://squeezeos-api.onrender.com/api/web/read-markdown?url=https%3A%2F%2Fexample.com
Reference-rate currency conversion for agent pricing and calculations. No FX settlement or custody.
GET https://squeezeos-api.onrender.com/api/fx/convert?from=USD&to=EUR&amount=100
Public company, DNS, TLS, and web evidence for a domain.
GET https://squeezeos-api.onrender.com/api/enrich/domain?domain=example.com
Extract public webpage text and metadata.
GET https://squeezeos-api.onrender.com/api/web/extract-once?url=https%3A%2F%2Fexample.com
1. Call the target URL without payment. 2. Require HTTP 402 and read PAYMENT-REQUIRED. 3. Verify network, asset, payTo, amount, and resource from that fresh challenge. 4. Apply the caller's own spending policy. 5. If authorized, retry with PAYMENT-SIGNATURE. 6. Count payment only from successful settlement evidence / PAYMENT-RESPONSE.