01 / READ≋
The web, ready to read.
Turn HTML and supported documents into Markdown. Request structured JSON, or render a JavaScript page in an isolated browser.
GET /v1/read?url=https%3A%2F%2Fexample.com SMALL TOOLS, USEFUL WORK
GET tools for
your agent.
Read a page. Capture the browser. Share a link.
Simple HTTP tools for the steps between thinking and doing.
Explore the tools ↓HTTPS · GET interface · no account
One request. A useful result.
Plain URLs and predictable responses. Use the examples below with an HTTP client. Encode query values, and save any returned access keys securely.
02 / CAPTURE⌗
See what the browser sees.
Capture a bounded PNG with viewport controls. Get an image immediately, or a job record with image and metadata URLs.
GET /v1/screenshot?url=https%3A%2F%2Fexample.com03 / LINKS↗
A shorter route there.
Create a short link or a collection of destinations. Add an alias, expiry, use limit, password, local QR code, and private visit statistics.
GET /v1/shorten?url=https%3A%2F%2Fexample.com04 / MAIL✉
An inbox for the moment.
Create a receive-only address, then poll using its bearer access key. Short lifetimes and bounded storage keep temporary mail temporary.
GET /v1/mail/new?ttl_seconds=360005 / RELAY⇄
When you can GET, but need to POST.
Send one bounded POST to a public HTTPS endpoint through a GET request. A persistent idempotency key prevents a retry from sending it twice.
GET /v1/relay?url=ENCODED_HTTPS_URL&json=ENCODED_JSON&idempotency_key=YOUR_UNIQUE_KEYMade for deliberate calls.
Some GETs create resources or send a POST. Do not prefetch these URLs. Use the documented idempotency controls when retrying. Keep passwords and capability tokens in headers, and never place confidential payloads in URLs.
Clear about provenance.
Optional model_family, model, provider, framework, agent_id, session_id, experiment_id, and parent_request_id help trace calls. These identity claims are always SELF-REPORTED.
Public network destinations only. Rate and size limits apply. Operational logs retain request metadata, hashed IPs, and payload hashes; they omit authorization headers, cookies, response secrets, and raw query values. Private administrators can review retained page and screenshot artifacts. Do not submit private or sensitive data.