html_to_markdown
Convert an HTML string to clean Markdown (GFM tables, fenced code, nested lists). No fetch. Body: { "html": "...", "base_url"?: "https://...", "extract_main"?: false }. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/html-to-m...
This record as markdown: /tools/com-it-scorptech-x402/html-to-markdown.md
What html_to_markdown does on ScorpTech x402 API
AI agents call html_to_markdown to retrieve information from ScorpTech x402 API without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
html | string | Yes | HTML to convert (JSON body; the service caps request bodies at 256 KB) |
base_url | string | — | Optional http(s) URL used only to absolutise links (never fetched) |
extract_main | boolean | — | Strip boilerplate, keep main content (default false) |
include_links | boolean | — | default true |
include_images | boolean | — | default true |
Parameters from the server's own tool schema.
Why html_to_markdown is rated Low
Even though html_to_markdown only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts URL/endpoint input (base_url) · Accepts raw HTML/template content (html)
Attacks that exploit this kind of access
The rule that runs html_to_markdown safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ScorpTech x402 API, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For html_to_markdown, this is the rule to start with:
html_to_markdown is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ScorpTech x402 API, apply this rule, and every html_to_markdown call is checked against it from then on.
Questions about html_to_markdown
Convert an HTML string to clean Markdown (GFM tables, fenced code, nested lists). No fetch. Body: { "html": "...", "base_url"?: "https://...", "extract_main"?: false }. Price: $0.005 USDC per successful call (x402, Solana). Same tool over HTTPS: POST https://scorptech.it.com/api/x402/v1/html-to-markdown. It is categorised as a Read tool in the ScorpTech x402 API MCP Server, which means it retrieves data without modifying state.
html_to_markdown accepts 5 parameters: html, base_url, extract_main, include_links, include_images. Required: html. The full parameter table on this page comes from the server's own tool schema.
Register the ScorpTech x402 API MCP server in PolicyLayer and add a rule for html_to_markdown: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches ScorpTech x402 API. Nothing to install.
html_to_markdown is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the html_to_markdown rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for html_to_markdown. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
html_to_markdown is provided by the ScorpTech x402 API MCP server (https://scorptech.it.com/api/x402/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ScorpTech x402 API, and thousands of servers like it.
This server
Across the catalogue