OpenClaw

OpenClaw already browses. Grabbit gets the shots it can't.

Drop the Grabbit skill into your self-hosted OpenClaw agent, or add the hosted MCP server, so it captures the cookie walls, consent gates, and bot-walled pages its own browser is blocked on. Nothing to install on the box it runs on.

Get your free test keySee the install

Two ways to wire it in

Use the hosted MCP server if OpenClaw is talking MCP, or wrap the one-line CLI in a skill. Either way the capture runs on Grabbit, so a self-hosted deployment stays lean.

MCP config
// Point OpenClaw's MCP config at the hosted server
{
  "mcpServers": {
    "grabbit": {
      "url": "https://mcp.grabbit.live",
      "headers": { "Authorization": "Bearer sk_live_..." }
    }
  }
}
Skill (wraps the CLI)
# Or wrap the one-line CLI in a skill (skills/grabbit/SKILL.md).
# The capture is a single command (no browser for OpenClaw to manage):
npx grabbit.live <url> --out shot.png   # → hosted URL + local file
npx grabbit.live <url> --test           # free placeholder, no credits

The gap a browsing agent leaves

A self-driven browser handles the easy pages and stalls on the rest: a consent overlay it cannot dismiss, a bot wall that serves a blank, a layout that only finishes rendering after the scripts settle. Grabbit is the capture layer that fills that gap: one call, cookie banners handled, full-page support, and a clean image back for OpenClaw to read, store, or act on.

Prefer raw HTTP for a custom skill? Same endpoint. See the screenshot API reference.

Captures your agent's own browser can't get

Most agents can already drive a headless browser. It works on simple pages and quietly fails on the ones that matter: cookie and consent walls, bot detection, login or paywall gates, and heavy client-rendered pages. Grabbit runs the capture on hosted rendering infrastructure instead, so the shot comes back clean.

Local headless browser

  • Needs Chromium installed in the agent's runtime
  • Blank or blocked on bot-walled and consent-gated pages
  • You own the timeouts, retries, and scaling
  • Breaks in CI, sandboxes, and remote runners with no browser

Grabbit

  • One call, nothing to install or run
  • Dismisses cookie and consent banners automatically
  • Handles lazy-loaded, JavaScript-heavy, and full-page captures
  • Gets many sites a local headless browser is blocked on

Honest bound: no service captures literally every site. A handful of hard targets behind aggressive IP blocking still resist. But the cookie walls, consent gates, and JS-heavy pages that blank out a local headless browser are exactly what Grabbit is built to get.

Flat pricing, built for agents that loop

When an agent captures a page on every step, per-call metering turns into anxiety. Grabbit is one flat rate: $50 per year for 25,000 captures ($0.002 each), with prepaid packs that stack on top and never reset. No monthly quota to forfeit, no usage cliff. Test-environment keys render free placeholders, so you can wire the agent up before adding a card.

See full pricingCompare providers

OpenClaw FAQ

Why add Grabbit to OpenClaw if it can already browse?
OpenClaw's built-in browsing is great for navigating and extracting, but reliable, full-page, bot-wall-resistant screenshots are a different job. Grabbit runs the capture on hosted infrastructure that dismisses cookie and consent banners and gets many sites a self-driven browser is blocked on, so the image OpenClaw gets back is clean.
How do I add Grabbit to OpenClaw?
Two ways. Add the hosted MCP server (https://mcp.grabbit.live) to OpenClaw's MCP config, or wrap the one-line CLI (npx grabbit.live <url>) in a skills/grabbit/SKILL.md. Both authenticate with a Bearer key; a free test key works.
Does OpenClaw need a headless browser for this?
No. Whether you use the MCP server or the CLI skill, the render happens on Grabbit. Nothing to install on the box OpenClaw runs on, which keeps a self-hosted deployment lean.
Can it screenshot any site?
It captures public URLs and handles cookie and consent banners, lazy-loaded and JavaScript-heavy pages, and many sites that block a self-driven browser. Private and internal addresses are blocked by SSRF protection, and a few hard targets behind aggressive IP blocking still resist.
What does it cost?
A flat $0.002 per live capture on the $50/year plan, with prepaid packs that never reset or expire. Test captures are free.

Give OpenClaw eyes in two minutes

Free test key, one install, and your agent can screenshot the web.

Get your free test keyAll agent integrations