Noetis Travel Planning · Personal engine for app builders
Travel Planning Engine for Apps
Turns preferences and constraints into an itinerary and booking checklist.
Answers: "Can an app turn travel options into a draft itinerary?" For individual travellers.
No live booking or availability. Every option must be confirmed with the provider.
Available today
ImplementedImplemented: runs on the shared runtime with supplied material. One bounded development check on 2026-10-12 took 127s with 15 model calls and ended "incomplete". That is a development signal, not an evaluation. Customer access is by approved account.
What you send
- Question
- Supplied text material
- Text material up to 150,000 characters per run
What comes back
- Itinerary and booking checklist with estimates marked as estimates.
- Findings with the located quote and a support status from claim review
- Release status: released, incomplete with reasons, or failed
- Executed roles, usage and measured cost
Sample
Authored illustration. Written by Encevra to show the workflow. Not customer data and not a recorded model output.
Plan 4 days in Lisbon.
Dates 10 to 13 May. Budget $1,200 excluding flights. Like food and museums, slow pace. Hotel quote $140/night. Want a day trip to Sintra. Museum closed Mondays per guidebook (10 May is a Monday).
- A draft itinerary from the supplied options
- Timing conflicts between legs
- Items to confirm with providers
The real response shape is documented in the API reference.
How the workflow operates
Each role is a responsibility in the workflow, served by a third party language model. More roles are not automatically better; depth and routing decide which run.
Built with
Models this engine uses: OpenAI (GPT), Anthropic (Claude), SpaceXSI (Grok). Specialists run on OpenAI models and the claim review and final brief on Anthropic models. If a provider has a temporary failure, the step can fall back to an OpenAI model, and the run records that.
Preferences Mapper
Define dates, budget, pace and hard constraints.
Destination Researcher
Describe options using supplied information only.
Itinerary Planner
Sequence activities realistically by day.
Budget Analyst
Estimate costs from supplied figures and label every estimate.
Logistics Reviewer
Check transfer times, opening constraints and practicality.
Evidence and deployment
Evidence
This engine reads the text you send in the request. Each released finding carries the exact quote and its character span in that text, located mechanically before release. Quotes that cannot be located are labelled Insufficient evidence and never shown as source verified. Interpretation is reviewed as a separate step, and gaps such as a missing clause describe what was searched instead of citing text that is not there.
Deployment
Runs on Encevra hosted infrastructure using the third party models listed above. Every model call and fallback is checked against the deployment policy first. Private cloud and air-gapped deployment are planned; discuss deployment requirements.
What it does not handle
- Bookings
- Live availability or prices
- Authorized source retrieval is not available: Not built. Engines read only supplied material.
- Uses only supplied material. No freshness guarantee beyond the documents provided.
- Required for every output during trials.
How to integrate
Send "engine": "travel-planning" with your question and material from your server. Keys stay server side.
How to evaluate it
No published result for this workflow yet. Build a small answer key from your own work and compare against a strong single model baseline. See the evaluation checklist and method.
Cost and rights: pricing and licensing. Showing outputs to your own customers needs a written agreement.
Related engines
Content reviewed 2026-10-12 by the Encevra engine team. Engine version 0.1.0 on noetis-core-1.