Install Jentic One Beta

Connect the Chronary API to your agent

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

List and create calendars and manage the events within them

Read calendar and cross-agent availability and set availability rules

Create booking pages and scheduling proposals, and respond to or resolve a proposal

Manage webhooks and iCal subscriptions that track calendar changes

GET STARTED

Start building with Chronary API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Chronary API for, with concrete tasks.

★ Agent Calendar Management

Give an AI agent its own calendar to run. The agent registers, creates a calendar, and creates, lists, and updates events within it, then reads availability before booking. Because each agent gets its own calendars and events, several agents can keep separate schedules under one account.

Create a calendar, then create an event in it and read the calendar's availability

Booking Pages and Proposals

Coordinate a meeting time without a back-and-forth thread. The agent creates a booking page or a scheduling proposal, participants respond, and the agent resolves or cancels the proposal once a slot is agreed. Available booking slots are read first so the agent only offers times that are free.

Create a scheduling proposal, read its responses, and resolve it to a confirmed slot

AI Agent Integration via Jentic

An AI agent discovers and calls Chronary through Jentic without handling the API key directly. The agent searches by intent, receives the matching operation and its input schema, and creates events or availability while Jentic injects the stored key. This lets the agent manage a calendar without reading the reference docs or holding secrets.

Search Jentic for 'create a calendar event', load the operation schema, and create the event with Jentic-injected credentials

Key Endpoints

101 endpoints — the chronary api provides calendars, events, availability, and scheduling for ai and human agents.

METHOD

PATH

DESCRIPTION

GET

/v1/calendars

List calendars

POST

/v1/calendars

Create a calendar

POST

/v1/calendars/{cal_id}/events

Create an event in a calendar

GET

/v1/calendars/{id}/availability

Get calendar availability

POST

/v1/scheduling/proposals

Create a scheduling proposal

POST

/v1/agents

GET

/v1/calendars

List calendars

POST

/v1/calendars

Create a calendar

POST

/v1/calendars/{cal_id}/events

Create an event in a calendar

GET

/v1/calendars/{id}/availability

Get calendar availability

POST

/v1/scheduling/proposals

Create a scheduling proposal

POST

/v1/agents

Why Jentic?

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

Setup

Wiring Chronary by hand means creating an API key, sending it as a Bearer token on api.chronary.ai, and tracking which endpoints take the key versus a console session yourself. Through Jentic you install once, import Chronary from the API Directory, store the key once, and your agent calls it.

Permission scoping

Chronary puts the calendar id in the URL path, so a rule can pin your agent to one calendar and the operations you pick, such as listing and creating events, while leaving calendar deletion and API-key management out of the set.

Credential isolation

Your Chronary 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 'create a calendar event' or 'read availability', and Jentic returns the matching Chronary operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Chronary API through Jentic.

What authentication does the Chronary API use?

The Chronary API authenticates most operations with an API key sent as a Bearer token in the Authorization header, per its OpenAPI spec; console-only endpoints use a separate signed-in session cookie instead. Some endpoints, such as listing plans and the hosted booking pages, need no credential. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never reaches the agent.

Is there a Chronary MCP server?

You do not need a separate MCP server to give your agent Chronary. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls its calendar and scheduling operations on demand. Operations are discovered as needed, so no extra server's tool definitions load into the agent's context.

Can I create and book calendar events with the Chronary API?

Yes. Create a calendar, create events within it, and read the calendar's availability before booking. For coordinated scheduling, create a booking page or a scheduling proposal and resolve it once a slot is agreed.

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

Yes. Chronary puts the calendar id in the URL path, so with Jentic you can pin the agent to one calendar and allow only the operations it needs, such as listing and creating events, while withholding destructive ones like calendar deletion. Because you run Jentic One yourself, its actions are recorded in your own audit log.

What are the rate limits for the Chronary API?

The spec documents a limit of 10 requests per second per API key, with monthly operation quotas that vary by plan. Read your current usage on the usage operation, or see the Chronary documentation at https://docs.chronary.ai for the per-plan quotas.

How do I create a calendar event with the Chronary API through Jentic?

Search Jentic for 'create a calendar event' to get the matching Chronary operation and its input schema, then your agent creates the event in the chosen calendar. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Chronary API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyProductivityCalendar Schedulingbearer, apiKey101 EndpointsREST

For Agents

Create calendars and events, read and set availability, and run booking pages and scheduling proposals for agents, across 101 endpoints secured with a bearer API key.

Use for: Create a new calendar for my agent, I need to book an event on a calendar, Get a calendar's availability for next week, List all events in a calendar

Not supported: Does not send email or SMS reminders, process payments, or host video calls. Use for managing calendars, events, availability, and scheduling only.

The Chronary API provides calendars, events, availability, and scheduling for AI and human agents. It lists and creates calendars, manages the events within them, reads calendar and cross-agent availability, and sets availability rules. It registers agents and gives each one its own calendars, events, and iCal subscriptions, and it creates booking pages and scheduling proposals that participants respond to or resolve. Webhooks, iCal subscriptions, external calendar connections, and an audit log round out the surface.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

94%

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.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: A-Signals: 4

16%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

65%

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

30%

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.

47%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

84%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: CSignals: 1

55%

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

69%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Chronary API to your agent

Capabilities

Start building with Chronary API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Chronary API

Jentic AI Readiness Score

Chronary 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