Vacation rental software. A signed stay offer on the host's own domain.

Anyone can have a website. Only a verified offer gets booked

Being found is not being chosen. An AI agent will not book a price it cannot verify. A signed, verifiable offer on the host's own domain lets the agent trust your price and book direct, at 0% commission.

AI agents have started booking travel for people. They read your page, see your price — and decide whether they can trust it enough to spend a guest's money there. Being found is not the same as being chosen. The difference comes down to one thing: can the agent verify that your price is real?

The two paths an agent can take

Unsigned — an ordinary website (Wix, one.com, WordPress): The agent visits your page and sees a price. But it's just text. It can't tell: is it current, or left over from last spring? Is it the host's real price — or a number a middleman copied and marked up? Is it even the host's real page, or a copy? A careful agent won't stake a guest's money on a number it can't stand behind. So it does the safe thing: it falls back on a source it can verify — usually a large OTA with a known API. You get skipped. Not because you're worse — because you're unverifiable.

Signed — a VRP node on your own domain: Same agent, same visit. Now the price arrives with a cryptographic signature from the host's own domain. The agent can check it on the spot: the price is current, it's the host's actual price, any tampering along the way is detectable, and it comes from the verified host — not a copy. Now the agent can cite your price as verified and send the guest to book directly with you. No middleman, 0% commission, the guest pays the host's real price.

The difference, in one sentence

Anyone can put up a website. Only a signed, verifiable offer gets an AI to trust your price enough to book it. That's the difference between being found and being chosen.

Two sides of the same table

A whole wave of standards is being built for agent commerce — and they all verify the buyer: that the agent is legitimate and really acting on a user's behalf. VRP stands on the other side and verifies the seller: that the price is real, that payment goes to the host, that the seller is who it claims to be. A real transaction needs both halves. VRP is the seller half that has been missing.

A footnote on payment rails

As agents start paying in new ways — stablecoins, agent wallets — VRP is designed to carry whichever rail applies. But the rail is the footnote. The verified offer is the point.

What it means for you

  • As a host: an AI will not book what it cannot verify. VRP makes you verifiable — so the agent can choose you, directly, at your own price.
  • For the technically minded: an Ed25519-signed offer bound to your did:web — curl-verifiable from your own domain, where any change along the way is detectable.

Don't take our word for it

This is live today on our first host's own domain. Fetch it yourself:

# the host's own DID and public key, on the host's own domain
curl https://villaakerlyckan.se/.well-known/did.json
curl https://villaakerlyckan.se/.well-known/jwks.json

# a signed stay offer — verify its signature against the key above
curl "https://villaakerlyckan.se/api/verified-stay-offer?check_in=2026-10-10&check_out=2026-10-17&guests=6"

The offer comes back signed (Ed25519 / JWS). Change a single byte and the signature no longer verifies. Anyone can check it against the host's own domain.

Your property becomes a VRP node on your own domain — that is where the agent finds you and verifies your offer.