Ospitario for partners, developers and AI agents

Short description

Ospitario helps independent holiday-home hosts provide a public property passport, verify their identity or authority within the intended scope, and make the direct contact channels they release accessible. No commission.

Longer description

Ospitario is a registry of holiday homes in Italy, Germany, Spain, France and Portugal, currently piloting in Puglia. Every home has a passport: a public page with the essential facts, the verification level reached and the date since when it holds. The host proves what they can prove, such as control of their listing or their right to manage the property; the page names exactly that level. Guests write to the host directly through the channels the host releases. Ospitario takes no commission and handles neither bookings nor payments. The passport is also readable by search engines and AI assistants, through structured data, a REST interface and MCP. Joining is free during the pilot.

Social media text

Renting out a holiday home and want guests to write to you directly, without commission? Ospitario gives your property a public passport with its verified level and your contact channels. Free during the pilot. https://ospitario.com/

Newsletter text

New for holiday-home hosts: Ospitario. Every property gets a public passport with the essential facts, the level the host has proven and their direct contact channels. Guests write directly, with no platform in between and no commission. Ospitario takes no bookings and no payments. Joining is free during the pilot: https://ospitario.com/

Example post for a host community

Hi all, does anyone know Ospitario? It is a registry of holiday homes without commission. You create a passport for your property and prove what you can, for example that you control your own listing; the page then shows exactly that level. Guests write directly. Free during the pilot: https://ospitario.com/

Screenshots

The home page (Italian, 8 November 2026). No host's page, no booking platform logos.

Home page on a screen, PNGHome page on a phone, PNG

Levels in the response

The field verification.tier names the highest level reached, verification.date since when. The texts are the passports' own:

L0

Page not claimed by the operator. Information taken from public sources; the operator's identity has not been verified.

L2 · Listing verified

The operator proved control of the listing on the platform (calendar link, platform email or channel manager). For verifications from 7 November 2026 a person also checked the documents on the right to manage the property.

L2c · Calendar verified

The operator blocked a date Ospitario picked at random in the platform’s calendar within 48 hours: they manage that calendar. No longer used for new verifications since 7 November 2026.

LA · Right to manage verified (document review)

Ospitario checked documents tying the operator to this property (registration, deed, contract, mandate or company register). A person found them consistent; without SPID/CIE this does not prove who uses the account.

L3 · Operator verified

The operator’s SPID/CIE identity matches the CIN holder in the national register.

L4 · Document verified (automated check)

An ownership, lease or mandate document is consistent with the operator’s identity and the property (automated consistency check, not an authenticity check).

L5 · Manually verified

A person at Ospitario checked the document that entitles the operator to rent out this home.

L1 is not a level of its own in the response: whether the registration number (in Italy the CIN) is well formed and in the official register is in the field registration.

Which data

• Public: name, place, type, capacity, rooms, amenities, languages, registration number with its check, indicative price and, where connected, calendar days.
• Contact channels only where the host releases them (phone, WhatsApp, email, website). For an unclaimed page (L0) only the website and an inquiry through Ospitario.
• Prices and calendars are indicative; booking happens with the host.

REST

MCP

The same functions as MCP tools at https://ospitario.com/mcp (Streamable HTTP): search_properties, lookup_by_url, lookup_by_name, get_passport, send_inquiry.

A session starts with initialize; the response carries the header Mcp-Session-Id, which every further call sends.

No match and errors

No match is not an error: the response has status 200 and says so explicitly. Invalid input gets 400 with the fields concerned. Ospitario never guesses and fills nothing in.

Examples

curl "https://ospitario.com/api/v1/lookup/name?name=Casa%20Esempio&municipality=Lecce"

Excerpt of a response with example data; all fields: /openapi.json

{
  "results": [
    {
      "slug": "casa-esempio-lecce",
      "name": "Casa Esempio",
      "municipality": "Lecce",
      "type": "casa vacanza",
      "verification": {
        "tier": "L2",
        "label": "Listing verified",
        "date": "2026-11-01"
      },
      "contactPageUrl": "https://ospitario.com/p/casa-esempio-lecce?s=agent:unknown"
    }
  ]
}

curl "https://ospitario.com/api/v1/passport/not-a-passport"

{
  "found": false,
  "reason": "not_found"
}

curl "https://ospitario.com/api/v1/search?guests=0"

400 {
  "error": "invalid",
  "issues": [
    {
      "path": "guests",
      "message": "Invalid input"
    },
    {
      "path": "municipality",
      "message": "municipality or province required"
    }
  ]
}

curl -i -X POST https://ospitario.com/mcp \
  -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-03-26","capabilities":{},"clientInfo":{"name":"my-agent","version":"1"}}}'

# then, with the Mcp-Session-Id header of that answer:
#   {"jsonrpc":"2.0","method":"notifications/initialized"}
#   {"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"lookup_by_name","arguments":{"name":"Casa Esempio"}}}

Where agents find Ospitario

• /openapi.json · OpenAPI description, the binding contract
• /.well-known/ospitario.json · short description with the MCP address, tools and limits
• /llms.txt · a plain-text introduction; complements, but replaces neither OpenAPI nor MCP
• https://ospitario.com/mcp · MCP (Streamable HTTP)

The levels

Listing verified

The operator proved control of the listing on the platform (calendar link, platform email or channel manager). For verifications from 7 November 2026 a person also checked the documents on the right to manage the property.

Calendar verified

The operator blocked a date Ospitario picked at random in the platform’s calendar within 48 hours: they manage that calendar. No longer used for new verifications since 7 November 2026.

Right to manage verified (document review)

Ospitario checked documents tying the operator to this property (registration, deed, contract, mandate or company register). A person found them consistent; without SPID/CIE this does not prove who uses the account.

Operator verified

The operator’s SPID/CIE identity matches the CIN holder in the national register.

Document verified (automated check)

An ownership, lease or mandate document is consistent with the operator’s identity and the property (automated consistency check, not an authenticity check).

Manually verified

A person at Ospitario checked the document that entitles the operator to rent out this home.

What is not verified

• quality, cleanliness and amenities on site
• that prices and calendars are accurate
• that a booking comes about
• insurance the host states (shown as "declared" on the page)
• for L0, the operator's identity