Page2MD API

API ID 14824

网页转换为Markdown API:发送一个URL并返回干净、结构化的Markdown - 保留标题、链接和列表,去除样板。为LLM管道构建

API 文档

端点

请求
将提供地址上的网页转换为干净的结构化Markdown,并在响应中返回页面元数据
Endpoint ID: 38418
POST https://zylalabs.com/api/14824/page2md+api/38418/convert+page+to+markdown
输入参数

将页面转换为Markdown — 端点功能

对象 描述
请求体 必需 Json

剩余免费测试请求:3 / 3。


输入参数

API 示例响应
JSON
{
    "markdown": "From Wikipedia, the free encyclopedia\n\n| Markdown |  |\n| --- | --- |\n| [![](https://thumb.wikimedia.org/wikipedia/commons/thumb/4/48/Markdown-mark.svg/120px-Markdown-mark.svg.png?utm_source=en.wikipedia.org&utm_campaign=parser&utm_content=thumbnail)](https://en.wikipedia.org/wiki/File:Markdown-mark.svg) |  |\n| [Filename extensions](https://en.wikipedia.org/wiki/Filename_extension) | `.md`, `.markdown`[[1]](https://en.wikipedia.org/wiki/Markdown#cite_note-df-2022-1)[[2]](https://en.wikipedia.org/wiki/Markdown#cite_note-rfc7763-2) |\n| [Internet media type](https://en.wikipedia.org/wiki/Media_type) | `text/markdown`[[2]](https://en.wikipedia.org/wiki/Markdown#cite_note-rfc7763-2) |\n| [Uniform Type Identifier (UTI)](https://en.wikipedia.org/wiki/Uniform_Type_Identifier) | `net.daringfireball.markdown` |\n| UTI conformation | `public.utf8-plain-text` |\n| [Magic number](https://en.wikipedia.org/wiki/File_format#Magic_number) | None |\n| Developed by | [John Gruber](https://en.wikipedia.org/wiki/John_Gruber) |\n| Initial release | March 9, 2004 (22 years ago)[[3]](https://en.wikipedia.org/wiki/Markdown#cite_note-markdown-swartz-3)[[4]](https://en.wikipedia.org/wiki/Markdown#cite_note-gruber-2004-release-4) |\n| [Latest release](https://en.wikipedia.org/wiki/Software_release_life_cycle) | 1.0.1\nDecember 17, 2004 (21 years ago)[[5]](https://en.wikipedia.org/wiki/Markdown#cite_note-md-5) |\n| Type of format | [Open file format](https://en.wikipedia.org/wiki/Open_file_format)[[6]](https://en.wikipedia.org/wiki/Markdown#cite_note-license-6) |\n| Extended to | [pandoc](https://en.wikipedia.org/wiki/Pandoc), [MultiMarkdown](https://en.wikipedia.org/wiki/MultiMarkdown), [Markdown Extra](https://en.wikipedia.org/wiki/Markdown_Extra), [CommonMark](https://en.wikipedia.org/wiki/Markdown#CommonMark),[[7]](https://en.wikipedia.org/wiki/Markdown#cite_note-rfc7764-7) [RMarkdown](https://en.wikipedia.org/wiki/RMarkdown)[[8]](https://en.wikipedia.org/wiki/Markdown#cite_note-RMarkdown-8) |\n| Website | [daringfireball.net/projects/markdown/](https://daringfireball.net/projects/markdown/) |\n\n**Markdown**[[9]](https://en.wikipedia.org/wiki/Markdown#cite_note-philosophy-9) is a [lightweight markup language](https://en.wikipedia.org/wiki/Lightweight_markup_language) for creating [formatted text](https://en.wikipedia.org/wiki/Formatted_text) using a [plain-text editor](https://en.wikipedia.org/wiki/Text_editor). [John Gruber](https://en.wikipedia.org/wiki/John_Gruber) created Markdown in 2004 as an easy-to-read [markup language](https://en.wikipedia.org/wiki/Markup_language).[[9]](https://en.wikipedia.org/wiki/Markdown#cite_note-philosophy-9) Markdown is widely used for [blogging](https://en.wikipedia.org/wiki/Blog), [instant messaging](https://en.wikipedia.org/wiki/Instant_messaging), and [large language models](https://en.wikipedia.org/wiki/Large_language_models),[[10]](https://en.wikipedia.org/wiki/Markdown#cite_note-llm-markdown-10) and also used elsewhere in [online forums](https://en.wikipedia.org/wiki/Online_forums), [collaborative software](https://en.wikipedia.org/wiki/Collaborative_software), [note-taking software](https://en.wikipedia.org/wiki/Note-taking_software), [documentation](https://en.wikipedia.org/wiki/Documentation) pages, and [README files](https://en.wikipedia.org/wiki/README).\n\nThe initial description of Markdown[[11]](https://en.wikipedia.org/wiki/Markdown#cite_note-11) contained ambiguities and raised unanswered questions, causing implementations to both intentionally and accidentally diverge from the original version. This was addressed in 2014 when long-standing Markdown contributors released [CommonMark](https://en.wikipedia.org/wiki/Markdown#CommonMark), an unambiguous specification and test suite for Markdown.[[12]](https://en.wikipedia.org/wiki/Markdown#cite_note-FutureOfMarkdown-12)[*[better source needed](https://en.wikipedia.org/wiki/Wikipedia:Verifiability#Questionable_sources)*]\n\nMarkdown was inspired by pre-existing [conventions](https://en.wikipedia.org/wiki/Convention_(norm)) for marking up [plain text](https://en.wikipedia.org/wiki/Plain_text) in [email](https://en.wikipedia.org/wiki/Email) and [usenet](https://en.wikipedia.org/wiki/Usenet) posts,[[13]](https://en.wikipedia.org/wiki/Markdown#cite_note-ArsTechnica2014-13) such as the earlier markup languages [setext](https://en.wikipedia.org/wiki/Setext) (c. 1992), [Textile](https://en.wikipedia.org/wiki/Textile_(markup_language)) (c. 2002), and [reStructuredText](https://en.wikipedia.org/wiki/ReStructuredText) (c. 2002).[[9]](https://en.wikipedia.org/wiki/Markdown#cite_note-philosophy-9)\n\nIn 2002, [Aaron Swartz](https://en.wikipedia.org/wiki/Aaron_Swartz) created [atx](https://en.wikipedia.org/wiki/Atx_(markup_language)) and referred to it as \"the true structured text format\". Gruber created the Markdown language in 2004 with Swartz as his \"sounding board\".[[14]](https://en.wikipedia.org/wiki/Markdown#cite_note-Gruber-14) The goal of the language was to enable people \"to write using an easy-to-read and easy-to-write plain text format, optionally convert it to structurally valid [XHTML](https://en.wikipedia.org/wiki/XHTML) (or [HTML](https://en.wikipedia.org/wiki/HTML))\".[[5]](https://en.wikipedia.org/wiki/Markdown#cite_note-md-5)\n\nAnother key design goal was *readability*, that the language be readable as-is, without looking like it has been marked up with tags or formatting instructions,[[9]](https://en.wikipedia.org/wiki/Markdown#cite_note-philosophy-9) unlike text formatted with \"heavier\" [markup languages](https://en.wikipedia.org/wiki/Markup_language), such as [Rich Text Format](https://en.wikipedia.org/wiki/Rich_Text_Format) (RTF), HTML, or even [wikitext](https://en.wikipedia.org/wiki/Wikitext), each of which have obvious in-line tags and formatting instructions which can make the text more difficult for humans to read.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]\n\nGruber wrote a [Perl](https://en.wikipedia.org/wiki/Perl) script, `Markdown.pl`, which converts marked-up text input to valid, [well-formed](https://en.wikipedia.org/wiki/Well-formed_document) XHTML or HTML, encoding angle brackets (`<`, `>`) and [ampersands](https://en.wikipedia.org/wiki/Ampersand) (`&`), which would be misinterpreted as special characters in those languages. It can take the role of a standalone script, a plugin for [Blosxom](https://en.wikipedia.org/wiki/Blosxom) or [Movable Type](https://en.wikipedia.org/wiki/Movable_Type), or of a text filter for [BBEdit](https://en.wikipedia.org/wiki/BBEdit).[[5]](https://en.wikipedia.org/wiki/Markdown#cite_note-md-5)\n\n## Rise and divergence\n\n[[edit](https://en.wikipedia.org/w/index.php?title=Markdown&action=edit&section=2)]\n\nAs Markdown's popularity grew rapidly, many Markdown [implementations](https://en.wikipedia.org/wiki/Implementation) appeared, driven mostly by the need for additional features such as [tables](https://en.wikipedia.org/wiki/Table_(information)), [footnotes](https://en.wikipedia.org/wiki/Note_(typography)), definition lists,[[note 1]](https://en.wikipedia.org/wiki/Markdown#cite_note-17) and Markdown inside HTML blocks.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]\n\nThe behavior of some of these diverged from the reference implementation, as Markdown was only characterised by an informal [specification](https://en.wikipedia.org/wiki/Specification_(technical_standard))[[17]](https://en.wikipedia.org/wiki/Markdown#cite_note-18) and a [Perl](https://en.wikipedia.org/wiki/Perl) implementation for conversion to HTML.[*[citation needed](https://en.wikipedia.org/wiki/Wikipedia:Citation_needed)*]\n\nAt the same time, a number of ambiguities in the informal specification had attracted attention.[[18]](https://en.wikipedia.org/wiki/Markdown#cite_note-gfm_on_github-why_spec-19) These issues spurred the creation of tools such as Babelmark[[19]](https://en.wikipedia.org/wiki/Markdown#cite_note-babelmark-2-20)[[20]](https://en.wikipedia.org/wiki/Markdown#cite_note-babelmark-3-21) to compare the output of various implementations,[[21]](https://en.wikipedia.org/wiki/Markdown#cite_note-22) and an effort by some developers of Markdown [parsers](https://en.wikipedia.org/wiki/Parsing) for standardization. However, Gruber has argued that complete standardization would be a mistake: \"Different sites (and people) have different needs. No one syntax would make all happy.\"[[22]](https://en.wikipedia.org/wiki/Markdown#cite_note-23)\n\nGruber avoided using curly braces in Markdown to unofficially reserve them for implementation-specific extensions.[[23]](https://en.wikipedia.org/wiki/Markdown#cite_note-curlyBraces-24)\n\n| CommonMark |  |\n| --- | --- |\n| [Filename extensions](https://en.wikipedia.org/wiki/Filename_extension) | `.md`, `.markdown`[[2]](https://en.wikipedia.org/wiki/Markdown#cite_note-rfc7763-2) |\n| [Internet media type](https://en.wikipedia.org/wiki/Media_type) | `text/markdown; variant=CommonMark`[[7]](https://en.wikipedia.org/wiki/Markdown#cite_note-rfc7764-7) |\n| [Uniform Type Identifier (UTI)](https://en.wikipedia.org/wiki/Uniform_Type_Identifier) | *uncertain*[[24]](https://en.wikipedia.org/wiki/Markdown#cite_note-cm-uti-25) |\n| UTI conformation | public.plain-text |\n| Developed by | [John MacFarlane](https://en.wikipedia.org/wiki/John_MacFarlane_(philosopher)), open source |\n| Initial release |",
    "_note": "Response truncated for documentation purposes"
}
将页面转换为Markdown — 代码片段

