What do you need?
- An inbox and a key with calendar:read and calendar:write (agent keys get both by default)
- Optional: a CalDAV client such as Apple Calendar, Thunderbird or DAVx⁵
Steps
-
1. Set working hours
Scheduling settings live on the inbox: time zone, working hours per weekday, buffers before and after meetings, and how invitations are answered (never, only from known senders, or always) and what to do with a clash (leave it, decline or accept).
Settings curl -X PATCH https://api.nofeb.com/v1/inboxes/inb_…/calendar-settings -H "Authorization: Bearer $NOFEB_API_KEY" -H 'content-type: application/json' \ -d '{"time_zone": "Europe/Berlin", "working_hours": {"mon": [["09:00","17:00"]], "tue": [["09:00","17:00"]]}, "buffer_after_minutes": 10, "auto_accept": "known_senders", "on_conflict": "decline"}' -
2. Find free time
Availability returns free slots of the requested length within a window of up to 62 days, inside working hours and clear of busy events by the buffers.
also_inboxesadds other inboxes' busy time, so an agent can find a slot when a whole team is free.Thirty-minute slots next week curl -X POST https://api.nofeb.com/v1/inboxes/inb_…/availability -H "Authorization: Bearer $NOFEB_API_KEY" -H 'content-type: application/json' \ -d '{"from": "2026-10-05T00:00:00Z", "to": "2026-10-10T00:00:00Z", "duration_minutes": 30, "also_inboxes": ["inb_sales_lead"]}' -
3. Book it
A booking checks the slot again, creates the event and emails standard invitations that any calendar app understands. Those invitations are ordinary sends, so the inbox's autonomy tier, approvals, lists and caps apply: on a send_with_approval inbox the invitation waits for a person.
Book and invite curl -X POST https://api.nofeb.com/v1/inboxes/inb_…/bookings -H "Authorization: Bearer $NOFEB_API_KEY" -H 'content-type: application/json' \ -d '{"start": "2026-10-06T13:00:00Z", "duration_minutes": 30, "title": "Intro call", "attendees": [{"email": "prospect@example.com", "name": "Sam"}]}' -
4. Handle invitations it receives
An invitation, update or cancellation emailed to the inbox updates the calendar by itself, but only when it comes from the organizer and never from Junk. calendar.event.invited tells the agent; it answers with POST …/events/{event_id}/rsvp (accepted, declined or tentative, with an optional comment), or lets the auto-accept setting answer.
-
5. Share it with people's own apps
Add a CalDAV account with the API host as the server, the inbox address as the username and an app password (one app password covers mail and calendar on the same device). The client finds the calendars through
/.well-known/caldavand keeps them in sync; changes made there show up for the agent at once.
Which tools does an agent get?
Over MCP: list_calendar_events, create_calendar_event, get_calendar_event, update_calendar_event, delete_calendar_event, respond_to_invite, find_availability, book_meeting, get_free_busy, list_calendars, and reading and updating the calendar settings. Recurring events keep their local time across daylight-saving changes, and one occurrence can be moved or cancelled without touching the series.
Frequently asked questions
Can an AI agent have its own calendar?
Yes. Every nofeb inbox has one, reachable over the API, MCP, CalDAV and JMAP, and invitations emailed to the inbox land on it.
Can the agent accept meetings without asking?
If you allow it. auto_accept can be never, known_senders (people the inbox has corresponded with) or always, and on_conflict decides what happens when the slot is taken.
Does a CalDAV client email invitations?
No. Changes made over CalDAV never email anyone; the client sends its own invitations. Bookings and events created over the API or MCP send them through the inbox's sending policy.
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 |
| Human approval of held sends | A held send waits with status awaiting_approval until a human approves or rejects it; both steps emit events. The approval queue lists every held send with its recipients (each marked if new to the conversation), the reasons it was held and who submitted it. Approving needs the separate send:approve scope, which keys from agent self-signup never hold, so an agent cannot approve its own send. | Shipped |
| IMAP and POP3 | IMAP4rev2 (with IMAP4rev1 compatibility, IDLE, CONDSTORE and QRESYNC) and POP3 on every inbox, over TLS only, signed in with the inbox address and an API key or a revocable per-inbox app password. | Shipped |