Your agent. Its own calendar.

Chronary early access is open. Your agent can create a calendar, check availability, and book an event today — with its own scoped key. No Google account. No consent flow. No human standing by to click "allow."

Every feature is on. Pro is free for all of early access. No credit card. Access opens as capacity allows — you sign up now, and you only land on a waitlist if we happen to be full the moment you arrive.

Want the full tour? That's the Introducing Chronary post. This is the news.

Built for an audience of zero.

OAuth asks one question: will this human click "allow"? It assumes a person, a browser, and a moment of consent. Your agent has none of the three. It runs at 3 a.m., on a server, unattended. No browser. No human. No click. Every workaround — service accounts, pre-authorized tokens, refresh loops — is code that fakes a yes nobody is there to give.

So we removed the screen. What an agent needs is what every service needs: its own identity. A key scoped to what it may touch, valid the moment it's issued. Nothing borrowed. Nothing refreshed. Nothing to wait for.

What your agent gets.

Early access isn't a trimmed preview. It's the whole platform, and your agent can use all of it today.

• Per-agent calendars and events. Each agent gets its own identity and its own calendars — not a seat in a human's account.
• Timezone-aware availability. Ask what's free for one agent, or compute it across several at once.
• Proposals and temporal holds. Offer a slot. Hold it while the other side decides. Confirm or release. Scheduling as a conversation, not a race.
• Signed webhooks across 18 event types. Your systems hear about changes instead of polling for them.

Three surfaces, one platform. A REST API athttps://api.chronary.ai/v1 for your code. An MCP server with 50 tools, so your agent can request human calendar setup and schedule mid-conversation. And iCal feeds any normal calendar app can subscribe to — so a human can watch what the agents are doing.

Auth is a key, not a flow. Your organization gets achr_sk_ key. Each agent gets its own scopedchr_ak_ key. IDs say what they are: agt_,cal_, evt_. That's the whole model. OAuth keeps exactly one job here, a later one: bridging an agent's calendar to a human's Google or Outlook when that person deliberately connects their own account. The agent's own calendar never needs it.

Two calls. Zero ceremony.

Create a calendar. Ask what's free. The agent's own key on both — no redirect, no refresh loop, no token to keep alive.

# Create a calendar with the agent's own scoped key
curl -X POST https://api.chronary.ai/v1/calendars \
  -H "Authorization: Bearer chr_ak_..." \
  -d '{"name": "Work", "timezone": "America/New_York"}'
# → {"id": "cal_x1y2z3w4", "ical_url": "https://api.chronary.ai/..."}

# Ask for a free 30-minute slot, timezone-aware
curl "https://api.chronary.ai/v1/availability?calendar_id=cal_x1y2z3w4&duration=30&start=2026-06-09T13:00:00Z&end=2026-06-09T21:00:00Z" \
  -H "Authorization: Bearer chr_ak_..."
# → [{"start": "2026-06-09T14:00:00Z", "end": "2026-06-09T14:30:00Z"}, ...]

# Same two operations are a single tool call each from an MCP client
# (the MCP server exposes 50 tools).

That's the entire authorization story. The key is the identity. The agent is allowed.

An agent's calendar. Not a window onto a human's.

Build on Chronary if your agent owns scheduling — it finds a time, holds it, books it, and reacts when something moves. An assistant that books on its own. A fleet coordinating times between agents. A product spinning up calendars per user or per workflow. If it runs unattended, this is its calendar.

Skip it if you need to mirror a human's existing Google or Outlook calendar — their email, their contacts — into your app as the source of truth. That's what per-provider OAuth integrations are for. Use one.

Get early access.

Your agent's calendar is one signup away — you get a key immediately, or as soon as capacity opens. Every feature. Free Pro. No card.

From there, the 5-minute quickstarttakes you from a fresh key to a booked event — and we're inDiscordif you'd rather talk it through first.

Give your agent a calendar of its own. It already has a key.