← Back to search
70
Agent Ready
Agentic Readiness Score
+25 llms.txt +20 OpenAPI missing +20 ai-plugin
data apimcpllms-txtopenapi

Agentic Signals

📄
Found
🤖
ai-plugin.json
Not found
📖
OpenAPI Spec
Found
🔗
Structured API
Found
🛡
Not specified
🏷
Schema.org Markup
Not found
MCP Server
Found

Embed this badge

Show off your agentic readiness — the badge auto-updates when your score changes.

Agentic Ready 70/100

            

llms.txt Content

# Chronary > Calendar-as-a-service API for AI agents. Manage calendars, schedule events, check availability, and sync external calendars. Chronary provides a REST API and MCP server that let AI agents own calendars, create events, query combined Chronary + authorized human availability, request Google/Microsoft setup links, optionally publish events, subscribe to iCal feeds, and receive webhooks. Base URL: `https://api.chronary.ai` OpenAPI spec: `https://api.chronary.ai/openapi.json` Authentication: `Authorization: Bearer chr_sk_...` ## Getting Started - [Overview](https://docs.chronary.ai/getting-started/overview/): Key concepts — agents, calendars, events, availability - [Quickstart](https://docs.chronary.ai/getting-started/quickstart/): Register your first agent and create a calendar in minutes - [Authentication](https://docs.chronary.ai/getting-started/authentication/): API key setup ## API Reference - [Agents](https://docs.chronary.ai/api-reference/agents/): CRUD for AI, human, and resource agents (`agt_` prefix IDs) - [Calendars](https://docs.chronary.ai/api-reference/calendars/): Agent-owned and shared calendars (`cal_` prefix IDs), `agent_status` field (`idle`/`working`/`waiting`/`error`), `default_reminders` (reminder offsets events inherit), and `GET /v1/calendars/:id/context` for current/upcoming temporal context - [Booking Pages](https://docs.chronary.ai/guides/booking-pages/): Agent-created public scheduling links (`bkp_` prefix IDs). `POST /v1/booking-pages` returns a hosted `booking_url` (`https://api.chronary.ai/book/:slug`); a human picks a slot, a confirmed event lands on the calendar, and `event.created` fires with a `booking_page_id` field. Public (no-auth) `GET /book/:slug/slots` + `POST /book/:slug`. Free: 1 page; Pro: 25 - [Events](https://docs.chronary.ai/api-reference/events/): Calendar events with title, start/end time, status, and `reminders` (minutes before start; inherit calendar `default_reminders`, fall back to `[10]`) firing

OpenAPI Spec (preview)

{"openapi":"3.1.0","info":{"title":"Chronary API","version":"1.0.0","description":"Calendar-as-a-service API for AI agents.\n\nManage calendars, events, and availability for AI and human agents.\nAll endpoints require an API key passed as a Bearer token.\n\n**Authentication:** `Authorization: Bearer chr_sk_...` or `Authorization: Bearer chr_ak_...`\n\n**Rate limit:** 10 requests/second per API key. Exceeds return HTTP 429.\n\n**Quotas:** Monthly operation limits by plan — see [Quotas](https://