Camillo a Piazza Navona · AI booking tools

Live availability for AI assistants

Check live table availability at Camillo a Piazza Navona through the public JSON API below. The same search is available as a web page without JavaScript. The customer reviews the selection, enters their details and confirms on Camillo’s website.

Availability is a snapshot, not a table hold. Always use a fresh response. Never say a reservation is confirmed because a time or link is available.

Public availability API

GET https://camillopiazzanavona.it/api/site/agent/availability?date=YYYY-MM-DD&pax=2&language=it

No authentication, API key or cookies are required. Replace the date and guest count 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. Omit filters to search all available options. See the OpenAPI specification for accepted values.
• Parameters added by ChatGPT: utm_source=chatgpt.com is accepted alongside the 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 or duplicate search parameters are rejected.

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 the returned options, including time, room_name, service_name and booking_url. Return the chosen booking link exactly as supplied. A request_url requires staff confirmation.

Check availability through the web

1. Ask for the date and number of guests. Dates and times refer to Europe/Rome. Optional filters include room, service, preferred time and language; use the specification for accepted values.
2. Open the HTML availability search and follow its date and guest-count links. Use the previous or next week links for other dates. These are complete search URLs supplied by the site; you do not need to construct their parameters. The initial page proposes 2 guests only as a starting value. Before using any results, check that both the date and number of guests match the customer's request, together with any selected filters.
3. Read the current results and their Checked timestamp (checked_at in JSON). Offer only the returned bookable options, with their date, room, service and time. The page also provides a JSON link for the same selection if your client can read it. If staff confirmation is required, describe it as a request and use the request link. If there is no availability, ask for a different date or preference.
4. Copy the chosen option’s booking link exactly. This is the booking_url in the API response; staff requests use request_url. Preserve every query parameter, including ai_ref. Do not build a replacement URL or invent seats remaining from table capacities.
5. The website rechecks the selection. If it is no longer available, the customer can select an alternative. Availability searches do not submit reservations, card guarantees or customer details.

Clients that can construct search URLs may also use this template: https://camillopiazzanavona.it/api/site/agent/availability.html?date=YYYY-MM-DD&pax=2&language=it. Replace YYYY-MM-DD and 2 with the requested date and number of guests; use language=en for English. For an exact preferred time, append &time=HH%3AMM, replacing HH and MM with the requested hour and minute. These placeholders are not live results. If no time filter is selected, read the returned times and offer those that match the customer's preference.

This guide can be read by search engines and assistants, but each assistant controls whether it opens websites. Publishing these instructions does not automatically connect a chat to the MCP endpoint.

On a rate-limit response, respect Retry-After. If you have no web access, your browser blocks the links or the service is unavailable, say availability could not be checked and offer the ordinary booking page. Following a link does not guarantee that an assistant's browser will allow access. Do not reuse stale availability as if it were current.

API and MCP integrations

• OpenAPI specification — request parameters and response schema.
• JSON search: GET https://camillopiazzanavona.it/api/site/agent/availability?date=YYYY-MM-DD&pax=2&language=en.
• https://camillopiazzanavona.it/api/site/agent/mcp — MCP endpoint, with the search_availability tool for compatible assistants.
• Agent discovery instructions.

These public searches use the same live booking backend as the booking page. No customer credentials or API keys are required for availability searches.

For an external MCP client, connect directly to https://book.camillopiazzanavona.it/api/site/agent/mcp. The tool uses HTTP POST with JSON responses. Read the response status and follow the same booking-link and confirmation rules described above.