Agent-ready OpenAPI document · curated by JenticStorageDocument Managementbearer, oauth271 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Manage documents and folders in a secure data room: upload, download, copy, and move files, generate one-click share links, and ask natural-language questions about a document.
Use for: Upload a new document to a folder, Download a document by its id, Generate a one-click download link for a document, Ask a question about the contents of a document
Not supported: Does not handle e-signatures, payment processing, or email campaigns. Use for managing documents, folders, and secure download links in a data room only.
Jentic publishes the only available OpenAPI specification for the Docurex API, keeping it validated and agent-ready. The Docurex API manages documents and folders in a secure data room. It uploads, updates, downloads, copies, and moves documents, organizes them into folders, and generates one-click download links to share them. It also answers natural-language questions about a document, manages users and contacts, and configures folder notifications and exports.
Install Jentic One Beta
Connect the Docurex API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Docurex 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%2Fdocurex.com%2Fdocurex" | 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%2Fdocurex.com%2Fdocurex" | 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 Docurex API.
List, upload, update, and download documents in a data room
Organize documents into folders and copy or move them between folders
Generate one-click download links and send them to recipients
Ask a natural-language question about a document and get an answer
Manage users, contacts, and shortcuts in the data room
Configure folder notifications and export a folder's document list to Excel
Use Cases
Patterns agents use Docurex API for, with concrete tasks.
★ Agent-Managed Data Room
An AI agent handling due-diligence or deal documents can upload files, organize them into folders, and generate secure download links through the Docurex API. Because folders and documents are addressable by id, the agent keeps a data room organized without a user clicking through the web interface.
Upload a document to a folder, then generate a one-click download link and send it to a recipient
Document Question Answering
Review workflows can ask natural-language questions about a stored document using the Docurex API's document AI operation. The agent sends the question and receives an answer grounded in that document, so a reviewer gets a direct answer without reading the whole file.
Ask a question about a specific document and return the answer
Folder Organization and Export
Administrators can build and maintain folder structures, copy or move folders, and export a folder's document list to Excel with the Docurex API. This supports keeping large document sets organized and auditable.
Create a folder structure, move a set of documents into it, and export the folder's document list to Excel
Key Endpoints
71 endpoints — jentic publishes the only available openapi specification for the docurex api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/document
Get document collection
POST
/document
Add a new document
GET
/document/{document_id}/download
Download a document
POST
/document/{document_id}/ai
Ask a question on a document
POST
/document/link
Generate a one-click download link
GET
/folder
Get folder collection
POST
/folder/{folder_id}/move
Move a folder
GET
/folder/{folder_id}/download
Download a folder as a zip file
GET
/document
Get document collection
POST
/document
Add a new document
GET
/document/{document_id}/download
Download a document
POST
/document/{document_id}/ai
Ask a question on a document
POST
/document/link
Generate a one-click download link
GET
/folder
Get folder collection
POST
/folder/{folder_id}/move
Move a folder
GET
/folder/{folder_id}/download
Download a folder as a zip file
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
docurex 3 RestApi v2.0
- Foundational (C+)58/100
47
Foundational Compliance58
Developer Experience & Jentic Compatibility55
AI-Readiness & Agent Experience91
Agent Usability53
Security56
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
47
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
88%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
15%
Example Density
How richly the API is illustrated with examples.
68%
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.
55
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: CSignals: 4
62%
Description Coverage
Coverage of descriptions across API elements.
99%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
60%
Summary Coverage
Coverage of summaries across operations/tags/info.
91
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
91%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
53
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
53%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
56
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
56%
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 the Docurex API by hand means managing its JWT bearer token or OAuth 2.0 flow and juggling document, folder, link, and user operations across a large surface. Through Jentic you install once, import the Docurex API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The Docurex API puts the document and folder ids in the URL path, such as /folder/{folder_id}, so a rule can pin your agent to specific folders or documents. You choose which operations it may call, so it can read and download documents while deletion of documents, folders, and users stays out unless you add it.
Credential isolation
Your Docurex credential 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 'upload a document' or 'generate a download link', and Jentic returns the matching Docurex operation with its input schema so the agent calls the right endpoint without reading the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Docurex API through Jentic.
Why is there no official OpenAPI spec for the Docurex API?
Docurex does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Docurex API via structured tooling. It is validated against the live API and kept up to date. To run it on your own infrastructure, install Jentic One from its GitHub repo.
What authentication does the Docurex API use?
The Docurex API accepts a bearer token in the Authorization header, which uses the JWT format, and also supports an OAuth 2.0 flow, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.
Can I generate a download link with the Docurex API?
Yes. The Docurex API generates one-click download links for a document and sends them to recipients, and you can list and update the links you own. It also downloads documents directly and exports folders as zip files.
What are the rate limits for the Docurex API?
The OpenAPI spec does not specify rate limits for the Docurex API. Check the provider's documentation at https://docurex.com for the current limits that apply to your account.
Can I limit what my agent is allowed to do with the Docurex API?
Yes. Document and folder ids travel in the URL path, so a rule can pin your agent to specific folders or documents. Write a rule that allows only the read and download operations, so the agent can retrieve and share documents while deletion of documents, folders, and users stays out unless you add it, and every call it makes is logged.
How do I upload and share a document with the Docurex API through Jentic?
Search Jentic for 'upload a document to a data room' and it returns the matching Docurex operation with its input schema. Import the Docurex API from the Jentic API Directory, store your token once, and your agent can upload a file, place it in a folder, and generate a download link without hand-wiring the token on each request.
Is there a Docurex API MCP server?
You don't need an MCP server to give your agent the Docurex API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent calls the document, folder, and link operations. Nothing extra loads into the agent's context until an operation is actually used.
GET STARTED