Any URL,
clean Markdown.
Orsa's Scrape Markdown endpoint turns any webpage into LLM-ready Markdown fast. We handle proxy escalation, JS rendering, and HTML-to-Markdown conversion — you get text you can paste into prompts, vector stores, or docs.
Scrape any webpage and get clean markdown content.
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. Markdown 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. Markdown 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://notion.com/blog/introducing-projects
Render, retry, enrich
Orsa handles browser execution, proxy escalation, parsing, validation, caching, and typed response shaping behind the API.
One call in. Markdown out.
Use the result in rag knowledge bases without owning the extraction stack.
- REST path
- /api/v1/web/scrape/markdownSame endpoint used by the SDK examples below.
- Input shape
- URLhttps://notion.com/blog/introducing-projects
- SDKs
- TypeScript, Python, cURLStart with TypeScript, Python, or direct cURL.
- Best first use
- RAG knowledge basesCrawl a docs site, convert every page to Markdown, chunk it, embed it — Orsa handles capture and cleanup.
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 rag knowledge bases and ai agent context.
Endpoint
/api/v1/web/scrape/markdown
Example input
https://notion.com/blog/introducing-projects
Promise
One call in. Markdown out.
Pairs with
Scrape Sitemap, Crawl Website, Scrape HTML
What teams ship with
any url, clean markdown.
Each product page now speaks to the real workflow behind the endpoint, with concrete jobs instead of a generic feature list.
RAG knowledge bases
Crawl a docs site, convert every page to Markdown, chunk it, embed it — Orsa handles capture and cleanup.
AI agent context
When your agent needs to read a webpage, Markdown is the format that actually works with LLMs.
Content migration
Point Orsa at your sitemap and get clean Markdown for every post without maintaining a scraper.
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://notion.com/blog/introducing-projects",
"title": "Introducing Projects",
"markdown": "# Introducing Projects\n\nProjects is the new way...",
"word_count": 1247,
"reading_time_seconds": 312,
"published_at": "2026-01-14T09:00:00Z",
"language": "en"
}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.