Skip to content
Chronary Docs

Changelog

v1.0 — Public Beta Launch

Section titled “v1.0 — Public Beta Launch”

April 4, 2026

The initial public beta of Chronary, a calendar-as-a-service platform purpose-built for AI agents.

Core API

Section titled “Core API”
  • Agent CRUD — Create, read, update, delete, and list agents with agt_ prefixed IDs
  • Calendar CRUD — Full lifecycle management for calendars (cal_ IDs), linked to agents
  • Event CRUD — Create, read, update, delete, and list events (evt_ IDs) with support for single and recurring events
  • Availability engine — Query free/busy slots across one or more agents with configurable duration, buffer times, and working hours
  • Usage endpoint — GET /v1/usage returns current consumption against plan limits

Integrations

Section titled “Integrations”
  • iCal feeds — Generate read-only iCal feed URLs for any calendar, consumable by Google Calendar, Apple Calendar, Outlook, and other calendar apps
  • iCal subscriptions — Subscribe calendars to external iCal URLs; events sync automatically on a recurring schedule
  • Webhooks — Subscribe to calendar and event lifecycle events with HMAC-SHA256 signed payloads and automatic retry with exponential backoff
  • MCP server — Model Context Protocol server exposing 9 tools, sharing the same Worker and service layer as the REST API

Platform

Section titled “Platform”
  • API key authentication — Keys use chr_sk_live_ and chr_sk_test_ prefixes with full environment isolation between live and test modes
  • Rate limiting — 10 requests per second per key with Retry-After headers
  • Monthly quotas — Plan-based limits on agents, calendars, events, API calls, webhook deliveries, and availability queries
  • Console dashboard — Web UI at console.chronary.ai for account management, API key generation, and usage monitoring
  • Structured error handling — Consistent error response format with machine-readable type field and request_id on every response for debugging

Infrastructure

Section titled “Infrastructure”
  • Cloudflare Workers — API deployed globally on the Cloudflare Workers runtime for low-latency responses
  • Neon PostgreSQL — Serverless Postgres with connection pooling for the primary data store
  • Better Stack observability — Structured logging and uptime monitoring
  • Test coverage — 327 tests with 90%+ line, branch, function, and statement coverage