Agent Screenshot Hub

URL in, image out. Every call is paid inside the request over x402. No signup, no API key, no dashboard.

Endpoint

Route	Price	What it does
`POST /screenshot`	0.004 USDC	Viewport shot, png / webp / jpeg
`POST /screenshot` mit `full_page`	0.006 USDC	ganzes Dokument statt Viewport

Parameter: url, width, height, full_page, format, quality, delay_ms, selector, dark_mode, block_cookiebanner.

How a call works

curl -s -X POST https://shot.netzhandwerker.de/screenshot \
  -H "Content-Type: application/json" \
  -d '{"url":"https://example.com","width":1280,"height":800,"format":"webp"}'

The first call answers with HTTP 402 and the accepted payment terms. An x402 capable client signs the terms and repeats the request; the image arrives in the same round trip as base64 plus a fetch URL that stays valid for 15 minutes. Any x402 client library, or an MCP client pointed at /mcp, handles this without further setup.

Rules we follow

20 second budget per render, 8 MB cap per image.
Private and link local address ranges are refused.
Cookie banners are hidden, never clicked.
Paywalls and bot walls are not bypassed.
Images expire after 15 minutes.
A failed render is rejected before settlement.

Discovery

Operational figures

Rolling 30 day window, updated live: 1 requests, 0 of them paid, 0 settlements, 0 USDC volume, cache hit rate 0 percent over 0 lookups.