PDF.co API

Name: PDF.co API
Brand: PDF.co API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsTesting QaapiKey13 EndpointsREST

For Agents

Convert PDFs to CSV, JSON, XML, and images, parse invoices with AI, merge and split documents, and generate or read barcodes from uploaded files.

Install Jentic One Beta

Connect the PDF.co API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the PDF.co 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 PDF.co API.

Parse invoices and receipts with AI to extract structured line-item data

Convert PDF documents to CSV, JSON, XML, HTML, and PNG formats

Generate PDF files from HTML content with custom styling

Merge multiple PDF files into a single consolidated document

GET STARTED

Start building with PDF.co API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use PDF.co API for, with concrete tasks.

★ AI Invoice Parsing

Extract structured data from invoices and receipts using AI-powered document understanding. The POST /ai-invoice-parser endpoint accepts a PDF or image URL and returns parsed fields including vendor name, invoice number, date, line items with quantities and amounts, tax totals, and payment terms. This eliminates manual data entry for accounts payable automation and expense management workflows.

Upload an invoice PDF via POST /file/upload, then parse it via POST /ai-invoice-parser with the uploaded file URL to extract vendor name, invoice number, and line items

PDF Format Conversion

Convert PDF documents to machine-readable formats for downstream processing. The API supports conversion to CSV (for tabular data), JSON (for structured extraction), XML (for system integration), HTML (for web display), and PNG (for image rendering). Each conversion endpoint accepts a source URL and returns a download link for the converted output.

Convert a PDF containing a data table to CSV format via POST /pdf/convert/to/csv with the source URL and return the download link for the resulting CSV file

Document Assembly and Splitting

Merge multiple PDF files into a single document or split large PDFs into smaller files. The POST /pdf/merge2 endpoint accepts an array of source URLs and produces a combined PDF. POST /pdf/split separates a document by page ranges. These operations enable document workflow automation for contracts, reports, and multi-part submissions.

Merge three PDF files by providing their URLs to POST /pdf/merge2 and return the download URL for the combined document

AI Agent Document Processing via Jentic

AI agents use the PDF.co API through Jentic to parse invoices, convert documents, and extract data without managing API keys directly. Agents search by intent, receive typed schemas for document operations, and execute calls with Jentic handling the x-api-key header injection. This enables automated document workflows in accounting, legal, and data pipeline contexts.

Search Jentic for 'parse invoice from PDF', load the schema for POST /ai-invoice-parser, and execute with the invoice URL to extract structured payment data

Key Endpoints

13 endpoints — pdf.

METHOD

PATH

DESCRIPTION

POST

/ai-invoice-parser

Parse invoices with AI extraction

POST

/pdf/convert/to/csv

Convert PDF to CSV format

POST

/pdf/convert/to/json

Convert PDF to JSON format

POST

/pdf/convert/from/html

Generate PDF from HTML

POST

/pdf/merge2

Merge multiple PDFs into one

POST

/pdf/split

Split PDF into pages

POST

/barcode/generate

Generate a barcode image

POST

/barcode/read/from/url

Read barcodes from an image URL

POST

/ai-invoice-parser

Parse invoices with AI extraction

POST

/pdf/convert/to/csv

Convert PDF to CSV format

POST

/pdf/convert/to/json

Convert PDF to JSON format

POST

/pdf/convert/from/html

Generate PDF from HTML

POST

/pdf/merge2

Merge multiple PDFs into one

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your PDF.co API key is stored once, encrypted, by your own Jentic One instance and injected into the x-api-key header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'convert a PDF to a spreadsheet' or 'read a barcode from a URL', and Jentic returns the matching PDF.co operation with its input schema specifying source URL and output format so the agent calls the right endpoint without reading the reference docs.

Time to first call

FAQs

Specific to using PDF.co API through Jentic.

What authentication does the PDF.co API use?

The PDF.co API uses an API key passed in the x-api-key header. You obtain your key from the PDF.co dashboard after registration. Through Jentic, this API key is stored encrypted and injected into every request automatically so agents never handle the raw key.

Can I extract table data from PDFs with the PDF.co API?

Yes. POST /pdf/convert/to/csv extracts tabular data from PDF documents and returns it as a downloadable CSV file. For structured extraction with row and column awareness, POST /pdf/convert/to/json provides JSON output with positional data for each text element.

What are the rate limits for the PDF.co API?

PDF.co rate limits depend on your subscription plan. Free plans allow 100 API credits per month with a limit of 1 concurrent request. Paid plans provide higher credit allocations and up to 10 concurrent requests. Each endpoint call consumes 1 credit regardless of file size.

How do I parse an invoice through Jentic?

Search Jentic for 'parse invoice PDF', load the schema for POST /ai-invoice-parser, and execute with the invoice file URL. Jentic handles the x-api-key injection and returns the extracted fields including vendor, invoice number, line items, and totals in a structured response.

Does PDF.co support asynchronous processing for large files?

Yes. For large documents, you can include an async parameter in your request. The API returns a job ID immediately, and you poll POST /job/check with that ID to monitor progress. When complete, the response includes the download URL for the processed output.

Can I limit what my agent is allowed to do with the PDF.co API?

Yes. Because you run Jentic One yourself, your own rules decide which PDF.co operations and credentials your agent can use. Since PDF.co passes its source files and options in the request body, you scope the agent to just the operations it needs, such as converting a PDF to CSV or JSON with POST /pdf/convert/to/csv or reading a barcode with POST /barcode/read/from/url. Operations you leave out, like merge via POST /pdf/merge2, split, or invoice parsing via POST /ai-invoice-parser, stay unavailable to the agent unless you add them.

PDF.co API

Connect the PDF.co API to your agent

Capabilities

Start building with PDF.co API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs