Install Jentic One Beta

Connect the pdfs.build API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the pdfs.build 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%2Fpdfs.build%2Fpdfs" | 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%2Fpdfs.build%2Fpdfs" | 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 pdfs.build API.

Render a published template to a PDF by externalId with JSON data validated against the template's schema, optionally pinned to a version

Queue a batch of renders against one template and version through the batches endpoint and track it by batchId

Run a render in the background with async set to true, poll the render job, and download the finished PDF

Create a template with externalId, name, and code, then publish or unpublish it

GET STARTED

Start building with pdfs.build API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use pdfs.build API for, with concrete tasks.

★ Agent document rendering through Jentic

An agent that prepares invoices or certificates finds the pdfs.build render operation through Jentic, sends the record as data to a published template's externalId, and returns the PDF. pdfs.build validates data against the template schema first, so a missing field comes back as a validation error rather than a broken document. Jentic injects the bearer key at call time, so the agent never sees the prs_ key.

Call POST /v2/organizations/{organizationId}/templates/invoice/render with data containing company 'Acme Corp', items with name 'Consulting', qty 3, price 150, and due_date '2026-06-01', then return the PDF

Bulk certificates and statements

For a run of documents from one design, the batches endpoint takes an items list, up to 500 entries, against one template and one version resolved at submission, so a mid-batch template change does not mix versions. Progress is read from GET /v2/organizations/{organizationId}/batches/{batchId}, and on plans with webhooks a single batch completion event replaces per-item callbacks.

POST /v2/organizations/{organizationId}/templates/certificate/batches with an items list of attendee data, then poll GET /v2/organizations/{organizationId}/batches/{batchId} until it completes

Background renders with signed webhooks

Set async to true on a render to get a job handle instead of waiting, then poll the job or listen for render.completed and render.failed events. Webhook endpoints are managed per organization, a test event confirms the receiver works, rotate-secret replaces the signing secret, and the deliveries list shows recent attempts. webhookIds on a render limits which endpoints receive its events.

Call the render operation with async true and webhookIds containing one endpoint id, then GET /v2/organizations/{organizationId}/renders/{jobId} and download GET /v2/organizations/{organizationId}/renders/{jobId}/pdf when it finishes

Template editing inside your own product

SaaS products can let their customers edit document designs without a pdfs.build account. POST /v2/organizations/{organizationId}/templates/{externalId}/embed-sessions creates an editor session for an externalTenantId and externalUserId, with an optional expiresInSeconds, and the session can be revoked at any time. PATCH on a template sets its scopePath for tenant scoping.

Create an embed session for template 'invoice' with externalTenantId 'tenant_42' and externalUserId 'user_7', return the session to the frontend, and revoke it with DELETE /v2/organizations/{organizationId}/embed-sessions/{sessionId} when done

Key Endpoints

38 endpoints — the pdfs.

METHOD

PATH

DESCRIPTION

POST

/v2/organizations/{organizationId}/templates/{externalId}/render

Render a PDF from a published template

POST

/v2/organizations/{organizationId}/templates/{externalId}/batches

Render a batch

GET

/v2/organizations/{organizationId}/renders/{jobId}

Get render job status

POST

/v2/organizations/{organizationId}/templates

Create a template

POST

/v2/organizations/{organizationId}/templates/{externalId}/publish

Publish a template

GET

/v2/organizations/{organizationId}/logs

List render logs

POST

/v2/organizations/{organizationId}/webhooks

Create a webhook endpoint

POST

/v2/organizations/{organizationId}/templates/{externalId}/render

Render a PDF from a published template

POST

/v2/organizations/{organizationId}/templates/{externalId}/batches

Render a batch

GET

/v2/organizations/{organizationId}/renders/{jobId}

Get render job status

POST

/v2/organizations/{organizationId}/templates

Create a template

POST

/v2/organizations/{organizationId}/templates/{externalId}/publish

Publish a template

GET

/v2/organizations/{organizationId}/logs

List render logs

POST

/v2/organizations/{organizationId}/webhooks

Create a webhook endpoint

Why Jentic?

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

Setup

Wiring pdfs.build by hand means sending its prs_ bearer key, matching the organization id in every v2 URL to the key, and handling async jobs and batches yourself. Through Jentic you install once, import pdfs.build from the API Directory, store the key once, and your agent calls it.

Permission scoping

pdfs.build puts the organization id and the template's external id in the URL path (/v2/organizations/{organizationId}/templates/{externalId}/...), so a rule can pin your agent to one template and the operations you pick. You choose the operations it may call, so actions like unpublishing templates, deleting webhook endpoints, or minting delegated tickets are not included unless you add them.

Credential isolation

Your pdfs.build 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 'render a PDF from a template' or 'check a render job', and Jentic returns the matching pdfs.build operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using pdfs.build API through Jentic.

What authentication does the pdfs.build API use?

Per its OpenAPI spec, pdfs.build authenticates with an organization-scoped API key that starts with `prs_`, sent as an HTTP bearer token in the Authorization header. The organization in a v2 URL must match the key's organization, otherwise the request fails with organization_scope_mismatch. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

What is the difference between the v2 and v1 routes?

The v2 routes live under /v2/organizations/{organizationId} and address templates by an external id you control. The v1 routes identify templates by their generated internal id, are marked deprecated in the spec, and remain for existing integrations, so new work should use v2.

How do I render a PDF with pdfs.build through Jentic?

Search Jentic for 'render a PDF from a template', load the schema for the v2 render operation, and pass your organization id, the template's externalId, and the document data. The template must be published first. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the pdfs.build API?

The OpenAPI spec does not state a per-second rate limit. It describes a monthly render quota tied to your plan, with batches admitted in full or rejected with a 429. Check https://pdfs.build/docs/ for current plan limits.

Is there a pdfs.build MCP server?

You don't need an MCP server to give your agent the pdfs.build API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

Can I limit what my agent is allowed to do with the pdfs.build API?

Yes. For example, write a rule that allows only the render operation on the 'invoice' template plus the two render job reads (job status and PDF download), so the agent can produce and fetch invoices from that one template and cannot publish templates, delete webhooks, or mint delegated tickets. Every call it makes is logged by your Jentic One instance.

pdfs.build API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer38 EndpointsREST

For Agents

Create, publish, and render PDF templates by external id, run background and batch renders, read render logs, manage signed webhooks, and issue embedded editor sessions or delegated grants for your own tenants.

Use for: I need to render the invoice template with this customer's data, Queue renders of the certificate template for every attendee, Check whether background render job is finished and fetch the PDF, Create a new template from a gallery design

Not supported: Does not convert arbitrary web pages or HTML strings to PDF, collect e-signatures, or edit existing PDF files. Use for rendering, publishing, and managing pdfs.build templates only.

The pdfs.build API renders PDFs from templates you create and publish, validating the data you send against each template's schema before compiling it. The v2 routes address templates by an external id you control inside an organization, and support synchronous renders, background renders with job polling, and batch renders against one pinned template version. Around rendering it exposes render logs, signed webhook endpoints with secret rotation and delivery history, a gallery of ready-made designs, embedded editor sessions for your own users, and delegated connect tickets with scoped grants. Legacy v1 routes remain for existing integrations and are marked deprecated.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

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: BSignals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

57%

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: C-Signals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

55%

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: A-Signals: 1

74%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the pdfs.build API to your agent

Capabilities

Start building with pdfs.build API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

pdfs.build API

Jentic AI Readiness Score

pdfs.build 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