Host-signed trust for vacation rentals

AI booking needs trust. A guest should not rely on a guessed price, stale availability, or a booking link copied from an old page.

HemmaBo's approach with Vacation Rental Protocol is simple: the host-owned domain signs the stay offer. Agents and reviewers can verify that the offer came from the domain that represents the property.

What VRP proves

VRP is designed to prove operational booking facts:

• the offer was signed by the host-domain node
• the offer has a freshness window
• the price, dates, currency, and guest count match the signed payload
• the direct booking URL points back to the host-owned domain
• the agent can treat unverifiable states as unknown instead of guessing

What HemmaBo refuses to become

HemmaBo is not a trusted issuer registry. It is not a scorer, accreditation body, OTA, marketplace, merchant of record, or booking intermediary.

That matters because independent hosts should not need permission from a central registry before their own domain can present a verifiable direct booking offer.

Portable attestations without guest exposure

VRP Portable Attestations v0.1 are privacy-minimized. They focus on node, policy, and payment-path trust. They do not publish guest names, emails, phone numbers, guest scores, guest histories, or exact stay dates that could identify a guest.

For v0.1, the goal is conservative: help agents verify the host-domain trust history without making HemmaBo the owner of that truth.

The business consequence

A HemmaBo host gets the selling product people understand: a complete direct booking website. Underneath, VRP gives the site a verifiable offer layer, and UCP/MCP discovery makes the node easier for compatible agents to inspect.

That is the wedge: vacation rental software that stays host-owned and AI-readable.