78trust / 100

Url Render

by 2s in Search & web

x402 APIPassing, checked 2 h ago

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.

GET
https://2s.io/api/url/render
Price
$0.015
per call in USDC
Uptime
100%
last 30 days
Response time
207 ms
361 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

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

Each call costs $0.015 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://2s.io/api/url/render?format=markdown&url=https%3A%2F%2Freact.dev

Parameters

ParameterTypeRequiredDescription
formatstringNo One of: markdown, text, both, html, pdf. Default: "markdown".
timeoutMsintegerNo Default: 12000.
urlstringYes
waitUntilstringNo One of: load, domcontentloaded, networkidle0, networkidle2. Default: "networkidle2".

Example response

The listing has no example response.

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.015.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://2s.io/api/url/render?format=markdown&url=https%3A%2F%2Freact.dev'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://2s.io/api/url/render?format=markdown&url=https%3A%2F%2Freact.dev' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.015 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.015" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.015 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2F2s.io%2Fapi%2Furl%2Frender
const res = await pay("https://2s.io/api/url/render?format=markdown&url=https%3A%2F%2Freact.dev");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.015 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.015"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://2s.io/api/url/render?format=markdown&url=https%3A%2F%2Freact.dev")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
2 h agoPassed402160 ms$0.015
7 h agoPassed402292 ms$0.015
12 h agoPassed402164 ms$0.015
16 h agoPassed402163 ms$0.015
26 h agoPassed402172 ms$0.015
Show 10 older checks
30 h agoPassed402207 ms$0.015
34 h agoPassed402172 ms$0.015
39 h agoPassed402292 ms$0.015
43 h agoPassed402247 ms$0.015
47 h agoPassed402206 ms$0.015
2 days agoPassed402479 ms$0.015
2 days agoPassed402266 ms$0.015
2 days agoPassed402297 ms$0.015
3 days agoPassed402219 ms$0.015
3 days agoPassed402153 ms$0.015