Install Jentic One Beta

Connect the Koncile API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Koncile 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%2Fapi.koncile.ai%2Fkoncile" | 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%2Fapi.koncile.ai%2Fkoncile" | 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 Koncile API.

Upload invoices, pay slips, or contracts for automated data extraction

Retrieve the structured data extracted from a processed document

Define extraction templates and the fields captured from each document type

Add parsing instructions that guide how a field is extracted

Organize documents into folders and check extraction task results

GET STARTED

Start building with Koncile API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Koncile API for, with concrete tasks.

★ AI Document Processing Agent

An AI agent ingests incoming invoices or contracts, uploads each file to Koncile, waits for the extraction task, and reads back the structured fields to post into downstream systems. Through Jentic the agent discovers the upload and fetch operations by intent and calls them without hand-wiring the API, so document intake runs end to end.

Upload a PDF invoice, poll for the task result, and return the extracted total and line items

Invoice Data Extraction

Convert scanned or PDF invoices into structured data ready for accounting or ERP entry. Koncile parses each document against a template, and the fetch-document-data operation returns the captured fields once processing completes. This removes manual keying while keeping the mapping under your control through templates and fields.

Extract the invoice number, date, and total from an uploaded supplier invoice

Template and Field Configuration

Set up how a new document type is parsed by creating a template, adding the fields to capture, and attaching instructions that guide extraction. This lets teams onboard a new supplier or contract format without changing code, and keeps extraction consistent across every document routed to that template.

Create a template for supplier contracts and add a field that captures the renewal date

Key Endpoints

25 endpoints — the koncile api extracts structured data from documents such as invoices, pay slips, and contracts using configurable templates and fields.

METHOD

PATH

DESCRIPTION

POST

/v1/upload_file/

Upload a file for extraction

GET

/v1/fetch_document_data/

Fetch extracted document data

GET

/v1/fetch_tasks_results/

Fetch extraction task results

POST

/v1/create_template/

Create an extraction template

POST

/v1/create_field/

Add a field to a template

POST

/v1/upload_file/

Upload a file for extraction

GET

/v1/fetch_document_data/

Fetch extracted document data

GET

/v1/fetch_tasks_results/

Fetch extraction task results

POST

/v1/create_template/

Create an extraction template

POST

/v1/create_field/

Add a field to a template

Why Jentic?

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

Setup

Wiring the Koncile API by hand means handling its bearer-token auth, the upload then poll then fetch sequence, and the template setup yourself. Through Jentic you install once, import Koncile from the API Directory, store the token once, and your agent calls it.

Permission scoping

Koncile identifies folders, templates, and documents through query parameters and the request body, so rules bound which operations your agent may call, not which document it touches. You choose the operations it may call, so destructive ones like deleting a template or document are not included unless you add them.

Credential isolation

Your Koncile token 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 an invoice for extraction' or 'get extracted document data', and Jentic returns the matching Koncile operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Koncile API through Jentic.

What authentication does the Koncile API use?

The Koncile API authenticates with a bearer token in the Authorization header, per its OpenAPI spec. Through Jentic the token 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 extract data from an invoice with the Koncile API?

Yes. Upload the file with POST /v1/upload_file/, then call GET /v1/fetch_document_data/ once the extraction task completes to read the structured fields. The template you assign controls which fields are captured.

What are the rate limits for the Koncile API?

The OpenAPI spec does not specify rate limits. Check the Koncile documentation at https://api.koncile.ai/documentation for current limits before running large batch extraction jobs.

Is there a Koncile MCP server?

You don't need an MCP server to give your agent the Koncile API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the upload and extraction operations it needs.

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

Yes. Write a rule that allows only the upload and fetch-document-data operations, so the agent can submit files and read results but cannot delete templates or documents, and every call it makes is logged.

How do I extract document data with the Koncile API through Jentic?

Search Jentic for 'extract data from a document', and it returns the POST /v1/upload_file/ and GET /v1/fetch_document_data/ operations with their input schemas so your agent runs the extraction directly. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Koncile API

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentData Transformationbearer25 EndpointsREST

For Agents

Upload invoices, pay slips, and contracts for automated data extraction, then retrieve the structured results. Configure the templates, fields, and instructions that control how each document type is parsed.

Use for: Upload an invoice for data extraction, Get the extracted fields from a processed document, Create a template for a new document type, I need to add a field to an extraction template

Not supported: Does not handle accounting, payment processing, or document e-signature. Use for document data extraction only.

The Koncile API extracts structured data from documents such as invoices, pay slips, and contracts using configurable templates and fields. It uploads files for processing, returns the extracted document data once a task completes, and manages the folders, templates, fields, and instructions that control how each document type is parsed.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: C-Signals: 4

84%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

17%

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

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

48%

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: DSignals: 4

33%

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.

50%

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

60%

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.

Connect the Koncile API to your agent

Capabilities

Start building with Koncile API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Koncile API

Jentic AI Readiness Score

Koncile 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