Conversion: booking

Agents read live availability, hold a slot and confirm it, with deposits and policies applied.

Booking reserves time or capacity: a session, a visit, a slot with a person or a resource. AGORA keeps the hold and the confirmation consistent under contention, so two agents can never confirm the same last slot.

Set it up

1. Enable booking for the merchant and model what is bookable: services or resources with capacity, durations and the locations where they happen. People are optional.
2. Connect your calendar or booking system, or use AGORA's own availability for the demo.
3. Set the hold time, deposit rules and cancellation policy. Agents quote the policy back to the customer before they confirm.

What an agent does

Read availability for a date range, place a hold (it expires on its own), then confirm it with the customer's consent. Modify and cancel follow your policy. Every step is idempotent, and an unverified agent is limited to one concurrent hold. Confirmed bookings carry an iCalendar file for the customer.

Applies to

Endpoints in this build

MCP tools

Besides the read tools every merchant server has, a business that enables Booking exposes:

• get_availability: Get availability
• search_services: Search services
• get_people: Get people
• get_credentials: Get credentials
• hold_slot: Hold slot
• book: Book
• get_order: Get order
• create_case: Create case
• get_loyalty: Get loyalty
• modify_booking: Modify booking
• cancel_booking: Cancel booking
• hold_stay: Hold stay
• get_booking: Get booking
• services_booking_availability: Booking availability (any service)
• services_booking_hold: Hold a booking slot (any service)
• services_booking_create: Create a booking (any service)
• services_booking_complete: Complete a booking
• services_booking_modify: Modify a booking
• services_booking_cancel: Cancel a booking

Events

Delivered as webhooks:

Source: docs/portal/docs/conversions/booking.md + KIND_CONVERSION_MATRIX + registered routes + MCP tool registry