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.
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.
{
"name": "URLtoMarkdownSkill",
"arguments": {
"url": "https://www.example.com/article"
}
}You do not name the tool yourself; the model picks it. Asking about https://www.example.com/article 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"
}
}
}https://api.vervekit.com/v1/mcpPer-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 |
|---|---|---|
urlRequired | string | The URL of the webpage to convert to Markdown url |
includeImagesOptionalPremium | boolean | Whether to include image references in the Markdown output |
includeLinksOptionalPremium | 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.
{
"status": "ok",
"error": null,
"data": {
"url": "https://example.com/blog/getting-started",
"title": "Getting Started Guide",
"markdown": "# Getting Started Guide\n\nWelcome to our platform. This guide will help you get up and running quickly.\n\n## Prerequisites\n\nBefore you begin, make sure you have:\n\n- A registered account\n- API credentials\n- Node.js 18 or higher\n\n## Installation\n\nInstall the package using npm:\n\n```\nnpm install example-sdk\n```\n\n## Quick Start\n\nHere's a simple example to get you started:\n\n1. Import the SDK\n2. Initialize with your API key\n3. Make your first request\n\n## Next Steps\n\nCheck out our [documentation](https://example.com/docs) for more details.\n\n",
"wordCount": 87,
"imageCount": 1,
"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/blog/getting-started | The original URL that was converted |
title | string | Getting Started Guide | Page title extracted from the webpage |
markdown | string | # Getting Started Guide
Welcome to our platform. This guide will help you get up and running quickly.
## Prerequisites
Before you begin, make sure you have:
- A registered account
- API credentials
- Node.js 18 or higher
## Installation
Install the package using npm:
```
npm install example-sdk
```
## Quick Start
Here's a simple example to get you started:
1. Import the SDK
2. Initialize with your API key
3. Make your first request
## Next Steps
Check out our [documentation](https://example.com/docs) for more details.
 | The converted Markdown content |
wordCount | number | 87 | Number of words in the extracted content |
imageCount | number | 1 | 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
- Content Migration
- Use the URL to Markdown API to migrate web content to Markdown-based systems like static site generators, documentation platforms, or content management systems
- Documentation
- Convert web documentation to Markdown for offline reading, archiving, or integration with documentation tools like GitBook, MkDocs, or Docusaurus
- Content Archiving
- Archive web content in a portable, readable format that can be version controlled and easily searched
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.
Related
More in Data Conversion: