Get started

FileToPDF.dev for AI agents

FileToPDF.dev converts files, HTML, and Markdown into PDF documents through a simple API for developers who need PDF output without building a rendering pipeline themselves. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect FileToPDF.devSee the 4 actions ↓
DocumentsAPI keyMCP + RESTfiletopdf.dev
AUDIT LOG · FILETOPDF.DEVPOLICY: acme-support
09:41:07 · claude · u_8f2read
filetopdf_dev.get_account_status
Get Account Status✓ allowed · 212ms
09:41:08 · claude · u_8f2read
filetopdf_dev.convert_html_to_pdf
Convert HTML to PDF✓ allowed · 164ms
EVERY FILETOPDF.DEV CALL, ON THE RECORD
01 · USE CASES

What agents do in FileToPDF.dev.

01

Convert HTML to a PDF

Convert an HTML page into a PDF so a report can be shared as a downloadable file.

02

Convert Markdown notes to PDF

Convert a Markdown document into a PDF for distribution outside the team's usual tools.

03

Check account status first

Get account status as a read-only check before running a batch of conversions.

02 · ACTIONS

4 FileToPDF.dev actions, graded by risk.

Every FileToPDF.dev action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

4

Look things up. Allowed by default.

  • filetopdf_dev.get_account_status
    Get Account Status
  • filetopdf_dev.convert_html_to_pdf
    Convert HTML to PDF
  • filetopdf_dev.convert_file_url_to_pdf
    Convert File URL to PDF
  • filetopdf_dev.convert_markdown_to_pdf
    Convert Markdown to PDF

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

FileToPDF.dev in three steps.

  1. 01Your users connect FileToPDF.devThey add their FileToPDF.dev api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 03Any agent can actYour agent calls FileToPDF.dev through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
POLICY.TS
await arc0.policies.set('filetopdf_dev', {
  read: 'allow',
  write: 'ask',        
  destructive: 'deny',  
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2
04 · AUTH AND DATA

How FileToPDF.dev connects.

Users add their FileToPDF.dev api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same FileToPDF.dev connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH
API key
CREDENTIALS
Per-tenant encrypted vault
MODEL SEES
Results only, never credentials
AUDIT LOG
Every call, on every plan
05 · WORKS WITH

Use FileToPDF.dev from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
06 · RELATED

More documents apps.

Google Docs43 actionsActiveMerge13 actionsAirparser10 actionsAlgodocs3 actionsDocuSign338 actionsSharePoint Graph162 actionsSharePoint105 actionsDocumenso77 actions
ALL DOCUMENTS APPS →
07 · FAQ

FileToPDF.dev and Arc0, answered.

Q01

Can I use FileToPDF.dev with Claude, ChatGPT or Cursor?

Yes. Connect FileToPDF.dev to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the FileToPDF.dev actions you allow.

Q02

How do users connect FileToPDF.dev?

Users add their FileToPDF.dev api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which FileToPDF.dev actions can my agent take?

4 in total: 4 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.

Q04

Can I make my agent read-only in FileToPDF.dev?

Yes. Allow read actions and deny writes in the FileToPDF.dev policy. Your agent can still look things up, and any write it attempts is blocked and logged.

Q05

Can my own backend call FileToPDF.dev too?

Yes. The same FileToPDF.dev connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug FileToPDF.dev into your agent.

Your users connect FileToPDF.dev once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.

Connect FileToPDF.devBrowse all apps →

Free to build · MCP + REST · Audit log on every plan