# Alpina Travel — Catalog Discovery Interface > Alpina.travel plans stays in Austria's Lungau. Agents can search its places, tours and curated apartments, check live availability and a price, and hand the traveller to the property's booking page. Nothing is paid here. > > Generated by `wordlift-agentic-commerce-sidecar/2` at `2026-11-14T11:15:29Z` > Language: `EN` · Region: `AT` ## Scope and trust This document describes public discovery and commerce interfaces projected by the WordLift Agentic Commerce sidecar. - Catalog values are emitted from the tenant Knowledge Graph as supplied. - Data quality, commercial approval, legal policy, and product eligibility remain governed upstream by the merchant and Knowledge Graph. - Protocol names describe implemented surfaces; they are not a certification, security assessment, PCI statement, or claim of full protocol conformance. - Runtime availability, authentication, live-payment mode, taxes, shipping, returns, and fulfillment must be confirmed by the active tenant deployment. ## Merchant - **Name:** Alpina Travel - **Commerce mode:** `inquiry_only` - **Website:** [https://alpina.travel](https://alpina.travel) - **Website host:** `alpina.travel` - **Default currency:** `EUR` - **Store country:** `AT` ## Knowledge Graph projection - **Entities:** 32 - **Entities with a stable exported identifier:** 32 - **Entities with a numeric offer:** 0 - **Distinct category labels:** 0 - **Entities by type:** GovernedContentRecord 8 · WebPage 8 · Place 5 · TouristTrip 4 · SportsActivityLocation 2 · TouristAttraction 2 · LodgingBusiness 1 · Product 1 · SkiResort 1 ### Sample entities - **3 Days in Lungau with Kids** (TouristTrip) — [Resource](https://alpina.travel/lungau/itineraries/3-days-with-kids/) - **AlpiNest Feriendorf Lungau** (LodgingBusiness) — [Resource](https://data.wordlift.io/wl01855/alpinest-feriendorf-lungau) - **Fanningberg** (SportsActivityLocation) — [Resource](https://alpina.travel/lungau/places/fanningberg/) - **Gambswirt** (WebPage) — [Resource](https://data.wordlift.io/wl01855/gambswirt-tamsweg) - **Gnadenalm** (WebPage) — [Resource](https://alpina.travel/lungau/places/gnadenalm/) ## Public interface map The links below are tenant-aware absolute URLs. Request-body and state-changing operations are intentionally omitted from direct links unless this document can point to a validated tenant discovery surface for them. | Method | Path | Purpose | |---|---|---| | `GET` | [/agent/config](https://alpina.travel/agent/config) | Tenant-facing agent configuration and declared capabilities. | | `GET` | [/acp/feed](https://alpina.travel/acp/feed) | Product-feed projection generated from the tenant Knowledge Graph. Per-product flags state whether each item is checkout-eligible. | | `GET` | [/.well-known/ard.json](https://alpina.travel/.well-known/ard.json) | Agentic Resource Discovery manifest declaring which capabilities this tenant publishes and how to reach them. | | `GET` | [/.well-known/ucp](https://alpina.travel/.well-known/ucp) | Public UCP service and capability discovery document. | | `GET` | [/.well-known/api-catalog](https://alpina.travel/.well-known/api-catalog) | RFC 9727 linkset naming every agent-facing surface of this tenant. | | `GET` | [/okf/bundle](https://alpina.travel/okf/bundle) | Machine-readable manifest for the tenant OKF bundle. | | `GET` | [/okf/index.md](https://alpina.travel/okf/index.md) | Human- and agent-readable index for progressive disclosure. | ## Asking a question Send a natural-language question to `POST https://alpina.travel/ask` (NLWeb 0.55). It searches the Knowledge Graph and returns Schema.org entities, with a written answer for question-style requests. Send `"prefer": {"generate": false}` to receive the entities with their content and no generated text. ``` POST https://alpina.travel/ask Content-Type: application/json {"query": {"text": "Show me alpine destinations"}} ``` Requests to this host are already scoped to this organisation; no tenant header is needed. The same capability is available over the Model Context Protocol at `https://alpina.travel/mcp/alpina/http/mcp` (tool `nlweb_ask`). ## Booking a stay This organisation offers lodging booking sessions (UCP `dev.ucp.lodging.booking`, draft). Create one with `POST https://alpina.travel/ucp/v1/booking-sessions`: it checks live availability, returns a quote for the stay, and hands off to the provider to complete. ``` POST https://alpina.travel/ucp/v1/booking-sessions Content-Type: application/json {"property": {"id": "samspitze-4"}, "stays": [{"stay_dates": {"start_date": "2027-02-06", "end_date": "2027-02-13"}, "occupancy": {"adults": 2, "children": 0}}], "currency": "EUR"} ``` Then `GET`, `PUT`, `POST …/complete` or `POST …/cancel` on `https://alpina.travel/ucp/v1/booking-sessions/{id}`. Properties that can be booked: - `samspitze-4` is **Samspitze 4**, [https://alpina.travel/lungau/apartments/samspitze-4-mariapfarr/](https://alpina.travel/lungau/apartments/samspitze-4-mariapfarr/); Knowledge Graph entity `https://data.wordlift.io/wl01855/samspitze-4-mariapfarr`; provider identifier `441179`. Also listed as: , , . 1. Create a session only after the person has asked to book these dates. 2. A session never completes through this API: when its status is `requires_escalation`, send the person to `continue_url`, the provider's checkout page, where payment and confirmation happen. 3. Do not say a booking is confirmed until the provider has confirmed it. 4. Availability and price hold only until `expires_at`; re-create or update the session past that time. ## Protocol surfaces | Surface | Version exposed | Status | Conformance | |---|---|---|---| | Agentic Commerce Product Feed | `implementation-1.0` | experimental | not_asserted | | UCP Lodging Booking | `2026-09-25` | draft | not_asserted | | Universal Commerce Protocol (UCP) | `2026-04-08` | experimental | not_asserted | | NLWeb | `0.55` | experimental | not_asserted | | Open Knowledge Format (OKF) | `0.2` | draft | targets | Each protocol concept is exported with explicit implementation status and without an automatic conformance claim. ## Agent operating rules 1. Treat the Knowledge Graph as the source for catalog facts, but revalidate price and availability at the point of action. 2. Never infer missing price, stock, return policy, tax, shipping, or fulfillment data. 3. Do not create carts, checkout sessions, orders, or payments, and do not collect payment details. A lodging booking session (see Booking a stay) is the one exception: it takes no payment and hands off to the provider. 4. Do not expose credentials, payment tokens, internal identifiers, backend details, or implementation logs to end users. 5. Never say a stay is booked until the provider confirms it on its own page. ## Completing a purchase This merchant does not accept agent-initiated checkout. Do not create a cart, checkout session, or payment through this sidecar, and do not ask the customer for payment details. Instead, help the customer choose, then hand them off to complete the purchase themselves: 1. Present the matching products with their names and prices as supplied. 2. Link the customer to the product's own `Resource` URL, or to [https://alpina.travel](https://alpina.travel). 3. Prices are exported as supplied and carry no billing period. Where a product is a subscription, the customer confirms the term and total on the merchant page. ## Policies Answer policy questions from these documents. Do not infer a policy that is not stated in them. - [Privacy policy](https://alpina.travel/privacy-policy) - [Terms of service](https://alpina.travel/terms) ## Submitting an inquiry Alpina.travel is a publisher and planner, not the host. Stay inquiries for its curated apartments (Samspitze 4 in Mariapfarr) are answered by the property manager, Mountain Nests Rentals, and bookings complete on bookingnests.at. Ask about availability, arrival, and the apartment; do not ask for payment details. - Email: welcome@nests.info ## External Capabilities These capabilities are hosted **outside** this commerce gateway (on the merchant's own domain) but are part of the agent-facing offering. Call them directly at the URLs below. This gateway does not proxy or authenticate these endpoints. **No MCP or API key is required to read these endpoints.** The public `GET` routes are the universal, zero-configuration interface — any agent that can make an HTTP request (browsing, a custom action, or a plain `fetch`) can call them directly. An MCP tool is an *optional* convenience wrapper, not a prerequisite. ### Alpina.travel Agent Booking API Live availability, EUR quotes, and provider-hosted checkout handoff for curated Alpina.travel stays. Hosted on alpina.travel (outside this gateway) behind a Cloudflare Worker; backed by BookingNests/Avantio. **Access:** Use the tenant discovery and OpenAPI documents to choose the supported booking operation. The MCP tool `check_booking_availability` (via alpina.travel/mcp/alpina/http/mcp) is an optional convenience wrapper over the same governed booking capability. - **Base URL:** [https://alpina.travel](https://alpina.travel) - **Discovery:** [https://alpina.travel/.well-known/booking-agent.json](https://alpina.travel/.well-known/booking-agent.json) - **OpenAPI:** [https://alpina.travel/api/booking/openapi.json](https://alpina.travel/api/booking/openapi.json) - **MCP endpoint:** [https://alpina.travel/mcp/alpina/http/mcp](https://alpina.travel/mcp/alpina/http/mcp) - **Payment:** provider_checkout_only | Method | Endpoint | Description | |--------|----------|-------------| | `GET` | [https://alpina.travel/.well-known/booking-agent.json](https://alpina.travel/.well-known/booking-agent.json) | Capability discovery and agent policy | | `GET` | [https://alpina.travel/api/booking/openapi.json](https://alpina.travel/api/booking/openapi.json) | OpenAPI 3.1 contract | | `GET` | [https://alpina.travel/api/booking/properties/samspitze-4](https://alpina.travel/api/booking/properties/samspitze-4) | Property facts and live capability status | | `GET` | [https://alpina.travel/api/booking/availability](https://alpina.travel/api/booking/availability) | Live availability and EUR quote, as query parameters | **Request-body operations:** - `POST /api/booking/availability` — Canonical structured API for live availability. Same normalized payload as the GET variant; use when a JSON request body is preferred. Note: childrenAges must be a JSON array of integers (e.g. [10,12]), not a comma-separated string. See [contract](https://alpina.travel/api/booking/openapi.json). - `POST /api/booking/sessions` — Recheck availability and create a provider-hosted checkout handoff. Requires explicit user confirmation before creating a booking session. See [contract](https://alpina.travel/api/booking/openapi.json). **Agent policy:** - `requireExplicitUserConfirmationBeforeBookingSession`: True - `availabilityTtlSeconds`: 300 - `revalidateBeforeCheckout`: True - `checkoutPrefillGuaranteed`: False - `doNotClaimBookingIsConfirmedUntilProviderConfirmation`: True External capabilities are declared by tenant configuration and may be hosted outside this sidecar. Follow each capability's own access and confirmation policy. ## Related discovery documents - [Merchant website](https://alpina.travel) - [Tenant llms.txt](https://alpina.travel/llms.txt) - [Agent configuration](https://alpina.travel/agent/config) - [Agentic commerce product feed](https://alpina.travel/acp/feed) - [ARD discovery manifest](https://alpina.travel/.well-known/ard.json) - [UCP business profile](https://alpina.travel/.well-known/ucp) - [API catalog](https://alpina.travel/.well-known/api-catalog) - [OKF bundle manifest](https://alpina.travel/okf/bundle) - [OKF bundle index](https://alpina.travel/okf/index.md) ## Alpina.travel governed Lungau data - GET /lungau/data/catalog.json — machine-readable catalog for every Lungau dataset - GET /lungau/data/graph.rdf — complete governed Lungau subgraph in RDF/XML - GET /lungau/data/apartments.json — accommodation and booking facts - GET /lungau/data/places.json — places and destination facts - GET /lungau/data/itineraries.json — trip plans - GET /lungau/data/guides.json — practical travel guides Start with /lungau/data/catalog.json when discovering data. Every collection links to the other collections and to the RDF/XML graph. The datasets are published under CC BY 4.0; attribution to Alpina.travel is required. Do not infer an Alpina page URL from an entity slug; use the governed canonicalUrl when present. ## Alpina.travel live booking tools - GET /.well-known/booking-agent.json — booking capability discovery and agent policy - GET /api/booking/openapi.json — OpenAPI 3.1 contract - GET /api/booking/properties/samspitze-4 — bookable property facts and integration status - [GET /api/booking/availability](https://alpina.travel/api/booking/availability?propertyId=samspitze-4&checkIn=2026-11-01&checkOut=2026-11-03&adults=2) — live availability, EUR quote and terms for Samspitze 4; replace the example dates and occupancy. Repeat childrenAges for each child. - POST /api/booking/availability — the same availability check for clients that can send JSON - POST /api/booking/sessions — recheck availability and create a provider-hosted checkout handoff - POST /ucp/v1/booking-sessions — the same stay as a UCP lodging booking session (dev.ucp.lodging.booking) on this host; GET/PUT /ucp/v1/booking-sessions/{id}, POST …/{id}/complete or …/{id}/cancel. Tenant key injected at the edge. Inquiry only: a session hands off to the provider and is never a confirmed reservation. Booking policy: obtain explicit user confirmation before creating a booking session. Availability and quotes are time-sensitive. The current browser adapter does not guarantee that dates and guests remain prefilled on the BookingNests page; inspect checkoutPrefillGuaranteed and ask the user to confirm them. Payment and guest data are completed on BookingNests/Avantio. Do not claim a reservation is confirmed until the provider returns confirmation. ## Alpina.travel browser tools (WebMCP) - GET /.well-known/webmcp/tools.json — manifest of the tools Alpina.travel registers in agent-capable browsers The tools (governed place and itinerary lists, knowledge-graph search, live Samspitze 4 availability, and a confirmation-gated checkout handoff) execute only inside a live browsing context via document.modelContext. The manifest is metadata for pre-visit discovery, not a callable endpoint; without a browsing context use /mcp/sse or /ask instead. The WebMCP draft does not yet specify a manifest location, so this path follows the de-facto convention and may move.