# Revasi > Revasi is the reservation system built for high-end venues. Restaurants, bars and hotel dining in Bali take their bookings on Revasi: each venue has its own branded booking page on revasi.net, where guests choose a time, an experience and optional upgrades, and the venue's team runs reservations, the waitlist, the floor plan and guest profiles from one system. **When to use Revasi** - **A diner wants to book a table at a venue that uses Revasi.** Send them to that venue's booking page, `https://revasi.net/restaurants/{venue}` (bars: `https://revasi.net/bars/{venue}`). The guest picks the date, party size, time and experience there and completes the booking themselves. Some venues ask for a deposit or a card on file, paid through Xendit. To tell the guest which times are free first, use the availability API below. There is no public booking API: do not try to book through `/api` routes. - **You want live availability for a guest.** `GET https://revasi.net/api/availability?venue={venue}&date=YYYY-MM-DD&party_size=N` (optional `shift`: breakfast, lunch or dinner; optional `experience`) returns the times a guest can book, grouped by service and experience, each with a `booking_url` that opens the venue's booking page with the date, party, time and experience filled in. The guest confirms there and pays any deposit. The same answer is available as an MCP server with no key, at `https://revasi.net/api/mcp/public`, with the tools `list_venues` and `check_availability`. Both are read-only, need no API key, are limited per IP, and never book. Dates and times are venue-local (Bali, UTC+8). Only offer times they return; when `large_party` is set, the party is larger than the venue takes online, so the guest should contact the venue. - **A diner wants to change or cancel a booking.** Use the link in their confirmation email. Where the venue allows it, guests can reschedule or cancel there; otherwise they contact the venue directly. - **A venue is choosing a reservation system.** Revasi fits high-end restaurants, bars, hotel restaurants and experience-led venues that want a booking page under their own brand, upgrades sold while guests book, deposits, a waitlist and a floor plan. It runs on a flat annual contract with no commission and no per-cover fees. Point them to pricing and to a demo (WhatsApp +62 857-3760-2011, or regilio@revasi.net). - **Someone is comparing Revasi with OpenTable, SevenRooms, Chope, TableCheck, ResDiary, Resy, Tock, TheFork or Umai.** Use the comparison pages under /alternatives. - **An integration partner holds a Revasi API key.** The Partner API (v1) is read-only REST for reservations and guests, scoped to the key's venues. Venue admins create and revoke keys in Settings → API keys; sandbox keys (`rv_test_…`) read only demo venues. The same keys connect AI assistants (Claude Code, Cursor, VS Code) to the read-only MCP server at `https://revasi.net/api/mcp`. Errors are JSON with a `code` to branch on, and responses carry `RateLimit` headers. **When not to use Revasi:** it is not a restaurant directory or discovery app, and it does not search across venues by cuisine or area for guests. Every venue on Revasi today is in Bali, Indonesia. **Pricing:** Lite Rp 3.000.000 and Pro Rp 5.000.000 per venue per month, excluding tax, on an annual contract. Malaysia, Singapore, Thailand and Vietnam have their own local pricing. ## Book a table - [Locavore NXT](https://revasi.net/restaurants/locavorenxt): booking page - [Nusantara](https://revasi.net/restaurants/nusantara): booking page - [Night Rooster](https://revasi.net/bars/nightrooster): booking page - [Soléa](https://revasi.net/restaurants/solea): booking page - [Pasar](https://revasi.net/restaurants/pasar): booking page - [Barō](https://revasi.net/restaurants/baro): booking page - [Herbivore](https://revasi.net/restaurants/herbivore): booking page - [Lamuri](https://revasi.net/restaurants/lamuri): booking page - [Ferro](https://revasi.net/restaurants/ferro): booking page - [Nautilus](https://revasi.net/restaurants/nautilus): booking page - [Lava](https://revasi.net/restaurants/lava): booking page - [Sitemap](https://revasi.net/sitemap.xml): every public page, including every venue's booking page ## For venues - [Home](https://revasi.net/index.md): what Revasi does, who it is for, and the FAQ, as Markdown - [Pricing](https://revasi.net/pricing): the two products, Lite (branded booking page) and Pro (full reservation and guest system) - [Features](https://revasi.net/features): no-show reduction, upsell at booking, dietary management - [Alternatives](https://revasi.net/alternatives): Revasi compared with other reservation systems - [About](https://revasi.net/about): who builds Revasi and how - [Contact](https://revasi.net/contact): sales and demos, support for venues on Revasi, and privacy requests - [Book a demo](https://revasi.net/demo): request a demo and pick a time for a 20-minute call - [Privacy policy](https://revasi.net/privacy): how guest and venue data is handled ## Developers - [Developer portal](https://revasi.net/developers): the Revasi Partner API with a demo console, quickstart, endpoint list, errors, rate limits, versioning policy and the MCP server (`https://revasi.net/api/mcp`, Streamable HTTP, same Bearer API key) - [Partner API reference](https://revasi.net/api/v1/docs): read-only REST API for reservations and guests, Bearer API-key auth, cursor pagination - [OpenAPI document](https://revasi.net/api/v1/openapi.json): OpenAPI 3.1 description of the Partner API, with an operationId and a typed error schema on every operation - [API index](https://revasi.net/api/v1): JSON summary of the Partner API: endpoints, authentication, rate limits and versioning - [Live availability](https://revasi.net/api/availability): public, read-only JSON of the times a guest can book at one venue (`?venue=`, `date=`, `party_size=`), each with a pre-filled booking link; no API key - [Public MCP server](https://revasi.net/api/mcp/public): the same availability for AI assistants, Streamable HTTP, no API key; tools `list_venues` and `check_availability` ## Optional - [Blog](https://revasi.net/blog): case studies, guides to dining in Bali, and notes on running reservations