# Meet.bot: Full LLM Context

> AI-first scheduling platform. Personalized scheduling pages and a powerful API for AI agents to check availability and book meetings. Pay per meeting booked, not per user seat.

## Overview

Meet.bot is a scheduling platform built for both people and AI agents. Users create scheduling pages that can be shared via link or embedded on websites. AI agents can check availability and book meetings programmatically through the REST API or MCP server.

**Key differentiators:**
- AI-first: API and MCP server are core features, not afterthoughts
- Pay per meeting booked, not per user seat. Unlimited users at no extra cost
- Complete scheduling solution for partners, not just a calendar API (Nylas alternative)
- Same-day launch for partner integrations. No Google/Microsoft app setup required
- MCP server for Claude, ChatGPT, Cursor, Windsurf, and other AI assistants

## API Reference

Base URL: `https://meet.bot`

Authentication: Bearer token in the Authorization header.
```
Authorization: Bearer YOUR_TOKEN
```
Get your token at https://meet.bot/automation

### Endpoints

#### GET /v1/pages
List all scheduling pages for the authenticated user.

Response: Array of page objects with slug, title, duration, and configuration.

#### GET /v1/slots
Get available time slots for a scheduling page.

Parameters:
- `slug` (required): The scheduling page slug
- `start_date` (optional): Start of date range (ISO 8601)
- `end_date` (optional): End of date range (ISO 8601)

Response: Array of available time slots with start/end times.

Example:
```
GET /v1/slots?slug=product-demo&start_date=2025-01-20&end_date=2025-01-24
```

#### POST /v1/book
Book a meeting on a scheduling page.

Body (JSON):
- `slug` (required): The scheduling page slug
- `slot` (required): The selected time slot (ISO 8601)
- `name` (required): Name of the person booking
- `email` (required): Email of the person booking

Example:
```json
POST /v1/book
{
  "slug": "product-demo",
  "slot": "2025-01-22T14:00:00Z",
  "name": "Jane Smith",
  "email": "jane@example.com"
}
```

Response: Booking confirmation with calendar event details.

#### GET /v1/page-config
Get configuration for a specific scheduling page.

Parameters:
- `slug` (required): The scheduling page slug

Response: Page configuration including duration, availability windows, buffer times, and branding.

#### POST /v1/page-create
Create a new scheduling page.

Body (JSON): Page configuration including title, slug, duration, and availability settings.

#### GET /v1/info
Get account information for the authenticated user.

Response: User profile, connected calendars, and account status.

#### Webhooks (/v1/webhooks)
Manage outbound webhooks that notify your URL the instant a meeting is booked, rescheduled, or cancelled.

- GET /v1/webhooks — list your webhooks
- POST /v1/webhooks — create one (body: webhook_url, optional description, coverage [all|selected], scope [self|team], pages, is_active)
- PATCH /v1/webhooks/{id} — update a webhook
- DELETE /v1/webhooks/{id} — delete a webhook

Each event POSTs a JWT-signed (HS256) JSON payload to your URL, signed with the webhook's shared secret (the same contract as the partner webhook). Events: `booking_received`, `booking_rescheduled`, `booking_cancelled`. Coverage `all` (default) fires for every page including ones created later; `selected` only for chosen pages. Configurable in settings (Webhooks) or via the API/MCP.

### Full API Documentation

- Interactive ReDoc: https://meet.bot/api
- OpenAPI YAML spec: https://meet.bot/api/yaml/
- OpenAPI JSON spec: https://meet.bot/api/json/
- Swagger UI: https://meet.bot/api/swagger-ui/

## MCP Server

Meet.bot provides an MCP (Model Context Protocol) server that enables AI assistants to directly interact with scheduling functionality.

Compatible with: Claude Desktop, ChatGPT, Cursor, Windsurf, and any MCP-compatible AI assistant.

Setup guide: https://help.meet.bot/en/articles/130659-meet-bot-mcp-model-context-protocol

The MCP server exposes tools for:
- Listing scheduling pages
- Checking available time slots
- Booking meetings
- Creating and configuring scheduling pages
- Getting account information
- Managing outbound booking webhooks (list/create/update/delete)

## Integrations

- **MCP Server**: Direct AI assistant integration (Claude, ChatGPT, Cursor, Windsurf)
- **REST API**: Full programmatic access with Bearer token auth
- **n8n**: Native workflow automation node. https://help.meet.bot/en/articles/130539-meet-bot-n8n-integration
- **Zapier**: Connect to 5000+ apps. https://help.meet.bot/en/articles/130543-meet-bot-zapier-integration
- **Make.com**: Visual automation builder. https://help.meet.bot/en/articles/130550-meet-bot-make-com-integration
- **Browser Extension**: Access scheduling from Gmail, LinkedIn, anywhere. https://help.meet.bot/en/articles/116957-meet-bot-browser-extension
- **Website Embed**: Embed booking widget on your website. https://help.meet.bot/en/articles/123507-how-do-i-embed-meet-bot-scheduling-on-my-website

## Partner Program

For companies that want to embed scheduling in their own product.

