iOS SDK · OTAs · Music · Live events · Sport

You bring the audience. Helix handles the travel.

From online travel agencies (OTAs) to artist managers, event organisers and sports teams: put flights and hotels in front of the people you already reach. Organise travel for touring teams or help fans get to the show or match. Helix powers the branded booking experience; travellers choose and confirm.

Put it inside your iOS app, run it under your own brand, or connect your own agent to it. A ready-to-configure white label can go live in as little as a day once branding, supplier and payment setup are ready.

Illustrative: one Helix engine, three operator brands

iOS SDK · Live

Helix, inside your app.

A white-label iOS SDK. Travel chat, search, booking and payment, in your brand, signed in as your user. Distributed with Swift Package Manager for iOS 16.4 and up.

Example banking app with a Concierge tabFlight results inside the example app, powered by HelixHotel detail inside the example app
Shown in an example banking app. The travel screens are live Helix.

No new login

Your sign-in is the only sign-in. Flights and hotels are found, compared and paid for inside the app people already trust, as themselves.

Looks like you

Fifteen colour tokens, four corner radii and one font, set for light and dark. Travel screens sit under your navigation bar, in your tab bar.

A new revenue line

Helix runs supply, payments, ticketing and servicing. Use your supplier keys, or Helix's. Your app can show the trip on its own home screen.

Your home screen

Your app knows about the trip.

Upcoming trip

A card on your home screen, read from the SDK, for the next trip.

The moment it books

A banner when a booking confirms, and a badge on your travel tab when something needs attention.

From the statement

Each booking carries its own statement suffix, so a card transaction can open that booking.

From a link or a push

Links in email and push notifications open the right screen inside your app.

Identity

Your sign-in is the only sign-in.

Your user id becomes their Helix account. A different user signs the previous one out and clears that session on the device. Sessions stay in memory, and the app re-vouches quietly when one expires.

  1. 01Open. Your app shows the Helix chat.
  2. 02Ask. The SDK asks your app for a short-lived assertion.
  3. 03Sign. Your backend signs one for the user already in your session.
  4. 04Exchange. Helix checks it and finds or creates that person’s account.
  5. 05Load. The product loads in your brand. Same user id, same account, every time.
Configure once at launch
import HelixSDK

let configuration = HelixConfiguration(
    environment: .production,
    brand: "your-brand",
    assertionProvider: {
        try await MyBackend.shared.helixAssertion()
    },
    theme: HelixTheme(
        light: HelixThemeColors(
            accent: HelixColor(hex: "#111111"))),
    applePay: HelixApplePayConfiguration(
        merchantIdentifier: "merchant.com.example"),
    urlScheme: "myapp")
try Helix.shared.configure(configuration)

HelixChatView(initialMessage: nil, onClose: { /* dismiss */ })
SwiftUI or UIKit. Call configure again with a new theme and open chats re-theme in place.

Supply

Your supplier keys, or Helix's.

Flights, hotels, experiences and payments with Helix keys or your keys
ProductHelix keysYour keys
FlightsHelix airline contentYour Mystifly account
HotelsProperties on Helix contractsYour Travelport contract
ExperiencesTickets and tours, when agreedYour own partner supply
PaymentsHelix handles payment in version 1Apple Pay on your merchant ID

Data

You choose how much your app sees.

  • NothingThe default. Your app learns nothing about the trip.
  • Ids and statusTrip and booking ids, kinds and statuses.
  • Trip detailsAlso titles, places, dates, references, amounts and the statement suffix.

A brand switch turns the SDK off for your users within a minute. Signing out revokes the session and clears its data on the device.

Version 1.0

Search, book and pay. Today.

Version 1.0 searches, books and pays for flights and hotels, and opens a read-only booking sheet. It feels native: your navigation title, your back gesture, sheets in your colours. Bookings are a real-world service, paid with Apple Pay and card, not an in-app purchase.

Change and cancel inside the SDK, Android, and push delivery from Helix come next. You own your App Store submission.

Ways to build on Helix

One engine, six ways in

Put Helix inside your iOS app, under your brand, in your site, or behind your own agent. Early-access partners on the booking API and MCP server are set up in days, around their use case.

Live

iOS SDK

Put Helix travel inside your iOS app: chat, search, booking and payment, in your brand, signed in as your user.

  • Your sign-in, no second account
  • Your colours, type and navigation
  • Swift Package Manager, iOS 16.4+
