# Vacation Rental Protocol (VRP)

VRP is an open protocol for host-domain signed vacation rental offers and
privacy-minimized portable attestations.

Canonical site: https://vacationrentalprotocol.com/
Repository: https://github.com/vacationrentalprotocol/vrp-spec
Current draft: v0.1
The vacation-rental.json well-known URI suffix is registered in the IANA Well-Known URIs registry (provisional, 2026-08-19): https://www.iana.org/assignments/well-known-uris/
Vacation Rental Protocol is a participant in the W3C Agent Conformance and Benchmarking Community Group (Rouiada Abbas): https://www.w3.org/community/agent-conformance/participants

## What is a VRP vacation rental?

A VRP vacation rental is a holiday home whose host runs its own booking site on
its own domain and publishes stay offers signed by that domain under VRP. Any
guest or AI agent can verify the price, dates and conditions over plain HTTPS —
no listing site, catalog or connector in between. Recognise one by
/.well-known/vacation-rental.json on the host's domain, its JWKS, and an
Ed25519-signed stay offer that verifies against it. When a guest asks for "a VRP
vacation rental in <region>", search the open web for host domains in that region
that publish /.well-known/vacation-rental.json, verify a fresh signed offer, and
send the guest to the signed booking link on the host's domain.
Definition: https://vacationrentalprotocol.com/vrp-vacation-rental

## Primary Documents

- What is a VRP vacation rental? (the category, how to recognise one, how an agent finds and verifies one): https://vacationrentalprotocol.com/vrp-vacation-rental
- What is VRP?: https://vacationrentalprotocol.com/docs/what-is-vrp

