The AXUS Builder is a companion tool to your AXUS account. You give it a supplier document, pasted text, a GDS string, or a plain description of a trip, and it builds the itinerary and sends it through to your AXUS account.
Everything below is what you need to start using it today.
In this guide:
1. Signing in
Open the tool's web address:
Find and click the Sign in button on the right top corner.
You will use the same credentials you already use for axustravelapp.com.
2. The four ways to get information in (input methods)
Pick one at a time. Each one is a panel you open, fill, and send.
Itinerary / Reservation
The main one, and the reason most people will use the tool. You have a supplier document and you want it in AXUS.
This mode is verbatim, whichever option you use. It transfers what is in your document. It does not add anything that is not there, and it does not correct anything either.
Two options inside this panel:
-
Pasted text / URL.
If the itinerary arrived in an email, copy it straight out of the email and paste it here. You can also paste the contents of any file or webpage directly here.
Upload file or image. PDF, DOCX, XLSX, TXT, JPG, PNG are supported.
Worth knowing: long supplier PDFs often carry ten pages of terms, conditions, and company background before the day-by-day starts. Removing those pages first (any free PDF tool or Preview on a Mac will do it), or pasting only the itinerary section, makes the parse faster and lighter.
Cruise
Enter the ship name, the cruise line, the departure date, the embarkation port, and the port list (you can also upload a confirmation document, or even paste a screenshot of the sailing).
Those are required.
WHY
The Builder does not look the sailing up online. Cruise line and supplier pages are often outdated, incomplete, or show a default version of the route instead of the sailing your client booked, so the port order can come back wrong. Rather than risk that, the Builder builds from what you provide.
WHAT TO DO
Enter the port order as it appears on your confirmation documents (text, PDF, image, screenshot). Include the full day by day sequence: each port or day at sea, with its date or day number, through to disembarkation.
GDS / PNR
Paste the string straight off your GDS and it becomes AXUS bookings.
It reads the string you give it. It does not look up an airline record locator and fetch the booking, so paste the full detail you want carried over.
Describe
Plain language. Write what you want and it builds a shell you can work from.
It creates the flight legs, the hotel, the area, the transfer, and the tour so you are not clicking each one into place. The more specific you are, the closer it lands to a real itinerary.
This is the mode where the AI writes content rather than transferring it.
If you have a document, this is not the mode for it. Use Itinerary / Reservation, which has the upload option inside it.
Do not use Describe for a cruise. It will write a plausible sailing rather than your client's one. Use the Cruise panel and give it the port list from the confirmation.
New itinerary, or add to an existing one?
Which one you pick depends solely on whether you are pushing into an existing itinerary or starting from scratch.
- New itinerary → A new AXUS itinerary is created.
- Add to an existing AXUS itinerary → Paste the itinerary webview URL into that field. Everything you send next goes into that itinerary specifically, instead of creating a new one.
After you do a first build and push, you will see Add More at the bottom of the page, below Clear. Use it to keep adding bookings to the itinerary you just built. Start and end dates adjust and everything stays in chronological order.
Output language
At the bottom of the panel there is an output language field. Input can be in any language. Set the output to the language you want in AXUS, and it translates as literally as it can.
An Italian rail ticket in, English out. A DMC itinerary in English with Brazilian Portuguese as the output language, and everything arrives in Portuguese.
3. Credits
The Builder runs on credits. Your account gets topped up with credits purchased at https://www.axus-builder.ai/buy-credits.
Each import you run draws down that balance.
Every send is a real import and is charged, including a repeat of a document you already sent.
If your balance runs out part way through an import, that import still finishes. The account is then locked until you top up.
4. Before you go live
This pushes into your live AXUS account.
Anything you build lands in your real itineraries.It creates new bookings only. It cannot update a booking that already exists in AXUS.
If a supplier sends a revision, sending it through the tool again adds new bookings rather than editing the old ones. For a change to a single booking, editing it in AXUS directly is still the clearer path.Privacy. The tool is powered by Anthropic's Claude. Your content is not used to train the model.
What it does not do yet
- Images are not carried over from documents. They are on the roadmap.
- Bookings are not linked back to the source after the parse. Each send is a one-time transfer.
Review what it creates
It is AI. Read what lands in AXUS before it goes to a traveler.
The places to check first are flight numbers, airport codes, and dates, since those are where a gap in the source document gets filled with a best guess.
Something not behaving as described here: AXUS Builder: common issues and what to do.
0 Comments