#Agent UsageCopy page

Tools and best practices when using curl.md (and these docs) with agents.

#Tell Your Agent To Use curl.md

One of the simplest ways to get better URL context is to tell your agent to use curl.md whenever it fetches URLs. You can add a project rule like:

When you need to fetch a URL, prefer curl.md so you get markdown instead of raw HTML.
Use curl.md for docs pages, articles, changelogs, and reference material.
If curl.md docs are relevant, prefer .md docs pages or llms.txt over raw page fetches.

This usually gives the agent cleaner, lower-noise context than a raw page fetch or browser snapshot.

#Skills

If your agent supports skills, install the official curl.md skills with:

$npx skills add https://curl.md --yes

Hosted skills are available at https://curl.md/.well-known/skills/index.json.

Skills are useful when you want the agent to:

• fetch pages through the CLI
• use curl.md inside local terminal workflows
• follow recommended curl.md usage patterns without manual prompt setup

For broader integration options, see Plugins, CLI, and API & SDK.

#Single-Page Markdown Access

There are multiple ways to get the curl.md docs as markdown.

#.md Endpoints

Append .md to any documentation URL to get the markdown version of that page.

Example:

• HTML: https://curl.md/docs/guide/cli
• Markdown: https://curl.md/docs/guide/cli.md

The markdown version includes features such as: full page content in plain markdown format, metadata for agents, code blocks with syntax markers, links preserved as markdown links, and tables formatted as markdown tables.

#Using .md Endpoints

You can use these endpoints in various ways:

# Fetch documentation content with curl
curl https://curl.md/docs/guide/cli.md

# Pipe directly to an AI tool
curl https://curl.md/docs/guide/cli.md | pbcopy

You can also use curl.md itself to render docs pages as markdown in the browser or terminal, for example with https://curl.md/curl.md/docs/guide/cli (a little inception never hurt).

#Content Negotiation

To obtain the markdown version of a single documentation page, you can:

• Use a .md endpoint - Append .md to the end of any docs page URL to get the markdown version.
• Use Accept: text/markdown - Send the header to a normal /docs/... URL when you want markdown without rewriting the path.

For example:

$curl https://curl.md/docs/guide/cli -H 'Accept: text/markdown'

That returns the same generated markdown as https://curl.md/docs/guide/cli.md.

If you omit the header, /docs/... keeps serving the normal HTML docs page.

$curl https://curl.md/docs/guide/cli

Prefer .md URLs when you want a canonical markdown link you can paste into prompts, rules, or agent context. Use content negotiation when you already have a /docs/... URL and want markdown without rewriting the path.

#Copy Page

Every docs page includes agent-friendly page actions:

• Copy page copies the page’s canonical markdown to your clipboard
• View markdown opens the generated .md page in a new tab

This is the fastest manual workflow:

1. Open the docs page.
2. Click Copy page.
3. Paste the markdown into your agent.

Use View markdown when your agent can fetch URLs directly and you want to give it a stable markdown endpoint instead of pasted content.

#llms.txt

We implement llms.txt and llms-full.txt as follows:

• llms.txt - A compact directory of curl.md’s docs and agent entry points. It includes a short product summary, example CLI and HTTP usage, links to important docs pages, and links to things like skills.
• llms-full.txt - The full contents of the canonical curl.md documentation in a single file, intended for broad indexing, bulk ingestion, or large-context workflows. It is much larger than llms.txt, so it is usually not the right default for routine prompts.

Prefer page-level .md URLs first, then llms.txt, then llms-full.txt only when broader context is necessary.