Install Jentic One Beta

Connect the EasyPDFServer to your agent

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

Render an arbitrary HTML string into a PDF document

Convert a publicly reachable URL into a PDF snapshot of the rendered page

Pass rendering options such as page size, margins, and orientation per request

Return the rendered PDF in the HTTP response for direct download or storage

Use Cases

Patterns agents use EasyPDFServer API for, with concrete tasks.

GET STARTED

Start building with EasyPDFServer API

Explore with Jentic One

View OpenAPI Document

★ Invoice and receipt rendering

SaaS billing and order systems often template their invoices as HTML for browser preview. Calling POST /make-pdf with the rendered HTML string returns a print-ready PDF in a single request, removing the need to ship a wkhtmltopdf or headless Chromium dependency in the application image.

Render the supplied invoice HTML to a PDF using A4 page size and 1cm margins, then return the PDF bytes.

Report archiving from URLs

Compliance and audit pipelines can capture the rendered state of dashboards or report pages by sending the URL to /make-pdf. The endpoint resolves the page server-side, runs the render, and returns a PDF that can be filed alongside the audit record without browser screenshots.

Convert the URL https://example.com/q2-report into a PDF and return the document for archiving.

Templated document generation

Document workflows like contracts, onboarding packs, or certificates render an HTML template with merged data and need a final PDF for signature or distribution. EasyPDFServer accepts the rendered HTML string and applies consistent print styling so every generated document has matching pagination and margins.

Given an HTML string containing a contract, render it to a PDF with A4 portrait page size and return the PDF for signature.

Agent-driven document export

An AI agent that produces structured outputs in HTML can pipe its own output through EasyPDFServer to deliver a polished PDF to the end user. Through Jentic, the agent picks the right operation by intent and submits the HTML without the user managing rendering infrastructure.

Given the agent's HTML summary output, send it to EasyPDFServer with letter page size and return the resulting PDF.

Key Endpoints

1 endpoints — easypdfserver is a focused html-to-pdf rendering service that exposes a single endpoint for converting raw html or a target url into a downloadable pdf.

METHOD

PATH

DESCRIPTION

POST

/make-pdf

Convert HTML or a URL to a PDF document

POST

/make-pdf

Convert HTML or a URL to a PDF document

Why Jentic?

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

Setup

Wiring EasyPDFServer by hand means coding the HTML-to-PDF and URL-to-PDF render call against its host and handling the binary response yourself. Through Jentic you install once, import EasyPDFServer from the API Directory, and your agent calls it.

Permission scoping

EasyPDFServer exposes a single render operation and takes its HTML or URL input in the request body rather than the URL path, so scope your agent to the /make-pdf operation it needs. Nothing beyond that render is available unless the API adds it.

Credential isolation

Any header or token EasyPDFServer requires 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 'convert html to a pdf', and Jentic returns the EasyPDFServer /make-pdf operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using EasyPDFServer API through Jentic.

What authentication does the EasyPDFServer API use?

The published OpenAPI spec for EasyPDFServer does not declare a security scheme on /make-pdf. Check your account dashboard for plan-specific access controls, and through Jentic any required token or header can be added to the request once the auth model is confirmed.

Can I convert a live URL to PDF with EasyPDFServer?

Yes. POST /make-pdf accepts either an HTML body string or a target URL parameter. When a URL is supplied, EasyPDFServer fetches and renders the page server-side and returns the PDF in the response.

What are the rate limits for the EasyPDFServer API?

The OpenAPI spec does not publish numeric rate limits. EasyPDFServer applies per-account quotas based on plan tier - consult the EasyPDFServer pricing page or contact support for the conversion limit applied to your subscription.

How do I render HTML to a PDF through Jentic?

Search Jentic for 'render html as a pdf', load the schema for POST /make-pdf, then execute with the HTML string and any rendering options. The flow is: pip install jentic, then await client.search, await client.load, await client.execute.

Does EasyPDFServer support adding watermarks or signatures?

The /make-pdf endpoint accepts standard render options like page size and margins. Watermarks and digital signatures are typically added by composing the HTML or by post-processing the returned PDF with a signing service such as DocuSign.

Can I limit what my agent is allowed to do with the EasyPDFServer API?

Yes. Because your Jentic One instance is self-hosted, you set the rules that decide which operations and credentials your agent may use. EasyPDFServer exposes a single render operation, so you can scope your agent to just the POST /make-pdf operation, which takes its HTML or URL input in the request body. Nothing beyond that render is reachable, and any token the API requires is held by your own instance and injected only when that operation runs.

EasyPDFServer

Name: EasyPDFServer API
Brand: EasyPDFServer
Availability: InStock

Community OpenAPI document · agent-readyMediaContent Deliverynone1 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Convert HTML strings or live URLs into PDF documents through a single rendering endpoint.

Use for: Convert this HTML invoice template into a PDF, Render a public URL as a PDF for archiving, Generate a PDF report from a templated HTML string, Snapshot a webpage as a PDF document

Not supported: Does not handle PDF editing, splitting, merging, or digital signatures - use for HTML-to-PDF and URL-to-PDF rendering only.

EasyPDFServer is a focused HTML-to-PDF rendering service that exposes a single endpoint for converting raw HTML or a target URL into a downloadable PDF. The /make-pdf endpoint accepts the source content along with rendering options like page size and margins, and returns the rendered PDF. It is used by reporting tools, invoicing systems, and document generation flows that need a hosted converter without running a headless browser themselves.

Jentic One on Github View OpenAPI Document