Web content for AI agents — no subscriptions, no sign-ups.
WebFetch is a simple API that turns any webpage into clean, readable text. AI agents use it to grab articles, docs, and site content — paying just half a cent per page through an automatic micropayment system. No monthly fees, no accounts, no human in the loop.
Like a retriever, but for URLs.
Your agent sends a URL. We fetch it in a real browser, strip the cruft, and hand back clean Markdown. The whole thing costs half a cent.
Agent sends a URL
Your agent calls POST /fetch with any web URL. No account, no API key, no human.
402 — Payment Required
The API returns payment terms. Your agent's crypto wallet automatically signs a micro-payment of $0.005 in USDC and sends it back.
Browser renders the page
We run a real headless Chromium on Cloudflare's edge. JavaScript, SPAs, dynamic content — everything works.
Clean Markdown delivered
We strip ads, nav, scripts. What comes back is the content — readable, structured, LLM-ready.
$ curl -X POST https://webfetch.app/fetch \
-H "Content-Type: application/json" \
-d '{"url":"https://example.com/article"}'
→ 402 Payment Required — $0.005 USDC on Base
→ Agent signs payment with x402 wallet
$ curl -X POST https://webfetch.app/fetch \
-H "Content-Type: application/json" \
-H "Payment-Signature: <signed-payload>" \
-d '{"url":"https://example.com/article"}'
# Article Title
Here's the full article content in clean,
readable Markdown. No ads. No nav bars.
No cookie consent popups. Just the text.
$ ▌
Simple. Usage-based. Agent-ready.
No subscriptions. No commitments. Pay exactly what you use.
PAY PER FETCH
- No account required
- No API key to manage
- Agent pays autonomously
- Any URL, any format
One command. Zero setup.
WebFetch publishes an MCP server at webfetch.app/mcp. Add the URL to your MCP client config and any compatible tool discovers it as a native tool. No API keys, no sign-up.
{
"mcpServers": {
"webfetch": {
"url": "https://webfetch.app/mcp"
}
}
}
// Agent auto-discovers tool: webfetch_fetch(url)
→ x402 payment: $0.005 USDC
→ Markdown delivered
How MCP works
Add the WebFetch MCP server URL to your MCP client config. Your agent auto-discovers the webfetch_fetch tool and calls it whenever it needs web content. No curl commands, no API keys, no copy-paste. The agent handles the x402 micropayment through its wallet — $0.005 per page in USDC on Base.
One endpoint is all you need.
Works with any HTTP client. No SDK required. Just POST a URL and get back clean Markdown.
POST /fetch
Send a URL, get Markdown. First call returns 402 with payment instructions. Pay via x402, retry with signature, get content.
https://webfetch.app/fetch# Request body
{
"url": "https://example.com/article",
"options": {
"waitUntil": "networkidle0",
"timeout": 15000
}
}
# Response (200 — Paid)
{
"success": true,
"url": "https://example.com/article",
"markdown": "# Article Title\n\nContent...",
"metadata": { "title": "...", "browserMs": 2340, "chars": 12450 }
}
# Response (402 — Payment Required)
HTTP 402 Payment Required
PAYMENT-REQUIRED: <base64-payment-instructions>
# Client retries with payment signature
PAYMENT-SIGNATURE: <signed-payload>
Questions agents would ask if they could.
But since they can't, here's what their humans want to know.
What is x402 and why should I care?
Do I need a crypto wallet to use WebFetch?
What kind of pages work?
How is this different from Firecrawl?
Do you respect robots.txt and site blocklists?
robots.txt before fetching. If a site explicitly disallows crawling, we return an error. If a publisher contacts us (dmca@webfetch.app), we add their domain to our blocklist immediately.
What's with the dog?
Does WebFetch work with Claude Code, Cursor, or other AI tools?
webfetch.app/mcp. Any tool that supports MCP — Claude Code, Cursor, OpenCode, Codex — can discover and use WebFetch as a native tool by adding the server URL to their MCP config. Your agent just needs a wallet with a little USDC on Base to pay per fetch.
Terms of Service
1. Service. WebFetch provides a URL-to-Markdown conversion API. You send a URL, we return the rendered content as Markdown.
2. Payment. Usage is billed per request via the x402 protocol in USDC on the Base network. Prices are listed on our pricing page and may change with notice. You are responsible for all charges associated with your wallet address.
3. Acceptable Use. You agree not to use WebFetch to violate any applicable law or third-party rights. You are responsible for how you use fetched content. WebFetch maintains a built-in blocklist of known paywalled and subscription-only news sites — these domains are blocked at the API level and cannot be fetched. We also respect robots.txt and maintain a manual blocklist for any publisher who requests removal via DMCA.
4. No Guarantee. The service is provided "as is" without warranty. We do not guarantee that every URL will render successfully, that content will be complete, or that the service will be uninterrupted.
5. Limitation of Liability. WebFetch is not liable for any damages arising from your use of the service or the content delivered through it.
6. DMCA. If you believe content available through WebFetch infringes your copyright, send a notice to dmca@webfetch.app. We respond promptly.
7. Changes. These terms may be updated. Continued use after changes constitutes acceptance.
Last updated: July 2026. Questions? hello@webfetch.app