API directory
Markdown APIs for Web Pages: Documented Outputs & Requirements
Find web extraction APIs with documented Markdown output. Compare supported output modes, request interfaces, source evidence and billing terms.
Choose an API that can return web-page content as Markdown and identify its output and billing requirements.
- Does the API return Markdown directly or inside a response envelope?
- Does the required extraction mode also request browser rendering?
- Which plan, request options or credit multipliers apply? Read the linked product sources.
This collection covers our reviewed proxy and web-data catalog. It is not an exhaustive market survey or a performance ranking.
Category reviewed . Review due .
Compare documented requirements
3 of 3 listingsSwipe or scroll horizontally to compare requirements. Scroll back to the first column to see listing names.
| API / service | Interface & output | Documented behavior | Billing & restrictions | Evidence |
|---|---|---|---|---|
| Nimble Extract APINimble · official publisher Fetch HTML, Markdown and screenshots with configurable rendering, CSS parsing, browser actions and asynchronous batches. Details & setup →Provider discussionSourced JSON record | HTTP API HTML, JSON, markdown, PNG Scraping API | For this task: Request formats: ["markdown"]; the documented response places it in data.markdown. Rendering is a separate option and defaults off. Screenshot output enables rendering and can affect pricing.[1][4][3]
| Successful URL extractions; public API pricing lists USD 1 per 1,000 URLs for Extraction Tools. Requirements & limitations
| Documentation checkedReview due 4 source references
|
| ScrapeOps Proxy API AggregatorScrapeOps · official publisher Route scraping requests across upstream services, with rendering, proxy-pool and extraction options. Details & setup →Provider discussionSourced JSON record | HTTP API HTML, JSON, markdown, screenshot Scraping API | For this task: Markdown uses llm_extract=true with llm_extract_response_type=markdown. This LLM extraction path adds 25 credits to the fetch cost; HTTP 404 responses are also billable.[4][1]
| Monthly API credits determined by target and options; HTTP 200 and 404 responses consume credits. Requirements & limitations
| Documentation checkedReview due 4 source references
|
| ScrapingBee HTML APIScrapingBee · official publisher Fetch rendered pages, apply CSS extraction rules or run browser scenarios through an HTTP API. Details & setup →Provider discussionSourced JSON record | HTTP API HTML, JSON, markdown, text, screenshot Scraping API | For this task: Set return_page_markdown=true for Markdown output. This is separate from AI extraction. JavaScript rendering defaults on, so choose rendering and proxy options before estimating credits.[1]
| Monthly API credits; rendering and proxy tier determine base credits, with AI extraction add-ons. Requirements & limitations
| Documentation checkedReview due 1 source references
|
How to use this comparison
Compare the documented request interface, output and account product before checking price. A JSON response can contain raw HTML; it does not by itself establish structured extraction. A browser action in one request does not by itself establish a reusable browser session.
Each row keeps the publisher’s billing basis and restrictions alongside its sources. Unknown prices or limits remain unknown. These are documentation reviews; no live connection, purchase or comparative performance test is claimed.
Overdue records remain visible with a label. This collection leaves search indexing when its category review is overdue or fewer than 3 current, visible records qualify. Individual detail pages retain their own review policy.
The collection JSON link covers the whole category before filters.
Suggest a correction · Affiliate disclosure · Collection JSON records