URL to Markdown Skill

Overview

URL to Markdown works by fetching the webpage content and parsing the HTML structure. It intelligently converts HTML elements to their Markdown equivalents while preserving formatting. Images are not loaded during fetch for performance, but image links are reconstructed in the output Markdown.

Live Test URL to Markdown Skill Skill →

The tool

Once your client is connected to the VerveKit server, this appears in its tool list as URLtoMarkdownSkill. It is read-only and open-world — it fetches and never mutates anything on your side — so most clients call it without asking you to confirm.

Tool call

{
  "name": "URLtoMarkdownSkill",
  "arguments": {
    "url": "https://example.com/"
  }
}

You do not name the tool yourself; the model picks it. Asking about https://example.com/ in the terms this skill covers is enough for it to reach for URLtoMarkdownSkill on its own — naming it explicitly also works, and is the way to force the call.

Connecting

One server URL covers every skill in the catalog, including this one. Authorization is OAuth: the client opens a browser once, and there is no key to paste into a config file.

{
  "mcpServers": {
    "vervekit": {
      "url": "https://api.vervekit.com/v1/mcp"
    }
  }
}

Per-client setup — Claude, Cursor, VS Code, ChatGPT — is on the MCP setup page.

Arguments

These are the properties on the tool's inputSchema, so a well-behaved client validates them before the call is made. Premium arguments are accepted on every plan but only take effect on plans that include them.

Argument	Type	Description
`url`Required	string	The URL of the webpage to convert to Markdown url
`includeImages`OptionalPremium	boolean	Whether to include image references in the Markdown output
`includeLinks`OptionalPremium	boolean	Whether to include hyperlinks in the Markdown output

What the model gets back

The result carries a structuredContent object matching the tool's declared outputSchema, so a client reads fields without parsing prose. status is "ok" and error is null on success; a null field means the value was not available for that input, not that the call failed.

Result

{
  "status": "ok",
  "error": null,
  "data": {
    "url": "https://example.com/",
    "title": "Example Domain",
    "markdown": "# Example Domain\n\n\nThis domain is for use in documentation examples without needing permission. Avoid use in operations.\n\n\n[Learn more](https://iana.org/domains/example)",
    "wordCount": 20,
    "imageCount": 0,
    "linkCount": 1
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`url`	string	`https://example.com/`	The original URL that was converted
`title`	string	`Example Domain`	Page title extracted from the webpage
`markdown`	string	`# Example Domain This domain is for use in documentation examples without needing permission. Avoid use in operations. [Learn more](https://iana.org/domains/example)`	The converted Markdown content
`wordCount`	number	`20`	Number of words in the extracted content
`imageCount`	number	`0`	Number of images found in the content
`linkCount`	number	`1`	Number of links found in the content

Failure modes

Errors come back as tool errors carrying a sentence the model can act on, not a bare status code. Error handling covers the full list.

Status	What it means
`400` / `422`	The arguments did not validate. The message names the offending one.
`401`	The OAuth session is invalid or expired — reconnect the server.
`403`	Blocked by a key restriction or an IP allow-list. Never a bad identity.
`404`	This skill is not part of VerveKit. Check the catalog.
`429`	Out of credits, or a brief rate limit. The message tells them apart.

A call costs 10 credits each time the tool actually runs; a model that reasons about the tool without calling it costs nothing.

Use cases

Static Site Migration: Developers moving legacy blogs to static site generators extract page titles and converted text to generate clean Markdown source files automatically.
Offline Documentation Readers: Technical writers turn public product docs into offline Markdown manuals, tracking extracted word counts across pages to structure revision bundles.
Knowledge Base Ingestion: Feed live help center URLs to internal knowledge bases, stripping unnecessary HTML markup while preserving document headings and lists for local search.
Web Page Archiving: Before third-party guides go offline, research teams store target articles as version-controlled Markdown text plus recorded image and link counts.

Other ways to use URL to Markdown Skill

Set up URL to Markdown Skill on VerveKit, or reach the same source a different way. Your VerveKit account and credits work on all of them — one key, one balance.

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →