Install Jentic One Beta

Connect the iFillPDF API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iFillPDF 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.

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%2Fifillpdf.com%2Fifillpdf" | sh

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%2Fifillpdf.com%2Fifillpdf" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 iFillPDF API.

Upload a PDF by file, pdf_url, or pending_upload_id and start AI field detection on it

Analyse a PDF synchronously with POST /api/v1/documents/analyze when the caller needs fields back at once

Fill an analysed document with values and get the PDF back, or a signed URL with format=url

Save an analysed document as a template and clone it into a new working document without debiting page quota

GET STARTED

Start building with iFillPDF API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use iFillPDF API for, with concrete tasks.

★ AI agent completing PDF forms through Jentic

A developer wants their agent to complete administrative PDF forms from data it already has. Through Jentic the agent searches for 'fill a PDF form', loads the iFillPDF document creation operation with its input schema, uploads the form, waits for analysis to finish, and then calls the fill operation with the values, all with the API key injected at call time. The agent returns a signed URL to the filled PDF.

POST /api/v1/documents with a pdf_url, poll GET /api/v1/documents/{document_id} until analysis completes, then POST /api/v1/documents/{document_id}/fill with values and format=url

Reusable form templates

Teams that file the same form repeatedly analyse it once and reuse it. POST /api/v1/templates creates a template from a source_document_id, and POST /api/v1/templates/{template_id}/use clones it into a new working document pre-filled with its frozen defaults. The spec notes the clone does not re-run analysis and does not debit the page quota.

POST /api/v1/templates with source_document_id and a name, then POST /api/v1/templates/{template_id}/use and fill the new document

Document status review

Operations staff track which uploaded forms are ready and which need attention. GET /api/v1/documents lists the team's documents newest first, with q to search by name, status to filter by states such as completed or analysis_failed, and cursor pagination. A failed document can be retried with the reanalyze operation.

Call GET /api/v1/documents with status=analysis_failed, then POST /api/v1/documents/{document_id}/reanalyze for each result

Key Endpoints

18 endpoints — the ifillpdf api uploads pdf forms, runs ai field detection on them, stores the values a user enters, and generates the filled pdf.

METHOD

PATH

DESCRIPTION

POST

/api/v1/documents

Create and analyse a document asynchronously

POST

/api/v1/documents/analyze

Create and analyse a document synchronously

GET

/api/v1/documents/{document_id}

Get a document

POST

/api/v1/documents/{document_id}/fill

Fill a document

GET

/api/v1/documents

List documents

POST

/api/v1/templates

Create a template from a document

POST

/api/v1/templates/{template_id}/use

Instantiate a template

POST

/api/v1/documents

Create and analyse a document asynchronously

POST

/api/v1/documents/analyze

Create and analyse a document synchronously

GET

/api/v1/documents/{document_id}

Get a document

POST

/api/v1/documents/{document_id}/fill

Fill a document

GET

/api/v1/documents

List documents

POST

/api/v1/templates

Create a template from a document

POST

/api/v1/templates/{template_id}/use

Instantiate a template

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring iFillPDF by hand means sending a bearer API key, choosing between multipart, pdf_url, and signed-upload paths, and polling an asynchronous analysis before you can fill. Through Jentic you install once, import iFillPDF from the API Directory, store the key once, and your agent calls it.

Permission scoping

iFillPDF puts the document id in the URL path (/api/v1/documents/{document_id}/...), so a rule can pin your agent to one document and the operations you pick for it. You choose the operations it may call, so destructive ones like document or template deletion are not included unless you add them.

Credential isolation

Your iFillPDF 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 'fill a PDF form' or 'create a template from a document', and Jentic returns the matching iFillPDF operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using iFillPDF API through Jentic.

What authentication does the iFillPDF API use?

The iFillPDF API authenticates with an API key sent as a bearer token in the Authorization header, per its OpenAPI spec. Two operations are declared with no auth requirement: creating a pending upload and resolving a public template by slug. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I get the filled PDF as a link instead of a file with the iFillPDF API?

Yes. POST /api/v1/documents/{document_id}/fill takes the values and returns the filled PDF by default. Pass format=url to get a signed URL instead; the spec also says a signed URL is returned when the PDF is too large for a direct response. An optional watermark field rides in the same body.

What are the rate limits for the iFillPDF API?

The OpenAPI spec does not specify rate limits, though it notes that creating a document debits your page quota. Check https://www.ifillpdf.com for current limits and quota by plan.

Is there an iFillPDF MCP server?

You don't need an MCP server to give your agent iFillPDF. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the upload, analysis, and fill operations it needs, discovered on demand.

Can I limit what my agent is allowed to do with the iFillPDF API?

Yes. As a worked example, allow GET and the fill operation only under /api/v1/documents/{document_id} for one document id, and the agent can read that form and produce its filled PDF but cannot delete documents, change templates, or write to the vault. Every call it makes is logged.

How do I fill a PDF form through Jentic?

Search Jentic for 'fill a PDF form', load the document creation operation, and upload the form or pass a pdf_url. Poll GET /api/v1/documents/{document_id} until analysis completes, then call the fill operation with values. To run it on your own infrastructure, install Jentic One from its GitHub repo.

iFillPDF API

AI ReadinessFoundational (D+)48/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageDocument Managementbearer18 EndpointsREST

For Agents

Upload a PDF form, let iFillPDF detect its fields, write values into them, and download the filled PDF or reuse it as a template.

Use for: Fill out this PDF form with my details, I want to upload a PDF and detect its form fields, Get the filled PDF as a download link, List all documents that failed analysis

Not supported: Does not collect e-signatures, convert office files, or edit PDF page layout. Use for detecting and filling PDF form fields only.

The iFillPDF API uploads PDF forms, runs AI field detection on them, stores the values a user enters, and generates the filled PDF. A document can be created from a multipart upload, a pdf_url, or a pending_upload_id, analysed asynchronously or synchronously, then filled with POST /api/v1/documents/{document_id}/fill, which returns the PDF directly or a signed URL when format=url. Analysed documents can be saved as reusable templates and cloned into new working documents without re-running analysis, and a per-user vault holds ID or financial documents for later pre-filling.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

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).

25%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4

27%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

85%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the iFillPDF API to your agent

Capabilities

Start building with iFillPDF API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

iFillPDF API

Jentic AI Readiness Score

iFillPDF API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness