Render a URL in a real headless browser (JavaScript executed) and return its article co…

What it does

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.

Tags: public-records · identifiers · ai-agents · us-gov-data · x402 · bazaar

Call contract

Method

GET

Input

query parameters

Output

json

Last paid call

2026-10-08

{
  "format": "markdown",
  "url": "https://react.dev"
}

Use with an agent

1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
2. Inspect. Fetch /resources/42864.json for the price and payment options.
3. Pay. Call GET https://2s.io/api/url/render. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, Solana, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price

$0.015 / request

Protocol

x402 v2

Auth

No account or API key. Pay per request.

Networks

Base, Solana

Demand

1 calls · 1 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x2b6D4988Db4723E6908Db86Ab2b8dFBc51FC32C5",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "15000",
    "amountUsd": 0.015,
    "maxTimeoutSeconds": 60
  },
  {
    "scheme": "exact",
    "network": "solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp",
    "payTo": "TW6ntaGzvj63ZgPjszd4FCGmVTGfzv1MAYZbjYcyWhn",
    "asset": "EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v",
    "amount": "15000",
    "amountUsd": 0.015,
    "maxTimeoutSeconds": 60
  }
]

Examples

curl -X GET 'https://2s.io/api/url/render'
# -> 402 Payment Required; read PAYMENT-REQUIRED
# retry the identical request with PAYMENT-SIGNATURE

const res = await fetch("https://2s.io/api/url/render", {
  "method": "GET"
});
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

import httpx
res = httpx.request("GET", "https://2s.io/api/url/render")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider

2s.io

Endpoint

https://2s.io/api/url/render

Machine-readable

/resources/42864.json