Install Jentic One Beta

Connect the Doqlo Bulk Fill Public API to your agent

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

Submit a bulk fill export job from a source PDF, a configuration package, and inline rows or a CSV file

Set a failure threshold so a job stops when too many rows fail to fill

Poll an export job for its current state while it runs

Download the completed output once the export job finishes

Use Cases

Patterns agents use Doqlo Bulk Fill Public API for, with concrete tasks.

GET STARTED

Start building with Doqlo Bulk Fill Public API

Explore with Jentic One

View OpenAPI Document

★ Agent-driven bulk document fill

An AI agent connected through Jentic submits a Bulk Fill export job from a stored template and a CSV of rows, polls the job until it completes, and retrieves the download handle, producing a batch of filled PDFs without a human stepping through a UI. The agent sets the failure threshold so a bad batch stops early rather than producing broken output.

Create an export job from a stored template and a CSV of rows, poll until it completes, and return the download handle

Mail-merge style document batches

Operations teams generate personalized document batches, such as certificates or statements, by filling one PDF template with each row in a dataset. Doqlo runs the fill as a single asynchronous export job and enforces a maximum failed-row percentage so a partial dataset does not silently produce an incomplete batch.

Submit an export job that fills a certificate template for 200 rows and reject it if more than 2 percent of rows fail

Export job status polling

An integration that kicks off a long-running fill needs to know when the output is ready. The Doqlo API returns an export job's current state on each read, so a workflow can poll until the job completes and then redeem the download handle for the finished documents.

Read the state of an export job and, once it reports complete, redeem the download handle

Key Endpoints

3 endpoints — the doqlo bulk fill api turns a source pdf, a reusable configuration package exported from the bulk fill editor, and a row-data input into a batch of filled documents through an export job.

METHOD

PATH

DESCRIPTION

POST

/v1/bulkfill/export-jobs

Create a Bulk Fill export job

GET

/v1/bulkfill/export-jobs/{job_id}

Read the current state of an export job

GET

/v1/bulkfill/export-jobs/{job_id}/download

Download a completed export job's output

POST

/v1/bulkfill/export-jobs

Create a Bulk Fill export job

GET

/v1/bulkfill/export-jobs/{job_id}

Read the current state of an export job

GET

/v1/bulkfill/export-jobs/{job_id}/download

Download a completed export job's output

Why Jentic?

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

Setup

Wiring Doqlo by hand means handling its Bearer auth, attaching the Idempotency-Key header on job creation, assembling the multipart upload of the PDF, config package, and CSV, and polling the job to completion yourself. Through Jentic you install once, import Doqlo from the API Directory, store the token once, and your agent calls it.

Permission scoping

Doqlo carries the job id in the URL path on the read and download operations, so a rule can pin your agent to creating and reading export jobs. You choose the operations it may call, so the agent only touches the export-job surface you grant.

Credential isolation

Your Doqlo token 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 'create a bulk fill export job' or 'download a completed export', and Jentic returns the matching Doqlo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Doqlo Bulk Fill Public API through Jentic.

What authentication does the Doqlo Bulk Fill API use?

The Doqlo Bulk Fill API authenticates with a Bearer token per its OpenAPI spec, sent in the Authorization header on every request, and job creation also requires an Idempotency-Key header. Through Jentic the token is stored once and injected at call time so it never enters the agent's prompt.

Can I fill one PDF template with many rows at once with the Doqlo API?

Yes. You submit a source PDF, a configuration package, and either inline rows or a CSV file to the create-export-job endpoint, set a maximum failed-row percentage, then poll the job and download the batch of filled documents when it completes.

What are the rate limits for the Doqlo Bulk Fill API?

The spec defines dedicated rate-limited and create-cooldown error responses but does not publish fixed numeric limits. Check the Doqlo documentation for the current per-plan limits and handle the cooldown response when creating jobs in quick succession.

Is there a Doqlo API MCP server?

You don't need an MCP server to give your agent the Doqlo Bulk Fill API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent creates, polls, and downloads export jobs on demand without loading another server's tool definitions into its context.

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

Yes. Write a rule that allows only the create-job and read-job operations, so the agent can submit fills and check their status but cannot reach anything outside the export-job surface, and every call it makes is logged.

How do I generate a batch of filled PDFs with the Doqlo API through Jentic?

Search Jentic for 'create a bulk fill export job', add the Doqlo API from the directory, and store your token once; your agent can then submit a job, poll it to completion, and redeem the download handle. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Doqlo Bulk Fill Public API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyStorageDocument Managementbearer3 EndpointsREST

For Agents

Create bulk PDF fill export jobs from a template and row data, track their progress, and download the finished documents when the job completes.

Use for: Create a bulk fill export job from my template and a CSV of rows, Check whether my export job has finished yet, Download the finished documents from a completed job, Fill one PDF template with many rows of data at once

Not supported: Does not sign documents, host a document library, or send email. Use for bulk PDF fill and export jobs only.

The Doqlo Bulk Fill API turns a source PDF, a reusable configuration package exported from the Bulk Fill editor, and a row-data input into a batch of filled documents through an export job. You submit the job with either inline rows or a CSV file and a required failure threshold, then poll the job until it finishes and redeem a download handle for the output. It is built for producing many filled PDFs from one template in a single asynchronous run.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

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

60%

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: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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: D+Signals: 4

81%

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.

16%

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

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Doqlo Bulk Fill Public API to your agent

Capabilities

Use Cases

Start building with Doqlo Bulk Fill Public API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Doqlo Bulk Fill Public API

Jentic AI Readiness Score

Doqlo Bulk Fill Public 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