The AI 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.
It is currently in beta with a small group of agencies. Everything below is what you need to start using it today.
In this guide
1. Signing in
Open the beta link:
https://axusbuilder.brunomathieu-roy.workers.dev/
Enter the same credentials you use for axustravelapp.com and enter the following for client ID:
b1e9118e-c31d-4dba-93e0-930208db06b2
The beta address is temporary. The released version has its own permanent address, and you sign in there with the same AXUS credentials.
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, and the embarkation port. Those four are required. The disembarkation port is optional, and it helps the tool land on the exact sailing.
If you have the ports handy, paste them into the field.
Unlike the itinerary mode, this one supplements information about the destinations and ports. You can, and should, edit or delete any of it once it is inside AXUS.
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.
3. 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.
4. 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.
5. A few things to know before you start
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 and it is not retained long term. Full privacy detail will be published on the tool itself.
6. 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.
7. Review what it creates
It is AI, and it is in beta. 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.
8. What we are asking for
Use it on real work and tell us where it helps and where it does not. Specific cases are worth more than general impressions: the document, what you expected, what you got.
If there is a supplier format you deal with constantly, run it through and tell us what happened.
Finding the places it gets things wrong is the most useful thing you can send us.
9. Payment during the beta
Nothing is charged during the beta. Pricing will be published once it is set.
10. If something goes wrong
Signing in and access
A 401 or an authorization error. The credentials were not accepted. Use the same email and password as axustravelapp.com, and check that the client ID was entered exactly as informed above.
You are asked to sign in again mid-session. Sessions expire. Sign in again and continue.
During the push
An error mentioning JSON, or a build that ends without producing anything. The build did not finish cleanly. Send it again once, since most first attempts clear on a retry. If the same document fails twice, trim it to the itinerary pages or paste the itinerary text instead of uploading, and send the document to support@axustravelapp.com for our review.
A timeout, or a 524, on a long document. The build ran longer than the connection allows. Cut the document down to the pages that are the actual itinerary, or paste that section as text, and send it again.
The file will not upload. There is a file size limit during the current stage. Split the document, remove the pages you do not need, or paste the text instead.
After pushing it to AXUS
Nothing arrived in AXUS at all. Confirm you were signed in and the client ID was entered, then check your itinerary list and Advisor View before assuming the push failed.
Bookings created a new itinerary instead of going into an existing one. Check that the itinerary webview URL is in the existing-itinerary field before you send. An empty field means a new itinerary.
Bookings are in the wrong order within a day. A booking can land out of sequence inside its date, which is most likely when you are pushing into an existing itinerary. Drag it into the correct position in AXUS.
Duplicate bookings. Every send creates new bookings, so sending the same document twice produces two sets. Delete the extra set in AXUS.
Pasted text came through out of order. Some layouts, multi-column ones especially, scramble when copied. Paste into a plain text editor first to check the reading order. If it is scrambled there, upload the file instead of pasting.
Anything not on this list, send it to support@axustravelapp.com with the document and what you expected to see.
0 Comments