Documentation · Markdown source · Edit on GitHub · CC0 1.0

VRP Interop and Trust Positioning

Status: Public draft Date: 2026-05-31

Summary

VRP is the host-domain offer verification layer for vacation rentals.

Core VRP proves that a concrete offer is real. Portable Attestations prove selected trust history without making HemmaBo, or any other operator, the authority over truth.

VRP is intentionally not a complete booking, payment, guest identity, legal verification, or discovery-index protocol. It is designed to compose with those layers while keeping the host-owned domain first-class.

No Central Issuer

VRP's trust model is no-gatekeeper by design.

VRP does not require:

Verification starts from the host-owned domain:

  1. Fetch the host-domain VRP discovery document.
  2. Resolve the host-domain keys or DID document.
  3. Verify the signed offer or attestation.
  4. Apply protocol rules for freshness, exact price, availability, privacy, and status.
  5. Apply the verifier's own trust policy.

A verifier may still use a trust policy. That policy can include local legal requirements, insurer requirements, municipal registries, payment providers, property managers, identity verification providers, or allowlists chosen by the verifier. Those choices are not HemmaBo approval and not VRP-wide certification.

Self-Attestation Boundary

Self-issued host-domain credentials are appropriate for facts controlled by the host domain, including:

Self-issued host-domain credentials are not enough for claims that require independent evidence, including:

Future VRP versions may define optional third-party credential profiles for those claims. The issuer trust decision should remain verifier-chosen, not centralized in HemmaBo or the VRP standards site.

Relationship to Adjacent Standards

VRP should compose with the agent-commerce stack instead of replacing it.

LayerVRP position
UCPComplementary. UCP can handle checkout, order lifecycle, and merchant-of-record commerce flows, including lodging flows as the UCP lodging profile matures. VRP proves the host-domain offer and can hand off through a signed direct booking URL or future optional UCP manifest reference.
AP2Complementary. AP2 can handle cryptographic payment mandates and payment authorization. VRP v0.1 does not define payment mandates or raw payment processing.
MCPComplementary. MCP can expose retrieval or verification behavior as tools in a future profile. VRP v0.1 defines documents and verification rules, not runtime tools.
A2AComplementary. A2A can carry future guest-agent and host-agent negotiation. VRP v0.1 does not define an A2A binding.
A2A Agent CardA node may publish an A2A Agent Card at https://{host-domain}/.well-known/agent-card.json. Its provider is the host. It may carry a data-only extension with uri https://vacationrentalprotocol.com/spec/v0.1 and required: false, whose params repeat the VRP v0.1 §2 discovery fields of the same host domain. Its skills name only tools the host domain serves, and it lists no A2A interface the host domain does not serve. The card describes the node; it is not a registry entry and does not replace verification of the signed offer against jwks_url.
CM AI Docking PortAn independent, read-only entry point for AI agents into CM Free nodes (AGPL-3.0). Its Request and Response Envelopes map field by field onto the StayIntent query and response, and its signed-offer tool, when exposed, onto the Node Tool Binding; see the mapping. VRP is unchanged by it.
W3C VC 2.0Used by VRP Portable Attestations.
VC JOSE/COSECanonical v0.1 security format for VRP Portable Attestations as compact JWS with typ: "vc+jwt" and alg: "EdDSA".
W3C Data IntegrityPossible future interoperability mapping. VRP v0.1 does not use embedded proof objects.

What VRP Should Not Copy

VRP should not add a mandatory central trusted issuer registry merely to look more complete.

VRP should not publish a HemmaBo trust score.

VRP should not call host-domain self-attestation "right-to-let verification" or "legal compliance verification."

VRP should not publish guest reviews, guest risk, guest outcome, guest scores, or guest history in v0.1.

VRP should not define runtime MCP tools until the document layer is stable and there is at least one interoperable verifier profile.

Roadmap Gaps

The verified gaps are real and should be named directly:

The recommended path is not to make HemmaBo the missing authority. The recommended path is to add optional profiles that let independent issuers, payment providers, search indexes, and host tools interoperate while VRP keeps the host-domain offer proof gatekeeper-free.