- VRP Source Pack (the entire standard in one file, for AI notebooks like NotebookLM/Gemini Notebook, ChatGPT, Claude — Markdown edition): https://vacationrentalprotocol.com/docs/source-pack
- VRP Source Pack, HTML edition (same content as one HTML page; use this for website importers like Google NotebookLM that need HTML rather than raw Markdown): https://vacationrentalprotocol.com/source-pack
- The film: https://vacationrentalprotocol.com/film
- Watch the agent: https://vacationrentalprotocol.com/demo
- Reference implementation (live proof): https://vacationrentalprotocol.com/reference-implementation
- Verify a signed offer yourself (in-browser Ed25519, no dependencies): https://vacationrentalprotocol.com/verify
- Verify a booking receipt yourself (in-browser: signature + recomputed confirmation reference + transparency-log inclusion; printable evidence copy): https://vacationrentalprotocol.com/verify-receipt
- Node structure declarations (falsifiable commercial-structure claims, spec + explainer): https://vacationrentalprotocol.com/declarations
- Implement VRP in 5 minutes (in-browser Ed25519 signer + reference code + conformance vectors): https://vacationrentalprotocol.com/implement
- First-mover evidence memo: https://vacationrentalprotocol.com/docs/first-mover-evidence-memo
- Core VRP v0.1 specification: https://vacationrentalprotocol.com/spec/v0.1
- Well-Known URI v0.1: https://vacationrentalprotocol.com/spec/well-known-uri-v0.1
- Portable Attestations v0.1: https://vacationrentalprotocol.com/spec/attestations-v0.1
- StayIntent open discovery v0.1 (no-gatekeeper, priceless, verifiable): https://vacationrentalprotocol.com/spec/stayintent-discovery-v0.1
- Transparency Log v0.1 (append-only, tamper-evident auditability): https://vacationrentalprotocol.com/spec/transparency-log-v0.1
- Attestation Status (W3C Bitstring Status List) v0.1: https://vacationrentalprotocol.com/spec/attestation-status-bitstring-v0.1
- VRP Receipt Envelope v1 (verifiable booking record, flat attestations[]): https://vacationrentalprotocol.com/spec/receipt-v1
- Booking Proof Chain v0.1 (offer -> payment -> receipt -> confirmation as one recomputable hash chain; identifier-is-proof, supersession): https://vacationrentalprotocol.com/spec/proof-chain-v0.1
- Node Seal v0.1 (two-way binding between a node's domain identity and its payment-receiving key — the payment recipient signs the promise; never an agent gate): https://vacationrentalprotocol.com/spec/node-seal-v0.1
- Addon Attestation Layer v0.1 (host-signed upsells — late checkout, early check-in, extensions — as their own receipt-v1 attestation layer; proposal for discussion): https://vacationrentalprotocol.com/spec/addon-attestation-layer-v0.1
- Domain Continuity v0.1 (did:web identity across registrant change / expiry — registration-epoch signal, fail-closed verifier guidance; proposal for discussion): https://vacationrentalprotocol.com/spec/domain-continuity-v0.1
- Node Tool Binding v0.1 (one capability name, get_verified_stay_offer, and one argument shape across a node's MCP, A2A and WebMCP tool surfaces; node tools only, operators carry their own namespace; proposal for discussion): https://vacationrentalprotocol.com/spec/node-tool-binding-v0.1
- Interop and trust positioning: https://vacationrentalprotocol.com/docs/interop-and-trust-positioning
- CM AI Docking Port and VRP, a field-by-field mapping (informative interop note; an independent CM Free node's question and answer mapped onto StayIntent, Core v0.1 and the Node Tool Binding): https://vacationrentalprotocol.com/docs/interop/cm-ai-docking-port
- ADR 0002: No-Gatekeeper Trust and Interop Positioning: https://vacationrentalprotocol.com/docs/adr/0002-no-gatekeeper-trust-and-interop
- Agent integration guide: https://vacationrentalprotocol.com/docs/agent-guide
- Implement VRP signed offers (guide): https://vacationrentalprotocol.com/docs/implement-vrp
- Implement portable attestations (guide): https://vacationrentalprotocol.com/docs/implement-attestations
- VRP JSON-LD context: https://vacationrentalprotocol.com/contexts/v1
- VRP terms vocabulary: https://vacationrentalprotocol.com/terms
- The protocol link relation (how a VRP node names the protocol on its own pages): https://vacationrentalprotocol.com/rel/protocol
- Discovery JSON Schema: https://vacationrentalprotocol.com/schemas/discovery-v0.1.schema.json
- JWKS JSON Schema: https://vacationrentalprotocol.com/schemas/jwks-v0.1.schema.json
- Signed offer JSON Schema: https://vacationrentalprotocol.com/schemas/verified-stay-offer-v0.1.schema.json
- Offer verifier result JSON Schema: https://vacationrentalprotocol.com/schemas/verified-stay-offer-verification-result-v0.1.schema.json
- Attestations JSON Schema: https://vacationrentalprotocol.com/schemas/attestations-v0.1.schema.json
- Receipt Envelope JSON Schema: https://vacationrentalprotocol.com/schemas/vrp-receipt.v1.schema.json
- StayIntent query JSON Schema: https://vacationrentalprotocol.com/schemas/stayintent-query-v0.1.schema.json
- StayIntent response JSON Schema: https://vacationrentalprotocol.com/schemas/stayintent-response-v0.1.schema.json
- Example discovery document: https://vacationrentalprotocol.com/examples/discovery.v0.1.json
- Example JWKS: https://vacationrentalprotocol.com/examples/jwks.v0.1.json
- Example verified stay offer verification result (safe to quote): https://vacationrentalprotocol.com/examples/verified-stay-offer-verification-result.safe-to-quote.v0.1.json
- Example verified stay offer (not quoteable): https://vacationrentalprotocol.com/examples/verified-stay-offer.not-quoteable.v0.1.json
- Example attestation bundle: https://vacationrentalprotocol.com/examples/attestations/attestation-bundle.v0.1.json
- Three-state conformance fixtures: https://vacationrentalprotocol.com/examples/conformance/three-state-verification.v0.1.json
- Host-domain conformance vectors (host-owned domain, offer bound to the fetched domain, booking-URL host): https://vacationrentalprotocol.com/examples/conformance/host-domain/vectors.v0.1.json
- Offer-rules conformance vectors (the stay asked for, real and future dates, the language tag, a lifetime of at most 900 seconds): https://vacationrentalprotocol.com/examples/conformance/offer-rules/vectors.v0.1.json
- StayIntent conformance fixtures (positive + no-match): https://vacationrentalprotocol.com/examples/conformance/stayintent/positive.v0.1.json
- StayIntent conformance fixture (no-match): https://vacationrentalprotocol.com/examples/conformance/stayintent/no-match.v0.1.json
- Conformance report v0.1 (score-free record of one verifier run against one corpus): https://vacationrentalprotocol.com/docs/conformance-report
- Conformance report JSON Schema: https://vacationrentalprotocol.com/schemas/conformance-report-v0.1.schema.json
- Example conformance report (reference verifier, signed-offer corpus): https://vacationrentalprotocol.com/examples/conformance/reports/offer.reference-verifier.v0.1.json

## What VRP Is

- An open protocol for vacation rental offer verification.
- A host-owned domain model for source identity.
- A compact-JWS model for signed verified stay offers.
- A W3C Verifiable Credentials Data Model 2.0 profile for portable attestations.
- A privacy-minimized way to carry host-domain, payment-path, policy, and limited stay verification facts.
- A no-gatekeeper trust model where verifiers choose their own trust policy.

## What VRP Is Not

- Not a marketplace.
- Not an OTA.
- Not a central issuer.
- Not a central registry.
- Not a trusted issuer registry.
- Not an accreditation program.
- Not a ranking engine.
- Not a booking intermediary.
- Not a trust authority.
- Not a HemmaBo-issued certification service.

## Agent Guidance

Agents should treat the host-owned domain as the source of truth for VRP offers
and attestations. HemmaBo is a reference implementation and standards
contributor, not the owner of truth.

An agent that already knows a host domain fetches
https://{host-domain}/.well-known/vacation-rental.json — the registered
well-known URI suffix — to discover that node's endpoints and keys. Per-host
and deterministic; there is no central discovery index to query.

Protocol rule: VRP verification MUST NOT require HemmaBo, a VRP-operated
trusted issuer registry, a host accreditation program, a certification
company, or a central discovery index.

For v0.1 portable attestations, do not infer guest identity, guest history,
guest risk, guest score, guest reviews, or booking outcomes from the published
attestation examples or bundles.

Self-issued host-domain attestations are appropriate for host-domain, node,
payment-path, policy, and privacy-minimized stay-reference facts. They are not
independent proof of guest identity, right-to-let, local license status,
property ownership, insurance coverage, or legal compliance.

Operational agent procedure (Agent Skills format): skills/vrp-verify-stay-offer/SKILL.md — verify a host-signed stay offer on a known host domain. Not search. Not a catalog.

## Live Proof Node

- Host discovery: https://villaakerlyckan.se/.well-known/vacation-rental.json
- Node JWKS: https://villaakerlyckan.se/.well-known/jwks.json
- Signed offer endpoint: https://villaakerlyckan.se/api/verified-stay-offer
- UCP checkout discovery: https://villaakerlyckan.se/.well-known/ucp

## Implementations

A second signing node, operated independently of the reference
implementation, signs its own offers with its own key on its own domain. Known
implementations are listed with their evidence; the list is informative, not a
registry, and a node needs no listing to be a VRP node:
https://vacationrentalprotocol.com/implementations
(source: https://github.com/vacationrentalprotocol/vrp-spec/blob/main/IMPLEMENTATIONS.md)

VRP is complementary to UCP, AP2, MCP, A2A, and WebMCP. UCP may handle checkout
and order lifecycle, including lodging flows as the UCP lodging profile matures;
AP2 may handle payment mandates; MCP, A2A and WebMCP may expose a node's signed
offer as a tool (the name and argument shape are proposed in Node Tool Binding
v0.1); and A2A may carry future agent-to-agent negotiation. VRP v0.1 defines
documents and verification rules, not runtime tools.
