Every AI agent
needs an inbox
and a calendar.
We give it both.
AgentDraft is one API your agents call to receive email, check availability, book meetings, and reply — with deterministic conflict resolution across every agent that touches the same calendar.
One API your agents call to receive email, check availability, book meetings, and reply — without colliding with the other bots in your stack.
Updated
No card required · 50 founding seats remain
By midday the inbox and the calendar are a collision of good intentions.
One agent reads an email and books a discovery call at 09:00. Another replies to a different thread and slots a client meeting at 09:30. A third blocks focus time that neither of the first two can see. The agents are each doing their job. No shared layer holds the rules they should all be following.
The market response has been more agents, not coordination. Every scheduling tool and every inbox integration builds its own private view of availability and commits in isolation. The user becomes the resolver — manually untangling collisions every morning.
AgentDraft is the missing layer. Every agent calls one API before it books — and reads its mail through one inbox. Every booking commits through one deterministic engine. Every action is recorded in one tamper-evident log. Switching tools is just reconfiguring an endpoint — adopting AgentDraft turns scheduling and agent email into infrastructure.
¹ By "agent" we mean any automated process that books or emails on a human's behalf — Cal.com handlers, OpenAI assistants, internal scripts, the sales bot you wrote last Tuesday.
Availability
Agents ask AgentDraft what's open — never the calendar directly. The response is filtered through buffer rules, focus blocks, and any active holds from sibling agents.
GET /v1/availability
?user_id=usr_01H...
?duration=30mCommit
Bookings commit through a single conditional write. When two agents collide, the priority engine resolves deterministically. No retries. No drift.
POST /v1/bookings agent: agt_sales slot: 16:00–16:30 → 201 COMMITTED
POST /v1/bookings agent: agt_recruit slot: 16:00–16:30 → 409 OUTRANKED
Audit
Every hold, commit, eviction and rule change is written immutably. Enterprise governance review is a curl away.
GET /v1/audit
?resource=bkg_3f9
→ 7 events, signedMailbox
Each agent gets a signed, deliverable inbox at inbox.agentdraft.io. Inbound mail is parsed into structured events; outbound replies are DKIM-signed from the same address.
POST /v1/mailbox/messages /<id>/reply → 200 DELIVERED · DKIM ✓
Two agents. One slot.
Deterministic outcome.
Time-bucketed conditional writes resolve in a single DynamoDB TransactWriteItems. No locks. No races. No human in the loop.
Point your agents here. Keep your calendar.
- 1 user · 1 calendar
- 3 agents · 1 mailbox
- 30-day audit retention
- Community support
- 5 users · 3 calendars / seat
- Unlimited agents · 5 mailboxes
- Multi-agent priority resolution
- 1-year audit retention
- Private-beta access · no card required
- White-label endpoint plan
- SSO / SCIM implementation plan
- 7-year audit · dedicated IP plan
- Negotiated SLA · dedicated CSM
"We're not building another scheduling tool. We're building the protocol that makes scheduling tools cooperate."