Aviation project: a charter search you can type as a sentence
A form of airports, dates and passenger counts is the slowest way to ask for a charter. This project lets a visitor type the request in plain English instead.
· 3 min read · By WebSurge Technologies
At a glance
Summary
| Status | Built. The AI search was published on 9 November 2026 and checked on the live site. |
|---|---|
| Type | Charter search, enquiry and thank-you pages, plus an AI search, added to an existing website. |
| Stack | JavaScript custom elements, a Laravel API, the Claude API (Claude Haiku 5.5) and the Wix website that hosts the pages. |
| Facts as of | 16 November 2026, from the project’s own progress file. |
The problem
Forms are slow, and models should not set prices
A charter customer usually knows the trip in a sentence: where from, where to, when and how many people. A form of airport pickers, a calendar and passenger counters makes them translate that sentence into fields.
An AI model can read the sentence, but a model that is allowed to choose airports, dates or prices on its own will eventually be wrong with great confidence. The brief was to give visitors the sentence box without giving the model any authority.
Our approach
The model reads, our code decides
Claude is called through a forced tool call, which means it can only answer with a structured request: origin, destination, dates and passengers, as far as the sentence states them. It does not choose airports, dates or prices; those stay with our code.
Our own code then takes that structured request and applies the rules: it checks the airports against the supported list, fills in defaults, validates the dates and applies the limits. The result is shown as a short summary with an animated route map, and the usual price cards appear below it.
- Visitor types a request. For example, a sentence with a route, a date and a group size.
- Claude reads it. A forced tool call returns a structured request.
- Code decides. Airports, defaults, dates and limits are applied by our code.
- Summary and route map. The visitor sees what was understood.
- Price cards. The normal search results appear.
Safety and cost
Limits are part of the design
- A throttle of 10 requests a minute, a daily cap and a 300-character input limit.
- A kill switch that turns the feature off.
- The API key stays on the server. The browser never sees it.
- Tests use a stand-in AI service, so the test suite never spends money.
What else was built
A search that works inside an existing site
The pages were built as a bundle of JavaScript custom elements that run inside the existing Wix website, talking to a Laravel API. Besides the AI search, the bundle includes a charter search with a 33-airport picker and its own calendar, an enquiry form and a thank-you page.
Evidence
What the figures are
The tests are counted from the project: 46 resolver tests and 25 controller tests on the server, plus 57 browser checks. These are test counts and design limits, not customer outcomes. We do not publish conversion or revenue figures for this project because we do not have any that we can verify.
Start a project
Have a platform or an AI idea that has to work in production?
Tell us what you are building. The first consultation is free, and you get a short technical read-out and a plan.