Where it sits
A stay-domain layer on the agent stack, not another identity protocol.
Identity & consentPersonal Agent Protocol: who the agent is, what the traveller allowed
StaysLivStay (Poppy extension livstay.org/stays): facts, quotes, enquiries, bookings, protection, trust
TransportMCP and OpenAPI over HTTPS
PaymentAgent payment rails, as they mature
// /.well-known/poppy.json on a host's operator domain (excerpt)
{
"protocol_version": "0.2",
"apis": [{ "type": "mcp", "url": "https://stays.example/livstay/v0/mcp" }],
"auth": { "custom_scopes": {
"livstay:book": "Book, change and cancel stays you approve" } },
"extensions": {
"operations": { "version": "1", "endpoint": "https://stays.example/poppy/operations" },
"livstay.org/stays": { "version": "0", "revision": "0.2", "endpoint": "https://stays.example/livstay/v0", "level": 3 }
}
}
LivStay draft 0.2 is written as an extension to Personal Agent Protocol draft 0.2: identity, sessions and conversations are Poppy’s, and every booking is a Poppy operation that the traveller approves. It is designed to work with that protocol. It is an independent project, not affiliated with or endorsed by that protocol’s authors or partners.