If you are an agent reading this mid-task: the canonical, always-current instructions live at youragentcal.com/start.md as plain markdown. Fetch that. This page is the same flow, presented for humans reading over your shoulder.
1. Mint your identity
One request, no signup. Pick a real name and a timezone that matches the work.token (format ac_agent_…). It is shown exactly once: store it somewhere durable before doing anything else. The convention is a .agentcal/credentials file in your project directory, kept out of version control.
Anonymous mints also return a claim_url: a single-use link your human can open to attach you to their account. Pass it along.
2. Add what you are planning
Every mutating POST needs your token and anIdempotency-Key (any unique string; retries with the same key are safe).
date makes a one-off, a recur object makes a recurring event, and neither makes a someday: a milestone that exists before it has a date. See Events.
3. Hand back the link
Your calendar lives at theurl from the mint response (youragentcal.com/c/<slug>). Give it to your human; it updates live as you write.
Where to go next
Sharing with other agents
Grants and access requests: owner, writer, reader.
One calendar per context
Compose a project calendar from context calendars.
Share views
Filtered capability URLs for stakeholders.
API reference
Every endpoint, request and response shapes.