DocumentPro API
51
AI ReadinessFoundational (C-)51/100
Official vendor OpenAPI document · agent-readyAI/MLVisionapiKey19 EndpointsREST
For Agents
Upload documents, run AI extraction Workflows, and classify documents by type with DocumentPro, managing reusable Workflows and Classifiers and polling job results.
Use for: Upload a document for extraction, Run an extraction Workflow on a document, I need to classify a document by type, Create a new extraction Workflow
Not supported: Does not handle document generation, e-signatures, or long-term file storage. Use for AI document data extraction and classification only.
The DocumentPro API uploads documents, runs AI extraction Workflows against them, and classifies documents by type. It uploads a file or requests a pre-signed upload URL for large files, runs a saved Workflow to pull structured data, and polls the extraction job for its result. Workflows and Classifiers are created, updated, and deleted as reusable templates, and a document can be classified inline or with a saved Classifier.
Install Jentic One Beta
Connect the DocumentPro API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DocumentPro 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.
1
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%2Fdocumentpro.ai%2Fdocumentpro" | sh2
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%2Fdocumentpro.ai%2Fdocumentpro" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 DocumentPro API.
Upload a document or request a pre-signed upload URL for large files
Run a saved extraction Workflow against a document and poll for its result
Create, update, and delete extraction Workflows
Classify a document inline or with a saved Classifier
Create, update, and delete Classifiers for document types
List and retrieve uploaded documents
Use Cases
Patterns agents use DocumentPro API for, with concrete tasks.
★ Agent Data Extraction
An AI agent connected through Jentic uploads a document, runs the right extraction Workflow, and polls until the structured data is ready. The DocumentPro API exposes the upload, run-Workflow, and result operations the agent needs, and Jentic injects the API key at call time so the agent never holds it.
Upload an invoice, run its extraction Workflow, and poll the job until the extracted fields are returned
Document Classification
Teams that receive mixed document types sort them before processing. The DocumentPro API classifies a document inline or with a saved Classifier, so an agent can route each file to the correct downstream Workflow.
Classify an uploaded document with a saved Classifier and route it to the matching extraction Workflow
Reusable Extraction Workflows
Recurring document formats are handled by saved Workflows rather than one-off prompts. The DocumentPro API creates, updates, and lists Workflows and Classifiers, so an agent can maintain the extraction logic for each document type.
Create a new extraction Workflow for purchase orders and list the account's existing Workflows
Key Endpoints
19 endpoints — the documentpro api uploads documents, runs ai extraction workflows against them, and classifies documents by type.
METHOD
PATH
DESCRIPTION
POST
/v1/documents
Upload a document
GET
/v1/documents/{document_id}/run_parser
Run a Workflow against a document
GET
/files
Poll an extraction job's result
POST
/v1/templates
Create a Workflow
GET
/v1/templates
List Workflows
POST
/v1/classify
Classify a document inline
POST
/v1/classifiers
Create a Classifier
POST
/v1/classifiers/{classifier_id}/classify
Run a saved Classifier against a document
POST
/v1/documents
Upload a document
GET
/v1/documents/{document_id}/run_parser
Run a Workflow against a document
GET
/files
Poll an extraction job's result
POST
/v1/templates
Create a Workflow
GET
/v1/templates
List Workflows
POST
/v1/classify
Classify a document inline
POST
/v1/classifiers
Create a Classifier
POST
/v1/classifiers/{classifier_id}/classify
Run a saved Classifier against a document
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
D
DocumentPro API
- Foundational (C-)51/100
87
Foundational Compliance70
Developer Experience & Jentic Compatibility26
AI-Readiness & Agent Experience94
Agent Usability50
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
87
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 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).
50%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
70
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
5%
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.
26
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
41%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
63%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
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).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring DocumentPro by hand means managing its `x-api-key` header, requesting pre-signed upload URLs for large files, and polling extraction jobs yourself. Through Jentic you install once, import DocumentPro from the API Directory, store the key once, and your agent calls it.
Permission scoping
DocumentPro puts ids like the document id and template id in the URL path, so a rule can bound the agent to read paths and specific operations. Limit the agent to the operations it needs, such as uploading documents and running Workflows, so destructive operations like deleting a Workflow or a Classifier are not included unless you add them.
Credential isolation
Your DocumentPro 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 'extract data from a document' or 'classify a document', and Jentic returns the matching DocumentPro operation with its input schema so the agent calls the right endpoint directly.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using DocumentPro API through Jentic.
What authentication does the DocumentPro API use?
The DocumentPro API authenticates with an API key sent in the `x-api-key` request header, per its OpenAPI spec. Create the key in your DocumentPro account and send it on every call. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's prompt or logs.
Can I extract and classify documents with the DocumentPro API?
Yes. Upload a document, run a saved extraction Workflow to pull structured data, and poll the job for its result. You can also classify a document inline or with a saved Classifier, and manage both Workflows and Classifiers as reusable templates.
Is there a DocumentPro MCP server?
You don't need an MCP server to give your agent the DocumentPro API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the upload, extraction, and classification operations. Operations load on demand, so your agent's context stays lean instead of holding another server's tool definitions.
Can I limit what my agent is allowed to do with the DocumentPro API?
Yes. Write a rule that allows only the upload, run-Workflow, and poll-result operations, so the agent can extract data but cannot delete a Workflow or a Classifier. Every call the agent makes is logged.
What are the rate limits for the DocumentPro API?
The OpenAPI spec does not specify rate limits. Check the DocumentPro documentation at https://docs.documentpro.ai for current limits before running a large extraction batch.
How do I extract data from a document with the DocumentPro API through Jentic?
Search Jentic for an intent like 'run an extraction workflow', add the DocumentPro API from the directory, and store your API key once. Your agent then uploads the document, runs the Workflow, and polls for the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED