Raw HTML,
no scraping stack.
Every page on the open web, rendered by us, delivered to you as raw HTML in under a second. Proxies, fingerprints, and retries stay on our side.
Fetch rendered HTML for any public URL.
Start free, no card required, most teams ship a first integration in under ten minutes.
Not another JSON page.
A production workflow in one call
One call in. HTML out.
Before Orsa
- A browser worker, proxy account, parser, retry queue, and schema contract for one endpoint.
- Product teams wait while platform teams debug website-specific failures.
- Every new data field becomes another brittle scraper branch.
After Orsa
- One call in. HTML out. With retries, rendering, and validation handled behind the API.
- The response shape is typed, documented, and ready for product code.
- Teams combine it with adjacent Orsa endpoints without adding vendors.
Teach the workflow,
then show the endpoint
Point Orsa at a url, let the platform handle the web work, and receive a response your product can trust.
Send a url
https://stripe.com/newsroom/news
Render, retry, enrich
Orsa handles browser execution, proxy escalation, parsing, validation, caching, and typed response shaping behind the API.
One call in. HTML out.
Use the result in legacy integrations without owning the extraction stack.
- REST path
- /api/v1/web/scrape/htmlSame endpoint used by the SDK examples below.
- Input shape
- URLhttps://stripe.com/newsroom/news
- SDKs
- TypeScript, Python, cURLStart with TypeScript, Python, or direct cURL.
- Best first use
- Legacy integrationsWhen you still need the full DOM — testing, migration, or a parser you already trust.
Performance your product
can actually plan around
Every endpoint page should answer the practical buying question: will this hold up once it leaves the demo?
More than the response.
The operating layer behind it
Stripe pages teach the system around the API: inputs, retries, observability, adjacent products, and the code path. This section does the same for Orsa endpoints.
- Typed response contracts for product code and AI tools.
- Browser, proxy, cache, and validation logic handled by Orsa.
- Direct fit for legacy integrations and pipeline control.
Endpoint
/api/v1/web/scrape/html
Example input
https://stripe.com/newsroom/news
Promise
One call in. HTML out.
Pairs with
Scrape Markdown, Scrape Images, Crawl Website
What teams ship with
raw html, no scraping stack.
Each product page now speaks to the real workflow behind the endpoint, with concrete jobs instead of a generic feature list.
Legacy integrations
When you still need the full DOM — testing, migration, or a parser you already trust.
Pipeline control
Pull HTML once, then run your own extractors without running Playwright in your VPC.
Debugging renders
See exactly what our browser sees when a page misbehaves in production.
Keep the code small.
Let Orsa do the messy part
Use the endpoint directly, then combine it with adjacent Orsa APIs as the workflow grows.
{
"url": "https://stripe.com/newsroom/news",
"status_code": 200,
"html": "<!DOCTYPE html><html>...</html>",
"title": "Stripe Newsroom",
"final_url": "https://stripe.com/newsroom/news"
}Build the full workflow,
not another point solution
The best product integrations usually combine two or three Orsa endpoints behind one customer experience.
The questions teams ask
before shipping
Short answers for the practical details: rendering, limits, freshness, and how this fits into production.
Put this endpoint
in your product today
Try the live endpoint, then wire the same response into your app with one API key.
One API key for every Orsa endpoint · No card required to start.