Merge branch 'main' of https://github.com/XSpoonAi/xspoonai.github.io

Author: veithly

llm.txt

@@ -15106,7 +15106,7 @@ sequenceDiagram
     Agent->>API Server: GET /premium-data
     API Server-->>Agent: 402 Payment Required (price, recipient)
     Agent->>Agent: Sign EIP-712 payment
-    Agent->>API Server: GET /premium-data + X-PAYMENT header
+    Agent->>API Server: GET /premium-data + PAYMENT-SIGNATURE (v2) / X-PAYMENT (v1)
     API Server->>x402 Facilitator: Verify signature
     x402 Facilitator->>Blockchain: Execute transfer
     Blockchain-->>x402 Facilitator: Confirmed
@@ -15117,9 +15117,9 @@ sequenceDiagram
 | Step | What Happens |
 |------|--------------|
 | **1. Request** | Agent calls a paid API endpoint |
-| **2. 402 Response** | Server returns payment requirements (amount, token, recipient) |
+| **2. 402 Response** | Server returns payment requirements (v2 via `PAYMENT-REQUIRED`, legacy v1 via JSON body) |
 | **3. Sign** | Agent signs an EIP-712 typed-data payload (no gas yet) |
-| **4. Retry** | Agent sends request again with signed payment header |
+| **4. Retry** | Agent sends request again with the signed payment header (`PAYMENT-SIGNATURE` for v2, `X-PAYMENT` for v1) |
 | **5. Verify & Execute** | Facilitator verifies signature and executes transfer on-chain |
 | **6. Success** | Server returns the requested data |
 
@@ -15218,21 +15218,21 @@ sequenceDiagram
         Agent->>Agent: Merge requirements + config overrides
         Agent->>Agent: Select signer (PRIVATE_KEY or Turnkey)
         Agent->>Agent: Build typed-data payload
-        Agent->>Agent: Sign -> X-PAYMENT header
-        Agent->>Paywall: Retry with X-PAYMENT
+        Agent->>Agent: Sign -> PAYMENT-SIGNATURE (v2) / X-PAYMENT (v1)
+        Agent->>Paywall: Retry with signed payment header
         Paywall->>Facilitator: verify_payment (optional settle)
         Facilitator-->>Paywall: Valid? + receipt
         alt Invalid
             Paywall-->>Agent: 402 / error
         else Valid
-            Paywall-->>Agent: 200 + X-PAYMENT-RESPONSE
+            Paywall-->>Agent: 200 + PAYMENT-RESPONSE (v2) / X-PAYMENT-RESPONSE (v1)
             Agent->>Agent: Log receipt / update memory
             Agent-->>User: Protected content + summary
         end
     end
 ```
 
-If the paid retry fails (for example `verify_payment` rejects the header or the facilitator reports an error), the paywall server immediately returns another `402` or error payload and the agent decides whether to run `x402_paywalled_request` again with corrected parameters. A successful verification moves straight into settlement and target agent execution, so there is no additional retry cycle once the `X-PAYMENT` header is accepted.
+If the paid retry fails (for example `verify_payment` rejects the header or the facilitator reports an error), the paywall server immediately returns another `402` or error payload and the agent decides whether to run `x402_paywalled_request` again with corrected parameters. A successful verification moves straight into settlement and target agent execution, so there is no additional retry cycle once the payment header is accepted (`PAYMENT-SIGNATURE` in v2, `X-PAYMENT` in legacy v1).
 
 ## Operational checklist
 
@@ -15731,10 +15731,10 @@ What happens:
 
 1. The script prints signer details and the target resource (`https://www.x402.org/protected` by default).
 2. A `SpoonReactAI` instance performs a ReAct loop:
-   - Calls `http_probe` (no payment) to capture the 402 challenge.
+   - Calls `web_scraper` (no payment) to capture the 402 challenge.
    - Calls `x402_paywalled_request` to sign and submit a 0.01 USDC payment.
    - Retrieves the protected payload (a SoundCloud embed) after settlement.
-3. The console logs tool traces, the signed `X-PAYMENT` header, and the decoded settlement receipt (transaction hash, payer, network).
+3. The console logs tool traces, the signed `PAYMENT-SIGNATURE` (x402 v2) header, and the decoded settlement receipt from `PAYMENT-RESPONSE` (transaction hash, payer, network).
 
 ## Troubleshooting
 
@@ -20925,9 +20925,11 @@ Consult [API Reference: x402](../api-reference/spoon_ai/payments/) for:
 Follow [Example: x402 ReAct agent](../examples/x402-react-agent.md) to run the ReAct demo (`uv run python examples/x402_agent_demo.py`). It walks through:
 
 - Preparing `.env` and funding the signer.
-- Observing the agent call `http_probe`, then `x402_paywalled_request`, retrieve the protected page, and print the signed `X-PAYMENT` + settlement receipt.
+- Observing the agent call `web_scraper`, then `x402_paywalled_request`, retrieve the protected page, and print the signed `PAYMENT-SIGNATURE` + settlement receipt.
 - Troubleshooting common facilitator or configuration errors.
 
+> Note: x402 v2 uses `PAYMENT-REQUIRED` / `PAYMENT-SIGNATURE` / `PAYMENT-RESPONSE` headers. SpoonOS tools still support the legacy `X-PAYMENT` / `X-PAYMENT-RESPONSE` headers for older v1 paywalls.
+
 ## Quick checklist
 
 - Fund the signer via [Circle faucet](https://faucet.circle.com/).