Back to Browse
Skim JS-Render Reader — JavaScript-Rendered Page to Markdown
x402
Skim JS-Render Reader — JavaScript-Rendered Page to Markdown is a paid API for AI agents from skim402.com, paid per call via x402, $0.005/call, status healthy (last checked 2026-09-15, last successful call 2026-08-30).
Fetches a JavaScript-rendered URL using a headless browser, then extracts and returns clean agent-ready markdown content
Price / call$0.005
Success100%
StatusHealthy
How this service works
Skim: JS-rendered reader — full headless browser render for SPAs and JS-gated pages; clean markdown ~4x smaller than raw HTML.
Output
A JSON object containing the extracted markdown content, plain text, page title, site name, the original URL, and the final (post-redirect) URL after JavaScript hydration and rendering.
Example use cases
Example prompt
“Pull the full article content from https://example.com/spa-page — it's a JavaScript-rendered single-page app, so it needs a headless browser render — and give me the clean markdown text.”
Technical details
Endpoint
GEThttps://skim402.com/api/v2/read/jsWhen to prefer
Use this endpoint specifically when the target URL is a JavaScript-rendered single-page application (SPA), lazy-loaded page, or JS-gated article that cannot be extracted by a simple HTTP GET. If the page uses React, Vue, Next.js, Angular, or similar frameworks and renders content client-side, this JS-render variant is required over a plain HTTP fetch endpoint. Prefer this over static scraping alternatives when content only appears after JavaScript execution.
Side effects
- URL is unreachable or returns a non-2xx status — endpoint may return an error or empty content
- Page JavaScript fails to hydrate within the headless browser timeout — partial or empty markdown returned
- URL points to a non-article page (e.g. dashboard, login wall) — markdown may be minimal or garbled
- Payment of $0.005 USDC not fulfilled via x402 — 402 Payment Required response returned
- Invalid or missing url query parameter — request rejected with schema validation error
- Headless render times out on extremely slow or complex SPAs — timeout error returned
Input
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"url": "https://example.com/article"
}
}
}Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object | |
| output | object |
Output
{
"url": "https://example.com/article",
"mode": "js",
"text": "This domain is for use in documentation examples without needing permission. Avoid use in operations.Learn more",
"finalUrl": "https://example.com/article",
"markdown": "This domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n[Learn more](https://iana.org/domains/example)",
"metadata": {
"lang": "en",
"title": "Example Domain",
"byline": null,
"length": 111,
"excerpt": "This domain is for use in documentation examples without needing permission. Avoid use in operations.",
"siteName": null,
"publishedAt": null
},
"fetchedAt": "2026-06-18T05:55:51.837Z",
"structured": null
}Schema · Response
{
"type": "json",
"example": {
"url": "https://example.com/spa-page",
"mode": "js",
"text": "SPA Article\n\nMarkdown extracted after the page's JavaScript hydrated the article body...",
"finalUrl": "https://example.com/spa-page",
"markdown": "# SPA Article\n\nMarkdown extracted after the page's JavaScript hydrated the article body.",
"metadata": {
"title": "SPA Article",
"siteName": "Example SPA"
}
}
}Tags
x402
Reviews
5★
0
4★
0
3★
0
2★
0
1★
0
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"