Live

White label

Run the Helix assistant as your own product, on your domain, with your logo, colours and emails.

  • Your brand on web and in email
  • Your payments account
  • Per-brand guardrails, tested before launch
Live

Bring your own keys

Book on your own supplier contracts and pay the supplier directly. Helix adds no margin to those bookings.

  • Flight, hotel and payment accounts
  • Your own AI model keys
  • Each key approved before it goes live
Live

Embeddable widget

Put Helix inside your own site with one script tag, so customers never leave your page.

  • Inline or overlay
  • Single sign-on from your site
  • English, French, German, Dutch and Spanish
Early access

Booking API

A versioned API to search, hold, book and manage trips from your own product, with no Helix interface.

  • Search, book, change and cancel
  • Preferences and rules applied server-side
  • Partner keys and usage reporting
Early access

MCP server

Helix search and booking exposed as Model Context Protocol tools, so any MCP-capable agent can complete a booking.

  • Flights, hotels and events as tools
  • Confirmation returned to the agent
  • Works alongside the booking API

Want the API or MCP server?

Request early access

For personal AI agents

Your agent can plan the trip. Helix can book it.

Personal agents are getting good at knowing what their users want. Turning that into a ticketed flight or a confirmed room still takes supplier contracts, payments, fare rules, changes and cancellations. That is the part Helix already does, every day, for its own products.

The booking API and MCP server put that engine behind your agent. Your agent keeps the relationship with its user; Helix completes the booking and handles what happens after it.

Talk to us about agents
agent ⇄ helix (MCP)Early access
// user: “get me to Lisbon for the 14th, usual hotel style”

→ search_flights  { from: "LHR", to: "LIS",
                   date: "2026-10-14", traveller: "t_…" }
← 3 options  ranked by the traveller's preferences

→ search_hotels   { near: "conference centre", nights: 2 }
← 3 options  within budget, usual style first

→ book            { offers: ["off_…", "htl_…"] }
← confirmed     flight ticketed, room confirmed
Illustrative example of an agent booking through the Helix MCP server.

What sits behind the interface

The same engine that runs Helix Business and Helix Black

Whichever way you connect, your customers or your agent get the full booking engine.

Flights

Search, book, seats, bags and extras, then changes and cancellations in the same thread.

Hotels

Global hotel inventory with live availability, shortlisted rather than listed.

Events and activities

Tickets and activities, with a whole trip built around the event.

Preference memory

Helix learns how each person travels, and they can see and change what it has learned.

Rules while it searches

Budgets, policies and approvals are applied during the search, not after the booking.

Money handled in code

Pricing, payment and booking run in deterministic code. No language model sits between a choice and the supplier.

Chat and voice

Type or speak a request. Both run on the same engine.

People when needed

Requests that need judgement can escalate to a concierge team with the full context.

Who builds on Helix

Built for the businesses that own the customer

Artists and management companies

Coordinate travel for artists, crew and touring teams, with preferences and travel rules accounted for.

Event organisers and promoters

Make travel part of the event experience, so attendees can find flights and places to stay around the dates that matter.

Sports teams and clubs

Help supporters travel to fixtures through your own branded experience, with opportunities to earn from bookings.

Online travel agencies and AI agents

Add Helix booking capabilities to the travel experience or assistant you already run.

Running a members' programme, private bank or premium card? Helix Black is built for you.

Availability

Live today, or early access

Everything on this page is available now. Early-access capabilities are switched on per partner and shaped around what you are building.

Helix platform capabilities and their availability
CapabilityStatus
iOS SDKLive
White-label web appLive
Bring your own supplier and model keysLive
Embeddable widgetLive
Booking API (versioned)Early access
MCP serverEarly access

How a partnership starts

From first call to launch in days

  1. 01

    Talk to us

    Tell us about your customers, your supply and where Helix would sit.

  2. 02

    Configure

    We set up your brand, keys and guardrails. There is nothing for you to build for the white label.

  3. 03

    Preview

    You test Helix as your own product on a private preview before anyone else sees it.

  4. 04

    Go live

    A ready-to-configure white label can launch in as little as a day once branding, supplier and payment setup are ready. Add the iOS SDK, the widget, the API or the MCP server as you need them.

Bringing people together? Help them get there.

Whether you manage an artist, run an event, lead a club or build a travel product, tell us who you serve. We'll show you how Helix could fit into their journey.