---
title: "Render a URL in a real headless browser (JavaScript..."
method: GET
path: "/api/url/render"
tags: ["url"]
---

# Render a URL in a real headless browser (JavaScript...

`GET /api/url/render`

## Request

- Base URL: `https://2s.io`
- URL: `https://2s.io/api/url/render`
- Auth: API key in header `PAYMENT-SIGNATURE`

Render a URL in a real headless browser (JavaScript executed) and return its article content with the clutter stripped — same cleaning + output formats as /api/url/clean, but for client-rendered / SPA pages whose content only appears after JS runs (where a raw HTTP fetch returns an empty shell). `format`: markdown (default), text, both (JSON envelope), html (self-contained reader page, raw text/html), or pdf (typeset reading doc, raw application/pdf). Optional `waitUntil` (load|domcontentloaded|networkidle0|networkidle2, default networkidle2) and `timeoutMs` (1000-15000, default 12000) control how long to let JS settle. Use /api/url/clean instead for server-rendered pages — it is faster and cheaper; only reach for render when JS rendering is required. Billing: payment settles before this endpoint runs (paid upstream), so an error after settlement IS charged — the error response then carries the payment receipt (PAYMENT-RESPONSE) and `X-2s-Charged: true`.

## Query parameters

- `url` string, uri, required
- `format` 'markdown' | 'text' | 'both' | 'html' | 'pdf'
- `waitUntil` 'load' | 'domcontentloaded' | 'networkidle0' | 'networkidle2'
- `timeoutMs` integer
- `trial` 1

## Response `200`

OK

## Other responses

- `400`: Invalid request. Parameter validation (BAD_REQUEST / INVALID_PARAM with error.details.issues, MALFORMED_JSON) runs before payment and is never charged; a request-specific 400 raised by the endpoint itself runs after settlement on this paid-upstream operation and IS charged (`X-2s-Charged: true` + PAYMENT-RESPONSE receipt).
- `402`: Payment required. Body is the x402 PaymentRequirements envelope with a multi-network accepts array; the per-call price is in accepts[].amount (and on the operation as x-2s-price). Sign for whichever rail you hold USDC on (EIP-3009 for Base, partial SPL transfer for Solana) and retry with the PAYMENT-SIGNATURE header (X-PAYMENT also accepted for v1 clients). Also PAYMENT_SETTLE_FAILED (error envelope) when a verified payment failed to settle: error.details.chargeStatus is "not_charged" (retry with a fresh payment) or "unknown" (the authorization may still settle before its deadline — check it before retrying).
- `429`: Too many requests — RATE_LIMITED: our per-IP / per-payer limiter. Not charged; retry after Retry-After.
- `5XX`: Server-side failure. 500 INTERNAL: unexpected error; quote error.errorId (also the X-2s-Error-Id header). 502 UPSTREAM_UNAVAILABLE (or another UPSTREAM_* code): the data provider failed — composite endpoints refuse unbilled when every source fails. 503 SERVICE_PAUSED: endpoint paused by the operator kill switch, retry after Retry-After; 503 SPEND_CAP: daily upstream budget exhausted. 504 UPSTREAM_TIMEOUT. On a paid-upstream operation (see its description) this can follow settlement: then the call WAS charged and the response carries `X-2s-Charged: true` plus the PAYMENT-RESPONSE receipt. SERVICE_PAUSED and SPEND_CAP are never charged.

---

[API](https://skmtc.dev/2s-io/apis/2s-the-most-everything-api.md) · [All operations](https://skmtc.dev/2s-io/apis/2s-the-most-everything-api/llms.txt) · [OpenAPI document](https://skmtc.dev/2s-io/apis/2s-the-most-everything-api/revisions/da4c5caf686e?raw)