Skip to content
plugmcp
DirectorySkillsCategoriesBlog
EN/δΈ­ζ–‡
Sign inSign up
Home/Servers/WebLens

WebLens

by dev.weblens

Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Server URL
https://api.weblens.dev/mcp
Provider
Add in Claude

Claude opens with the name and URL filled in. You still confirm it there.

Claude Code
claude mcp add --transport http dev.weblens-weblens https://api.weblens.dev/mcp

Run in a terminal.

Claude Desktop
{
  "mcpServers": {
    "dev.weblens-weblens": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.weblens.dev/mcp"
      ]
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

View more
  • FirecrawlπŸ”₯ Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
  • N
    NotionToken-auth Notion MCP: pages, databases, blocks, comments, files. Runs headless in CI and agents.
  • Context7Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

Related skills

View all
  • reaReverse engineer anything with agents, from app behavior down to native binaries.
  • rea-changelog-updatePrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
  • rea-tool-designDesign or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.

Questions

How do I install WebLens?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does WebLens need an API key?
No required environment variable is listed on this record.
What transport does WebLens use?
WebLens is reached over HTTP.
When was WebLens last checked?
Last checked 2026-10-16. Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.

Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.

WebLens

Premium web intelligence API for AI agents, with x402 micropayments. No account needed β€” pay per request in USDC on Base or Solana.

🌐 Live API: https://api.weblens.dev πŸ“– Interactive docs: https://api.weblens.dev/docs πŸ€– Agent guide: https://api.weblens.dev/llms.txt πŸ”Ž Marketplace: listed on x402scan

Try it free, right now

No wallet, no signup β€” these are rate limited to 10 requests/hour per IP:

curl https://api.weblens.dev/r/https://example.com     # any page as markdown
curl https://api.weblens.dev/s/cloudflare+workers      # web search

Preview before you pay (free)

An agent shouldn't have to buy a call to learn what it returns. POST /preview is free and answers that up front β€” the live price, a one-line summary, and a real sample of the exact response shape:

curl -X POST https://api.weblens.dev/preview \
  -H "Content-Type: application/json" \
  -d '{"endpoint": "/answer"}'
{
  "endpoint": "/answer",
  "price": "$0.05",
  "currency": "USD",
  "summary": "A direct answer with inline [n] citations to real sources.",
  "sample": { "query": "...", "answer": "...", "citations": [], "confidence": 0.92 },
  "sampleType": "recorded",
  "livePreviewAvailable": false,
  "livePreviewHint": "This endpoint calls a paid upstream provider, so free live previews are not offered β€” the recorded sample shows the exact response shape."
}

Live vs recorded. A real, truncated live preview runs only for endpoints whose marginal cost is a plain fetch β€” currently /fetch/basic, /contents and /map β€” and only when you pass a url. Everything else is backed by a metered upstream (SerpAPI, Anthropic); running those free would burn upstream credits, so they return the recorded sample, which still shows every field name and type. An endpoint that isn't sold returns 404.

# live: the first 500 chars of the real result, for free
curl -X POST https://api.weblens.dev/preview \
  -H "Content-Type: application/json" \
  -d '{"endpoint": "/fetch/basic", "url": "https://example.com"}'

Rate limited to 10 requests/hour per IP like the rest of the free tier.

ERC-8004: receipts and feedback

ERC-8004 (Trustless Agents) keeps compact signals on-chain and the detailed documents off-chain. WebLens hosts the off-chain half β€” the part a service operator can run without deploying a contract. To be precise about what that is and isn't: WebLens is not registered on-chain, holds no agent id, and writes nothing to any registry.

EndpointWhat it gives you
GET /.well-known/agent-registration.jsonThe ERC-8004 registration document: name, description, image, services, x402Support, payment info, feedback endpoints. registrations is empty (no on-chain registration) and supportedTrust is ["feedback"].
GET /receipts/{requestId}The receipt for a paid call β€” endpoint, status, outcome, price, payment method, network, pay-to. Every paid response returns X-Receipt-Id and X-Receipt-Url headers pointing here. Kept 30 days.
POST /feedbackHost a feedback document you author; returns {feedbackURI, feedbackHash} (keccak-256), the pair giveFeedback() expects. Required fields: agentRegistry, agentId, clientAddress, createdAt, value, valueDecimals β€” a missing one returns 400 naming it.
GET /feedback/{id}Serves that document byte-for-byte, so its keccak-256 hash matches the feedbackHash you were given. This URL is the feedbackURI.

Two more things worth stating plainly:

  • A receipt is unsigned. Its evidence is the settlement transaction it names, which anyone can check on-chain; nothing else here is trustless.
  • The buyer authors the feedback document and posts giveFeedback() themselves. WebLens only hosts the document verbatim and returns its hash; it never authors, edits, or submits feedback.

Endpoints

All paid endpoints are POST with a JSON body. Prices are per request in USDC.

Core

EndpointDescriptionPrice
/fetch/basicFetch a webpage as clean markdown$0.002
/fetch/proFetch with full JavaScript rendering (SPAs)$0.006
/fetch/resilientAuto-fallback: native scraper β†’ headless Chromium$0.008
/contentsBulk page text for 1–20 URLs$0.0015/URL
/screenshotCapture a webpage screenshot (PNG)$0.008
/mapDiscover a site's URLs (sitemaps + links, no page fetches)$0.004
/domainRegistration + DNS + SaaS stack + risk signals for a domain$0.005
/techDetect a site's framework, CMS, CDN, analytics and payments stack$0.005
/packagenpm/PyPI package health: deprecation, downloads, maintenance$0.003
/discussionsHacker News stories on a topic, with aggregates$0.004
/intel/projectOff-chain project due diligence: domain age, team/whitepaper, contract cross-check, A–F grade$0.05
/crawlBounded whole-site crawl β†’ markdown per page$0.0015/page

Search

EndpointDescriptionPrice
/searchReal-time web search (includeContent adds page markdown, +$0.0015/result)$0.015
/search/newsGoogle News articles with source and date$0.015
/search/imagesImage results with dimensions and source pages$0.015
/search/placesLocal businesses: address, rating, phone, coordinates$0.045
/search/shoppingProducts with prices, sellers, ratings$0.015
/search/scholarAcademic papers with citation counts$0.015
/search/autocompleteQuery suggestions (keyword/intent research)$0.015
/search/trendsInterest-over-time timeline$0.015

Social

EndpointDescriptionPrice
/social/youtube/transcriptFull video transcript with timestamps$0.03

Extraction & research

EndpointDescriptionPrice
/extractStructured extraction against a JSON schema$0.03
/pdfExtract text and metadata from a PDF$0.004
/answerGrounded answer with inline [n] citations$0.05
/research/deepCited research: one search (quick) or sub-questions β†’ search each (standard, deep) β†’ answer with inline [n] citations$0.08–$0.35

/research/deep is the only long-running endpoint: it plans sub-questions, runs a web search per sub-question, fetches and dedupes the sources, then synthesizes a cited answer β€” all in one synchronous call. A standard run (3 sub-questions, 8 sources, $0.20) takes roughly 30–60 seconds; deep (5 sub-questions, 12 sources, $0.35) takes longer. Set a generous HTTP timeout (120s+) and don't retry on a client timeout, or you'll pay twice.

Intelligence

EndpointDescriptionPrice

Free and unauthenticated: /, /health, /docs, /openapi.json, /llms.txt, /discovery, /.well-known/x402, /mcp, /r/{url}, /free/fetch, /preview, /.well-known/agent-registration.json, /receipts/{requestId}, /feedback, /feedback/{id}.

Dynamically-priced endpoints (/fetch/pro, /extract) apply a complexity multiplier β€” up to 3Γ— for bot-protected domains. Cached responses on the fetch family are 70% cheaper. The exact price is always in the 402 challenge.

Use with AI agents (MCP)

Remote HTTP β€” nothing to install:

{ "mcpServers": { "weblens": { "url": "https://api.weblens.dev/mcp" } } }

API usage

# Fetch a page as markdown
curl -X POST https://api.weblens.dev/fetch/basic \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com"}'

# Search, with page content included
curl -X POST https://api.weblens.dev/search \
  -H "Content-Type: application/json" \
  -d '{"query": "latest AI news", "limit": 5, "includeContent": true}'

# Structured extraction
curl -X POST https://api.weblens.dev/extract \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/product",
       "schema": {"title": {"type": "string"}, "price": {"type": "number"}},
       "instructions": "Extract the product title and price"}'

