Install Jentic One Beta

Connect the Sage HR API to your agent

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

List employees

Get employee

Integrate Sage HR API into automated workflows

Query and filter Sage HR API records by parameters

Monitor Sage HR API operational status and events

GET STARTED

Start building with Sage HR API

Explore with Jentic One

View OpenAPI Document

Automated Employees Management

Automate employees operations by combining multiple Sage HR API endpoints. Agents can get employee and then list leave requests in a single workflow.

Call GET /employees/{id} to get employee, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sage HR API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'list employees', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

7 endpoints — sage hr (formerly cakehr) api for managing employees, leave requests, timesheets, and hr data.

METHOD

PATH

DESCRIPTION

GET

/employees

List employees

GET

/employees/{id}

Get employee

GET

/leave-requests

List leave requests

GET

/leave-requests/{id}

Get leave request

GET

/timesheets

List timesheets

GET

/teams

List teams

GET

/positions

List positions

GET

/employees

List employees

GET

/employees/{id}

Get employee

GET

/leave-requests

List leave requests

GET

/leave-requests/{id}

Get leave request

GET

/timesheets

List timesheets

GET

/teams

List teams

GET

/positions

List positions

Why Jentic?

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

Setup

Wiring the Sage HR API by hand means managing its API key, attaching it to each call against api.sage.hr, and handling your own retries. Through Jentic you install once, import the Sage HR API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Sage HR puts the employee id in the URL path (/employees/{id}), so a rule can pin your agent to reading one employee. You choose the operations it may call, so it can read employees, leave requests, and timesheets without any write access unless you add it.

Credential isolation

Your Sage HR 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 'list employees' or 'look up leave requests', and Jentic returns the matching Sage HR API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sage HR API through Jentic.

What authentication does the Sage HR API use?

The Sage HR API uses an API key passed in the `X-Auth-Token` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I list employees with the Sage HR API?

Yes. Use the GET /employees endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Sage HR API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I list employees through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list employees'. Jentic returns the matching Sage HR API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Sage HR API have?

The Sage HR API exposes 7 endpoints covering employees, leave, organization operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sage HR operations and credentials the agent may use. Since Sage HR carries the employee id in the URL path (/employees/{id}), you can pin the agent to reading a single employee, and you can grant only read calls such as GET /employees, GET /leave-requests, and GET /timesheets while withholding any write access. The agent can call nothing you have not explicitly allowed.

Sage HR API

Name: Sage HR API
Brand: Sage HR API
Availability: InStock

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyHR recruitingEmployee ManagementapiKey7 EndpointsREST

For Agents

Programmatically list employees, get employee. Covers 7 operations with apiKey authentication.

Use for: I need to employees, I want to employee, Search for leave requests, Find all leave request

Not supported: Does not handle payments, communications, or crm - use for hr and recruiting only.

Sage HR (formerly CakeHR) API for managing employees, leave requests, timesheets, and HR data. The API exposes 7 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 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).

50%

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.

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

38%

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

50%

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 Sage HR API to your agent

Capabilities

Start building with Sage HR API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sage HR API

Jentic AI Readiness Score

Sage HR 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