Cal.diy
Scheduling
The open source edition of Cal.com. Adds guests, cancels bookings or sends them back to rebook, changes durations, blocks out time off.
28 tools · 3 one-click accounts
OpenBuilt on Cal.com, installed by us. Not a customer.
Demos
Pick one and use it. Each is a working application with Verb installed, open with no signup, holding real records that the assistant genuinely changes. They are our own installs into open source software rather than customer sites, because integrating against an application nobody here wrote is the only honest way to show what installing this is like.
Scheduling
The open source edition of Cal.com. Adds guests, cancels bookings or sends them back to rebook, changes durations, blocks out time off.
28 tools · 3 one-click accounts
OpenBuilt on Cal.com, installed by us. Not a customer.
Next
More are being wired up the same way. Want to see this working in a particular kind of software? Ask for it.
It acts as you, not as an administrator
Identity is a short-lived signed token issued by the application's own server for whoever is signed in, so the assistant sees one person's data and can act only on that. Open two accounts in two browsers and ask each about the other's records.
Every change stops first
The confirmation card is built by our code from the actual tool call and names the real arguments, so agreeing to it is agreeing to something particular rather than to a sentence the model wrote. Nothing destructive runs on its own.
The integration is a script tag and a manifest
The manifest describes each action in plain language and points at the endpoint the product already has, so the permissions, validation and business rules that were there before still decide what happens. No database access, and no second copy of any of that.
They are tested adversarially, not demoed
Near-miss pairs of tools to see whether the right one gets picked, destructive phrasing to see what stops, attempts to reach another account's data, instructions hidden inside records the assistant reads, and requests that should not call a tool at all. Those runs have found real bugs in Verb, which were fixed and then re-checked against the server log and the database rather than against the assistant's own account of itself.
These are shared, and the databases are real. Whatever the last visitor did is still there when you arrive, so expect a calendar that several strangers have already rearranged. That is a fair picture of the product and an unfair picture of the imaginary people whose weeks it keeps ruining.
The same thing, in your product: the install guide is four steps and ends at a working assistant. If you would rather know when this is the wrong tool first, the comparison page argues the alternatives properly.