Install Jentic One Beta

Connect the Kombo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kombo 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%2Fkombo.dev%2Fkombo" | 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%2Fkombo.dev%2Fkombo" | 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 Kombo API.

Read employees from a connected HRIS with filters such as employment_statuses, group_ids, legal_entity_ids, and updated_after

Request time off by creating an absence with employee_id, absence_type_id, start_date, end_date, and employee_note

Move an ATS application to a new stage_id, reject it with a rejection_reason_id, or add notes and attachments

Create a candidate or an application on a job in the connected ATS

GET STARTED

Start building with Kombo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Kombo API for, with concrete tasks.

★ AI agent HR workflows through Jentic

An HR assistant built into a SaaS product answers questions about a customer's workforce without knowing which HRIS they run. Through Jentic the agent searches for 'get employees', loads the Kombo employees operation with its input schema, and sends the X-Integration-Id for that customer. Your own Jentic One instance injects the Kombo API key at call time.

Call GET /hris/employees with the customer's X-Integration-Id header and employment_statuses 'ACTIVE', then summarise headcount by legal entity using GET /hris/legal-entities

Time off requests across HR systems

An employee asks an assistant to book leave. The agent reads absence types and the employee's time-off balances, then creates an absence with employee_id, absence_type_id, start_date, end_date, and employee_note, and Kombo writes it to whichever HRIS the integration connects.

Call GET /hris/absence-types and GET /hris/time-off-balances, then POST /hris/absences with employee_id, absence_type_id, start_date '2026-12-21', end_date '2026-12-24', and employee_note 'Holiday'

Recruiting pipeline actions

A recruiting tool reads applications and application stages from the connected ATS, moves a candidate forward by setting stage_id, schedules an interview, or rejects the application with a rejection_reason_id from the ATS's own list.

Call GET /ats/application-stages, then PUT /ats/applications/{application_id}/stage with the stage_id for 'Interview'

Customer onboarding with connection links

When a new customer signs up, the product creates a Kombo connection link that the customer uses to connect their HR or ATS tool. Once connected, the integration can be checked, re-linked, enabled or disabled, and forced to sync.

Call POST /connect/create-link for the new customer, then after they connect call POST /force-sync with their X-Integration-Id

Key Endpoints

128 endpoints — the kombo api gives one unified interface to the hris, ats, lms, and assessment tools your customers connect, so the same call reads employees or candidates from whichever system sits behind an integration.

METHOD

PATH

DESCRIPTION

GET

/hris/employees

Get employees

POST

/hris/absences

Create absence

GET

/hris/time-off-balances

Get time off balances

GET

/ats/applications

Get applications

PUT

/ats/applications/{application_id}/stage

Move application to stage

POST

/ats/candidates

Create candidate

POST

/lms/course-progressions

Enroll user in course

POST

/connect/create-link

Create connection link

GET

/hris/employees

Get employees

POST

/hris/absences

Create absence

GET

/hris/time-off-balances

Get time off balances

GET

/ats/applications

Get applications

PUT

/ats/applications/{application_id}/stage

Move application to stage

POST

/ats/candidates

Create candidate

POST

/lms/course-progressions

Enroll user in course

POST

/connect/create-link

Create connection link

Why Jentic?

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

Setup

Wiring Kombo by hand means picking the EU, US, or CA host, sending the bearer key plus an X-Integration-Id per customer, and paging through cursor results. Through Jentic you install once, import Kombo from the API Directory, store the key once, and your agent calls it.

Permission scoping

Kombo puts ids such as application_id and integration_id in the URL path (/ats/applications/{application_id}/stage, /integrations/{integration_id}), so a rule can pin your agent to one application or integration and the operations you pick. You choose the operations it may call, so destructive ones like deleting an integration or rejecting applications are not included unless you add them.

Credential isolation

Your Kombo 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 'get employees' or 'move an application to a stage', and Jentic returns the matching Kombo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Kombo API through Jentic.

What authentication does the Kombo API use?

The Kombo API authenticates with a bearer token per its OpenAPI spec: an API key created on the Secrets page of the Kombo dashboard, sent in the Authorization header. Most data operations also take an X-Integration-Id header naming the customer integration to act on. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

Which Kombo host should I call?

The spec lists three regional servers: https://api.kombo.dev/v1 for the EU, https://api.us.kombo.dev/v1 for the US, and https://api.ca.kombo.dev/v1 for Canada. Use the host for the region your Kombo environment lives in.

What are the rate limits for the Kombo API?

The OpenAPI spec does not specify rate limits. Check the Kombo documentation at https://docs.kombo.dev for current limits.

Is there a Kombo MCP server?

You don't need an MCP server to give your agent the Kombo API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the HRIS, ATS, and LMS operations on demand without loading another server's tool definitions into its context.

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

Yes. For example, write a rule that allows only GET /hris/employees, GET /hris/time-off-balances, and GET /ats/applications, so the agent can read workforce and recruiting data but cannot create absences, reject applications, or delete an integration. Every call it makes through your instance is logged.

How do I move a candidate to the next stage through Jentic?

Search Jentic for 'move an application to a stage', load the Kombo stage operation, read the available stage ids with GET /ats/application-stages, and call PUT /ats/applications/{application_id}/stage with the chosen stage_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What if a Kombo unified model does not cover a field I need?

Use POST /passthrough/{tool}/{api} to send a request straight to the connected tool's own API through Kombo, or map custom fields with PUT /integrations/{integration_id}/custom-fields/{custom_field_id} so they appear in the unified data.

Kombo API

AI ReadinessFoundational (C)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR recruitingEmployee Managementbearer128 EndpointsREST

For Agents

Read employees, absences, and payslips from connected HRIS tools, read and act on ATS candidates and applications, and enrol users in LMS courses through one unified Kombo API.

Use for: Get all active employees from our customer's HRIS, Check an employee's time off balance, Create an absence request for next week, Move this applicant to the interview stage

Not supported: Does not run payroll itself, host job boards, or store HR data as the system of record. Use for reading and writing HRIS, ATS, and LMS data in your customers' connected tools only.

The Kombo API gives one unified interface to the HRIS, ATS, LMS, and assessment tools your customers connect, so the same call reads employees or candidates from whichever system sits behind an integration. On the HRIS side it reads employees, employments, groups, locations, absences, time-off balances, timesheets, performance reviews, and payslips, and it can create absences or update employees. On the ATS side it reads jobs, candidates, applications, interviews, offers, and scorecards, and moves, rejects, or annotates applications; it also enrols LMS users in courses, manages connection links and integration field mappings, and offers a passthrough to the underlying tool's own API.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: DSignals: 4

75%

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).

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.

94%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

59%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

99%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

30%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A-Signals: 1

76%

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).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Kombo API to your agent

Capabilities

Start building with Kombo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Kombo API

Jentic AI Readiness Score

Kombo 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