Install Jentic One Beta

Connect the PDFBolt API to your agent

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

Render a PDF from a web page url, Base64 html, or a templateId with templateData and get the file back in the response body

Generate a PDF and receive a temporary download URL instead of the binary through the sync mode

Queue a background conversion that posts its result to your webhook, with optional retryDelays and additionalWebhookHeaders

Upload a generated PDF straight to your own S3-compatible bucket with a customS3PresignedUrl

GET STARTED

Start building with PDFBolt API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use PDFBolt API for, with concrete tasks.

★ Agent-generated documents through Jentic

An agent that drafts invoices, reports, or certificates as HTML finds the PDFBolt sync conversion operation through Jentic, sends the Base64 html, and returns the temporary download URL to the user. Jentic injects the API-KEY header at call time, so the agent produces finished PDFs without handling the key.

Base64-encode the invoice HTML, call POST /v1/sync with it in the html field, and return the documentUrl from the response

Template-driven invoices and statements

Teams keep layout in a published PDFBolt template and send only the data. A conversion request passes templateId and templateData, such as an invoice_number and total, and PDFBolt fills the Handlebars placeholders. Layout changes go through the Template API, so the code that sends data stays unchanged.

Call POST /v1/direct with templateId '00000000-0000-0000-0000-000000000000' and templateData containing invoice_number 'INV-2026-0112' and total '$250.00', then save the returned PDF

Background conversion with webhook delivery

For long pages or batch jobs, POST /v1/async accepts the source and a required webhook URL, then delivers the result there with fields such as documentUrl, status, and documentSizeMb. Optional retryDelays retry failed conversions, and a customS3PresignedUrl sends the PDF straight to your own bucket.

Call POST /v1/async with url 'https://example.com/report' and webhook 'https://example.com/hooks/pdf', then wait for the webhook payload and read documentUrl

Safe template changes

Before a template change ships, POST /v1/templates/validate checks the payload, POST /v1/templates/preview renders it against sampleData, and POST /v1/templates/{templateId}/diff compares it with the published version. A draft saved with POST /v1/templates/drafts goes live only when POST /v1/templates/{templateId}/publish is called.

Call POST /v1/templates/{templateId}/diff with the proposed content, sampleData, and parameters, review the result, then POST /v1/templates/drafts and POST /v1/templates/{templateId}/publish with a comment

Key Endpoints

14 endpoints — the pdfbolt api generates pdfs from base64-encoded html, https urls, or published templates filled with json data.

METHOD

PATH

DESCRIPTION

POST

/v1/direct

Generate a PDF and return it in the response

POST

/v1/sync

Generate a PDF and return a download URL

POST

/v1/async

Generate a PDF and deliver it by webhook

GET

/v1/usage

Get plan and remaining conversions

GET

/v1/templates

List templates

POST

/v1/templates/preview

Preview a template payload

POST

/v1/templates/{templateId}/publish

Publish a template draft

POST

/v1/direct

Generate a PDF and return it in the response

POST

/v1/sync

Generate a PDF and return a download URL

POST

/v1/async

Generate a PDF and deliver it by webhook

GET

/v1/usage

Get plan and remaining conversions

GET

/v1/templates

List templates

POST

/v1/templates/preview

Preview a template payload

POST

/v1/templates/{templateId}/publish

Publish a template draft

Why Jentic?

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

Setup

Wiring PDFBolt by hand means keeping two header credentials apart (API-KEY for conversions, PERSONAL-ACCESS-TOKEN for templates), Base64-encoding HTML, and picking the right delivery mode. Through Jentic you install once, import PDFBolt from the API Directory, store both credentials once, and your agent calls it.

Permission scoping

PDFBolt puts the template id in the URL path (/v1/templates/{templateId}), so a rule can pin your agent to one template for reads, diffs, and publishing. Conversions carry their source in the request body, so for rendering you limit the agent to the operations it needs, and destructive ones like template deletion are not included unless you add them.

Credential isolation

Your PDFBolt API key and Personal Access Token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'convert HTML to PDF' or 'generate a PDF from a template', and Jentic returns the matching PDFBolt operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PDFBolt API through Jentic.

What authentication does the PDFBolt API use?

Per its OpenAPI spec, PDFBolt uses two header credentials. The conversion and usage operations take an API key in the `API-KEY` header, while the Template API operations take a Personal Access Token in the `PERSONAL-ACCESS-TOKEN` header; both are created on the API Credentials page in the PDFBolt Dashboard. The Template Contract operation is declared with no security requirement. Through Jentic both credentials are stored encrypted by your own Jentic One instance and injected at call time.

What is the difference between direct, sync, and async conversion?

POST /v1/direct returns the generated PDF in the HTTP response body. POST /v1/sync returns a temporary download URL instead. POST /v1/async accepts a background job and delivers the result to the webhook URL you supply, which suits long renders and batch work.

How do I convert HTML to a PDF through Jentic?

Search Jentic for 'convert HTML to PDF', load the schema for POST /v1/sync, and send your HTML Base64-encoded in the html field. The response carries a temporary download URL for the PDF. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the PDFBolt API?

The OpenAPI spec defines a Too Many Requests error but does not state numeric limits. Check https://pdfbolt.com/docs for current limits, and use GET /v1/usage to see your plan and remaining conversions.

Is there a PDFBolt MCP server?

You don't need an MCP server to give your agent the PDFBolt API. Jentic connects it directly from the API Directory: import it, store your credentials 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 PDFBolt API?

Yes. For example, write a rule that allows only POST /v1/sync and GET /v1/usage, so the agent can render PDFs and check remaining conversions but cannot publish or delete templates. Every call it makes is logged by your Jentic One instance.

PDFBolt API

AI ReadinessAI-Aware (A-)72/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey14 EndpointsREST

For Agents

Render PDFs from HTML, a URL, or a published template with JSON data, choosing an inline, download-URL, or webhook delivery mode, and author reusable templates through validate, preview, and publish steps.

Use for: I need to turn this invoice HTML into a PDF, Convert the page at a URL into a PDF and give me a download link, Generate a PDF from my published invoice template with this order data, Render a large report in the background and send the result to my webhook

Not supported: Does not handle e-signatures, PDF editing or merging, or document storage beyond temporary download URLs. Use for generating PDFs from HTML, URLs, and templates only.

The PDFBolt API generates PDFs from Base64-encoded HTML, HTTPS URLs, or published templates filled with JSON data. Conversions run in three modes: direct returns the PDF in the response, sync returns a temporary download URL, and async accepts a background job and delivers the result to your webhook, with optional upload to your own S3-compatible bucket through a pre-signed URL. A separate Template API lets you validate, preview, diff, save as drafts, and publish reusable Handlebars templates, and a usage endpoint reports your plan and remaining conversions.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

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).

21%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

71%

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

79%

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.

89%

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

50%

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: ASignals: 1

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PDFBolt API to your agent

Capabilities

Start building with PDFBolt API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

PDFBolt API

Jentic AI Readiness Score

PDFBolt 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