canonical: https://jentic.com/apis/chronary.ai/chronary # Chronary API 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. ## For AI 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. ## Scope Does not send email or SMS reminders, process payments, or host video calls. Use for managing calendars, events, availability, and scheduling only. ## Capabilities - List and create calendars and manage the events within them - Register agents and give each one its own calendars, events, and availability - 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 ## Use cases ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Search Jentic for 'create a calendar event', load the operation schema, and create the event with Jentic-injected credentials ## Key endpoints | 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` | Register an agent | ## Key resources - **Calendars** — List, create, read, update, and delete calendars, and read or set their availability - **Events** — Create, read, update, and delete events, including confirming and releasing held events - **Agents** — Register agents and manage each agent's calendars, events, and availability - **Scheduling** — Create booking pages and scheduling proposals and respond to, resolve, or cancel them ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 98 / 100 - Developer Experience & Jentic Compatibility: 70 / 100 - AI-Readiness & Agent Experience: 44 / 100 - Agent Usability: 84 / 100 - Security: 55 / 100 - AI Discoverability: 69 / 100 - **View full report:** https://jentic.com/apis/chronary.ai/chronary/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Calendly** — Hosted meeting scheduling for people, versus Chronary's calendar and scheduling surface built for agents. - **Nylas** — Connectivity to Google and Microsoft calendars that can sync alongside Chronary. - **Google Calendar** — Google's own calendar store, which Chronary can connect to as an external calendar. ## FAQ ### 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.