Aurinia — book across venues via your AI assistant

Books at a network venue on the user's behalf. Takes provider_id and item, which the venue interprets: doctor — item={date,time}; hostel — item={check_in,check_out,guests,promo_code?} (underscores: check_in/check_out, not 'checkin'/'checkout'; guests is an integer; a dorm bed is the default, there is no room_type). No name or contact is required: identity comes from the one-time Telegram consent. At a hostel the call returns a HOLD together with a payment_url, and the booking is finalized by payment rather than by this call; a doctor visit is free. If the user is not yet authorized at that venue the call returns linked=false with consent_url (and consent_url_native when available) instead of a booking, and the same call succeeds once the user has approved in Telegram. Authorization: one Telegram consent per venue, which also covers later calls.

Cancels a booking at a network venue. Takes provider_id and item={booking_id}, where booking_id comes from list_current_bookings. A cancellation is reversible — the freed slot or bed can be booked again — which is why this tool is not marked destructive. If the user is not yet authorized at that venue the call returns a consent link instead. Authorization: one Telegram consent per venue, which also covers later calls.

Find a venue in the Aurinia network. Venue types currently bookable: doctor, hostel. Optional: query (e.g. 'vertebrologist'), city, type. Returns a providers array; use a provider_id from it for get_availability / book.

Availability and price at a venue. provider_id is required. Parameter names are venue-specific: doctor — date (YYYY-MM-DD); hostel — check_in, check_out, guests (with underscores: check_in/check_out, not 'checkin'/'checkout'; guests is an integer). There is no room_type parameter — a dorm bed is the default. Optional promo_code applies an AI-booking discount. A null availability usually means either nothing free or mistyped parameter names, check_in/check_out being the common slip.

Details for one venue by provider_id: id, type (doctor/hostel), name, city, address. Read-only, no auth. Use it to confirm a venue before get_availability / book.

The user's current/upcoming bookings at a network venue (by date, nearest first). Each has a status field (e.g. booked/confirmed/cancelled) — distinguish active vs cancelled. provider_id optional (without it — the first venue). Requires authorization.

The user's past bookings at a network venue (by date, most recent first). Each has a status field. provider_id optional; limit (default 20)/offset for pagination. Requires authorization.

Moves an existing booking at a network venue. Takes provider_id and item; for a doctor that is {date, from, to}, and the move is atomic within the same day — if the target slot is taken in the race, the user keeps the slot they already held, so either outcome leaves them with a booking. A move to a different day is a fresh booking, so book is the right call for that. Support varies by venue: a hostel has no reschedule, where a cancel followed by a new book is the equivalent. If the user is not yet authorized at that venue the call returns a consent link instead. Authorization: one Telegram consent per venue, which also covers later calls.