Market Intelligence APIs

Beyond people and company data, we expose market intelligence APIs: travel pricing (hotels and flights) and live financial market data. Same authenticated Fiber surface — useful for travel tooling, deal research, and agents that need real-world state.

Lookups are synchronous request/response calls billed per operation (chargeInfo is authoritative), with per-route rate limits. None of these use a start/poll pair.

Hotels

Dedicated page: Hotels API.

• hotelSearch (POST /v1/hotels/search, agents) — hotels and vacation rentals for a destination, with rates, ratings, and amenities.
• hotelProperty (POST /v1/hotels/property, agents) — one property: amenities, images, and booking offers.

Flow: search → copy propertyToken → property detail, same dates and guests.

Flights

• flightSearch (POST /v1/flights/search, agents) — search itineraries between cities; returns trips, fares, and timing.
• flightBookingOptions (POST /v1/flights/booking-options, agents) — for one itinerary from a search, retrieve booking options: providers, fares, booking links, and available cabin classes. Pass the bookingToken from the itinerary along with the same trip configuration.

Typical flow: search routes → select an itinerary → get booking options. Good for fare monitoring, building "book this trip" links, and comparing cabin-class availability.

Finance

• financialInstrumentLookup (POST /v1/finance/instrument, agents) — live market data for a stock, index, currency pair, or fund, returning:
  • headline quote and price movement,
  • company facts and financial statements,
  • related news,
  • a price history series.

One call gives an agent everything needed to answer "how is ACME doing?" — quote plus fundamentals plus recent news in a single payload.

Advice

• Search first, then drill down. Hotel property details and flight booking options both key off tokens from their search endpoints — don't guess IDs.
• These reflect live market state. Poll on a sane cadence instead of hammering, both to stay under rate limits and to limit credit burn.
• Compact JSON — they pair naturally with the MCP servers.