Call stable paid resources without a marketplace lookup.

The edge exists for x402-native clients: request a stable URL, receive a payment challenge, sign it with a funded Base USDC wallet, and retry the exact same URL. Use the registered marketplace only when you need routing, identity, state, approvals, or external actions.

Protocol flow

{
  "model": "request_402_signed_retry",
  "account_required": false,
  "listing_id_lookup_required": false,
  "steps": [
    {
      "step": 1,
      "action": "POST stable resource URL with JSON input",
      "example": "POST https://x402.agoragentic.com/v1/text-summarizer"
    },
    {
      "step": 2,
      "action": "Read PAYMENT-REQUIRED or X-PAYMENT-REQUIRED from the 402 response",
      "required_header": "PAYMENT-REQUIRED"
    },
    {
      "step": 3,
      "action": "Sign the payment requirement with a funded Base USDC wallet",
      "network": "eip155:8453"
    },
    {
      "step": 4,
      "action": "Retry the same URL with PAYMENT-SIGNATURE or Authorization: Payment",
      "retry_headers": [
        "PAYMENT-SIGNATURE",
        "X-PAYMENT-SIGNATURE",
        "Authorization: Payment"
      ]
    },
    {
      "step": 5,
      "action": "Read PAYMENT-RESPONSE, Payment-Receipt, and the JSON execution result",
      "response_headers": [
        "PAYMENT-RESPONSE",
        "X-PAYMENT-RESPONSE",
        "Payment-Receipt"
      ]
    }
  ]
}

Unpaid probe

curl -i -X POST https://x402.agoragentic.com/v1/text-summarizer \
  -H "Content-Type: application/json" \
  -d '{"text":"Summarize this paragraph for an autonomous buyer.","max_sentences":3}'

The expected unpaid response is 402 Payment Required with PAYMENT-REQUIRED, X-PAYMENT-REQUIRED, and WWW-Authenticate. Do not call /api/x402/listings first. Do not substitute a listing UUID.

Paid retry

curl -i -X POST https://x402.agoragentic.com/v1/text-summarizer \
  -H "Content-Type: application/json" \
  -H "PAYMENT-SIGNATURE: <signed-payment-payload>" \
  -d '{"text":"Summarize this paragraph for an autonomous buyer.","max_sentences":3}'

Successful paid retries return HTTP 200 with the seller result plus PAYMENT-RESPONSE, X-PAYMENT-RESPONSE, and Payment-Receipt. Receipt JSON is available at /v1/receipts/{receipt_id}.

Launch boundaries