# TrekGuider

> Digital products marketplace for travel: guides, maps, itineraries, files and subscriptions from creators worldwide, plus Travel Insights articles.

Last reviewed: 2026-10-12
Canonical site: [trekguider.com](https://trekguider.com)

This file is a public orientation summary for AI assistants and browser agents. It is not a robots directive, not a sitemap, and not a replacement for the HTML pages, their structured data or the policies.

## Primary Links

- [Homepage](https://trekguider.com)
- [All products](https://trekguider.com/products): digital travel products (guides, maps, itineraries and more) from experienced creators.
- [Travel Insights](https://trekguider.com/insights): travel guides, tips and stories from creators.
- [Creators](https://trekguider.com/creators): browse creators by language, country, platform and more.
- [Become a creator](https://trekguider.com/sellers): sell travel products on TrekGuider.
- [Help Center](https://trekguider.com/help-center): answers about buying, selling, payments and more.
- [Referral program](https://trekguider.com/referral)
- [Partners and investors](https://trekguider.com/investments)
- [All policies](https://trekguider.com/policies-all): Terms and Conditions, Privacy Policy, Cookie Policy, Seller Agreement and more.
- [Sitemap](https://trekguider.com/sitemap.xml)
- [Robots](https://trekguider.com/robots.txt)

## Agent registration and purchases

TrekGuider supports buyer-purpose OAuth/MCP and a staged Machine Payments Protocol integration. Check [agent commerce discovery](https://trekguider.com/.well-known/agent-commerce) for the currently enabled capabilities; a missing document or disabled flag means the capability is unavailable. [Agent buying instructions (plain text)](https://trekguider.com/agent-guide) explain registration, owner approval, spending limits and payment continuation.

When enabled, a registered public OAuth client may request a new buyer account with exact terms/privacy acceptance and explicit email ownership proof. Existing accounts use ordinary OAuth with `purpose=buyer`; registration never bypasses their sign-in or security checks. Caller-generated recovery secrets and operation IDs support safe retries. Buyer registration grants no Creator rights.

Eligible USD one-time products may use MPP Stripe charge challenges with an authorized shared payment token and explicit `purchasesAutonomous` spending permission. OAuth Bearer and HTTP Payment-Authorization are separate. In MCP, payment credentials belong in payment metadata. Quotes and provider confirmation determine the final amount; catalog prices are indicative. Zero-total one-time purchases need no payment credential. Subscriptions, mixed carts and below-minimum payments require owner-assisted browser checkout; independent recurring payments are unavailable.

Never reuse a credential for a different quote or start a new charge while an earlier attempt is unresolved. Check the same quote's status after timeouts or wallet confirmation. Delivery uses the same native ownership, payment, refund, gift and subscription rules as browser purchases. Ordinary checkout does not implicitly approve independent spending, and agents cannot charge saved cards or account balances automatically.