How it works

Booking a flight, in one sentence

Flyte is a travel agent you talk to. You describe the trip; it searches real inventory, books it, and settles in crypto or by card.

You type

“I need to get from Chicago to Athens for about two weeks sometime this autumn, and I’d rather not connect.”

Flyte prices real dates across that window and shows you what the timing is worth.

What happens

  1. Say where you want to go

    Plain language, no dropdowns. “Chicago to Athens, second week of November, nonstop if you can.” Dates, cabin, bags and preferences are picked out of the sentence.

  2. Real fares, not estimates

    Live carrier inventory, checked at the moment you ask. Every price shown is one that was quoted, and it is re-checked before you pay so the fare you agreed to is the fare you get.

  3. Pay in USDC, or by card

    Crypto settles on Base. Card is there when you would rather not touch a wallet. Either way the amount is calculated from the fare on screen, never from anything your browser sends.

  4. Ticketed, then confirmed

    You get a booking reference and e-ticket numbers once the airline has actually issued them - not when the reservation was made. The two are not the same thing, and only one of them gets you on a plane.

What protects you

  • Your money waits in escrow

    Payment is held, not forwarded. It is released only once a ticket exists. If the airline never issues one, it goes back automatically - you do not have to ask, and nobody has to remember.

  • Nonstop unless you say otherwise

    Direct flights are the default rather than the upsell. Connections and long stopovers are offered when they genuinely save money or make a trip better, and they are labelled as what they are.

  • Checks before the payment screen

    Passport validity, name format against the document, the six-month rule, and whether the fare moved since you looked. The failures worth catching are the ones that would otherwise surface at the airport.

Paying in crypto

Flyte settles in USDC on Base. You send the fare to an escrow wallet from your own wallet, and the transfer is confirmed by reading the chain - not by your browser telling us it happened.

Escrow is the part that matters. The money sits there while the booking is attempted. A ticket releases it; anything else returns it. That means a failed booking is a refund rather than a support conversation.

Prefer not to? Card payment goes through a hosted checkout, and card details never touch Flyte.