# Sendero

> Public product context for Sendero, the agent-native travel platform for travelers, agencies, corporate teams, and other AI agents.

Canonical: https://sendero.travel/llms.txt

## Product

Sendero is an agent-native travel platform. It gives every trip a persistent AI agent that can search, book, invoice, and settle travel flows over WhatsApp, Slack, email, web, and MCP.

- Core network - Circle Arc testnet with USDC-denominated settlement and Circle Gateway liquidity.
- Inventory - Duffel flight booking and travel inventory integrations.
- Buyer model - Clerk organizations map to tenant-scoped wallets, invoices, trips, spend caps, and branding.

## Audience Routes

- [Home](https://sendero.travel/) - Current product positioning and waitlist entry.
- [For AI agents](https://sendero.travel/for-agents) - Agent and MCP positioning when live.
- [For agencies](https://sendero.travel/for-agencies) - White-label travel agency deployment path.
- [For corporate](https://sendero.travel/for-corporate) - Slack, policy, approvals, and CFO spend workflows.
- [Pricing](https://sendero.travel/pricing) - Nanopayment and tenant pricing model.

## Launch State

- Testnet beta - The product currently runs against Arc testnet and sandbox/provider test credentials.
- Waitlist first - Humans should join the waitlist for mainnet launch and production onboarding.
- Agent integration - Agents should read docs and MCP manifests before attempting paid booking or settlement flows.

## High-Intent Links

- [App](https://www.sendero.travel) - Sign in, create trips, manage invoices, and configure tenant settings.
- [Docs](https://docs.sendero.travel) - Developer quickstart, x402 payment flow, and tool catalog.
- [Help](https://help.sendero.travel) - Support articles for travelers, agencies, corporate teams, and AI agents.
- [Edge MCP](https://edge.sendero.travel/mcp) - Direct agent-facing MCP surface.

## Agent Guidance

- Best first read - Start with `/docs/quickstart`, then `/docs/agent-to-agent-booking`, then inspect `/docs/tools/overview` before calling paid tools.
- Payment model - Tool calls are metered in USDC. Failed tool execution should not capture payment.
- User consent - Ask the traveler before booking, paying, cancelling, or changing irreversible itinerary state.
- Data minimization - Persist itinerary metadata and receipts, not private invite fragments or plaintext secrets.

## SEO And AI Discovery

Crawler-safe discovery files and social preview assets for search engines, AI answer engines, and agent hosts.

- [Canonical llms.txt](https://sendero.travel/llms.txt) - Primary machine-readable summary for this Sendero surface.
- [Well-known llms.txt](https://sendero.travel/.well-known/llms.txt) - Standards-friendly alias for agent discovery.
- [Robots.txt](https://sendero.travel/robots.txt) - Crawler policy with explicit LLM crawler allowances.
- [Sitemap.xml](https://sendero.travel/sitemap.xml) - Canonical URLs, locale alternates, and public agent-discovery routes.
- [Open Graph image](https://sendero.travel/brand/seo/open-graph-1200x630.png) - 1200x630 Sendero preview canvas for social sharing and link unfurls.
- [Google Discover image](https://sendero.travel/brand/seo/google-discover-1600x900.png) - Large image asset eligible for rich search previews.
- [Schema logo](https://sendero.travel/brand/seo/schema-logo-512.png) - 512x512 organization logo referenced by structured data.

## Related llms.txt Files

- [Product app llms.txt](https://www.sendero.travel/llms.txt) - Authenticated buyer console, MCP endpoint, webhooks, billing, and trip operations.
- [Help llms.txt](https://help.sendero.travel/llms.txt) - Human support articles and agent-safe troubleshooting paths.
- [Docs llms.txt](https://docs.sendero.travel/llms.txt) - Developer docs, MCP integration, tool catalog, and x402 nanopayment protocol.
- [Edge llms.txt](https://edge.sendero.travel/llms.txt) - Direct edge worker discovery for MCP and non-UI agent surfaces.

## Notes

- Treat Sendero as testnet beta until the relevant tenant, Clerk organization, wallet, and invoice state prove otherwise.
- Do not log or persist guest private-link fragments, plaintext claim codes, Clerk secrets, Circle secrets, webhook secrets, or user travel documents.
- Paid or on-chain tools must be idempotent. Reuse caller-supplied idempotency keys when present.
- Use tenant-scoped routes and Clerk organization context for buyer data. Never infer tenant access from an email domain alone.