For the complete documentation index, see llms.txt.

How Vennio is different

The core difference

Most scheduling tools are supply-side: they publish your calendar and let people book time with you. Vennio is demand-side: it lets you schedule on behalf of others — with their explicit consent.

This isn't a UX distinction. It's an architectural one. Vennio is scheduling infrastructure for developers and AI agents that need to coordinate time across multiple parties, not just accept inbound bookings.

Demand-side vs supply-side

Supply-side scheduling (Calendly, Cal.com, etc.) works like this:

  1. You connect your calendar
  2. You publish a booking link
  3. Someone visits the link and picks a time that works for you

Demand-side scheduling (Vennio) works like this:

  1. Multiple parties connect their calendars and grant consent
  2. You (or an AI agent) query mutual availability across all parties
  3. You propose times, negotiate, and confirm — programmatically

Consent at the API level

Vennio treats consent as a first-class API primitive. Before any scheduling action that touches another person's calendar, that person must have granted an explicit consent token. This is enforced at the API level — not just in the UI.

This makes Vennio suitable for:

Comparison table

Feature Vennio Calendly Cal.com Cronofy
Demand-side scheduling
Consent-based booking
REST API
MCP / AI-native tools
Multi-party coordination Partial Partial Partial

When to use Vennio

Use Vennio when:

Use a supply-side tool (Calendly, Cal.com) when you just need a booking page for yourself.