Invitations by email, handled
Invitations, updates, cancellations, replies and counter-proposals that arrive by email update the calendar on their own, and only when they come from the organizer, or from the guest who is answering; nothing in Junk touches the calendar. Each inbox chooses its auto-accept policy (never, known senders, or always) and what to do about a conflict (leave it, decline, or accept anyway).
Invitations and answers the inbox sends are ordinary email sent through the normal sending path, so autonomy tiers, approvals, sponsor gating, lists, caps and hooks apply to them as to any other message. An agent on a send_with_approval inbox cannot invite anyone a person has not approved.
Find a time and book it
Availability takes working hours, buffers, a time zone, a duration and a step, and can include other inboxes' busy time, so an agent offering slots for a team offers times that are actually open. Booking checks the slot again, creates the event and emails the invitations in one call. Free/busy can be read for any window.
POST /v1/inboxes/{inbox_id}/availability
{ "from": "2026-10-05T00:00:00Z", "to": "2026-10-09T00:00:00Z",
"duration_minutes": 30, "time_zone": "Europe/London",
"also_inboxes": ["inb_..."] }
POST /v1/inboxes/{inbox_id}/bookings
{ "start": "2026-10-06T14:00:00Z", "duration_minutes": 30,
"title": "Intro call",
"attendees": [{ "email": "candidate@example.com" }] } Events that behave like a calendar's
- Recurrence in the event's own time zone, correct across daylight-saving changes, with per-occurrence changes and exceptions; one occurrence can be read, edited or answered on its own.
- Nothing lost on an edit. Each event is kept whole, so alarms, attendee details and properties another client added survive every change.
- Time zones from any client, including the Windows names Outlook sends.
- Calendar events as webhooks: calendar.event.invited, replied, counter_proposed, cancelled and more, through the same webhooks, feed and stream as mail.
MCP tools and standard clients
Scheduling is a set of MCP tools beside the mail ones: list_calendar_events, create_calendar_event, respond_to_invite, find_availability, book_meeting, get_free_busy and more. The same calendars are served over CalDAV, so Apple Calendar, Thunderbird or any CalDAV client can open an agent's calendar, and over JMAP Calendars with push; all of them stay in sync with the API.
Status of everything on this page
Every capability named above, with its status as reconciled against the engine.
| Capability | What it does | Status |
|---|---|---|
| Calendar per inbox | A calendar on every inbox: events with recurrence and time zones, invitations, updates, cancellations and replies by email, auto-accept rules, free/busy, availability and booking that sends the invitations, MCP tools for scheduling, and CalDAV and JMAP Calendars for standard clients. Invitations an agent sends follow its inbox's autonomy tier. | Shipped |
| Autonomy tiers enforced by the server | Every inbox carries a sending policy, from read-only to autonomous, enforced on the server for every surface that sends, so switching from the API to MCP cannot bypass it. | Shipped |
| MCP server | A remote MCP server over streamable HTTP whose tools are generated from the same operation table as the REST API and dispatched through the same router, so a tool cannot behave differently from its endpoint. | Shipped |
| JMAP | JMAP Mail, submission, vacation responses and push, one account per inbox a key can see, sharing one change history with the API and IMAP, with extensions for typed metadata and approvals. A send over JMAP meets the same autonomy tiers as any other. | Shipped |
| Webmail for the humans in the loop | A full webmail and calendar on the same mailboxes the agents use, with an agent-activity timeline, the approval queue, a per-thread driver lock and a metadata panel, signed in through the same accounts as the console. It opens with hosted access. | Shipped |
| Built-in and custom extractors | Receipts and orders, invoices (account numbers masked), calendar invitations and named entities extracted into typed metadata as mail arrives, plus your own extraction schemas run on your own model key, with the output validated against the schema. | Shipped |