Product overview
What is markdown2pdf.ai?
markdown2pdf.ai converts Markdown produced by an AI agent or application into a PDF intended for human delivery. Instead of rendering HTML to PDF, the service uses LaTeX and supports document elements such as cover pages, tables of contents, chapters, and tables. This makes it suitable for reports, books, and other structured outputs.
The service is designed for machine-to-machine workflows. Developers can use REST endpoints, Python and TypeScript SDKs, or an MCP server. Payment is requested per conversion through Lightning using L402 or through USDC on Solana using X402; the workflow does not require a user account, OAuth, subscription, or conventional API key.
How to Use markdown2pdf.ai
- Prepare valid Markdown and the desired document options.
- Choose the REST API, Python SDK, TypeScript SDK, or MCP server.
- Submit the Markdown and receive payment details.
- Complete the supported per-call payment.
- Poll the job when required and download the generated PDF.
- Inspect layout, fonts, tables, links, and sensitive content before delivery.
Core Features
- Markdown conversion: Turns agent-friendly Markdown into human-readable PDF.
- LaTeX rendering: Produces structured, print-oriented output.
- Agent-native interfaces: Supports REST, Python, TypeScript, and MCP.
- L402 payment: Accepts satoshi payments over the Lightning Network.
- X402 payment: Accepts USDC payment on Solana.
- No subscription: Charges each generated document without account plans.
- Asynchronous jobs: Provides generation status and output retrieval endpoints.
Use Cases
- Deliver AI research as a formatted report.
- Turn generated chapters into a book-style PDF.
- Add final-document export to an MCP or agent workflow.
- Produce recurring reports without managing a browser renderer.
Pricing
Each PDF costs 5 satoshis through Lightning or $0.01 USDC through Solana. There are no subscription tiers in the current documentation. Exchange-rate, wallet, network, or custody costs may apply outside the service.
Frequently Asked Questions
Does it require an API key?
No. The official documentation describes per-call payment without OAuth or API keys.
Is it intended for an interactive end-user editor?
No. It is positioned primarily as an API and MCP service for agents.
Should generated PDFs be reviewed?
Yes. Layout, confidential data, source accuracy, and accessibility still need inspection.
