Fetch web content via residential proxy
The agent retrieves the raw HTML or JSON response from a target URL using a residential IP address, bypassing geo-restrictions or anti-bot measures without requiring an account.
How it works
Read-onlyResearch and knowledge
The agent constructs a POST request to the /x402/fetch or /mpp/fetch endpoint with the target URL. It handles the HTTP 402 response containing the payment quote, signs the quote using x402 or MPP protocols, and retries the request to receive the raw content. The agent should verify the target URL is valid and check the pricing page for current limits before initiating the paid fetch.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Prompt for Fetch web content via residential proxy
Fetch the content of https://example.com using a residential proxy. Use the agproxy MCP server to handle the payment quote and retrieve the raw response.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
Residential proxy packs and a raw fetch for AI agents, paid per call in stablecoins with x402 or MPP.agproxy MCP documentation