### How it works:
1. Sign up and request a partner token (hello@meet.bot)
2. Add a "Connect with Meetbot" button: `https://meet.bot/partner/{short_id}/connect?partner_user_id={your_id}`
3. Receive `partner_token_created` webhook with API token for each connected user
4. Use the API on behalf of your users (list pages, check slots, book meetings)
5. Receive `booking_received` webhooks when meetings are booked

### Partner advantages:
- No Google or Microsoft app setup required for your users
- Same-day launch with no approval waits
- Full API or scheduling pages. You control the experience
- Scheduling page embed with styling: `?show_background=0&primary_color=hex`
- JWT-signed webhooks with shared secret verification
- Pay per meeting, not per user. Scales with your customer base

More details: https://meet.bot/partners and https://meet.bot/embed-scheduling

## Use Cases

### AI Demo Booking Bot
Product demos booked by AI: native MCP server and REST API so agents check rep availability and complete bookings in conversation. No manual scheduling loop.
More: https://meet.bot/ai-demo-booking-bot

### AI Sales Agent Scheduling
Scheduling layer for AI SDR stacks: most tools stop at outreach; Meet.bot closes the loop from "yes" to a confirmed call via API and MCP.
- Check availability: GET /v1/slots
- Book the meeting: POST /v1/book
- Webhooks for booked, rescheduled, cancelled
More: https://meet.bot/ai-sales-agent

### AI Support Agent
Support bots can schedule callbacks and escalation meetings right in the conversation. The API lets you include ticket context so specialists are prepared.
More: https://meet.bot/ai-support-agent

### Personal AI Assistant
Use Claude, ChatGPT, or any MCP-compatible AI to manage your calendar. Ask in plain language: "Book a 30-minute call with john@example.com next Tuesday afternoon."

### Embed in Your Product
Add scheduling capabilities to your application via the partner program. Create scheduling pages for your users, receive booking webhooks, and white-label the experience.
More: https://meet.bot/embed-scheduling

## Comparisons

### Meet.bot vs Nylas
Nylas provides raw calendar and email API access. You build scheduling on top. Meet.bot is a complete scheduling solution with pages, availability, booking, and calendar sync out of the box. No Google/Microsoft app setup required. Pay per meeting booked, not per connected account.
More: https://meet.bot/nylas-alternative

### Meet.bot vs Cronofy
Cronofy is powerful scheduling infrastructure but complex to set up and per-user pricing. Meet.bot offers the same scheduling capabilities with simpler integration, same-day launch, and pay-per-meeting pricing. Cronofy has broader calendar support (Apple, Exchange) and enterprise features (SSO, meeting intelligence) that Meet.bot doesn't include.
More: https://meet.bot/cronofy-alternative

## Pricing

Meet.bot charges per meeting booked, not per user seat.
- Unlimited users at no extra cost
- No per-seat fees on any plan
- Your entire team can use Meet.bot

Pricing details: https://meet.bot/pricing

## Frequently Asked Questions

### How do I let my AI agent book meetings?
Get your API token at meet.bot/automation, then use the REST API or MCP server. Your AI agent can call GET /v1/slots to check availability and POST /v1/book to book meetings.

### What AI platforms work with Meet.bot?
Any AI platform. MCP server works with Claude Desktop, ChatGPT, Cursor, Windsurf. REST API works with any AI agent framework. n8n, Zapier, and Make for no-code workflows.

### What authentication does the API use?
Bearer token authentication. Include your token in the Authorization header: `Authorization: Bearer YOUR_TOKEN`. Get your token at meet.bot/automation.

### How do I get available time slots?
Call GET /v1/slots with a scheduling page slug and optional date range. Returns available slots based on connected calendars and page settings.

### What happens when a meeting is booked via API?
Calendar events are created for both parties, confirmation emails are sent, and connected calendars are synced. If you've configured a webhook (and partners, if connected), Meet.bot POSTs a signed `booking_received` event to your URL.

### How do I get notified when a meeting is booked, rescheduled, or cancelled?
Configure an outbound webhook in settings (Webhooks) or via the API/MCP (the `set_webhook` tool). Meet.bot POSTs a JWT-signed JSON payload to your URL for each `booking_received`, `booking_rescheduled`, and `booking_cancelled` event, so your agent can wire bookings straight into a CRM or downstream step.

### How is Meet.bot different from Calendly for AI?
Meet.bot is built AI-first. API and MCP are core features. Pay per meeting booked, not per user seat. Unlimited users at no extra cost.

### How is Meet.bot different from Nylas?
Meet.bot is a complete scheduling solution, not just a calendar API. Users get scheduling pages, availability management, and calendar sync out of the box. No Google/Microsoft app setup required.

### Do I need a paid plan to use the API?
Start with a free account at meet.bot/signup. Get your API token at meet.bot/automation. You only pay when meetings are booked.

### Can I create scheduling pages via API?
Yes. Use POST /v1/page-create to create new scheduling pages and GET /v1/page-config to read page settings programmatically.

### What calendars does Meet.bot sync with?
Google Calendar and Microsoft Outlook. Calendar events are created for both parties when meetings are booked.

## Links

- Website: https://meet.bot
- API Docs: https://meet.bot/api
- OpenAPI Spec: https://meet.bot/api/yaml/
- Helpcenter: https://help.meet.bot
- Sign Up: https://meet.bot/signup
- Get API Token: https://meet.bot/automation
- Contact: hello@meet.bot