Install Jentic One Beta

Connect the DigiParser Agent API to your agent

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

List the parsers and classifiers available to your API key

Upload documents to a parser to extract structured data

Send uploads to a classifier to categorize documents

Process a batch of files in a single upload request

Invoke a DigiParser tool operation for an agent workflow

GET STARTED

Start building with DigiParser Agent API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DigiParser Agent API for, with concrete tasks.

★ Automated Document Extraction

An AI agent turns incoming documents into structured data: it lists the parsers available to its key, picks the one that matches the document type, and uploads the files for extraction. The agent discovers the list and upload operations through Jentic by intent, so it extracts data without hardcoding endpoint paths.

List the available parsers, choose the one matching the document, and upload the files to extract the structured fields

Document Classification

A document pipeline needs to sort incoming files before processing. The agent uploads files to a classifier, which routes each document to its category so the right parser can run next. DigiParser handles the classification server-side, so the agent only submits the files.

Upload a batch of files to a classifier and return the category assigned to each document

Parser Discovery

Before processing, an agent confirms which parsers its API key can use so it selects a valid one. It lists the parsers and classifiers tied to the key and matches them to the task at hand. This read-only step keeps the agent from uploading to a parser it cannot access.

List the parsers and classifiers available to the API key and return the one that matches a given document type

Key Endpoints

3 endpoints — the digiparser api extracts structured data from documents by routing uploaded files through configured parsers and classifiers.

METHOD

PATH

DESCRIPTION

GET

/api/v1/parsers

List parsers available to an API key

POST

/api/v1/process/files

Upload files to a parser or classifier

POST

/mcp

Call a DigiParser tool operation

GET

/api/v1/parsers

List parsers available to an API key

POST

/api/v1/process/files

Upload files to a parser or classifier

POST

/mcp

Call a DigiParser tool operation

Why Jentic?

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

Setup

Wiring DigiParser by hand means issuing an API key, sending it as a bearer token in the Authorization header, and selecting the right parser before uploading files. Through Jentic you install once, import DigiParser from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which DigiParser operations your agent may call, so you can allow listing parsers and uploading documents for extraction while leaving other operations out unless you add them. That keeps the agent to the parse-and-extract path you intend.

Credential isolation

Your DigiParser 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 list available parsers or extract data from a document, and Jentic returns the matching DigiParser operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using DigiParser Agent API through Jentic.

What authentication does the DigiParser API use?

The DigiParser API authenticates with an API key sent as a bearer token in the Authorization header, and its spec also declares an OAuth2 authorization-code flow for signed-in agent access. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never lands in the agent's prompt or logs.

Can I extract structured data from documents with the DigiParser API?

Yes. List the parsers available to your key, then upload files to the parser that matches the document type and read back the extracted fields. A classifier can categorize documents first so the right parser runs.

What are the rate limits for the DigiParser API?

The OpenAPI spec does not publish rate limits for the DigiParser API. Check DigiParser's REST API documentation for the current limits that apply to your key and plan.

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

Yes. Write a rule that allows only listing parsers and uploading documents for extraction, so the agent can parse files while other operations stay out unless you add them. Every call the agent makes is logged.

How do I extract data from a document with the DigiParser API through Jentic?

Search Jentic for an intent like extract data from a document, store your DigiParser key once, and your agent lists the parsers and uploads the files to the matching one. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a DigiParser MCP server?

Yes, DigiParser offers an MCP server. You can also connect the DigiParser REST API directly through Jentic: your agent gets the API's operations without loading another server's tool definitions into its context, your key is injected at call time by your self-hosted instance, and your rules decide which operations the agent may call.

DigiParser Agent API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData TransformationapiKey, oauth23 EndpointsREST

For Agents

List parsers, upload documents to a parser or classifier, and extract structured data through DigiParser. Route files to the right parser and retrieve the parsed fields.

Use for: List the parsers available to my API key, Upload a document to a parser for extraction, Extract structured data from an invoice, Classify a batch of uploaded documents

Not supported: Does not handle document storage, e-signatures, or spreadsheet generation. Use for parsing documents into structured data only.

The DigiParser API extracts structured data from documents by routing uploaded files through configured parsers and classifiers. An agent lists the parsers available to its API key, uploads files to a chosen parser or classifier, and gets back the extracted fields. A tool endpoint exposes the same actions for signed-in agent workflows.

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

42%

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

12%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

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

46%

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.

43%

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

70%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DigiParser Agent API to your agent

Capabilities

Start building with DigiParser Agent API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

DigiParser Agent API

Jentic AI Readiness Score

DigiParser Agent 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