ChatPDF API

Name: ChatPDF API
Brand: ChatPDF API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentAI/MLLanguage ModelsapiKey4 EndpointsREST

For Agents

Upload a PDF and ask questions about its content with citations across 4 endpoints.

Install Jentic One Beta

Connect the ChatPDF API to your agent

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

Upload a PDF file directly to ChatPDF and receive a source identifier for chat

Send a natural-language question about a PDF and receive a grounded answer

GET STARTED

Start building with ChatPDF API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for ChatPDF API, keeping it validated and agent-ready. ChatPDF lets applications upload a PDF and ask natural-language questions about its content. The API exposes four endpoints to register a PDF source from a URL or a direct file upload, delete sources when no longer needed, and send chat messages that are answered against the document. It is designed for teams building research, support, or compliance tools that need answers grounded in a specific document rather than the open web.

Use Cases

Patterns agents use ChatPDF API for, with concrete tasks.

★ Document Q&A for Customer Support

Let a support agent or end user ask plain-English questions against a product manual, terms-of-service PDF, or knowledge-base export. The integration uploads the PDF once via POST /v1/sources/add-url or /v1/sources/add-file and then routes user questions to POST /v1/chats/message, returning answers grounded in the document with optional page references. This avoids fine-tuning a model on the corpus and keeps answers traceable.

Add the PDF at https://example.com/manual.pdf as a source, then ask 'How do I reset the device?' and return the answer with the cited page numbers.

Contract and Compliance Review

Upload a contract or policy document and run targeted questions to surface obligations, dates, and clause locations. ChatPDF's chat endpoint accepts free-form questions and returns the answer plus references to the pages it relied on, so a reviewer can verify the source. Useful in legal, procurement, and compliance workflows where citations are mandatory.

Upload a vendor contract PDF, then ask 'What is the notice period for termination?' and 'What are the data residency commitments?' and return both answers with page citations.

Research Paper Summarisation

Ingest a research paper or whitepaper and ask the API to summarise sections, list cited works, or compare claims across documents. Each PDF is added as a source with a stable identifier, so a research session can ask multiple questions without re-uploading. When the session ends, /v1/sources/delete cleans up sources to keep storage tidy.

Add a research paper PDF, ask 'Summarise the methodology section in 5 bullets', then delete the source.

AI Agent Document Workflows

Embed PDF Q&A inside a larger agent workflow through Jentic, where the agent searches for 'chat with a pdf', loads the chat schema, and executes calls without ever seeing the raw API key. Combine with Jentic-discovered storage or email APIs to fetch attachments, ask questions, and post answers back to a ticket — all in a single agent run.

Search Jentic for 'chat with a pdf', load the ChatPDF send-message schema, and answer 'What is the refund policy?' against a previously uploaded source.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for chatpdf api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/sources/add-url

Add a PDF source by URL

POST

/v1/sources/add-file

Upload a PDF file as a source

POST

/v1/chats/message

Ask a question against a PDF source

POST

/v1/sources/delete

Delete one or more PDF sources

POST

/v1/sources/add-url

Add a PDF source by URL

POST

/v1/sources/add-file

Upload a PDF file as a source

POST

/v1/chats/message

Ask a question against a PDF source

POST

/v1/sources/delete

Delete one or more PDF sources

Why Jentic?

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

Credential isolation

ChatPDF API keys are stored encrypted in the Jentic vault. Agents receive scoped tokens and execute calls through Jentic — the raw x-api-key value never enters agent context.

Intent-based discovery

Agents search by intent (e.g., 'chat with a pdf' or 'add a pdf source') and Jentic returns the matching ChatPDF operation with its input schema, so the agent calls the right endpoint without browsing the docs.

Time to first call

Direct ChatPDF integration: half a day to wire upload and chat into an app. Through Jentic: under 15 minutes from search to first answered question.

FAQs

Specific to using ChatPDF API through Jentic.

Why is there no official OpenAPI spec for ChatPDF API?

ChatPDF does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call ChatPDF API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the ChatPDF API use?

The API uses an API key passed in the x-api-key header on every request. Keys are issued from chatpdf.com. Through Jentic, the key is stored encrypted in the credential vault and injected at execute time, so the agent never holds the raw key.

Can I ask questions about a PDF I uploaded earlier?

Yes. POST /v1/sources/add-url or POST /v1/sources/add-file returns a sourceId. Pass that id to POST /v1/chats/message along with your question, and the API replies with an answer grounded in the document plus optional page references.

What are the rate limits for the ChatPDF API?

The OpenAPI spec does not declare numeric rate limits. ChatPDF applies per-account quotas that vary by plan, so agents should handle 429 responses with exponential backoff and surface plan limits to the caller.

How do I add a PDF and ask the first question through Jentic?

Search Jentic for 'add a PDF source', load the schema for POST /v1/sources/add-url, and execute with the document URL. Then search 'chat with a pdf', load POST /v1/chats/message, and execute with the returned sourceId and your question — two steps from intent to answer.

Can I delete a PDF after I am done with it?

Yes. POST /v1/sources/delete accepts a list of source identifiers and removes them. This is useful when documents contain sensitive data and need to be purged once the analysis run completes.

ChatPDF API

Connect the ChatPDF API to your agent

Capabilities

Start building with ChatPDF API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs