API2PDF for AI agents
Api2Pdf is a REST API for generating and manipulating PDFs from HTML, URLs, and other document formats, used by developers to automate document creation in their own apps. 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.
What agents do in API2PDF.
Merge multiple PDFs into one file
Combine several PDF documents into a single file ready to deliver to a client.
Generate a barcode or QR code
Create a barcode or QR code image to embed into a document or label.
Confirm before deleting a generated PDF
Removing a stored PDF file is permanent and should be confirmed before it happens.
10 API2PDF actions, graded by risk.
Every API2PDF action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
2Look things up. Allowed by default.
- api2pdf.check_statusCheck API Status
- api2pdf.extract_pagesExtract PDF Pages
write
6Create and change things. Allow, or ask the user first.
- api2pdf.add_header_footerAdd Header Footer
- api2pdf.optimize_pdfOptimize PDF
- api2pdf.reorder_pagesReorder PDF Pages
- api2pdf.libreoffice_thumbnailLibreOffice Thumbnail
- api2pdf.zebra_generate_barcodeGenerate Barcode or QR Code
- api2pdf.libreoffice_pdf_to_htmlLibreOffice PDF to HTML
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- api2pdf.delete_pdfDelete PDF
- api2pdf.merge_pdfsMerge PDFs
API2PDF in three steps.
- 01Your users connect API2PDFThey add their API2PDF api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “add Header Footer” can wait for the user, and “delete PDF” can be denied outright.
- 03Any agent can actYour agent calls API2PDF through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('api2pdf', { read: 'allow', write: 'ask', // add_header_footer destructive: 'deny', // delete_pdf }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How API2PDF connects.
Users add their API2PDF 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 API2PDF 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
Use API2PDF from any agent.
API2PDF and Arc0, answered.
Can I use API2PDF with Claude, ChatGPT or Cursor?
Yes. Connect API2PDF 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 API2PDF actions you allow.
How do users connect API2PDF?
Users add their API2PDF 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.
Which API2PDF actions can my agent take?
10 in total: 2 read, 6 write and 2 destructive, such as “add Header Footer”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in API2PDF?
Yes. Actions like “delete PDF” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call API2PDF too?
Yes. The same API2PDF connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug API2PDF into your agent.
Your users connect API2PDF once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan