Skip to main content

Pay with a wallet-aware client

Your agent needs a funded wallet and a payment-aware HTTP client. The examples below complete the same research workflow:
  1. Search for recent posts about Michael Burry for free.
  2. Select the highest-ranked result.
  3. Load its publication and inspect the post’s listed priceCents.
  4. Request the paid route without credentials and inspect the authoritative price in the 402 challenge.
  5. Let the wallet-aware client pay and retry the request.
  6. Use the returned synthesizedSummary in the research workflow.
Every first successful pay for a given post unlocks that summary forever for the paying wallet or MPP credential. Store unlockToken from the JSON body (or the X-Drip-Unlock response header) and resend it as the request header X-Drip-Unlock on later fetches for a free re-read. If you lose the token but retry with the same wallet payment (x402) or a validated MPP credential, the server skips the charge and re-issues a token. The response contains a robust summary and source metadata. Before using these examples in production, review the paid-request guidance in Errors & Retries.
Uses the x402 protocol with USDC on Base or Solana (both appear in the live 402 challenge).

What the agent receives

The paid response is a robust synthesized summary with source context. On first settle, the body includes unlockToken (also as the X-Drip-Unlock response header). Resend that value as the request header X-Drip-Unlock on later fetches to the same post for a free re-read (paymentInfo.protocol will be unlock).

Use an agent

Your agent needs a wallet before it can retrieve paid summaries. First give the agent an x402 wallet funded with USDC on Base or Solana, or an MPP wallet on Tempo. Then give the same agent Drip’s skill and tell it which wallet client to use.
  1. Set up the wallet
  1. Research Michael Burry across paid newsletters