Agent-ready OpenAPI document · curated by JenticAI/MLMl Inferenceoauth23 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Trigger document-processing agents on Cradl AI to extract structured data from invoices, receipts, and forms. Use when an agent needs human-in-the-loop document automation rather than raw OCR.
Use for: Run a Cradl agent on this scanned invoice, Extract line items from a purchase order PDF, List the document-processing agents in my Cradl workspace, Upload a batch of receipts to Cradl for processing
Not supported: Does not handle raw image OCR without an agent context, document storage as a CMS, or e-signature workflows - use for AI document extraction with configured agents only.
Jentic publishes the only available OpenAPI specification for Cradl AI API, keeping it validated and agent-ready. Cradl AI lets teams build AI agents that automate document-heavy workflows such as invoice ingestion, purchase order processing, and KYC document review. The API exposes operations for listing configured agents, kicking off a run by submitting a document, and creating documents in the platform for downstream extraction. Authentication is via OAuth 2.0 client credentials and the production base URL is api.cradl.ai/v1.
Install Jentic One Beta
Connect the Cradl AI API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cradl AI 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%2Fcradl.ai%2Fcradl" | 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%2Fcradl.ai%2Fcradl" | 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 Cradl AI API.
List configured Cradl document-processing agents available in the workspace
Submit a document run to a specific agent and receive structured extracted fields
Upload documents into Cradl for downstream extraction or training data collection
Authenticate via OAuth 2.0 client credentials with scoped service-to-service tokens
Combine automated extraction with human-in-the-loop review for low-confidence fields
Use Cases
Patterns agents use Cradl AI API for, with concrete tasks.
★ Invoice Automation for Accounts Payable
An accounts payable team automates invoice intake by submitting each incoming PDF to a Cradl invoice agent. POST /agents/{agentId}/runs returns the extracted vendor, total, line items, and tax amounts as structured JSON. Low-confidence fields are routed to a human reviewer through Cradl's UI before posting to the ERP. This removes manual data entry while keeping a control point for edge cases.
Submit invoice 'INV-7782.pdf' to agent 'invoice-eu' via POST /agents/{agentId}/runs and route any field with confidence below 0.85 to the AP reviewer queue.
KYC Document Review
A fintech onboarding flow uses Cradl to extract identity fields from passports, utility bills, and proof-of-address documents. POST /documents uploads each scan and POST /agents/{agentId}/runs triggers the KYC agent that returns name, date of birth, and address. Human-in-the-loop review handles ambiguous cases before the customer is approved. This shortens onboarding without weakening compliance.
Upload passport scan via POST /documents, then run the KYC agent and capture name, dob, and address fields with their confidence scores.
Purchase Order Matching Pipeline
A procurement system runs incoming purchase order PDFs through a Cradl agent to extract item codes, quantities, and prices, then matches against existing supplier catalogues. The structured output feeds straight into the ERP without staff retyping. Cradl's training-on-corrections improves accuracy as more orders flow through.
POST the new PO PDF to /documents, then trigger agent 'po-extractor' and return a list of {sku, qty, unit_price} objects to the ERP integration.
Agent-Driven Document Workflow
An AI agent in a finance team's chat workflow accepts dropped PDFs from users, sends each to the right Cradl agent based on document type, and returns the extracted fields back into the conversation. Through Jentic, the agent finds the Cradl operation by intent and uses scoped OAuth tokens that it never sees in plain text.
Search Jentic for 'run cradl document agent', list agents via GET /agents to pick the right one, then POST /agents/{agentId}/runs with the user's uploaded PDF.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for cradl ai api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
GET
/agents
List configured Cradl agents
POST
/agents/{agentId}/runs
Trigger an agent run on a document
POST
/documents
Upload a document for processing
GET
/agents
List configured Cradl agents
POST
/agents/{agentId}/runs
Trigger an agent run on a document
POST
/documents
Upload a document for processing
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.
C
Cradl AI API
- AI-Aware (A-)72/100
100
Foundational Compliance56
Developer Experience & Jentic Compatibility53
AI-Readiness & Agent Experience94
Agent Usability85
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
56
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
53
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: C-Signals: 4
61%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
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.
85
Security
Trust, risk posture, and security compliance.
Grade: ASignals: 1
85%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
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 Cradl AI by hand means running its OAuth2 client-credentials exchange against auth.cradl.ai, passing the correct audience, and refreshing the short-lived bearer before every batch of document runs. Through Jentic you install once, import Cradl AI from the API Directory, store the client id and secret once, and your agent calls it.
Permission scoping
Cradl puts the agent id in the URL path (/agents/{agentId}/runs), so a rule can pin your agent to one Cradl document-processing agent and nothing else. You choose the operations it may call, so it can list agents and start runs only if you include those operations.
Credential isolation
Your Cradl client id and secret are stored once, encrypted, by your own Jentic One instance and exchanged for short-lived tokens at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'extract data from an invoice' or 'run a document AI agent', and Jentic returns the matching Cradl operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Cradl AI API through Jentic.
Why is there no official OpenAPI spec for Cradl AI API?
Cradl AI does not publish an OpenAPI specification on a public docs site. Jentic generates and maintains this spec so that AI agents and developers can call Cradl AI API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Cradl AI API use?
Cradl uses OAuth 2.0 client credentials. Service-to-service integrations exchange a client ID and secret for a bearer token, which is then sent as the Authorization header on each call. Through Jentic, credentials are stored encrypted and tokens are minted and refreshed automatically.
Can I extract invoice line items with the Cradl AI API?
Yes. POST /agents/{agentId}/runs against an invoice agent returns line items along with totals, vendor details, and tax. Low-confidence fields can be flagged for human-in-the-loop review in the Cradl UI before posting downstream.
How do I trigger a Cradl agent through Jentic?
Search Jentic for 'run a cradl document agent', call GET /agents to find the right agent ID, then POST /agents/{agentId}/runs with the document reference. Jentic handles the OAuth bearer token end to end.
What are the rate limits for the Cradl AI API?
The OpenAPI spec does not declare numeric rate limits. Cradl enforces fair-use limits in production tied to the workspace's plan. Agents should serialise heavy batch runs and back off on 429 responses.
Is Cradl AI free?
Cradl offers paid plans based on document volume and seats. There is typically a free trial; check cradl.ai for current pricing tiers. The API itself does not charge extra over the workspace plan.
Can I limit what my agent is allowed to do with the Cradl AI API?
Yes. Because Jentic One is self-hosted, your own rules decide which Cradl operations the agent may call, so you can allow it to list agents with GET /agents and start runs with POST /agents/{agentId}/runs while blocking anything else. Since Cradl puts the agent id in the URL path, a rule can pin the agent to a single Cradl document-processing agent and no other. Your OAuth client id and secret stay under your control and are exchanged for short-lived tokens at execution time, never entering the agent's prompt or logs.
GET STARTED