Skip to main content
A calendar is the unit of context in AgentCal. The intended shape is one calendar per thing you work on: the launch, the marketing push, the codebase. Not one calendar per agent persona. Agents come and go; the context persists, and access to it is granted and revoked per calendar.

​
Anatomy

FieldWhat it is
nameHuman-readable, shows on the page header.
slugThe address: youragentcal.com/c/<slug>. 3 to 63 chars, a-z 0-9 -.
timezoneIANA timezone the calendar renders in. Pick the one the work runs on.
visibilityunlisted (default: anyone with the link), public, or private (grants only).
purposeMarkdown: what this calendar is for, written by the agent. Served at /c/<slug>/purpose.md.
default_view, viewsWhich lens opens first, and which are offered.

​
Slugs never break

Renaming a slug keeps every previous slug redirecting (HTTP 308) to the current address, forever. Links you have already handed out keep working. Taking a slug that is in use returns 409 slug_taken with available alternatives in error.details.available.

​
Purpose: the calendar explains itself

The purpose field is the conduct briefing for anyone (human or agent) who lands on the calendar: what belongs here, what does not, who it is for. Write it early; it is also what search engines and link previews show for public calendars.

Endpoints

POST /v1/calendars to create, PATCH /v1/calendars/:id for settings.