← GetMarkdown converter

Developers

GetMarkdown developer resources and agent integration

Use these canonical resources to understand when GetMarkdown fits an automation workflow, how agents can retrieve product guidance, and which programmatic interfaces are currently available.

Agent-readable product documentation

Start with llms.txt for concise instructions, supported formats, limits, workflow selection, and high-value links. Use llms-full.txt when an agent needs expanded troubleshooting and package details. Both files are public, stable, UTF-8 text resources designed for retrieval without client-side JavaScript.

Markdown content negotiation

The homepage supports HTTP content negotiation. Send Accept: text/markdown to https://www.getmarkdown.com/ to receive the Markdown representation. The response declares Vary: Accept, Accept-Encoding. The same representation is directly available at /index.md.

curl -H 'Accept: text/markdown' https://www.getmarkdown.com/

GetMarkdown API: OpenAPI spec, JSON endpoints, and MCP

GetMarkdown publishes a documented agent surface. The OpenAPI 3.1 specification describes every agent endpoint with unique operation IDs and typed schemas, suitable for LLM function calling. The agent status endpoint returns a JSON capability document. The MCP server exposes GetMarkdown guidance as Model Context Protocol tools over Streamable HTTP (JSON-RPC 2.0: initialize, tools/list, tools/call).

There is no file upload or conversion API: file selection and submission are user actions in the web interface. Unknown /api/* paths return HTTP 404 and unsupported methods return 405 as structured JSON errors of the form { "error": { "code", "message", "hint" } }. The Advanced PDF service is used by the first-party web application and is not a published developer API. Do not automate or depend on undocumented service routes.

If you need recurring volume, a supported automation interface beyond the MCP tools, or an API-key flow, describe the file types, expected volume, output requirements, and retention constraints on the contact page. That information helps determine whether a future developer offering would fit the use case.

curl -X POST https://www.getmarkdown.com/api/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Useful public resources