PDF-API.io for AI agents

PDF-API.io generates dynamic PDFs from a drag-and-drop template designer using HTML and CSS. Developers use it to produce customizable, on-brand PDF documents. 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 PDF-API.io See the 1 actions ↓

DocumentsAPI keyMCP + RESTpdf-api.io

AUDIT LOG · PDF-API.IOPOLICY: acme-support

09:41:07 · claude · u_8f2read

pdf_api_io.list_templates

List Templates✓ allowed · 212ms

EVERY PDF-API.IO CALL, ON THE RECORD

01 · USE CASES

What agents do in PDF-API.io.

Check available PDF templates

List templates read-only to pick the right layout before generating a document.

Review a template before reuse

Look up a saved template's fields to confirm what data it expects.

Confirm template inventory

List templates to audit what document layouts already exist in the account.

02 · ACTIONS

1 PDF-API.io actions, graded by risk.

Every PDF-API.io action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

pdf_api_io.list_templates
List Templates

write

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

No write actions.

destructive

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

No destructive actions.

03 · HOW IT WORKS

PDF-API.io in three steps.

01Your users connect PDF-API.ioThey add their PDF-API.io api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
03Any agent can actYour agent calls PDF-API.io 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('pdf_api_io', {
  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 PDF-API.io connects.

Users add their PDF-API.io 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 PDF-API.io 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 PDF-API.io from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

PDF-API.io and Arc0, answered.

Q01

Can I use PDF-API.io with Claude, ChatGPT or Cursor?

Yes. Connect PDF-API.io 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 PDF-API.io actions you allow.

Q02

How do users connect PDF-API.io?

Users add their PDF-API.io 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 PDF-API.io actions can my agent take?

1 in total: 1 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 PDF-API.io?

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

Q05

Can my own backend call PDF-API.io too?

Yes. The same PDF-API.io connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug PDF-API.io into your agent.

Your users connect PDF-API.io once, under your brand. Your agent gets 1 actions behind your policies, with every call on the record.

Connect PDF-API.io Browse all apps →

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