Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ExactPDF 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%2Fexactpdf.com%2Fexactpdf" | 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%2Fexactpdf.com%2Fexactpdf" | 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 ExactPDF API.
Read a PDF's page count and metadata
Extract plain text from a PDF
Convert a PDF to structured Markdown or to per-page JSON
Compress a PDF and optionally report whether it fits a target size
Merge several PDFs and compress the combined file
GET STARTED
Convert images to a PDF and compress the output
Patterns agents use ExactPDF API for, with concrete tasks.
★ Document Text and Data Extraction
A pipeline needs machine-readable content out of PDFs. The ExactPDF API extracts plain text, converts a PDF to structured Markdown that preserves headings and lists, and returns per-page JSON with metadata, so downstream steps can index, summarize, or feed the content to a model.
Read a PDF's page count with the pdf-info operation, then extract its text and convert it to structured Markdown
PDF Assembly and Compression
A team produces a single compact PDF from scattered inputs. The ExactPDF API merges several PDFs and compresses the result, converts a set of images into a compressed PDF, and can report whether a compressed file meets a target size, so attachments stay within upload limits.
Merge several PDFs and compress the combined file, then check whether the output meets the requested target size
AI Agent Document Processing via Jentic
An AI agent processes documents through Jentic without holding the ExactPDF key itself. It searches by intent, receives the matching operation and its input schema, and runs extraction, conversion, and compression with the credential injected at run time, so a PDF-to-data step fits into a larger workflow.
Search Jentic for 'extract text from a PDF', load the extract-text operation schema, and run it with Jentic-managed credentials
13 endpoints — the exactpdf api inspects pdfs and turns them into structured data for document workflows.
METHOD
PATH
DESCRIPTION
/api/v1/extract-text
Extract plain text from a PDF
/api/v1/pdf-structured-markdown
Convert a PDF to structured Markdown
/api/v1/pdf-to-json
Extract PDF metadata and per-page text as JSON
/api/v1/pdf-info
Read PDF page count and metadata
/api/v1/compress
Compress a PDF and report target-size fit
/api/v1/merge-compress
Merge PDFs and compress the result
/api/v1/capabilities
Discover document workflow limits
/api/v1/extract-text
Extract plain text from a PDF
/api/v1/pdf-structured-markdown
Convert a PDF to structured Markdown
/api/v1/pdf-to-json
Extract PDF metadata and per-page text as JSON
/api/v1/pdf-info
Read PDF page count and metadata
/api/v1/compress
Compress a PDF and report target-size fit
/api/v1/merge-compress
Merge PDFs and compress the result
/api/v1/capabilities
Discover document workflow limits
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ExactPDF by hand means carrying its bearer key, tracking credit balances, and polling the asynchronous workflow for direct uploads yourself. Through Jentic you install once, import ExactPDF from the API Directory, store the key once, and your agent calls it.
Permission scoping
ExactPDF carries the file in the request body, so rules bound which operations your agent may call, not which file. Limit the agent to the operations it needs, such as text extraction and PDF-to-Markdown conversion, so compression, merging, and the account operation are not included unless you add them.
Credential isolation
Your ExactPDF 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 'extract text from a PDF' or 'convert a PDF to Markdown', and Jentic returns the matching ExactPDF operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using ExactPDF API through Jentic.
What authentication does the ExactPDF API use?
The ExactPDF API authenticates with a bearer API key in the Authorization header per its OpenAPI spec, and the capability-discovery operation is public and free. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I convert a PDF to Markdown or JSON with the ExactPDF API?
Yes. The ExactPDF API has a structured-Markdown operation that preserves document structure and a pdf-to-json operation that returns metadata and per-page text. An agent can pick the format that best feeds its next step, such as Markdown for summarization or JSON for indexing.
What are the rate limits for the ExactPDF API?
The OpenAPI spec does not specify numeric rate limits for the ExactPDF API; execution endpoints spend API credits instead. The account operation reports the credit balance and the capabilities operation reports workflow limits, so an agent can check both before running paid calls.
How do I extract text from a PDF with the ExactPDF API through Jentic?
Search Jentic for 'extract text from a PDF' and it returns the ExactPDF extract-text operation with its input schema. Load the schema, send the PDF, and the key is injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the ExactPDF API?
Yes. ExactPDF carries the file in the request body, so a rule bounds which operations your agent may call rather than which file. Limit it to the operations it needs, such as text extraction and conversion, and leave the asynchronous workflow and account operations out unless you add them.
Is there an ExactPDF API MCP server?
You don't need an MCP server to give your agent the ExactPDF API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls the extraction and conversion operations it needs without a separate server to install.
For Agents
Inspect PDFs, extract text, convert PDFs to structured Markdown or JSON, and compress or merge files. Authenticated with a bearer API key; capability discovery is public.
Use for: Extract the text from a PDF, Convert a PDF to structured Markdown, Get the page count and metadata of a PDF, Compress a PDF to a smaller size
Not supported: Does not handle PDF e-signing, form filling, or long-term storage. Use for inspecting, extracting from, converting, and compressing PDFs only.
The ExactPDF API inspects PDFs and turns them into structured data for document workflows. It reads page count and metadata, extracts plain text, and converts a PDF to structured Markdown or to per-page JSON. It also compresses PDFs against a target size, merges and compresses several files, and converts images into a compressed PDF, with an asynchronous workflow for direct uploads. Capability discovery is public, while execution endpoints spend API credits.
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>