AI Constructor
The AI Constructor is a family of sector-specialized agents that turn a natural language question into a plan of calls to public, open-data or enterprise services, producing a useful, terse, verifiable answer.
Unlike traditional document chat -- which searches your documents -- the Constructor draws from external sources specialized for your company sector: tourism open-data, tax databases, regulatory registries, weather APIs, public transport, events, and so on.
When to use it
Use the Constructor when the answer depends on external data more than on your documents: trip planning, up-to-date tax deadlines, international regulatory compliance, market data. For internal document analysis the standard chat remains the right tool.
How it works
The Constructor follows a six-step flow, fully automatic:
- Intent detection -- recognizes whether the question falls within the sector's domain (tourism, tax, etc.).
- Entity extraction -- identifies places, dates, constraints, preferences.
- DSL planning -- translates the request into a sequence of semantic calls (e.g.
location.geocode,weather.forecast,events.search). - Provider selection -- chooses the best providers (free first, paid if configured).
- Execution -- calls the APIs, normalizes results, handles fallbacks.
- Synthesis -- composes a useful answer with explicit confidence level and assumptions.
The user sees only the final answer: API complexity remains hidden.
Available Constructors
Each Constructor targets a specific sector. Availability depends on the subscription plan and the integrations active on your company.
Tourism Constructor
The first available Constructor, designed for tourism operators (tour operators, agencies, destination management, hotels).
What you can ask:
What to visit in Florence in 2 days with kids, avoiding the lines?
One-week itinerary in eastern Sardinia, August, solo traveler.
Free events in Bologna on the weekend of June 14.
What's the weather in Trapani next week?
Typical DSL modules covered (extent depends on plan):
| Module | Use cases |
|---|---|
location.* | Geocoding, place normalization |
places.* | POIs, attractions, museums, restaurants by category |
route.* | A->B itineraries, multi-stop optimization |
weather.* | Forecast, outdoor risk |
mobility.* | Public transport, stations, airports |
events.* | Events, festivals, exhibitions |
culture.* | Wikipedia/Wikivoyage historical context |
currency.* | FX conversions |
images.* | Free Wikimedia Commons photos |
Free providers (always available): OpenStreetMap Nominatim, Overpass, Open-Meteo, Wikipedia, Wikivoyage, Wikidata, Frankfurter, Wikimedia Commons.
API-key providers (optional, admin-configurable): Ticketmaster Discovery (events), OpenRouteService (advanced routing), Geoapify (extra POIs), OpenWeather.
Booking
The Tourism Constructor does not simulate hotel availability or live flight prices. It returns areas of interest and guides, never invented bookings. For real bookings it points back to official channels.
Sector Constructors (roadmap)
Additional Constructors planned or in development: Tax (Italian Revenue Agency), Healthcare (FDA/EMA), Legal (extended Normattiva), Logistics, Energy. The company configuration determines which Constructor is active.
Anatomy of a response
Every Constructor response contains four standard elements:
1. Direct answer
A concise block that answers the question. Never invented: if data is incomplete, the Constructor declares it explicitly.
2. Assumptions and constraints
A dedicated box with the assumptions made (e.g. "assumed peak season", "walking estimate 13 min/km", "7-day weather forecast may change").
3. Confidence level
| Level | Meaning |
|---|---|
| High | Official or verified open-data, recent, multiple converging sources |
| Medium | Reasonable open-data, single source or estimated |
| Low | Indirect data (e.g. encyclopedic articles), fallback applied |
4. Sources
List of APIs consulted with timestamp, color badge by source type, links to official pages when available. Same citation mechanism as the document chat - every fact is traceable.
Configuring the AI Constructor
The administrator configures which Constructor is active per topic or canvas. The configuration lives in the chat pipeline canvas DSL: the Constructor is not a black box, it is a pipeline that can be inspected and modified like any other canvas.
What the admin can customize:
- Which DSL modules to enable (e.g. hide
events.*if not relevant). - Which API-key providers to activate (requires the API key configured in OAuth & Service Canvas).
- Final synthesis prompt, tone, language, output format.
- Combination with internal document search (e.g. first find tour packages in the KB, then enrich with external data).
For operational details see Chat DSL (Canvas).
Limits
- No bookings: the Constructor produces information, not transactions.
- Connectivity dependence: if external APIs are slow or offline, known fallbacks apply (e.g. estimated visit time without routing) marking lower confidence.
- Source language: some open-data sources are partial in Italian. The Constructor answers in the language of the question, optionally translating the source data.
- Rate limit: free providers have hourly limits (e.g. Nominatim 1 req/s). For intensive use configure paid providers.
Tips for effective questions
- Be specific on constraints: "in August, mid budget, with kids" produces better plans than "in summer".
- Indicate preferred output language if different from the question's.
- One intent per query: multi-intent questions are still executed but sequentially. Splitting helps speed.
- Trust the assumptions box: it makes explicit what the Constructor assumed. If an assumption is wrong, rephrase and correct it.
Queria v3.5.0 -- AI Constructor (Tourism reference)