ImoVertical

Use this to display the live status of an existing ImoVertical report after get_report_status.

render_report_status

Use this to display the ImoVertical comparison matrix after compare_property_reports, when the user is choosing between properties.

render_report_comparison

Use this when the user hesitates between two to five properties they already have ImoVertical reports for. Returns a category-by-category comparison, the real differences and what is missing — never an investment recommendation.

compare_property_reports

Use this compatibility alias only in older ImoVertical conversations after get_property_report. It preserves the full report view expected by cached clients. For the new flow, use get_property_report_pdf instead.

render_report_summary

Use this only when an older ImoVertical conversation explicitly calls get_property_report. It preserves the complete structured report contract for cached ChatGPT connections. For the new product flow, use get_property_report_pdf to return the actual complete PDF.

get_property_report

Use this when you need to know whether the user is connected to their ImoVertical account and which kind of account it is. Never reveals internal identifiers or personal data.

get_account_context

Use this when the user mentions a French property address and you need a stable, normalised address before any ImoVertical analysis. Returns candidate matches; ask the user to pick one when several are returned.

resolve_address

Use this when the user refers to their existing ImoVertical reports, or before creating a new one, to check whether a recent report already covers the same address. Only ever returns reports owned by the connected user.

list_property_reports

Use this after resolve_address when the user asks ONE precise question about a French address, such as the cadastral plan, nearby transport, schools, DPE, risks or shops. It runs ONLY the requested ImoVertical collector and returns ONLY that topic as plain conversation data. The account may run 20 checks during its first 7 days, then 10 per 7-day period with no carry-over, and at most 10 different categories on any single address; these are technical caps that cannot be raised. Address resolution and technical failures never count. Never bundle topics: use one separate call per topic. Never pick a topic yourself for a broad or vague question (an opinion about the address, whether it is a good choice): ask the user which topic they want and let them choose the topic, then wait for their answer.

get_address_information

Use this when the user asks about a French TOWN or CITY rather than a specific address — which town to look in, what a place is like, or how two towns compare. It needs no address: pass the town name (or its INSEE code) directly, without calling resolve_address first. Returns only town-wide indicators — resale market, property tax, safety, household income, rental tension, long-term vacancy of the private housing stock (with its 2020-2025 trend), dominant energy label, natural hazards, disaster orders and radon — each valid for the whole town. When several towns share the name, the answer lists them and you MUST ask the user to pick one before continuing. This counts as one unit of the same usage allowance as get_address_information.

get_commune_profile