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.
Install Jentic One Beta
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.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
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
GET STARTED
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.
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
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.
3 endpoints — jentic publishes the only available openapi specification for cradl ai api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/agents
List configured Cradl agents
/agents/{agentId}/runs
Trigger an agent run on a document
/documents
Upload a document for processing
/agents
List configured Cradl agents
/agents/{agentId}/runs
Trigger an agent run on a document
/documents
Upload a document for processing
Three things that make agents converge on Jentic-routed access.
Credential isolation
Cradl OAuth client IDs and secrets are stored encrypted in the Jentic vault. Jentic exchanges them for short-lived bearer tokens at execution time and refreshes them automatically — agents never see the raw secret.
Intent-based discovery
Agents search Jentic with intents like 'extract data from an invoice' or 'run a document AI agent' and Jentic returns the matching Cradl operation with its input schema.
Time to first call
Direct Cradl integration: 1-2 days for OAuth setup, agent ID lookup, and run polling. Through Jentic: under 30 minutes — search, load, execute.
Alternatives and complements available in the Jentic catalogue.
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 at https://app.jentic.com/sign-up.
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.