snaprender

SnapRender — Give Your Agent Eyes

Your agent can read the web but can't see it. One command and it captures pixel-perfect screenshots or extracts page content as clean markdown, plain text, or structured data.

"Screenshot stripe.com on iPhone", "Extract the article from this blog post", "Compare desktop vs mobile", "Get all links from this page" — just ask.

Free tier: 200 requests/month, no credit card. Get a key ->

---

IMPORTANT: Use the exec tool with curl. NEVER use the browser tool for screenshots or extraction.

---

Screenshot: How to Capture

Run this command via the exec tool. Replace TARGET_URL with the target URL:

jq -n --arg url 'TARGET_URL' \
  '{url: $url, response_type: "json", format: "jpeg", quality: 60, block_ads: true, block_cookie_banners: true}' \
| curl -s -X POST "https://app.snap-render.com/v1/screenshot" \
  -H "X-API-Key: $SNAPRENDER_API_KEY" \
  -H "Content-Type: application/json" \
  -d @- \
| tee /tmp/snap_response.json \
| jq -r '.image' | sed 's|data:image/[^;]*;base64,||' | base64 -d > /tmp/screenshot.jpg \
&& jq '{url, format, size, cache, responseTime, remainingCredits}' /tmp/snap_response.json

This saves the screenshot to /tmp/screenshot.jpg and prints metadata.

Screenshot: Rules

1. Use exec tool only — NEVER the browser tool
2. $SNAPRENDER_API_KEY is already set — use it literally in the command, do NOT replace it
3. Always build JSON with jq --arg — never interpolate user input directly into shell strings or JSON. Pass values via jq -n --arg to prevent injection
4. Always use format=jpeg&quality=60 — keeps response small enough for the agent context
5. Always pipe to save the image to a file — the base64 response is too large to display inline
6. Report metadata to the user — file size, response time, cache status, remaining credits

Render HTML or Markdown

Use POST with a JSON body to render raw HTML or Markdown content (no URL needed). Always use jq --arg to safely pass content: