Official vendor OpenAPI document · agent-readyMediaImage Processingbearer9 EndpointsREST
For Agents
Lets an AI agent convert, merge, and compress PDF and image files through iLovePDF and manage electronic signature requests from creation to signed download.
Use for: I need to merge several PDFs into one document, Convert an image into a PDF file, Compress a large PDF before sending it, Send a document out for electronic signature
Not supported: Does not handle document storage, text search, or accounting. Use it for PDF and image processing and electronic signatures only.
iLovePDF is a PDF and image processing API with electronic signature support. It authenticates by exchanging a project public key for a token, then runs tasks that convert, merge, compress, and otherwise transform PDF and image files across processing servers. A signature workflow lets applications create signature requests, list them, and download signed documents.
Install Jentic One Beta
Connect the iLovePDF API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the iLovePDF 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%2Filovepdf.com%2Fmain" | 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%2Filovepdf.com%2Fmain" | 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 iLovePDF API.
Convert, merge, and compress PDF and image files
Start a processing task and upload files to it
Process uploaded files and download the result
Create electronic signature requests for documents
List signature requests and download signed files
Exchange a project public key for a session token
Use Cases
Patterns agents use iLovePDF API for, with concrete tasks.
★ Document conversion and assembly
An application needs to turn user uploads into a single clean PDF. iLovePDF starts a processing task, accepts the uploaded files, runs the chosen tool such as convert or merge, and returns a downloadable result, so a product can assemble documents without shipping its own conversion stack. Each task runs on the processing server the API assigns.
Start a merge task, upload the source PDFs, process them, and download the combined file
Electronic signature workflow
A team needs signatures on contracts without a separate signing tool. iLovePDF creates a signature request for a document, lists outstanding requests, and returns the signed file once complete, letting an application drive the signing flow programmatically. Requester views expose the status of a pending request.
Create a signature request for a contract and download the signed document when it completes
AI agent document processing
An AI agent handling document tasks can convert, combine, and route files for signature end to end. The agent authenticates, runs the processing task, and either returns the output or opens a signature request, keeping file operations behind the tools the operator has allowed. The token stays managed outside the agent's context.
Given an uploaded file, run a compression task and return the smaller PDF to the caller
Key Endpoints
9 endpoints — ilovepdf is a pdf and image processing api with electronic signature support.
METHOD
PATH
DESCRIPTION
POST
/auth
Request a signed token using your public key
GET
/start/{tool}/{region}
Start a processing task for a tool
POST
/{server}/v1/upload
Upload a file to a processing task
POST
/{server}/v1/process
Process the uploaded files
GET
/{server}/v1/download/{task}
Download the processed output
POST
/{server}/v1/signature
Create a signature request
POST
/auth
Request a signed token using your public key
GET
/start/{tool}/{region}
Start a processing task for a tool
POST
/{server}/v1/upload
Upload a file to a processing task
POST
/{server}/v1/process
Process the uploaded files
GET
/{server}/v1/download/{task}
Download the processed output
POST
/{server}/v1/signature
Create a signature request
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.
I
iLovePDF API
- AI-Aware (B-)63/100
85
Foundational Compliance63
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability75
Security53
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
85
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
99%
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).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
63
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
0%
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.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
24%
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.
50%
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).
53
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C-Signals: 1
53%
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 iLovePDF by hand means exchanging a project public key for a token, tracking the processing server assigned to each task, and threading the token through upload, process, and download calls. Install Jentic One once, import the API from the Jentic API Directory, and store the credential once for your agent to reuse.
Permission scoping
Scope your agent to the operations it needs, such as conversion tasks or signature requests, and withhold the rest. You decide which operations are callable, so an agent can process files without gaining signing rights.
Credential isolation
Your iLovePDF token is stored once, encrypted, by your own Jentic One instance and injected only at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents find iLovePDF through Jentic's intent search: a query such as 'convert and merge PDF files' matches the processing operations, which the agent then calls with your stored credential.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using iLovePDF API through Jentic.
What can an AI agent do with the iLovePDF API?
An agent can start processing tasks to convert, merge, and compress PDF and image files, download the results, and drive an electronic signature workflow from request to signed download. It covers document processing and signing.
How does the iLovePDF API authenticate?
iLovePDF authenticates with a bearer token that you obtain by exchanging your project public key. Jentic injects the token at execution time so it stays out of the agent's context.
Can I limit what my agent is allowed to do with the iLovePDF API?
Yes. Your Jentic One instance controls which operations an agent may call, so you can allow document conversion tasks while withholding the signature operations, or the reverse. Nothing outside the operations you allow is reachable.
What file operations does iLovePDF support?
It converts, merges, compresses, and transforms PDF and image files through processing tasks, and adds an electronic signature workflow for sending documents and downloading signed copies.
How do I connect the iLovePDF API to my AI agent with Jentic?
Install Jentic One with its setup script, import the iLovePDF API from the Jentic API Directory, and store your credential once. Your agent can then call the processing and signature operations you allow.
GET STARTED