An appointment scheduling API your agent or app can actually call. Check real availability and book meetings on Google and Microsoft calendars over a clean REST API and a native MCP server. Calendar events and confirmations handled. Billed per meeting booked, live the same day, no Google or Microsoft app review.
Raw calendar APIs hand you free/busy data and event CRUD, then you build the hard parts. Meet.bot ships the hard parts. You call two endpoints and a meeting is booked.
One GET /v1/slots call returns bookable times with working hours, buffers, minimum notice, and daily limits already applied. No free/busy math on your side.
POST /v1/book creates the calendar event on both sides and sends confirmation emails. Reschedule and cancel are single calls too. No event plumbing to build.
The same booking power as a drop-in MCP server for Claude, ChatGPT, Cursor, and Windsurf. Your AI agent books a real meeting in conversation, no glue code.
Subscribe to booked, rescheduled, and cancelled events, JWT-signed, so your agent or backend reacts the instant a meeting changes. Configure them over the API too.
Partner Connect lets your users link a calendar in two clicks. No Google or Microsoft OAuth app, no verification, no app review wait. You launch the same day.
Not per seat, not per connected account, and no monthly minimum to clear before you ship. User accounts are unlimited and free. Your cost tracks meetings actually booked, the value delivered. Free tier, no card.
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"
If your goal is to book meetings, a scheduling API gets you there in an afternoon. A calendar API gets you a toolbox.
| Meet.bot meeting API | Raw calendar API | |
|---|---|---|
| Availability logic | Built in (hours, buffers, limits) | You build it on free/busy |
| Booking + confirmations | Automatic events + emails | You build it |
| AI agents | Native MCP server + REST | REST only, if any |
| Booking webhooks | Booked, rescheduled, cancelled | Raw calendar change events |
| OAuth app setup | Not required | Required per provider |
| Time to first booking | An afternoon | Weeks |
| Pricing model | Per meeting booked | Per connected account |
| Calendar coverage | Google, Microsoft Outlook | Often broader |
Honest take: if you need raw calendar CRUD, free/busy plumbing, or Apple and CalDAV coverage, a calendar API covers more ground. To book meetings, Meet.bot is faster to ship, cheaper to run, and AI-native. Compare the calendar APIs directly: Meet.bot vs Nylas and Meet.bot vs Cronofy.
Most stacks nail the conversation, then hand off finding a time to a clunky link. The API closes that loop, in code or in the agent.
Turn a yes into a booked demo without leaving the chat. The booking fires a webhook your CRM and sequencing tools pick up instantly.
Schedule callbacks and escalations mid-conversation, with ticket context passed straight into the booking and a webhook back to your system.
Give your own users scheduling through the partner program. No Google or Microsoft setup for them, billed per meeting as you grow.
No sales call required. The free tier ships a live API key.
Sign up and get an API key at meet.bot/automation. No card, unlimited user accounts.
GET /v1/slotsOne call returns bookable times with your rules already applied. Filter by page, date range, and timezone.
POST /v1/bookOne call creates the calendar events and sends confirmations. Reschedule and cancel are single calls too.
Receive booked, rescheduled, and cancelled events, JWT-signed, so your agent or backend stays in sync the instant anything changes.
Tell us what you are building and grab 15 minutes. We will map it to the Meet.bot API and answer pricing and integration questions directly.
Booked straight on our calendar. Yes, with the Meet.bot API.
An appointment scheduling and booking API an agent or app can call to read real calendar availability and book a meeting on a connected Google or Microsoft calendar, with the event and confirmations created for you. Meet.bot exposes it as REST and a native MCP server. It is not a meeting recording or transcription bot.
A calendar API gives raw free/busy and event CRUD, and you build availability, booking, and confirmations. Meet.bot already built those. You call /v1/slots and /v1/book and you are done.
Yes, that is the point. A native MCP server (Claude, ChatGPT, Cursor, Windsurf) plus REST means an agent books a real meeting in conversation, then gets a webhook the instant it happens.
Per meeting booked, not per user or per connected account. Unlimited user accounts free, so cost tracks bookings, not connections. Free tier, no card required.
No. Partner Connect links a calendar in two clicks, with no OAuth app registration, no verification, and no app review wait, so you launch the same day.
Yes. Subscribe to booked, rescheduled, and cancelled events, JWT-signed, configurable in the dashboard or over the API and MCP.