# Crawl a site (pay for the page budget you request)
curl -X POST https://api.weblens.dev/crawl \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com", "limit": 10, "maxDepth": 2}'

# Deep research with inline citations (slow β€” 30-60s, so raise the client timeout)
curl --max-time 120 -X POST https://api.weblens.dev/research/deep \
  -H "Content-Type: application/json" \
  -d '{"query": "How are AI agents using micropayments in 2026?", "depth": "standard"}'

Each returns 402 Payment Required with the price until you attach payment β€” see below.

How payments work

WebLens implements x402 v2:

  1. POST any paid endpoint with no payment.
  2. Get 402 Payment Required with a PAYMENT-REQUIRED header carrying the price, network, asset, and pay-to address.
  3. Sign a USDC transfer authorization with your wallet.
  4. Retry the same request with a Payment-Signature header.
  5. The payment is verified on-chain and you get your data.

On Base, payments settle through Coinbase's CDP facilitator, with PayAI taking over any payment CDP fails on; on Solana, through PayAI. Any x402 v2 client works β€” @x402/axios, @x402/fetch, or the bundled MCP server, which handles the whole flow for you.

Prepaid API keys are the alternative for developers who pay by card, where card sales are switched on: POST /billing/checkout {"pack": "10"} returns a Stripe Checkout link for a $10, $50 or $100 pack, and the page after payment shows an API key once. Send it as Authorization: Bearer <key> on any paid endpoint; each call is debited at its list price, and failed calls are refunded. GET /account shows the balance.

