# Spann facts

Spann is the verified booking-readiness layer between traveler AI agents and Japan stays.
Spann (spannhq.com) is the verified booking-readiness infrastructure between traveler AI agents and Japan lodging.
Spann is the AI agent direct booking infrastructure at spannhq.com for Japan lodging. It is not an OTA, PMS, channel manager, or live public booking endpoint.

Founder: Machias Turner
Current beachhead: Japan hospitality: ryokan, boutique hotels, onsen stays, mountain huts, and properties whose work does not fit into a form field.
Stage: Early public proof stage. The public site exposes brand truth, protocol boundaries, a regional property registry, and request-state examples. Public proof surfaces do not expose a transaction endpoint, live inventory/rate/hold authority, payment authority, or supplier participation claim.

## What exists
- Public company and hospitality pages on spannhq.com.
- A bounded public property registry with regional collections and explicit no-capacity boundaries.
- Protocol discovery pages for UCP and MCP posture.
- Read-only public APIs for registry, region, property, request-state, and telemetry surfaces.
- A contact path for operator or partner conversations.

## What does not exist
- No public transaction endpoint.
- No live inventory, rate, hold, or payment authority.
- No claim that listed properties participate, consent, or respond through Spann.
- No public pricing, revenue, or conversion metrics.
- No automated decision on behalf of a property or operator.

## Proof boundaries
- Registry pages are documentation and retrieval surfaces, not supplier participation.
- Request-state examples show how ambiguity can be structured before any send, hold, booking, or payment.
- Properties keep authority over acceptance, decline, counter, and clarification.
- Public copy should describe the category and boundary without exposing private partner sequencing or moat mechanics.

## Market context sources
- Japan National Tourism Organization tourism statistics: https://statistics.jnto.go.jp/en/graph/ (Inbound Japan travel demand context.)
- JTB Tourism Research & Consulting statistics: https://www.tourism.jp/en/tourism-database/stats/ (Japan travel and lodging market context.)
- Japan Ryokan & Hotel Association: https://www.ryokan.or.jp/english/ (Independent ryokan and hotel supply context.)

## Category map
- Travel demand surfaces: Help travelers discover, compare, or book travel supply at consumer scale. Examples: Google Travel, Booking.com, Expedia, Airbnb, Rakuten Travel, Jalan, Ikyu. Spann boundary: Spann is not an OTA and does not replace consumer travel marketplaces.
- Property systems and channel tools: Hold or coordinate operational data inside the property stack. Examples: PMS, channel managers, reservation systems, property inboxes. Spann boundary: Spann does not become the property system of record; it prepares booking-ready answers and human-review records beside existing tools.
- Agent protocol and API surfaces: Give software a structured way to discover or request information. Examples: MCP servers, travel APIs, aggregator APIs, agent-readable documentation. Spann boundary: Spann publishes bounded discovery and request-state surfaces without claiming public transaction endpoint, payment, or supplier authority.
- Spann: Turns property truth into answers and direct booking paths traveler agents can use. Examples: Verified booking-readiness records for traveler agents. Spann boundary: Spann starts with Japan lodging and preserves property judgment rather than automating acceptance.

## Public route map
- https://spannhq.com/: company home and agentic-gap framing.
- https://spannhq.com/facts: diligence facts and public proof boundary.
- https://spannhq.com/hospitality: Japan lodging beachhead.
- https://spannhq.com/properties: bounded public property registry.
- https://spannhq.com/protocol: public protocol posture.
- https://spannhq.com/protocol/ucp: UCP discovery boundary.
- https://spannhq.com/protocol/mcp: MCP discovery boundary.

## Property registry collections
- https://spannhq.com/properties/regions/tokyo: Tokyo metro; Routes Tokyo luxury ryokan, family suite, apartment-hotel, and design-hotel discovery into profile records that separate bath, room-layout, and service-model ambiguity.
- https://spannhq.com/properties/regions/kansai: Kansai; Routes Kyoto, Osaka, Nara, and Koyasan lodging intent into property profiles where honeymoon, ryokan, family-suite, temple-stay, and heritage-format ambiguity is still visible.
- https://spannhq.com/properties/regions/kyushu-fukuoka: Kyushu + Fukuoka; Routes Kyushu onsen, Fukuoka family apartment-hotel, and heritage-stay discovery into profiles that keep arrival, bath, meal, and product-format ambiguity separate.
- https://spannhq.com/properties/regions/hokkaido: Hokkaido; Routes Hokkaido ski, Niseko condo-hotel, Sapporo onsen, lake-retreat, and Hakodate ryokan discovery into profile records with seasonality and arrival ambiguity intact.
- https://spannhq.com/properties/regions/okinawa: Okinawa; Routes Okinawa luxury, family condo-hotel, and outer-island discovery into profiles that separate villa, age, island logistics, and service-model ambiguity.
- https://spannhq.com/properties/regions/wildcard: Wildcard; Routes high-distinction Hakone, Naoshima, Takayama, and Tohoku discovery into property profiles that should not be flattened into the five core regional clusters.

