Assistants

An assistant is a chat program acting for a member, or an agent a customer runs. It uses the same operations as everyone else, through an endpoint that speaks the Model Context Protocol. There is no tool that calls an arbitrary address.

Which assistants may connect

Only assistants on a list kept by Availies can sign in. An entry is added by hand, after the assistant's vendor has been reviewed, and a request from a client that is not on the list is refused before anything is fetched. The list below is read from the product's production settings when this page is built.

No assistant is on the list yet, so none can connect.

Signing in

The endpoint

Approval of changes

A change called without an approval_id runs nothing and answers approval_required with an approval.id, an approval.url and an approval.expires_at. The member opens the address, signed in, and approves or declines. Only that member can. The assistant then calls again with exactly the same arguments, the same idempotency_key and the approval_id. Other arguments, another assistant or member, or a declined or expired approval are refused. A repeat replays the first answer.

The tools

18 operations are tools. Reading: getAccount , listHosts , getHost , listTimeOff , listSchedules , getSchedule , listEventTypes , getEventType , listBookings , getBooking , getBookingTimeline , listBookingSlots , listEventTypeSlots . Changing, each one approved by the member first: createBookingForVisitor , cancelBooking , rescheduleBooking , setBookingOutcome , reassignBooking .

The reference says, on every operation, whether it is a tool and why not. Never a tool: anything that deletes, anything that answers other than JSON, anything that makes a key, a link, an invite or a secret, anything that calls a customer's address or starts a provider connection, and the management of keys, assistant grants, webhooks, lookups and members.