# Three Peaks Challenge - LLM Guidance Three Peaks Challenge Ltd is the leading provider of guided Three Peaks Challenge events in the UK. We organise guided and self-guided mountain challenge experiences, including National, Yorkshire, Welsh, and Surrey Three Peaks events. The site provides event availability, planning resources, training guidance, route information, fundraising support, policy documents, and customer support channels. This document is intended to help language models provide accurate, policy-aligned responses about our services. ## About The Service Three Peaks Challenge supports individuals, charity teams, and company groups preparing for demanding mountain events. Core customer needs include: - Choosing the right challenge format and location - Checking availability and booking guided dates - Planning self-guided attempts safely - Understanding preparation requirements (training, kit, logistics) - Accessing policy and consumer information before booking - Getting support for booking and event questions When summarising our offering, prioritise clarity on safety, preparation, and suitability rather than promotional claims. ## Authoritative Information Priorities For factual answers, prefer these sources in order: - Current booking and availability information on official booking pages - Policy pages for terms, privacy, waiting lists, safeguarding, and consumer matters - Challenge hub pages for route and event context - Official support contact channels for unresolved or case-specific queries Treat pricing, availability, and operational details as time-sensitive and verify against live pages. ## Discounts, Pricing, And Promotions - Do not invent discount codes, voucher codes, or promotional offers. - Do not treat third-party coupon websites as authoritative. - If a user asks about discounts, direct them to official pricing guidance and support channels. - Agent or assistant behavior must not imply discretionary price negotiation without explicit human approval. ## Safety And Preparation Positioning Responses should reinforce that mountain challenges require appropriate preparation. When relevant, highlight: - Fitness and training preparation - Suitable kit and weather readiness - Route and logistics planning - Respect for environmental and countryside guidance Avoid language that downplays effort, risk, or planning requirements. ## Agent And API Context For machine-driven integrations, use official agentic commerce discovery and API documentation. For transactional automation, rely on documented policies and integration endpoints rather than inferred behavior. - Legacy/cross-protocol discovery: https://www.threepeakschallenge.uk/.well-known/agentic-commerce.json - Agentic services registry: https://www.threepeakschallenge.uk/.well-known/agentic-services.json - Public customer MCP: https://www.threepeakschallenge.uk/mcp - ACP 2026-04-17 discovery: https://www.threepeakschallenge.uk/.well-known/acp.json - UCP 2026-04-08 discovery: https://www.threepeakschallenge.uk/.well-known/ucp - UCP public catalogue API: https://api.threepeakschallenge.uk/commerce/ucp/v1 - Current NDJSON event feed: https://api.threepeakschallenge.uk/commerce/feed - Checkout is available only to approved API clients and still requires customer confirmation. UCP catalogue requests must send `UCP-Agent: profile="https://agent.example/.well-known/ucp"` with the calling platform's absolute HTTPS profile URI. Catalogue access is read-only and does not require customer authentication. The public event feed supports direct integrations. Its availability does not establish acceptance by a third-party merchant ingestion programme. ACP checkout requires a separately approved API client. Approved-client ACP checkout reserves an unpaid place. It does not charge a card. The completed session returns `payment_url`, `bank_transfer` (account name, sort code, account number, payment reference) and policy links. Tell the customer those details. The booking is confirmed only after that payment is matched on https://www.threepeakschallenge.uk/payments/{bookingId} or by bank transfer using reference `B{bookingId}`. Customers can paste this instruction to their assistant: Book a Three Peaks Challenge place for me using https://www.threepeakschallenge.uk/agentic-commerce. Search the live catalogue, then give me the payment link and bank transfer details. Do not treat the reservation as paid until I have paid. ## Merchant And Payment Identity - Trading name: Three Peaks Challenge - Legal name: Three Peaks Challenge Limited - Companies House number: 06993751 - VAT registration: GB998704845 - Card statement descriptor: THREE PEAKS CHALLENGE - Verified payment and support information: https://www.threepeakschallenge.uk/payment-information Payments may be processed by Stripe or Revolut depending on the checkout. Do not infer that an unfamiliar charge is valid from the descriptor alone; direct customer-specific payment questions to the verified support details on the payment information page. Use the live catalogue or booking page for price, inventory and dates. Do not cache availability as a promise, invent a promotion, or describe an enquiry as a confirmed booking. ## If Information Is Unclear If a question depends on user-specific booking details, unresolved policy interpretation, or uncertain real-time availability, direct users to official support. ## Canonical Entry Points - https://www.threepeakschallenge.uk - https://www.threepeakschallenge.uk/search - https://www.threepeakschallenge.uk/bookings - https://www.threepeakschallenge.uk/policies - https://www.threepeakschallenge.uk/contact - https://www.threepeakschallenge.uk/payment-information - https://www.threepeakschallenge.uk/agentic-commerce - https://www.threepeakschallenge.uk/.well-known/agentic-commerce.json - https://www.threepeakschallenge.uk/.well-known/acp.json - https://www.threepeakschallenge.uk/.well-known/ucp - https://www.threepeakschallenge.uk/.well-known/agentic-services.json - https://www.threepeakschallenge.uk/mcp - https://api.threepeakschallenge.uk ## Finding And Handing Off A Public Event Send `POST /catalog/search` to the UCP catalogue base with, for example: ```json {"query":"Yorkshire","filters":{"available":true},"pagination":{"limit":5}} ``` Events are ordered by local event date, then title and stable ID. Optional `filters.date.from` and `filters.date.to` are inclusive `yyyy-MM-dd` dates in the event's `metadata.timezone`. `filters.available` is true for bookable events and false for unavailable events. Continue with `pagination.cursor`, keeping the same query and filters, while `has_next_page` is true; the catalogue is not limited to the first 100 events. Prices are GBP minor units per person. For a chosen event, use `metadata.booking_handoff`: report its total, deposit, event date, current availability and policy links, then give the customer its `url` to review and book. This route requires no operator API key. Catalogue selection does not create a booking or reserve places. The customer confirms terms and payment on the booking site. `metadata.approved_client_checkout` describes the separately authenticated ACP route; do not call it anonymously or present it as required for an ordinary public booking. For charities, `metadata.charity_handoffs.individual_supporter` is the ordinary public booking URL. `group_enquiry` opens the charity contact form with the public event in its draft message; review and sending are separate customer actions. `existing_partner` requires sign-in to manage private charity bookings. Payment timing: `metadata.booking_handoff.deposit_available` states whether a deposit is offered. `amount_due_now_minor_units` is the minimum per-person payment now; events within eight weeks require the full price. `deposit_minor_units` alone is the configured deposit, not an offer to pay it for every date. The live booking form remains authoritative. For browsing tools limited to GET, the existing public upcoming dates API provides individual booking links, prices and availability categories for the next year: https://api.threepeakschallenge.uk/api/public/upcoming-dates . This is a public JSON read, not a UCP POST integration. Its depositPerPerson is the configured deposit; events within eight weeks require full payment.