Development

pnpm install
pnpm run dev          # local dev server on :8787
pnpm run build        # tsc --noEmit (type check)
pnpm run lint         # eslint
pnpm run test         # vitest (unit + property + workerd integration)
pnpm run deploy       # wrangler deploy (production)

Secrets are set with wrangler, never committed:

wrangler secret put SERP_API_KEY        # search + all verticals + transcripts
wrangler secret put ANTHROPIC_API_KEY   # AI extraction, research, answers, intel
wrangler secret put CDP_API_KEY_ID      # optional: CDP facilitator fallback
wrangler secret put CDP_API_KEY_SECRET
VariablePurpose
PAY_TO_ADDRESSWallet that receives payments (wrangler.toml var)
NETWORKbase (production) or base-sepolia (testnet)
SERP_API_KEYSerpAPI key β€” search, verticals, YouTube transcripts
ANTHROPIC_API_KEYClaude β€” extraction, research, answers, intel
API_KEY_PREFIXPrefix of the API keys this environment sells (wl_live_ / wl_test_, wrangler.toml var)
STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRETOptional: card sales of prepaid API keys (Stripe Managed Payments); without both, /billing/* answers 503
PAYAI_FACILITATOR_URLOptional: override the facilitator endpoint

Testing against testnet

wrangler dev --env testnet          # Base Sepolia, fake USDC
API_URL=http://localhost:8787 PRIVATE_KEY=0x... npx tsx scripts/test-payment-testnet.ts

Get free testnet USDC from the Circle faucet on Base Sepolia.

Discovery

pnpm run verify-bazaar    # check the x402 discovery extension on every route

/openapi.json doubles as the discovery document for x402scan β€” it carries info.x-guidance, per-operation x-payment-info, and security: [] on free operations. WebLens is listed on x402scan and indexed in the PayAI facilitator catalog.

Note on the Coinbase CDP Bazaar: it only indexes services whose payments the CDP facilitator itself settles. WebLens uses PayAI as its primary facilitator (CDP has an open Base-mainnet settlement bug, x402#1065), so it does not appear there.

Tech stack

  • Cloudflare Workers β€” edge runtime, Durable Objects, KV, Browser Rendering
  • Hono β€” web framework
  • x402 β€” HTTP-native micropayments
  • Zod β€” request validation
  • Vitest + fast-check β€” unit, property, and real-workerd integration tests

Links

  • API documentation
  • LLM-optimized guide
  • Service discovery
  • x402 protocol

License

MIT

How do I install WebLens?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does WebLens need an API key?
No required environment variable is listed on this record.
What transport does WebLens use?
WebLens is reached over HTTP.
When was WebLens last checked?
Last checked 2026-10-16. Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.

No tool list yet. Remote servers get one after the first health check.

plugmcp

Plug any tool into any agent. MCP servers for people who do not write servers. Gateway for volume, n8n for apps.

  • github.com/TODO
  • x.com/TODO
  • linkedin.com/company/TODO

PlugMCP, 2026

Product
  • Browse
  • Install
  • Host your own
  • Pricing
  • Voice mode
  • Browser
Directory
  • All MCP servers
  • MCP Apps
  • Tools
  • Agent skills
  • Categories
  • New
  • Voice
  • Submit a server
Developers
  • Docs
  • Blog
  • Club
  • Work with us
  • What is MCP
  • What is WebMCP
  • Status
Company
  • About
  • Contact
  • Terms
  • Privacy
  • DPA