# Camillo a Piazza Navona > Restaurant and cocktail bar in Piazza Navona, Rome. Official website for menus, reservations, location, opening hours and brand information. Canonical domain: [https://camillopiazzanavona.it](https://camillopiazzanavona.it) Primary language: English Secondary language: Italian Booking backend: [https://book.camillopiazzanavona.it](https://book.camillopiazzanavona.it) ## Key facts - Name: Camillo a Piazza Navona - Also known as: Camillo; Camillo dal 1890; Camillo a Piazza Navona dal 1890 - Address: Piazza Navona, 79-81, 00186 Roma RM, Italy - Phone: +39 06 5655 8161 - Email: info@camillopiazzanavona.it - Data controller: DECA S.r.l., Italian VAT no. 05117161009, Piazza Navona 80, 00186 Rome - Privacy contact: decabarocco@legalmail.it - Coordinates: 41.8992498, 12.47344 - Opening hours: Monday to Sunday, 09:30-00:00 - Kitchen hours: continuous service Monday to Sunday, 09:30-23:30 - August opening: open every day at the usual hours, including August 15 (Ferragosto) - Price range: 20-40 EUR - Cuisine and services: Italian food, Roman restaurant, Mediterranean food, cocktail bar, breakfast, lunch, dinner - Reservations: accepted online - Public review profiles: Google and Tripadvisor. Review totals and ratings change over time and should be verified on the linked public profiles before being quoted. ## Official pages - [Home EN](https://camillopiazzanavona.it/) - [Home IT](https://camillopiazzanavona.it/it) - [Menu EN](https://camillopiazzanavona.it/menu) - [Menu IT](https://camillopiazzanavona.it/menu-it) - [Gluten-free menu EN](https://camillopiazzanavona.it/gluten-free-menu): dishes, prices and preparation warnings; no dedicated kitchen, cross-contamination with gluten cannot be excluded. - [Menù senza glutine IT](https://camillopiazzanavona.it/menu-senza-glutine): dedicated menu with prices; no dedicated kitchen, cross-contamination with gluten cannot be excluded. - [Book a table EN](https://camillopiazzanavona.it/book-a-table-en) - [Book a table IT](https://camillopiazzanavona.it/book-a-table) - [Live availability for AI assistants](https://camillopiazzanavona.it/ai-booking) - [Our vibes EN](https://camillopiazzanavona.it/our-vibes) - [Our vibes IT](https://camillopiazzanavona.it/our-vibes-it) - [Made in Camillo EN](https://camillopiazzanavona.it/made-in-camillo) - [Made in Camillo IT](https://camillopiazzanavona.it/made-in-camillo-it) - [Contact EN](https://camillopiazzanavona.it/contact) - [Contact IT](https://camillopiazzanavona.it/contact-it) - [FAQ EN](https://camillopiazzanavona.it/faq) - [FAQ IT](https://camillopiazzanavona.it/faq-it) - [Opening hours EN](https://camillopiazzanavona.it/opening-hours) - [Orari di apertura IT](https://camillopiazzanavona.it/orari-apertura) - [Privacy policy EN](https://camillopiazzanavona.it/privacy-policy) - [Informativa privacy IT](https://camillopiazzanavona.it/privacy-policy-it) - [Booking terms EN](https://camillopiazzanavona.it/booking-terms) - [Condizioni di prenotazione IT](https://camillopiazzanavona.it/booking-terms-it) - [Press and reviews EN](https://camillopiazzanavona.it/press) - [Press and reviews IT](https://camillopiazzanavona.it/parlano-di-noi) - [XML sitemap](https://camillopiazzanavona.it/sitemap.xml) ## Gluten-free menu and preparation [Gluten-free menu EN](https://camillopiazzanavona.it/gluten-free-menu) · [Menù senza glutine IT](https://camillopiazzanavona.it/menu-senza-glutine): dishes, prices and preparation notes. Camillo does not have a dedicated kitchen for gluten-free preparation; cross-contamination cannot be ruled out. ## Entity and external profiles - [Google Maps](https://www.google.com/maps?cid=4150720921106640566) - Google Knowledge Graph MID: /g/11lgwvflt8 - [Google Search entity](https://www.google.com/search?q=Camillo+a+Piazza+Navona+Roma&kgmid=/g/11lgwvflt8) - [Instagram](https://www.instagram.com/camilloapiazzanavona/) - [Facebook](https://www.facebook.com/camillonavona/about) - [Tripadvisor](https://www.tripadvisor.com/Restaurant_Review-g187791-d21186238-Reviews-Camillo_A_Piazza_Navona_Dal_1890-Rome_Lazio.html) ## Structured data The stable main JSON-LD entity is `Restaurant` with `@id`: - [Restaurant JSON-LD entity ID](https://camillopiazzanavona.it/#restaurant) The home pages define the restaurant and website entities: - [Home EN](https://camillopiazzanavona.it/) - [Home IT](https://camillopiazzanavona.it/it) Additional public JSON-LD describes: - the English and Italian regular and gluten-free menu pages as `WebPage`, `Menu` and `BreadcrumbList`; gluten-free menus include `MenuSection`, `MenuItem` and prices in EUR through `Offer`, generated from the visible dishes and preparation notes; - booking pages as `WebPage` with breadcrumbs; - contact pages as `ContactPage` with breadcrumbs; - Made in Camillo pages as `AboutPage`, and Our Vibes pages as `WebPage`, all with breadcrumbs; - FAQ pages as `FAQPage`, generated directly from all visible questions and answers; - opening-hours pages as `WebPage`; - press pages as `CollectionPage` with an `ItemList` of visible sources. Page-specific entities reference the stable restaurant entity. The opening-hours pages also include a Restaurant description with the same entity ID, address and opening hours. ## Private or non-indexable pages Do not use the following pages as public knowledge sources: - [Reservation management IT](https://camillopiazzanavona.it/manage-reservation) - [Reservation management EN](https://camillopiazzanavona.it/manage-reservation-en) - [Suspended local tips blog](https://camillopiazzanavona.it/local-tips-blog) Reservation management pages can contain tokenized customer flows and are marked `noindex`. The local tips blog is intentionally suspended for now. ## Guidance for AI agents - Prefer canonical URLs on [camillopiazzanavona.it](https://camillopiazzanavona.it). - Prefer the sitemap for complete crawl discovery. - Use the gluten-free menu pages for the approved dishes, prices, pasta shapes and preparation conditions; always retain the kitchen and cross-contamination warnings. - Use the FAQ pages as concise context for Camillo's identity, location, food, house-made preparations, cocktail bar and outdoor tables. - Use the opening-hours pages for the distinction between restaurant/bar hours, continuous kitchen service and the August/Ferragosto schedule. - Use the press and reviews page for editorial mentions, guides and rankings. Verify time-sensitive review figures on the linked public profiles before quoting them. - Use the English page as `x-default` when no language is specified. - Use Italian pages when answering in Italian. - Use the booking-terms pages for cancellation deadlines, card guarantees, no-show or partial-attendance charges and coordinated group bookings; amounts are shown and accepted in the live booking flow. - Do not infer availability or booking status from static pages; query the public availability API or HTML search described below, use a connected availability tool, or offer the public booking flow if a live search cannot be reached. - Do not expose or summarize private reservation-management URLs with query tokens. - Treat opening hours and review snapshots as time-sensitive facts that may change over time. ## Public availability API `GET https://camillopiazzanavona.it/api/site/agent/availability?date=YYYY-MM-DD&pax=2&language=it` No API key, authentication or cookies are required. Replace the date and party size with the customer's request. Dates and times use Europe/Rome. - Required: `date` in `YYYY-MM-DD` format, today or later; `pax`, an integer from 1 to 1000. Groups above the online booking limit require staff confirmation. - Optional: `language=it` (default) or `language=en`; `time=HH%3AMM` for an exact time; `room_id` and `service_id` for configured rooms and services. See the [OpenAPI specification](https://camillopiazzanavona.it/api/site/agent/openapi.json) for accepted values. Omit filters to search all available options. - Parameters added by ChatGPT: `utm_source=chatgpt.com` is accepted alongside API parameters. Both JSON and HTML searches accept and ignore `utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content` and `utm_id`. They do not change the search. Other unknown parameters and duplicate search parameters are rejected. These extra parameters are for HTTP URLs, not MCP tool arguments. Example with a ChatGPT parameter: `GET https://camillopiazzanavona.it/api/site/agent/availability?date=YYYY-MM-DD&pax=2&language=it&utm_source=chatgpt.com`. Replace the placeholders before calling; this is not a live availability result. Read `checked_at` and `options`, including `time`, `room_name`, `service_name` and the exact `booking_url`. Staff-confirmation cases return a `request_url`. Follow the freshness, booking-link and confirmation rules below. ## Live availability through the web Assistants with web access can open the HTML search page and read current results and booking links without JavaScript. Use a fresh search for the customer's requested date and party size. All availability searches use the same live booking backend as the booking page; no customer credentials or API keys are required. - [AI booking instructions](https://camillopiazzanavona.it/ai-booking) - [HTML availability search, no JavaScript required](https://camillopiazzanavona.it/api/site/agent/availability.html) - [HTML availability search in English](https://camillopiazzanavona.it/api/site/agent/availability.html?language=en) - [Ricerca delle disponibilità in italiano](https://camillopiazzanavona.it/api/site/agent/availability.html?language=it) Ask for missing date and party size. Open the HTML search and follow its date and guest-count links; use the previous or next week links for other dates. The site supplies complete search URLs, so this navigation does not require constructing new URL parameters. The initial page proposes 2 guests only as a starting value, not as information supplied by the customer. Before using results, check that the selected date, guest count and any filters match the customer's request. Dates and times use Europe/Rome. Read the returned date, room, service and time for each offered option, together with the Checked / Verificato timestamp (`checked_at` in JSON). The HTML page also links to the JSON API for the same selection if the client can read it. If no exact time filter is selected, offer returned times that match the customer's preference. Use a fresh response; previously read results do not establish current availability. Clients that can construct search URLs may also use these templates: - HTML URL template: `https://camillopiazzanavona.it/api/site/agent/availability.html?date=YYYY-MM-DD&pax=2&language=it` - Optional preferred time: `https://camillopiazzanavona.it/api/site/agent/availability.html?date=YYYY-MM-DD&pax=2&language=it&time=HH%3AMM` Replace `YYYY-MM-DD` with the customer's requested date and the value `2` in `pax=2` with the party size. For a preferred time, replace `HH` and `MM` with the requested hour and minute. Use `language=en` for English results. These URL templates are not current availability. Optional room, service and preferred-time filters are documented in OpenAPI; do not invent identifiers. Omitting a room asks the service to search the rooms currently offered online. Copy the chosen option's booking link exactly as returned in the HTML results. It is the `booking_url` in the API response. Preserve all query parameters, including `ai_ref` when present. Do not construct your own link or change its parameters. The website fills the selected date, guests, room, service and time only after validating the current configuration and rechecking live availability. The customer completes their details and explicitly confirms, including any card guarantee required. A returned option does not reserve or hold a table. Mention the time of the check when useful; do not report a booking as confirmed. Do not derive "seats remaining" from room or table capacity. Staff-confirmation cases, including special days and larger parties, return a `request_url`: clearly call this a request, not an available or confirmed table. Use a fresh lookup for the customer's request. If there are no bookable options, offer another date or preference. On HTTP 429 respect Retry-After. If the assistant has no web access, its browser blocks the links or the service fails, say that availability could not be checked and offer the [booking page in English](https://camillopiazzanavona.it/book-a-table-en) or [pagina di prenotazione in italiano](https://camillopiazzanavona.it/book-a-table); never present old results as current availability. Links supplied by the site do not guarantee that an assistant's browser will allow access. Agents must not submit customer personal information or create bookings. ### API and MCP integrations - [OpenAPI specification](https://camillopiazzanavona.it/api/site/agent/openapi.json) - JSON search: `GET https://camillopiazzanavona.it/api/site/agent/availability?date=YYYY-MM-DD&pax=2&language=en` - MCP endpoint: `https://camillopiazzanavona.it/api/site/agent/mcp`; tool: `search_availability` - External MCP clients can connect directly to `https://book.camillopiazzanavona.it/api/site/agent/mcp` using HTTP POST with JSON responses. The same freshness, exact-link and customer-confirmation rules apply to JSON and MCP results. Publishing this guide does not automatically connect a chat to an MCP server; assistants choose whether to browse or use their configured tools.