PDF Generator API
77
AI ReadinessAI-Ready (A-)77/100
Official vendor OpenAPI document · agent-readyMediaContent Deliverybearer11 EndpointsREST
For Agents
Generate PDF documents from templates with PDF Generator API: list and manage templates, merge them with data, and render output within a workspace.
Use for: Show the templates in my workspace, Create a new invoice template, Render a PDF from a template and this data, Copy a template so I can make a variant
Not supported: Renders PDF documents from templates and manages those templates and workspaces. Does not store your business records, send the finished documents, or extract data from existing PDFs.
PDF Generator API turns reusable templates into finished PDF documents through a REST interface. You design a template once, then merge it with your own data to render invoices, reports, contracts, and other documents on demand. Templates live inside workspaces, so a product can keep each customer's designs separate, and a browser-based editor endpoint lets end users adjust a template without leaving your application. It suits SaaS products and back-office tools that need document output driven by data rather than hand-built files.
Install Jentic One Beta
Connect the PDF Generator API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PDF Generator API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpdfgeneratorapi.com%2Fpdfgeneratorapi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fpdfgeneratorapi.com%2Fpdfgeneratorapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with PDF Generator API.
List, read, create, update, and delete document templates
Render a PDF by merging a stored template with supplied data
Render a PDF from an inline template passed in the request
Copy an existing template to start a new variant
Open a template in the browser-based editor for end-user changes
Read and delete workspaces that group a customer's templates
Use Cases
Patterns agents use PDF Generator API for, with concrete tasks.
★ Render documents from stored templates
Produce finished PDFs on demand from templates a team maintains. The agent reads the available templates, then merges the chosen one with the supplied data and returns the rendered document, so a product can issue invoices or reports without assembling files by hand.
List the templates, then render the selected template with the provided data and return the resulting PDF.
Manage a template library
Keep a product's document templates current. The agent creates, updates, copies, and removes templates so the library reflects the documents the product needs, and a new variant can start from a copy of a proven design.
Create or update a template, or copy an existing one, so the template library matches the product's current document set.
Offer template editing to end users
Let a product's own users adjust their document designs. The agent opens a template in the browser-based editor so a customer can change layout or content, keeping design self-service without shipping a separate editor.
Open the chosen template in the editor so an end user can adjust it, then confirm the editor session for that template.
Separate templates per customer
Keep each customer's document designs isolated. The agent reads and removes workspaces so a multi-tenant product can manage template groups per customer and clean up when an account closes.
Read a workspace to see its templates, or delete a workspace when its customer account closes.
Key Endpoints
11 endpoints — pdf generator api turns reusable templates into finished pdf documents through a rest interface.
METHOD
PATH
DESCRIPTION
GET
/templates
List the templates in the workspace
POST
/templates
Create a new template
POST
/templates/output
Render a PDF from an inline template and data
GET
/templates/templateId
Read a single template by its identifier
DELETE
/workspaces/workspaceId
Delete a workspace and its grouping
GET
/templates
List the templates in the workspace
POST
/templates
Create a new template
POST
/templates/output
Render a PDF from an inline template and data
GET
/templates/templateId
Read a single template by its identifier
DELETE
/workspaces/workspaceId
Delete a workspace and its grouping
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
P
PDF Generator API
- AI-Ready (A-)77/100
87
Foundational Compliance82
Developer Experience & Jentic Compatibility56
AI-Readiness & Agent Experience94
Agent Usability75
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
82
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: ASignals: 4
57%
Example Density
How richly the API is illustrated with examples.
98%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
56
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
65%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
61%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring PDF Generator API by hand means signing JWT bearer tokens from your key and secret, learning how templates and workspaces relate, and choosing between stored and inline rendering. Through Jentic you install once, import PDF Generator API from the Jentic API Directory, configure your credentials, and your agent calls it.
Permission scoping
Rendering and template management sit behind the same key, and because Jentic One is self-hosted, your own rules decide which operations the agent may call. You can allow document rendering while withholding operations that delete templates or workspaces, so the agent reaches only what you approved.
Credential isolation
Your PDF Generator API key and secret are held encrypted by your own Jentic One instance, which produces the bearer token and attaches it to each request only at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent, such as rendering a PDF from a template, and Jentic returns the matching operation with typed inputs, so the agent calls the right one without reading the whole template and workspace surface.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using PDF Generator API through Jentic.
What authentication does PDF Generator API use?
PDF Generator API authenticates requests with a JWT bearer token that your integration signs from its API key and secret. Through Jentic, the credentials you configure are held encrypted by your own Jentic One instance and used to produce that bearer token at execution time. Check PDF Generator API's developer documentation for how the token is constructed.
Can PDF Generator API render a document without saving a template first?
Yes. Alongside rendering from stored templates, there is an output operation that accepts an inline template and data in the request, so you can produce a one-off PDF without creating a persisted template.
What are the rate limits for PDF Generator API?
The OpenAPI description does not specify rate limits. Check PDF Generator API's developer documentation for the limits on your plan before rendering documents in bulk.
Is there an MCP server for PDF Generator API?
You don't need an MCP server to use PDF Generator API with your agent. Through Jentic, your agent finds the template and rendering operations by intent and calls them directly, with your credentials injected at run time by your own Jentic One instance.
How do I connect PDF Generator API to my agent through Jentic?
To run it on your own infrastructure, install Jentic One from its GitHub repo, then import PDF Generator API from the Jentic API Directory and configure your API key and secret. Your agent can then manage templates and render documents with the bearer token produced at execution time.
Can I limit what my agent is allowed to do with PDF Generator API?
Yes. Because Jentic One is self-hosted, your own rules decide which PDF Generator API operations the agent may call, so you can allow rendering documents while withholding operations that delete templates or workspaces. Your credentials stay encrypted on your own instance and are used only when a permitted request runs.
GET STARTED