Done with Nylas v3 migrations and per-connected-account bills? Meet.bot is complete scheduling, with pages, availability, booking, and calendar sync over a REST API and a native MCP server. Billed per meeting booked, live the same day, no Google or Microsoft app review.
Works with the calendars your users already use
The same three reasons come up again and again. Meet.bot removes all three.
Nylas has deprecated two API versions. Each v2 to v3 jump means weeks of rewrites that break integrations and delay your roadmap, for no new functionality. Meet.bot has one stable v1 API.
At about $3 to $5 per connected account, a product with 500 customers spends $18k to $30k a year on the API layer, growing with every connection, not every booking. Meet.bot bills per meeting booked.
Every Nylas customer registers and maintains their own Google or Microsoft OAuth app and survives verification. Meet.bot Partner Connect needs none of it. Users connect in two clicks.
Nylas is a broad calendar and email API you build scheduling on top of. Meet.bot is the scheduling product, finished, and AI-native.
| Meet.bot | Nylas | |
|---|---|---|
| What it is | Complete scheduling solution | Raw calendar + email API |
| Scheduling pages | Included, ready to share | Build your own |
| Availability engine | Built in (buffers, hours, limits) | Build your own logic |
| Booking & confirmations | Automatic events + emails | Build your own |
| AI agents | Native MCP server + REST API | REST API only |
| OAuth app setup | Not required | Required per provider |
| Time to launch | Same day | Weeks to months |
| Forced version migrations | None, one stable API | v1 to v2 to v3 |
| Pricing model | Per meeting booked | Per connected account |
| Free tier | Yes, no card required | Limited sandbox |
| Calendar coverage | Google, Microsoft Outlook | Google, Microsoft, Apple, more |
| Email API | Not included | Included |
| Raw calendar CRUD | Via scheduling abstraction | Full CRUD access |
Honest take: if you need raw calendar CRUD, Apple or CalDAV, or an email API, Nylas covers more ground. For scheduling, Meet.bot is faster, cheaper to run, and AI-native. More below.
A sync-engine API copies your users' calendars onto its servers. Meet.bot does not. We read availability live from Google and Microsoft only when a request needs it, so your users' calendar data stays with their provider, not in our database.
We never download your users' calendars into our system. Free/busy and events are read on demand from Google or Microsoft when a request needs them, then discarded, never mirrored into our database.
We request the minimum calendar scopes to read availability and write the meetings you book. No mailbox access, no broad data grants.
GDPR-compliant data handling, TLS encryption in transit, and JWT-signed webhooks so your systems can trust every event. Details in our privacy policy.
Read live availability and create a real booking, calendar invites and confirmations included. Wire it to your backend, or drop in the MCP server and let an AI agent do it.
// check availability const slots = await fetch( "https://meet.bot/v1/slots?slug=demo", { headers: { Authorization: "Bearer " + token } } ).then(r => r.json()); // book the first open slot await fetch("https://meet.bot/v1/book", { method: "POST", headers: { Authorization: "Bearer " + token }, body: JSON.stringify({ slug: "demo", slot: slots[0].start, name: "Jane", email: "jane@acme.com" }) });
// add to your MCP client config { "mcpServers": { "meetbot": { "command": "npx", "args": ["-y", "@meetbot/mcp"], "env": { "MEETBOT_AUTH_TOKEN": "<token>" } } } } // then just ask: "Book a 30-min demo with jane@acme.com next Tue PM"
Most stacks nail the conversation, then hand off finding a time to a clunky link. Meet.bot closes that loop. Your AI agent checks real availability and books on the user's Google or Outlook calendar, in the conversation.
Turn a yes into a booked demo without leaving the chat. Slots in alongside your outbound stack via API or MCP.
Schedule callbacks and escalations mid-conversation, with ticket context passed straight to the booking.
Give your own users scheduling via the partner program. No Google or Microsoft setup, billed per meeting as you grow.
Works great, I use it almost every day!
We added a calendar integration for our AI agent in less than 30 minutes.
If you use Nylas for scheduling, the mapping is direct.
GET /v1/slotsSwap Nylas free/busy and availability calls for a single slots endpoint that already applies buffers, working hours, and limits.
POST /v1/bookOne call books the meeting and sends calendar events and confirmation emails to both sides.
Drop the OAuth app registration and verification entirely. Users connect with two clicks, you get their API token by webhook.
Receive booked, rescheduled, and cancelled events, JWT-signed, to keep your system in sync.
Tell us what you are building and grab 15 minutes. We will map it to Meet.bot and answer pricing and migration questions directly.
Booked straight on our calendar. Yes, with Meet.bot.
For scheduling, yes: availability, booking, and calendar events, usually migrated in a day. For raw calendar CRUD or an email API, Nylas covers a broader scope.
Nylas bills per connected account (about $3 to $5 per account per month). Meet.bot bills per meeting booked, unlimited users free, so cost tracks bookings, not connections.
No. Partner Connect lets users link a calendar in seconds, with no OAuth app registration, no verification, no app review wait.
It is the differentiator: a native MCP server (Claude, ChatGPT, Cursor, Windsurf) plus REST API, so an agent books real meetings in conversation.
About a day for scheduling. Slots, book, and Partner Connect map directly. Email hello@meet.bot and we will map your calls.
Yes. Embed pages with ?show_background=0&primary_color=hex, or build your own UI on the Slots and Book endpoints.