LLM Webpage Markdown Extractor API

API ID 15142

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.

API Documentation

Endpoints

Request
Fetches any public HTTP or HTTPS webpage, strips navigation menus, scripts, and cookie banners, converts the main article into structured Markdown, and calculates estimated language model token usage.
Endpoint ID: 40415
GET https://zylalabs.com/api/15142/llm+webpage+markdown+extractor+api/40415/convert+webpage+to+clean+markdown
INPUT PARAMETERS

Convert Webpage to Clean Markdown — Endpoint Features

Object Description
url Required Public HTTP or HTTPS webpage URL to fetch and transform into clean Markdown text.
include_links Optional Keep resolved absolute hyperlinks inside the converted Markdown document.
include_metadata Optional Include extracted title, description, OpenGraph, Twitter Card, JSON-LD, and headings outline.
check_ai_files Optional Probe the target origin for llms.txt and robots.txt AI crawler configuration files.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

url
include_links
include_metadata
check_ai_files
API EXAMPLE RESPONSE
JSON
{
    "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"
            }
        ]
    }
}
Convert Webpage to Clean Markdown — CODE SNIPPETS

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' 


    
Request
Extracts structured OpenGraph tags, Twitter Cards, JSON-LD schema blocks, canonical URLs, heading outlines, internal and external links, plus llms.txt and robots.txt availability.
Endpoint ID: 40416
GET https://zylalabs.com/api/15142/llm+webpage+markdown+extractor+api/40416/extract+webpage+metadata+and+ai+readiness
INPUT PARAMETERS

Extract Webpage Metadata and AI Readiness — Endpoint Features

Object Description
url Required Public HTTP or HTTPS URL whose structured SEO and social metadata should be extracted.
check_ai_files Optional Check whether the website publishes llms.txt and robots.txt files at its root.

Free test requests remaining: 3 of 3.


INPUT PARAMETERS

url
check_ai_files
API EXAMPLE RESPONSE
JSON
{
    "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
        }
    }
}
Extract Webpage Metadata and AI Readiness — CODE SNIPPETS

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' 


    

API Access Key & Authentication

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.

Headers
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 🎉)

Starts at
$10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Overview

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.

LLM Webpage Markdown Extractor API FAQs

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.

General FAQs

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

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.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

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.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

Please have a look at our Refund Policy: https://zylalabs.com/terms#refund


Related APIs