Eledo PDF for AI agents
Eledo PDF generates PDF documents from reusable templates and structured data, with APIs for templates, schemas, and downloads, used by teams automating recurring paperwork like statements and letters. 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 Eledo PDF.
Generate a PDF from a template
Generate a PDF by merging a template with a record's data for a customer request.
Check a template's schema
Read a template's schema to confirm which fields it expects before mapping data to it.
Read-only account checks
Get current account details as a read-only step before running a generation job.
4 Eledo PDF actions, graded by risk.
Every Eledo PDF action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- eledo_pdf.list_templatesList Templates
- eledo_pdf.get_current_accountGet Current Account
- eledo_pdf.get_template_schemaGet Template Schema
write
1Create and change things. Allow, or ask the user first.
- eledo_pdf.generate_pdfGenerate PDF
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Eledo PDF in three steps.
- 01Your users connect Eledo PDFThey add their Eledo PDF api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “generate PDF” can wait for the user to approve.
- 03Any agent can actYour agent calls Eledo PDF through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('eledo_pdf', { read: 'allow', write: 'ask', // generate_pdf destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Eledo PDF connects.
Users add their Eledo PDF 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 Eledo PDF 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 Eledo PDF from any agent.
Eledo PDF and Arc0, answered.
Can I use Eledo PDF with Claude, ChatGPT or Cursor?
Yes. Connect Eledo PDF 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 Eledo PDF actions you allow.
How do users connect Eledo PDF?
Users add their Eledo PDF 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 Eledo PDF actions can my agent take?
4 in total: 3 read, 1 write and 0 destructive, such as “generate PDF”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Eledo PDF?
Yes. Allow read actions and deny writes in the Eledo PDF policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Eledo PDF too?
Yes. The same Eledo PDF connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Eledo PDF into your agent.
Your users connect Eledo PDF once, under your brand. Your agent gets 4 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan