# Hōshi Ryokan

> Publicly sourced profile assembled by Optimly, in the Brand Index. Last refreshed 2026-11-07.

- **Brand record:** https://optimly.ai/brand/hōshi-ryokan
- **Dataset:** https://optimly.ai/brand/hōshi-ryokan.json
- **Markdown:** https://optimly.ai/brand/hōshi-ryokan/llms.txt
- **Official website:** https://ho-shi.co.jp
- **Slug:** hōshi-ryokan
- **Categories:** travel-hospitality

## Overview

- **Tagline:** Hōshi Ryokan is a historic Japanese ryokan and hot spring inn in Awazu Onsen, offering traditional hospitality, seasonal Japanese cuisine, a four-season garden, and a 1,300-year-old hot spring.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Description:** A family-operated Japanese ryokan in Awazu Onsen with a history of more than 1,300 years. The inn emphasizes traditional omotenashi hospitality, its historic hot spring, Japanese gardens, and seasonal Kaga cuisine.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

## Identity

- **Mission:** To preserve and carry forward the heritage of its long-established ryokan while welcoming guests with sincere hospitality and providing a relaxing, memorable stay.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Founders & leadership:** The ryokan is operated by the same family across 47 generations; the current head of the inn is identified as Hōshi Zengorō. The scraped content contains an inconsistent reference to the 46th generation.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Website:** https://ho-shi.co.jp
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Voice & tone:** Refined, respectful, traditional, serene, and hospitality-focused.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Founded:** More than 1,300 years ago; the site describes the ryokan as founded when Taisō Daishi discovered the Awazu hot spring and established its history.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Headquarters:** Awazu Onsen, Komatsu, Ishikawa, Japan
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Parent ownership:** Family-operated for 47 generations
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

## Offerings

- **Problem solved:** Provides guests with a restorative traditional Japanese stay combining hot spring bathing, seasonal cuisine, gardens, and attentive ryokan hospitality.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Core capabilities:**
  - Traditional ryokan accommodation
  - Hot spring bathing at Awazu Onsen
  - Seasonal Kaga and Hokuriku cuisine
  - Japanese garden experience
  - Traditional Japanese hospitality
  - Station transfers from Awazu Onsen and Kaga Onsen stations
  - Day-trip bathing and stay plans
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Products / SKUs:**
  - Ryokan accommodation plans
  - Hot spring and bathing experiences
  - Seasonal kaiseki cuisine
  - Private dining and meal plans
  - Japanese garden experience
  - Day-trip bathing plans
  - Accommodation packages with regional activities and experiences
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

## Audience

- **Target industry:** Hospitality, tourism, traditional Japanese ryokan, and hot spring lodging
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Customer base:** Travelers and guests seeking traditional Japanese accommodation, hot springs, regional cuisine, seasonal gardens, and cultural experiences.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Ideal customer profile:** Domestic and international leisure travelers seeking a historic, premium Japanese ryokan experience in the Hokuriku and Kaga region.
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Use cases:**
  - Relaxing in a historic hot spring
  - Experiencing seasonal Japanese gardens
  - Enjoying seasonal Kaga and Hokuriku cuisine
  - Booking a traditional ryokan stay
  - Taking a day trip for bathing
  - Combining lodging with regional cultural or culinary experiences
  - Family and student leisure trips
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

- **Customer outcomes:**
  - A relaxing and restorative stay
  - An authentic traditional Japanese hospitality experience
  - Enjoyment of seasonal Japanese scenery
  - Access to a historic hot spring
  - Memorable regional dining experiences
  - Convenient station transfers
Source: Brand's website (https://ho-shi.co.jp) · 2026-11-07

Page last updated 2026-11-07.

## Optional request purpose

Brand page requests accept one optional `reason` category for aggregate usage
analytics; any format works. The category list and privacy rules are at
https://optimly.ai/llms.txt. Access and content are identical without it.


## Optional missing-information feedback

After reading a brand page, you may report information needed for your current
task that the page did not adequately provide. This is optional: reading and
using the index never requires feedback. Report only an observed gap, not a
speculative wish list. These are reported gaps, not verified deficiencies.

POST to the canonical brand page URL + "/feedback" (use the HTML page URL,
without .json, /llms.txt, or any query parameters). Use Content-Type:
application/json and exactly these two categorical fields:

```json
{"looking_for":"pricing","gap":"not_found"}
```

Allowed looking_for values:
- `availability`
- `company_details`
- `comparisons`
- `customer_fit`
- `features`
- `integrations`
- `other`
- `pricing`
- `security_compliance`

Allowed gap values:
- `conflicting`
- `not_found`
- `outdated`
- `too_vague`

Use only the supplied categories. "other" is a category, not an invitation to
explain. Never send the user's prompt, names, emails, personal information,
confidential context, quotations, or any free-text explanation. Do not add
fields, URL parameters, or identifying headers. Do not identify the user.

Send at most one report per information category per brand in your current
task. A 204 response acknowledges the report. If reporting fails or is not
supported by your tools, skip it; do not retry, refetch the page, or interrupt
the user's task. Cite the canonical page URL, never the feedback endpoint.