# ToolSnap MCP — fetch_rendered (JavaScript-rendered page fetch)

> ToolSnap MCP — fetch_rendered (JavaScript-rendered page fetch) is a paid API for AI agents from mcp.toolsnap.app, paid per call via x402, $0.04/call, status unknown (last checked 2026-10-30).

Fetches a fully JavaScript-rendered version of a web page and returns its content with significant token savings

## Facts

- Endpoint: POST https://mcp.toolsnap.app/x402/tools/fetch_rendered?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/toolsnap-mcp-fetch-rendered-javascript-rendered-page-fetch-977b66a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_cYfygMf1b2DZ50rA1-6oA

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability toolsnap-mcp-fetch-rendered-javascript-rendered-page-fetch-977b66a3 -d '<json body>'
```

Example prompt: Can you fetch the fully rendered content of https://example.com/dashboard — wait up to 3000ms for JavaScript to finish loading — and give me the text, keeping it under 10000 characters?

## When to prefer this

Use this endpoint when the target page relies on JavaScript (React, Vue, Angular, etc.) to render its content and a plain HTTP GET would return an empty shell. Prefer this over static fetch tools when you need the post-render DOM. The built-in token compression (median 98.1% savings) makes it far more cost-effective than piping raw HTML to an LLM. Ideal when you have authenticated sessions (pass cookies/auth headers) or need to wait for async data loads.

## Known failure modes

- URL is unreachable or returns a non-2xx status — content may be empty or an error message is returned
- Page requires authentication that wasn't supplied via headers — may return login page content instead of target data
- JavaScript rendering timeout if waitMs is too short for heavy SPAs — partial or empty content returned
- maxChars too low — content truncated before meaningful data is captured
- Invalid URL format — request rejected with validation error
- Payment failure (x402) — call not executed if USDC payment of $0.04 is not completed

## How this service works

47 server-side tools for AI agents through a single MCP connection. 36 free, no new accounts. Median 98.1% token savings on web content. Paid tools from $0.02.

## Output

Returns the fully rendered text/HTML content of the requested page after JavaScript execution completes, trimmed to the specified character limit. Median 98.1% token savings compared to raw HTML, making it highly efficient for downstream LLM processing.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  },
  "waitMs": {
   "type": "number"
  },
  "headers": {
   "type": "object",
   "description": "Headers to forward (Authorization, Cookie…)."
  },
  "maxChars": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/toolsnap-mcp-fetch-rendered-javascript-rendered-page-fetch-977b66a3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp.toolsnap.app](https://www.zero.xyz/host/mcp.toolsnap.app/llms.txt)