curl --location --request POST 'https://zylalabs.com/api/14824/page2md+api/38418/convert+page+to+markdown' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{"url": "https://en.wikipedia.org/wiki/Markdown"}'

    

API 访问密钥和身份验证

注册后,每个开发者都会被分配一个个人 API 访问密钥,这是一个唯一的字母和数字组合,用于访问我们的 API 端点。要使用 Page2MD API 进行身份验证,只需在 Authorization 标头中包含您的 bearer token。

标头
标头 描述
授权 必需 应为 Bearer access_key. 订阅后,请查看上方的"您的 API 访问密钥"。

无长期承诺。随时升级、降级或取消。

起价
$10,000/年


  • 自定义数量
  • 自定义速率限制
  • 专业客户支持
  • 实时 API 监控

概览

网页转Markdown API:发送一个URL并获取干净、结构化的Markdown——保留标题、链接和列表,去除多余的部分。为LLM管道构建。

Page2MD API FAQs

标准Markdown:保留标题 段落 链接 列表和代码块 移除导航 广告和页脚模板

不 仅支持公共可获取的页面 被阻止的页面会返回明确的错误

是的 确定性的Markdown输出具有稳定的结构正是分块和嵌入管道所期望的

每个电话一页,同步处理

它们返回错误而不是部分内容——没有静默的空结果

