Lists PDF-API.io templates with their required fields and variants, right inside the conversation.
1actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves all PDF-API.io templates available in the account. Support selects the right template for customer document generation requests.
Each card is one request a support team gets, and the Pdf api io actions Ayro runs to close it.
When a customer needs a specific document, Ayro lists the templates on the PDF-API.io account and matches one by name and type before anything gets generated.
Before a document is generated, Ayro checks the required fields for that template so the conversation collects exactly what's needed, nothing more.
When a template has more than one variant, Ayro can list what's available so a customer picks the right version instead of guessing.
Instead of routing a template question to a person, Ayro checks the PDF-API.io account's template list directly and answers from there.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Pdf api io actions it has and picks the ones a request needs.
Authorize the Pdf api io account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Pdf api io actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freePdf api io · Ayro
What can you do in Pdf api io without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Pdf api io.
The template's metadata: its name, the fields it requires, and the variants it offers - enough to identify the right one and know what information to collect before generating a document.
All 1 actions your agent can call on Pdf api io, straight from the live MCP connection.
List all available templates.
Same connection, same setup. Pick the next one your team already uses.
Partitions PDFs into text, tables, and images, files them into DocSets as tracked async tasks, and retrieves parsed elements or the original binary.
Generates documents from templates, fills PDF form fields, adds watermarks and page numbers, and merges several files into one.
Checks the DocuPost balance, then posts a letter from a PDF URL or a postcard from front and back images to a confirmed address.
Browses folders, reports who has access to a path and through which group, and revokes permissions, share links, and API keys on request.
Searches the wiki for the passage that answers a question, drafts and updates documents, files them into collections, and manages share links.
Searches documents and templates by text, reports whether the latest one was sent or completed, and maintains the folder structure.

Authorize the account and your agent has all 1 actions from the first conversation.
