hshintelligence/agent-scrape

> **Pay-per-call web scraping for AI agents — no signup, no API keys, just USDC.**
**Live:** agent-scrape.healingsunhaven.workers.dev
AI agents discover AgentScrape, pay per call in USDC on Base, and get clean structured data back — no accounts, no API keys, no human in the loop.
Two protocols, one service:
- **HTTP API** with x402 v2 payment gate — for agents using raw HTTP
- **MCP server** (Streamable HTTP transport) — for Claude Desktop, Cursor, Continue.dev, and any MCP-compatible framework
---
Why this exists
Traditional scraping APIs assume a human:
- Sign up with email
- Add a payment method
- Manage an API key
- Commit to a monthly subscription
**AI agents can't do any of that.** They have wallets. They have stablecoins. They need infrastructure built for them.
AgentScrape speaks two open standards:
- **x402** — HTTP-native payment protocol. The server returns 402 with payment requirements; the agent signs a USDC transfer; the facilitator settles on-chain; the data flows back. End-to-end in under 2 seconds.
- **MCP** — the standard agent tool interface. Agents browse, discover, and invoke tools without per-vendor SDKs.
No signup. No API keys. No subscription. Just USDC.
---
Tools
All tools cost **$0.001 USDC** during the mainnet validation window. Pricing ramps after stability is proven (see Pricing).
| Tool | Description |
|---|---|
| scrape_webpage | Scrape any URL to markdown, HTML, text, or JSON |
| extract_structured_data | AI-powered structured extraction with natural-language prompts and JSON schemas (Groq + Llama 4 Scout) |
| screenshot_webpage | PNG screenshot with viewport control (desktop/mobile/tablet, optional full-page) |
| extract_metadata | Title, description, Open Graph, Twitter cards, JSON-LD, canonical URL |
| create_browser_session | Stateful browser session with cookie + localStorage persistence |
| run_workflow | Multi-step atomic execution: navigate, click, type, wait, scroll, screenshot, extract, evaluate |
---
Quick start — HTTP API
---
Quick start — MCP
Add to any MCP-compatible client via Streamable HTTP:
The x402 payment metadata is broadcast inside the MCP tools/list response. Your client handles the payment handshake automatically when configured with an x402-compatible wallet.
---
Discovery
For machine-driven discovery, four standard endpoints are exposed (free, no auth):
| Endpoint | Purpose |
|---|---|
| / | Service profile JSON (tools, prices, network, payTo) |
| /.well-known/x402 (and .json alias) | x402 manifest — payTo, network, facilitator, all paid routes |
| /openapi.json | OpenAPI 3.1 spec for traditional tooling |
| /llms.txt | Agent-friendly plaintext description |
The 402 response itself carries the canonical payment requirements in the base64-encoded Payment-Required header, and the body includes a human-readable error with discovery links.
---
Architecture
**Stack:**
- **Runtime:** Cloudflare Workers (V8 isolates, global edge)
- **HTTP framework:** Hono + @x402/hono v2 payment middleware
- **MCP framework:** @modelcontextprotocol/sdk + agents/mcp with withX402 payment binding
- **Bazaar discovery:** @x402/extensions — every paid route declares input schema + output example
- **Browser:** Cloudflare Browser Rendering API + @cloudflare/puppeteer
- **AI extraction:** Groq + Llama 4 Scout (17B, 16E)
- **Storage:** Cloudflare KV (5-min response cache, browser sessions, free-tier counters)
- **Network:** Base mainnet (eip155:8453)