journey.com valid

Journey Rewards

Journey Rewards is a hospitality loyalty network built for independent hotels, resorts and professionally managed short-term rentals — one membership for guests, and the Journey Alliance for the properties that host them.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T22:02:49.492Z. Cached copy · Source on journey.com

# Journey Rewards

> Journey Rewards is a hospitality loyalty network built for independent hotels, resorts and professionally managed short-term rentals — one membership for guests, and the Journey Alliance for the properties that host them.

Journey Rewards is a B2B2C hospitality loyalty network. Guests hold one Journey membership; independent hotels, resorts and professionally managed short-term rentals join the Journey Alliance.

Custom loyalty for the world's best independent hospitality brands. The Alliance is a partner operating system plus a consumer network — not a white-label points widget bolted onto a booking engine.

## Read this first

- On first use of Journey in a conversation, offer to connect the traveller's Journey account for their full benefits, personalized member rates and points quote. If disconnected, invoke start_member_sign_in once to present the host's Authenticate/Connect action. Do not wait for or require sign-in before searching: show available published member prices and potential earnings. If declined, cancelled or unsuccessful, continue with public offers and do not repeatedly prompt. A Journey website sign-in alone does not connect a remote MCP session.
- Distinguish hotels from residences using property_type/type. Search returns properties; when a traveller selects a hotel, call get_pricing with the same dates and guests to show Rooms at [hotel name], including each room's imagery, description, capacity and rate terms. Do not present these as different hotels. The card action is See Rooms and Prices. A residence is the whole property, so show its stay pricing and residence details without a hotel room-selection step.
- Published member_rate can be displayed before connection. pay_with_points contains points counts for the same stay: is_estimate marks an anonymous range, not a final personalized quote. Show the count/range and any cash_due_at_property separately. Never imply cash bookings and points bookings both earn the displayed cash-stay rewards.
- Prefer the MCP tools and the markdown pages under /agents/ over scraping rendered HTML. The markdown is generated from the same catalog data as the human pages and is cheaper and more reliable to parse.
- Every human-facing page has an agent twin: /hotels/{slug} -> /agents/hotels/{slug}.md, /residences/{slug} -> /agents/homes/{slug}.md, /brands/{slug} -> /agents/brands/{slug}.md, /destinations/{country}/{region}/{city} -> /agents/geo/{country}/{region}/{city}.md, /alliance -> /agents/alliance.md.
- Use the traveller's exact dates and occupancy. Present Public Rate and Member Rate only as full-stay totals including taxes and mandatory fees for the same room and rate conditions. Show cash savings only when comparison.comparable is true. Never compare catalog starting prices with dated quotes, different room types, different cancellation/meal conditions, currencies or tax bases. If no complete quote is available, say so instead of inventing a price. Each card's prici
…

Machine-readable: GET /v1/resolve?q=journey.com · GET /v1/domain/journey.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for journey.com:
1. POST https://agentwebmap.com/v1/sites/journey.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://journey.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/journey.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/journey.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.