Fetchgate

Fetchgate

A web-content API and machine-payable storefront for AI agents. Fetch anyURL as clean Markdown or structured metadata, and buy digital goods — all overplain HTTP or MCP, with a free tier or pay-per-call via x402(USDC on Base), no account required.

Live: https://fetchgate.dev · MCP endpoint: https://fetchgate.dev/mcp ·llms.txt ·openapi.json

This repository is the public home and documentation for the hosted service(the service runs on Cloudflare Workers). The machine-readable descriptors itserves are mirrored here: llms.txt, openapi.json,server.json.

Products — datasets & tools for agent builders

Curated, honestly-sourced digital products for people building AI agents. Buy bycard on Gumroad, or machine-to-machine via x402 at GET /v1/buy/:id. Freesamples of each are in samples/ — try before you buy.

💎 Best value: Fetchgate Complete Bundle — all 6 for $109 (save $39 vs. $148 separately).

What it does

Reader API

Turn a URL into agent-ready content, server-side:

# URL -> clean Markdown (scripts/nav/ads/boilerplate stripped)
curl "https://fetchgate.dev/v1/read?url=https://example.com"

# URL -> structured metadata (title, description, canonical, OpenGraph, ...)
curl "https://fetchgate.dev/v1/meta?url=https://example.com"

Free tier: 30 requests/day per IP. Beyond that, pay per call via x402(/v1/read $0.002, /v1/meta $0.001).

MCP server

The same tools are exposed over the Model Context Protocol(Streamable HTTP) at https://fetchgate.dev/mcp, so MCP-native agents can callread_url, get_metadata, list_products, and get_purchase_info directly.Listed in the official MCP registry as dev.fetchgate/fetchgate.

Storefront (buy digital goods over HTTP)

GET /v1/products returns a catalog; GET /v1/buy/:id is a standard x402402-then-pay flow that ends in a signed, time-limited download URL — an agentcan complete a purchase with no cart, checkout page, or human step. Currentinventory is agent-builder tooling (curated datasets, test corpora, harnesses).

curl "https://fetchgate.dev/v1/products"
curl "https://fetchgate.dev/v1/buy/x402-registry-2026-08-21"   # -> 402 x402 challenge

How x402 payment works

A request with no payment gets HTTP 402 with the payment requirements (amount,payTo, asset = USDC on Base). An x402-capable client re-sends the request witha signed X-PAYMENT header; a facilitator verifies and settles the USDCtransfer, and the request succeeds. No signup, no API key, no stored card.

Examples

See examples/: curl, Python client, and MCP client.

Articles

• x402 vs. Stripe: When Machine-Payable APIs Actually Make Sense
• x402 Integration Guide: The Mistakes That Silently Break It
• The x402 Facilitator Landscape in 2026: 21 Options Compared
• MCP Tool Poisoning: How a Tool Description Becomes an Attack
• How to Build an LLM Eval Harness That Catches Regressions Before Your Users Do
• The MCP Server Registry: 400 Servers, Cross-Referenced Across 5 Directories
• Prompt-Injection Defense Checklist
• ASCII Smuggling and Invisible Unicode: The Prompt-Injection Technique Your Filters Can't See

How it's built

ARCHITECTURE.md — the x402 flow in detail, why thepayment layer is hand-rolled instead of using the official SDK, thesigned-download-URL-as-receipt pattern, how MCP shares one authorizationpath with the plain HTTP routes, and the honest caveats (no chargebacks,facilitator trust, thin real x402 volume industry-wide).

Endpoints

Privacy & reliability

Fetched page content is not stored after a response is returned. Payments arein beta (settlement runs through a third-party x402 facilitator on Base);digital delivery only. This is an independent project — see llms.txt for thecurrent terms.