Docs
Get an API key

Book travel from your app or your agent in five calls.

One key for live hotel and flight supply, card payments, signed permission to spend and price watches. We route to the supplier, take the payment and keep the record.

69 endpoints34 guides1 key for all of it
Your first hotel
Terminal
# Sandbox host; your key from the dashboard
export BASE_URL=https://api.sandbox.oex.sh

curl -X POST "$BASE_URL/v1/hotel/search" \
  -H "x-api-key: $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "destination": { "city": "Dubai", "country_code": "AE" },
        "check_in": "2026-11-10", "check_out": "2026-11-12",
        "occupancy": [{ "adults": 2, "children": [] }],
        "guest_nationality": "GB", "currency": "USD" }'
  1. 1Search
  2. 2Offers
  3. 3Prebook
  4. 4Book
  5. 5Read back
Only Book charges a card.Full walkthrough →

Point your agent here.

Every page has a Markdown twin, and every guide lists the calls it makes in order. An agent reads the index, fetches one page and calls the API, without scraping HTML.

  • llms.txt lists every task in order, with the page to read and its calls.
  • .md on any URL returns the page as Markdown, with its calls up front.
  • skill.md teaches Claude when to use OEX and how not to double-book.
Read the task index
$ curl https://docs.oex.sh/llms.txt
Read one section
$ curl https://docs.oex.sh/hotel/llms.txt
Fetch one page as Markdown
$ curl https://docs.oex.sh/hotel/hotel-getting-started.md
Install the OEX skill for Claude
$ curl --create-dirs -o ~/.claude/skills/oex/SKILL.md https://docs.oex.sh/skill.md

Pick what you're building.

Travel is the core. Payments and Mandates decide how money moves. Watcher builds on both.

Keep these close.

The pages you'll come back to once you're past your first booking.