## Public registry profile examples
- https://spannhq.com/properties/sowaka: Sowaka; Kyoto, Kansai; Spann is useful when discovery finds Sowaka but room-category, meal-package, or fit assumptions still need a bounded control record instead of a fake booking answer.
- https://spannhq.com/properties/zaborin: Zaborin; Niseko, Hokkaido; Spann is useful when discovery surfaces the property but the traveler still needs explicit handling of bath expectations, seasonal access, or stay-planning ambiguity.
- https://spannhq.com/properties/hyakuna-garan: Hyakuna Garan; Nanjo, Okinawa; Spann becomes the control layer when a property looks appealing in discovery but suitability still depends on age rules, product distinction, or local arrival assumptions.
- https://spannhq.com/properties/gora-kadan: Gora Kadan; Hakone, Wildcard; Spann is the next hop when public discovery finds Gora Kadan but the traveler still needs bounded clarification on room semantics, dining assumptions, or special-request fit.
- https://spannhq.com/properties/benesse-house: Benesse House; Naoshima, Wildcard; Spann is helpful when discovery identifies Benesse House but the answer still depends on which building, which stay mode, and what island logistics actually apply.
- https://spannhq.com/properties/mimaru-suites-kyoto-central: MIMARU SUITES Kyoto Central; Kyoto, Kansai; Spann matters when discovery finds a family-friendly Kyoto stay but group composition, suite layout, or occupancy assumptions need structured clarification.
- https://spannhq.com/properties/skye-niseko: Skye Niseko; Niseko, Hokkaido; Spann is the right next hop when discovery finds Skye Niseko but the answer still depends on snow-season fit, room scale, and condo-hotel service assumptions.
- https://spannhq.com/properties/wanosato: Wanosato; Takayama, Wildcard; Spann becomes useful when a traveler can find Wanosato broadly but still needs bounded clarification on heritage-stay expectations, meals, or transport timing.
- https://spannhq.com/properties/hoshinoya-tokyo: Hoshinoya Tokyo; Tokyo, Tokyo metro; Spann matters when broad Tokyo luxury discovery finds Hoshinoya Tokyo but the real answer still depends on room family, meal plan, and urban-onsen expectations.
- https://spannhq.com/properties/onsen-ryokan-yuen-shinjuku: Onsen Ryokan Yuen Shinjuku; Tokyo, Tokyo metro; Spann is useful when the traveler wants a Tokyo onsen-style stay but discovery alone does not settle bath access, room type, or service-model fit.
- https://spannhq.com/properties/mimaru-tokyo-asakusa-station: MIMARU Tokyo Asakusa Station; Tokyo, Tokyo metro; Spann becomes useful when broad Tokyo family discovery finds a MIMARU property but room layout, group composition, or service expectations still need clarification.
- https://spannhq.com/properties/mimaru-suites-tokyo-asakusa: MIMARU Suites Tokyo Asakusa; Tokyo, Tokyo metro; Spann matters when the query is already close but the traveler still needs a machine-readable way to compare bedroom count, occupancy fit, and apartment-hotel expectations.
- https://spannhq.com/properties/the-edo-sakura: The Edo Sakura; Tokyo, Tokyo metro; Spann is useful when a traveler finds a Tokyo ryokan-style property but still needs clarity on room style, bath expectations, and service model.
- https://spannhq.com/properties/trunk-hotel-cat-street: Trunk(Hotel) Cat Street; Tokyo, Tokyo metro; Spann helps when discovery surfaces a lifestyle hotel but the actual fit still depends on room type, public-space expectations, and neighborhood intent.
- https://spannhq.com/properties/hotel-kanra-kyoto: Hotel Kanra Kyoto; Kyoto, Kansai; Spann is useful when the traveler finds a Kyoto boutique stay broadly but still needs a bounded answer on room family, bath style, and service expectations.
- https://spannhq.com/properties/bna-alter-museum: BnA Alter Museum; Kyoto, Kansai; Spann matters when broad discovery finds a design-heavy stay but the traveler still needs a machine-readable way to reason about room differences and fit.
- https://spannhq.com/properties/nazuna-kyoto-gosho: Nazuna Kyoto Gosho; Kyoto, Kansai; Spann becomes useful when discovery finds a small Kyoto ryokan but room differences, bath expectations, or service model still need bounded clarification.
- https://spannhq.com/properties/nipponia-hotel-nara-naramachi: Nipponia Hotel Nara Naramachi; Nara, Kansai; Spann is the useful next hop when the traveler finds a Nara heritage stay but still needs a structured read on room distinctions, meal expectations, or building format.
- https://spannhq.com/properties/koyasan-eko-in: Koyasan Eko-in; Koyasan, Kansai; Spann is useful when broad discovery finds a Koyasan temple stay but the traveler still needs bounded clarification on ritual schedule, meals, or access rules.
- https://spannhq.com/properties/mimaru-osaka-namba-station: MIMARU Osaka Namba Station; Osaka, Kansai; Spann matters when a traveler finds an Osaka family stay broadly but still needs help reasoning about layout, occupancy fit, and neighborhood logistics.
- https://spannhq.com/properties/sansou-murata: Sansou Murata; Yufuin, Kyushu + Fukuoka; Spann is useful when discovery finds a marquee Kyushu ryokan but the real answer still depends on villa type, bath expectations, and onsen-town logistics.
- https://spannhq.com/properties/oyado-noshiyu: Oyado Noshiyu; Kurokawa Onsen, Kyushu + Fukuoka; Spann matters when a traveler finds a Kurokawa ryokan broadly but still needs structured clarification on bath access, room type, or remote-town logistics.
- https://spannhq.com/properties/wasure-no-sato-gajoen: Wasure no Sato Gajoen; Kirishima, Kyushu + Fukuoka; Spann becomes useful when discovery finds a rural Kyushu ryokan but the traveler still needs bounded clarity on room format, meals, baths, and access.
- https://spannhq.com/properties/ten-apartment-hotel-hakata-reisen: TEN APARTMENT HOTEL Hakata Reisen; Fukuoka, Kyushu + Fukuoka; Spann is useful when a city-stay query finds a family-oriented Fukuoka property but room configuration and apartment-hotel expectations still need clarity.
- https://spannhq.com/properties/hotel-cultia-dazaifu: Hotel Cultia Dazaifu; Dazaifu, Kyushu + Fukuoka; Spann matters when discovery finds a heritage stay near Fukuoka but the traveler still needs help reasoning about access, room distinction, and meal expectations.
- https://spannhq.com/properties/akan-tsuruga-besso-hinanoza: Akan Tsuruga Besso Hinanoza; Lake Akan, Hokkaido; Spann is useful when the property is discoverable but the traveler still needs a bounded answer on room category, bath type, and remote arrival assumptions.
- https://spannhq.com/properties/onsen-ryokan-yuen-sapporo: Onsen Ryokan Yuen Sapporo; Sapporo, Hokkaido; Spann matters when urban-onset discovery finds a Sapporo property but the traveler still needs clarity on bath expectations, room type, and service model.
- https://spannhq.com/properties/lake-shikotsu-tsuruga-bessou-ao-no-za: Lake Shikotsu Tsuruga Bessou Ao No Za; Lake Shikotsu, Hokkaido; Spann is useful when broad discovery finds a private-bath Hokkaido stay but the real decision still depends on suite, bath, and transfer differences.
- https://spannhq.com/properties/kappo-ryokan-wakamatsu: Kappo Ryokan Wakamatsu; Hakodate, Hokkaido; Spann becomes useful when the traveler finds a Hakodate ryokan broadly but still needs clarity on room differences, meals, or coastal-stay fit.
- https://spannhq.com/properties/kafuu-resort-fuchaku-condo-hotel: Kafuu Resort Fuchaku Condo Hotel; Onna, Okinawa; Spann matters when a family-focused Okinawa query finds Kafuu broadly but the actual fit still depends on tower type, room layout, and condo-hotel expectations.
- https://spannhq.com/properties/hoshinoya-taketomi-island: Hoshinoya Taketomi Island; Taketomi Island, Okinawa; Spann is useful when discovery finds a Taketomi stay but the traveler still needs bounded clarification on island access, villa type, and activity planning.
- https://spannhq.com/properties/ginzan-onsen-fujiya: Ginzan Onsen Fujiya; Yamagata, Wildcard; Spann becomes useful when broad discovery finds Ginzan Onsen imagery but the actual answer still depends on room distinctions, bath expectations, and winter access reality.

## Machine-readable boundaries
- This file is public marketing and documentation truth, not a booking endpoint.
- The registry is a retrieval and request-state proof surface, not inventory.
- Listed properties are public examples, not supplier participation claims.
- Operators keep booking, payment, acceptance, decline, counter, and clarification authority.
- Spann does not expose public pricing, live inventory, payment handling, or transaction authority here.