一般常见问题

Zyla API Hub 就像一个大型 API 商店,您可以在一个地方找到数千个 API。我们还为所有 API 提供专门支持和实时监控。注册后,您可以选择要使用的 API。请记住,每个 API 都需要自己的订阅。但如果您订阅多个 API,您将为所有这些 API 使用相同的密钥,使事情变得更简单。
价格以 USD(美元)、EUR(欧元)、CAD(加元)、AUD(澳元)和 GBP(英镑)列出。我们接受所有主要的借记卡和信用卡。我们的支付系统使用最新的安全技术,由 Stripe 提供支持,Stripe 是世界上最可靠的支付公司之一。如果您在使用卡片付款时遇到任何问题,请通过 [email protected]

此外,如果您已经以这些货币中的任何一种(USD、EUR、CAD、AUD、GBP)拥有有效订阅,该货币将保留用于后续订阅。只要您没有任何有效订阅,您可以随时更改货币。
定价页面上显示的本地货币基于您 IP 地址的国家/地区,仅供参考。实际价格以 USD(美元)为单位。当您付款时,即使您在我们的网站上看到以本地货币显示的等值金额,您的卡片对账单上也会以美元显示费用。这意味着您不能直接使用本地货币付款。
有时,银行可能会因其欺诈保护设置而拒绝收费。我们建议您首先联系您的银行,检查他们是否阻止了我们的收费。此外,您可以访问账单门户并更改关联的卡片以进行付款。如果这些方法不起作用并且您需要进一步帮助,请通过 [email protected]
价格由月度或年度订阅决定,具体取决于所选计划。
API 调用根据成功请求从您的计划中扣除。每个计划都包含您每月可以进行的特定数量的调用。只有成功的调用(由状态 200 响应指示)才会计入您的总数。这确保失败或不完整的请求不会影响您的月度配额。
Zyla API Hub 采用月度订阅系统。您的计费周期将从您购买付费计划的那一天开始,并在下个月的同一日期续订。因此,如果您想避免未来的费用,请提前取消订阅。
要升级您当前的订阅计划,只需转到 API 的定价页面并选择您要升级到的计划。升级将立即生效,让您立即享受新计划的功能。请注意,您之前计划中的任何剩余调用都不会转移到新计划,因此在升级时请注意这一点。您将被收取新计划的全部金额。
要检查您本月剩余多少 API 调用,请参考响应标头中的 "X-Zyla-API-Calls-Monthly-Remaining" 字段。例如,如果您的计划允许每月 1,000 个请求,而您已使用 100 个,则响应标头中的此字段将显示 900 个剩余调用。
要查看您的计划允许的最大 API 请求数,请检查 "X-Zyla-RateLimit-Limit" 响应标头。例如,如果您的计划包括每月 1,000 个请求,此标头将显示 1,000。
"X-Zyla-RateLimit-Reset" 标头显示您的速率限制重置之前的秒数。这告诉您何时您的请求计数将重新开始。例如,如果它显示 3,600,则意味着还有 3,600 秒直到限制重置。
是的,您可以随时通过访问您的账户并在账单页面上选择取消选项来取消您的计划。请注意,升级、降级和取消会立即生效。此外,取消后,您将不再有权访问该服务,即使您的配额中还有剩余调用。
为了让您有机会在没有任何承诺的情况下体验我们的 API,我们提供 7 天免费试用,允许您免费进行最多 50 次 API 调用。此试用只能使用一次,因此我们建议将其应用于您最感兴趣的 API。虽然我们的大多数 API 都提供免费试用,但有些可能不提供。试用在 7 天后或您进行了 50 次请求后结束,以先发生者为准。如果您在试用期间达到 50 次请求限制,您需要"开始您的付费计划"以继续发出请求。您可以在个人资料中的订阅 -> 选择您订阅的 API -> 定价标签下找到"开始您的付费计划"按钮。或者,如果您在第 7 天之前不取消订阅,您的免费试用将结束,您的计划将自动计费,授予您访问计划中指定的所有 API 调用的权限。请记住这一点以避免不必要的费用。
7 天后,您将被收取试用期间订阅的计划的全额费用。因此,在试用期结束前取消很重要。因忘记及时取消而提出的退款请求不被接受。
当您订阅 API 免费试用时,您可以进行最多 50 次 API 调用。如果您希望超出此限制进行额外的 API 调用,API 将提示您执行"开始您的付费计划"。您可以在个人资料中的订阅 -> 选择您订阅的 API -> 定价标签下找到"开始您的付费计划"按钮。
付款订单在每月 20 日至 30 日之间处理。如果您在 20 日之前提交请求,您的付款将在此时间范围内处理。
您可以通过我们的聊天渠道联系我们以获得即时帮助。我们始终在线,时间为上午 8 点至下午 5 点(EST)。如果您在该时间之后联系我们,我们将尽快回复您。此外,您可以通过 [email protected]

相关 API