{
"url": "https://example.com",
"status_code": 200,
"markdown": "This domain is for use in documentation examples without needing permission.",
"stats": {
"word_count": 25,
"char_count": 156,
"estimated_llm_tokens": 39,
"reading_time_minutes": 0.1
},
"metadata": {
"title": "Example Domain",
"canonical_url": null,
"headings": [
{
"level": 1,
"text": "Example Domain"
}
]
}
}
curl --location --request GET 'https://zylalabs.com/api/15142/llm+webpage+markdown+extractor+api/40415/convert+webpage+to+clean+markdown?url=https://example.com&include_links=true&include_metadata=true&check_ai_files=false' --header 'Authorization: Bearer YOUR_API_KEY'
{
"url": "https://example.com",
"status_code": 200,
"metadata": {
"title": "Example Domain",
"description": null,
"open_graph": [],
"json_ld": []
},
"ai_files": {
"llms_txt": {
"present": false,
"status_code": 404
},
"robots_txt": {
"present": false,
"status_code": 404
}
}
}
curl --location --request GET 'https://zylalabs.com/api/15142/llm+webpage+markdown+extractor+api/40416/extract+webpage+metadata+and+ai+readiness?url=https://example.com&check_ai_files=true' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the LLM Webpage Markdown Extractor API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
(Save 2 months with annual billing 🎉)
Convert any public webpage into clean boilerplate-free Markdown optimized for large language models and retrieval pipelines, complete with token estimates, OpenGraph tags, JSON-LD data, and llms.txt checks.
Stripping scripts, styles, navigation bars, and cookie banners reduces token usage dramatically while preserving headings, tables, lists, and code blocks for accurate retrieval and summarization.
The API parses page titles, meta descriptions, canonical links, OpenGraph tags, Twitter Cards, JSON-LD Schema blocks, heading outlines, and deduplicated internal and external links.
When enabled, the service probes the site root for llms.txt and robots.txt files and returns their HTTP status and content preview.
It returns the requested URL, HTTP status code, cleaned Markdown content, content statistics, and basic metadata. The Markdown contains the main page content in a structured, readable format, while metadata can include the title, canonical URL, and heading hierarchy.
`word_count` is the number of extracted words, `char_count` is the character count, `estimated_llm_tokens` approximates language-model token usage, and `reading_time_minutes` estimates reading duration. These values help size prompts, retrieval chunks, and processing workloads.
It returns the page URL and status code, plus metadata such as title, description, OpenGraph data, JSON-LD blocks, canonical information, headings, and page links. It also reports whether `llms.txt` and `robots.txt` are available and includes their status codes.
Responses are JSON objects. Clean page content is provided as a Markdown string, while statistics, metadata, structured tags, links, and AI-file checks are represented as nested objects or arrays. JSON-LD values remain structured data suitable for downstream parsing.
The service fetches the supplied public HTTP or HTTPS URL and identifies the primary page content while excluding common boilerplate such as navigation, scripts, and cookie banners. Results can vary when a page is inaccessible, heavily client-rendered, or has little extractable content.
Provide a publicly reachable webpage URL using either `http://` or `https://`. The endpoint processes that page and reports the resulting HTTP status in the response. Private, authentication-protected, or otherwise unreachable pages may not produce complete content.
Treat fields such as descriptions, canonical URLs, OpenGraph arrays, and JSON-LD arrays as optional. A `null` value or empty array generally means the source page did not expose that information, not that the request failed. Use the HTTP status code to assess fetch success.
Use the Markdown field as the primary document text, headings as section boundaries, and token estimates to guide chunk sizing. Use titles, canonical URLs, and structured metadata for indexing, while `llms.txt` and `robots.txt` results help assess machine-readable site guidance.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund