Onedoclabs API Doc

Name: API Doc API
Brand: API Doc
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaImage ProcessingapiKey2 EndpointsREST

For Agents

Render PDFs from React or HTML templates so an agent can produce branded contracts, receipts, and reports without running headless Chrome.

Install Jentic One Beta

Connect the API Doc to your agent

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

Initiate a PDF rendering session via /api/docs/initiate

Generate a final PDF document by calling /api/docs/generate with the prepared payload

Render React components to a styled PDF without managing a headless-browser pipeline

GET STARTED

Start building with API Doc API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use API Doc API for, with concrete tasks.

★ Receipt and Invoice Generation

Render branded receipts and invoices from a React template that already exists in the product UI, removing the need for a separate PDF stylesheet. After /api/docs/initiate prepares the session, /api/docs/generate returns the binary PDF that can be emailed to the customer or stored in the order record. This pattern keeps the visual design in one codebase.

Call POST /api/docs/initiate with the React component payload for the order receipt, then POST /api/docs/generate to retrieve the binary PDF for emailing

Contract Document Rendering

Generate signed-ready contract PDFs from a templated HTML or React document populated with deal-specific values. The two-step initiate-then-generate flow lets the caller validate the payload before paying for the render, which is useful when contract templates change frequently and rendering is the most expensive step.

Initiate a document with the contract template and merged variables, then generate the PDF and post the URL to the e-signature platform

Report and Statement Output

Produce monthly statements, analytic reports, or compliance documents as PDFs from a React component populated with data pulled from the warehouse. The Onedoc API handles pagination and styling, so backend services can focus on data assembly rather than maintaining a separate pdf-rendering stack.

Assemble the report data, send the populated React component payload to /api/docs/initiate, then /api/docs/generate to produce the PDF for storage

Agent-Driven Document Production

Let an AI agent produce PDFs in response to natural-language requests by searching Jentic for 'generate a pdf', loading the Onedoc operation schema, and executing with the template payload. The agent never holds the x-api-key - Jentic injects it at execution time.

Search Jentic for 'generate a pdf from a react template', load the schema for /api/docs/generate, and execute with the user's template payload

Key Endpoints

2 endpoints — the onedoc api generates pdf documents from react components and html, giving developers a programmatic way to render branded contracts, receipts, invoices, and reports.

METHOD

PATH

DESCRIPTION

POST

/api/docs/initiate

Initiate a PDF rendering session

POST

/api/docs/generate

Generate the final PDF document

POST

/api/docs/initiate

Initiate a PDF rendering session

POST

/api/docs/generate

Generate the final PDF document

Why Jentic?

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

Credential isolation

Your Onedoc x-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 'generate a PDF from a React template', and Jentic returns the initiate and generate operations with their input schemas so the agent calls the right sequence without reading Onedoc docs.

Time to first call

FAQs

Specific to using API Doc API through Jentic.

What authentication does the Onedoc API use?

API key authentication via the x-api-key header. Through Jentic the key is stored encrypted in the vault (your Jentic One instance) and never enters agent context - agents receive scoped access only.

Can I render React components directly to a PDF?

Yes. The two-step flow uses /api/docs/initiate to prepare the rendering session and /api/docs/generate to return the binary PDF. Onedoc's value proposition is that the React component used in your live UI is the same one rendered to PDF.

What are the rate limits for the Onedoc API?

The OpenAPI spec does not publish explicit rate limits. Limits are governed by your Onedoc subscription tier - check your account dashboard at onedoclabs.com for current quota before bulk rendering.

How do I generate a PDF through Jentic?

Run pip install jentic, then search 'generate a pdf from html'. Jentic returns POST /api/docs/initiate and POST /api/docs/generate with their input schemas - load each schema in turn and execute. The agent never sees the x-api-key.

Is the Onedoc API free to use?

Onedoc operates on a tiered subscription with per-render pricing above the free quota. The OpenAPI spec does not encode pricing - refer to onedoclabs.com for current plans.

Why two endpoints instead of one?

The /api/docs/initiate step lets you validate the payload and lock in template variables before the more expensive /api/docs/generate render call, which is helpful when rendering is metered or when previewing variants before committing.

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

Yes. The Onedoc API exposes only two operations, POST /api/docs/initiate and POST /api/docs/generate, and because Jentic One is self-hosted by you, your own rules decide which of these the agent may call and which credentials it may use. If you want the agent to prepare a rendering session but never trigger a paid render, you can add only the initiate operation and leave out generate. The agent can call nothing you have not added, and the x-api-key stays with your instance rather than the agent.

Onedoclabs API Doc

Connect the API Doc to your agent

Capabilities

Start building with API Doc API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs