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:
- You connect your calendar
- You publish a booking link
- Someone visits the link and picks a time that works for you
Demand-side scheduling (Vennio) works like this:
- Multiple parties connect their calendars and grant consent
- You (or an AI agent) query mutual availability across all parties
- 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:
- AI agents that schedule meetings on behalf of users
- B2B platforms that coordinate time between their customers and vendors
- Enterprise tools that need GDPR-compliant calendar access
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:
- You need to schedule on behalf of users, not just accept bookings for yourself
- You're building an AI agent that coordinates meetings autonomously
- You need multi-party availability — finding time when 2–5 people are all free
- You run many bookable hosts under one account — coaches, agents, practitioners — each individually booked and attributed (Multi-Host Accounts)
- You need consent management built into the scheduling layer
- You want composable primitives (availability, bookings, proposals, venn-links) rather than an opinionated SaaS product
Use a supply-side tool (Calendly, Cal.com) when you just need a booking page for yourself.