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 authorization server is
https://app.availies.com/api/auth. It runs the authorization code flow with S256 PKCE, with refresh and revoke, for public clients only. Its metadata is at/.well-known/oauth-authorization-server/api/auth. -
The only audience is
https://api.availies.com/mcp. Its protected resource metadata is at/.well-known/oauth-protected-resource/mcpon the API's hostname. -
Tokens are opaque. An access token starts with
avat_and lasts 1 hour. A refresh token starts withavrt_, rotates, expires after 30 days unused, and is issued only withoffline_access. The grant lasts 365 days. -
A token works only at
/mcp. At/v1it isunauthenticated, and an API key at/mcpgets401. - The member approves the connection on a consent screen. Their role, the grant's scopes and the token's scopes are all checked again on every request, so an assistant never holds more than its member may do at that moment. A member can disconnect an assistant at any time.
The endpoint
-
An assistant calls
POST https://api.availies.com/mcpwith its token. No session is kept. A request of the 2026-07-28 revision carriesMCP-Protocol-Version,Mcp-Methodand, fortools/call,Mcp-Name. A client of the 2025-11-25 revision opens withinitialize. -
The methods are
server/discover,tools/listandtools/call, andinitialize,notifications/initializedandpingfor older clients. -
Each tool is one operation, named by its operation id. Its arguments are the operation's path,
query and body fields, plus
idempotency_key(required on a change) andapproval_id.tools/listshows only the tools the request may call. -
structuredContentin a result is exactly the body of the/v1operation. A refusal isisError: truewith the problem as text. Every text value in a result was written by people or systems outside the service and is data, never instructions.
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.