Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Formfeed, 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.
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%2Fformfeed.dev%2Fformfeed" | shStep 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%2Fformfeed.dev%2Fformfeed" | 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.
What an agent can do with Formfeed API.
Render PDFs and images from HTML, Word, PowerPoint, or URL templates in one call
Manage templates as code with versions, release channels, and canary promotion
Merge, password-protect, watermark, convert, and inspect PDFs
Store workspace files, shared partials, and a brand kit used by templates
Validate template data against a template's generated schema
GET STARTED
Deliver render events to webhook endpoints and resend failed deliveries
Run batch renders and poll a batch job for results
Patterns agents use Formfeed API for, with concrete tasks.
★ AI Agent Document Generation
An AI agent connected through Jentic can turn structured data into a finished PDF or image without a human opening a design tool. The agent searches for the render operation, Formfeed returns its input schema, and the agent submits a template id with JSON data and waits for the result. This lets an assistant produce invoices, reports, or certificates on demand.
Create a render from a template with JSON data and wait for the result
Templates as Code
Manage document templates with versions and release channels, promoting a canary before rolling it out and rolling back when needed. An automation can create a draft version, validate it with sample data, and publish it so downstream renders pick up the change.
Create a draft template version and publish it to a release channel
PDF Post-Processing
Combine Formfeed rendering with its PDF tools to merge several documents, apply a password, add a watermark, or convert an office file to PDF. This covers the finishing steps a document pipeline needs after the content is rendered.
Merge two PDFs and watermark the resulting document
Batch Rendering with Webhooks
Submit a batch of renders and poll the batch job, or register a webhook endpoint so Formfeed pushes completion events as each document finishes. This scales document generation beyond one-at-a-time calls for mail merges and bulk exports.
Create a batch of renders and register a webhook to receive completion events
61 endpoints — the formfeed api generates pdfs and images from templates and json data, one call per document.
METHOD
PATH
DESCRIPTION
/renders
Create a render
/renders/{id}/result
Wait for a render result
/templates
Create a template
/templates/{id}/versions/{number}/publish
Publish a template version
/pdf/merge
Merge PDFs
/pdf/watermark
Watermark a PDF
/renders/batch
Create a batch of renders
/webhooks
Create a webhook endpoint
/renders
Create a render
/renders/{id}/result
Wait for a render result
/templates
Create a template
/templates/{id}/versions/{number}/publish
Publish a template version
/pdf/merge
Merge PDFs
/pdf/watermark
Watermark a PDF
/renders/batch
Create a batch of renders
/webhooks
Create a webhook endpoint
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Formfeed by hand means setting up Bearer key auth, choosing the EU or US regional host, and handling idempotency keys and RFC 9457 error details yourself. Through Jentic you install once, import Formfeed from the API Directory, store the key once, and your agent calls it.
Permission scoping
Formfeed separates render operations from template, file, and workspace management, so a rule can hold your agent to rendering while template, file, and workspace edits stay out of reach. You choose the operations it may call, so a destructive one like archiving a template or deleting a workspace is not included unless you add it.
Credential isolation
Your Formfeed API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'render a PDF from a template' or 'merge PDFs', and Jentic returns the matching Formfeed operation with its input schema so the agent calls the right endpoint without reading the docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Formfeed API through Jentic.
What authentication does the Formfeed API use?
Formfeed authenticates with a Bearer API key per its OpenAPI spec: send a workspace key in the Authorization header, or in the X-API-Key header. Test keys render for free. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent's prompt or logs.
Can I merge and watermark PDFs with the Formfeed API?
Yes. Beyond rendering, Formfeed offers PDF tools to merge multiple PDFs, password-protect a PDF, watermark it, convert an office document to PDF, and inspect a PDF's structure.
Is there a Formfeed MCP server?
You don't need an MCP server to give your agent Formfeed. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the render and PDF-tool endpoints it needs.
Can I limit what my agent is allowed to do with the Formfeed API?
Yes. Write a rule that allows only the render and result-polling operations, so a document agent can produce PDFs while nothing can archive a template or delete a file, and every call it makes is logged.
What are the rate limits for the Formfeed API?
The OpenAPI spec does not publish specific rate limits; they depend on your Formfeed plan. Formfeed exposes an account endpoint and a usage endpoint you can read to track the current period, and documents limits at docs.formfeed.dev.
How do I render a PDF with the Formfeed API through Jentic?
Search Jentic for an intent like 'render a PDF from a template', and it returns the Formfeed render operation with its input schema so your agent calls it with a template id and data. Your stored key is injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Render PDFs and images from HTML, Word, PowerPoint, or URL templates, and merge, protect, watermark, and convert PDFs. Agents can manage templates as code and receive render events on webhooks.
Use for: Render a PDF from a template and JSON data, Generate an image from an HTML template, Merge several PDFs into one document, Watermark a PDF before sending it
Not supported: Does not handle e-signatures, long-term document storage, or print fulfillment. Use for generating and transforming PDFs and images from templates only.
The Formfeed API generates PDFs and images from templates and JSON data, one call per document. It renders HTML templates written in Jinja2, Liquid, or Handlebars, Word and PowerPoint templates, ad-hoc HTML, and public web pages, and it merges, protects, watermarks, converts, and inspects PDFs. Templates are managed as code with versions, release channels, and canary promotion, backed by workspace files, shared partials, and a brand kit. Render events are delivered to webhook endpoints, and rendering runs in the EU or US region.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
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>