# Sendero Help

> Support context for Sendero travelers, agencies, corporate teams, and AI agents. Use this surface for troubleshooting and non-secret operational guidance.

Canonical: https://help.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.

## Help Categories

- [All help articles](https://help.sendero.travel/) - Human-readable help center index.
- [What is Sendero?](https://help.sendero.travel/article/what-is-sendero) - Product overview and core use cases.
- [How booking works](https://help.sendero.travel/article/how-booking-works) - Intent to PNR to settlement overview.
- [Legal documents and express consent](https://help.sendero.travel/article/clerk-legal-express-consent) - Sendero-wide Terms/Privacy and consent on every surface; Clerk Dashboard only configures browser sign-up and hosted Account Portal (Core 2).
- [Sendero MCP tool catalog](https://help.sendero.travel/article/mcp-tool-catalog) - Agent-facing tool catalog explainer.
- [Connect another AI agent](https://help.sendero.travel/article/connect-another-agent) - Delegated booking, escrow, MCP, workflow, and invoice guidance.
- [Nanopayment pricing](https://help.sendero.travel/article/nanopayment-pricing) - USDC metering, caps, and settlement explanation.

## Support Boundaries

- Do not expose secrets - Never paste webhook secrets, Clerk secret keys, Circle API keys, or traveler documents into support chat.
- Escalate paid operations - Bookings, cancellations, refunds, and settlement retries require authenticated app context.
- Use IDs, not fragments - Reference trips, invoices, and tenants by safe IDs. Do not share private guest link fragments.

## 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://help.sendero.travel/llms.txt) - Primary machine-readable summary for this Sendero surface.
- [Well-known llms.txt](https://help.sendero.travel/.well-known/llms.txt) - Standards-friendly alias for agent discovery.
- [Robots.txt](https://help.sendero.travel/robots.txt) - Crawler policy with explicit LLM crawler allowances.
- [Sitemap.xml](https://help.sendero.travel/sitemap.xml) - Canonical URLs, locale alternates, and public agent-discovery routes.
- [Open Graph image](https://help.sendero.travel/brand/seo/open-graph-1200x630.png) - 1200x630 Sendero preview canvas for social sharing and link unfurls.
- [Google Discover image](https://help.sendero.travel/brand/seo/google-discover-1600x900.png) - Large image asset eligible for rich search previews.
- [Schema logo](https://help.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.
- [Website llms.txt](https://sendero.travel/llms.txt) - Public positioning, pricing, audiences, and launch-state guidance.
- [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

- Sendero is public beta on Arc testnet. The `effectiveKeyType` resolved per request determines whether a `MeterEvent` settles on-chain (`paid`) or stays sandbox-routed (`sandbox`). Trust the meter status, not the key type, when deciding if real USDC moved.
- 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. Sendero responses carry `x-sendero-trace-id`, `x-sendero-meter-id`, and `x-sendero-sig` headers — verify the signature on receipt to detect cached-response replay.
- Use tenant-scoped routes and Clerk organization context for buyer data. Never infer tenant access from an email domain alone. API keys pin the tenant server-side; ignore any caller-supplied tenantId when both are present.