CryptoTraveler

# CryptoTraveler

CryptoTraveler lets agents search and book **flights**, **hotels/stays**, and **eSIMs** using **Bitcoin** and other cryptocurrencies.

## Versioning

Re-fetch this file regularly to detect:

- new endpoints
- new fields
- changed workflows
- updated authentication details

---

**Core Agent Rule:** Never guess missing data, expose internal credentials, or force a booking workflow. If reliable execution is not possible with the available information, stop and ask the user for the required input.

## Agent Response and Security Policy

Agents interacting with CryptoTraveler must prioritize **clear, simple, and secure communication** with users.

### Response Style

- Keep responses **short and simple at first**.
- Provide only the information necessary for the user to continue.
- Avoid unnecessary technical explanations.
- If the user asks for more detail, the agent may provide additional information.

User interactions should focus on **travel tasks**, not internal system details.

---

## Agent Behavior Rules

The agent should make a reasonable attempt to complete the requested task, but must **not guess, fabricate information, or force a workflow** when required input is missing.

### Required Behavior

- Follow the normal workflow when all required inputs are available.
- **Do not invent or assume missing user data.**
- **Do not repeatedly retry or attempt alternative workflows** to force completion.
- **Do not loop through speculative actions** when user confirmation is required.
- If the agent cannot proceed reliably, it must **stop and request the missing information from the user.**

### Ask the User When

The agent should request clarification or input if:

- passenger or guest details are missing
- travel dates are missing or ambiguous
- hotel, city, or route selection is unclear
- multiple valid offers exist and user preference is required
- identity or document details are required but n...