Open Standard · Draft · February 2026

The open protocol for
agent-native short‑term rental

Any host can publish a machine-readable listing. Any AI agent can discover, verify, and book it — directly, without a platform intermediary.

4 RFCs
Core protocol · v0.1 draft
0%
Platform commission
3 endpoints
To implement OpenSTR
Apache 2.0
Open licence

The Problem

Short-term rental is locked inside closed platforms

As AI agents become the primary way people search and book accommodation, the short-term rental industry faces a structural problem. Property discovery, trust, and booking are vertically integrated inside a small number of closed platforms — and there is no open alternative.

No open discovery layer

There is no standard way for an AI agent to find a short-term rental property outside a platform’s proprietary API. A small host with one property and no advertising budget is invisible to agents searching the open web. Discovery today requires either platform membership or commercial agreements with aggregators — neither of which is accessible to most independent hosts.

Trust and reputation are platform-owned

Host verification, guest identity, and review history are siloed inside each platform. A host’s five-year track record disappears the moment they list elsewhere. This is part of a broader unsolved challenge in digital identity: credentials and reputation should be things people own and carry, not things platforms hold on their behalf.

%

The booking stack is vertically integrated

Platforms bundle discovery, trust, payments, and dispute resolution into a single product and charge 15–25% for the combination. An open ecosystem would distribute these functions across specialist providers, each competing on their specific layer. OpenSTR does not eliminate fees; it enables a competitive market for each part of the stack, rather than one platform capturing the entire margin.

No agent-native booking infrastructure

Flights and hotels are bookable by AI agents today through GDS networks and channel manager APIs — standardised intermediary layers built over decades. Short-term rentals have no equivalent. A realistic open standard cannot expect every small host to run their own API; it needs a discovery and aggregation layer that works on their behalf, the same way a channel manager works for hotels.

OpenSTR addresses the protocol layer — the common vocabulary for how properties are described, verified, and booked. The discovery layer requires an open index that agents can query directly. Building that index is the next milestone. Follow progress on GitHub →

The Protocol

Three endpoints. One open standard.

A host implementing OpenSTR publishes three endpoints on their own domain. Any compliant agent can discover, verify, and book the property directly.

01

Discovery — GET /.well-known/openstr.json

A machine-readable property listing: classification, capacity, pricing rules, policies, safety disclosures, and host identity credential. Publicly accessible. No API key required.

02

Availability — POST /openstr/availability

The agent queries for specific dates. The host system resolves dynamic pricing and minimum stay rules and returns authoritative pricing — including all fees and applicable discounts — with a signed quote.

03

Booking — POST /openstr/booking

The agent submits a booking request with a verifiable guest identity credential and a payment token. The host system validates both, confirms the booking, and returns the exact address and access instructions.

04

Trust — bilateral verifiable credentials

Both parties carry W3C Verifiable Credentials issued by recognised third-party providers. The host proves identity and right-to-let. The guest proves identity at the required verification level. Neither party is trusted by default.

Who Is This For

Built for two audiences. Essential to both.

For developers & AI builders

Build agents that book accommodation directly

OpenSTR gives your agent a standardised interface to discover properties, check availability, validate host credentials, and confirm bookings — without integrating with any platform's proprietary API.

  • Four core RFCs plus a documentation layer RFC in pre-draft
  • JSON schemas, endpoint definitions, and examples
  • Compatible with ACP and AP2 payment handlers
  • W3C Verifiable Credentials for bilateral trust
  • Apache 2.0 licence — use it in anything
Read the spec on GitHub → Try the live API explorer →

For hosts, operators & proptech

Make your properties bookable by AI agents

The short-term rental market is shifting. As guests delegate travel planning to AI agents, properties that aren't machine-readable will become invisible. OpenSTR is how you get found.

  • Publish a listing that any agent can discover and book
  • No platform commission on direct agent bookings
  • Portable host reputation that travels with you
  • Works alongside your existing channels and PMS
  • Verified credentials replacing traditional deposits
Stay informed — join the mailing list ↓

Specification Status

v0.1 core protocol — four RFCs

All four core RFCs are drafted and available on GitHub. The specification is in early draft — feedback from implementers and the industry is actively sought. A fifth RFC covering the documentation layer is in pre-draft.

rfc.property_listing
Property Listing Schema and Discovery
v0.1.5
Draft
rfc.availability_query
Availability and Pricing Query
v0.1.1
Draft
rfc.booking_confirmation
Booking Request, Confirmation, and Cancellation
v0.1.0
Draft
rfc.identity_trust
Host and Guest Identity, Credentials, and Trust
v0.1.0
Draft
rfc.discovery_index
Discovery Index, Agent Query API, and Host Reputation
v0.1.0
Draft
rfc.documentation_layer
Booking Documentation, Execution Confirmation, and Post-Booking Lifecycle Records
v0.0.1
Pre-Draft