get_address_info
ChatGPTUse this endpoint to get complete property information (area, build year, coordinates, cadastral reference) for a specific address unit. Call it when you know the full street address including number. Required query parameters: - province_id (int), municipality_id (int), street_type (string, e.g. "CL"), street_name (string), street_number (string). Optional query parameters: - block, stair, floor, door (all strings) to narrow down to a specific unit inside a building. Returns a single object with cadastral reference, build_year, use, area_property (sqm), area_building (sqm), latitude, longitude, fragua_postal_code, fragua_district_name, fragua_district_id, and the census section code (sscc). Errors: 404 if no matching property found. Query Parameters: - province_id (Required): No description. - municipality_id (Required): No description. - street_type (Required): No description. - street_name (Required): No description. - street_number (Required): No description. - block: No description. - stair: No description. - floor: No description. - door: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_amenities_percent_chart
ChatGPTUse this endpoint to get chart data showing what percentage of listings include specific amenities (pool, storage, garage, lift, AC, terrace). Call it when you need to understand amenity saturation in a market. Required inputs (JSON body): same base as get_market_general_metrics, plus amenities list (default: ["swimming_pool","storage","garage","lift", "air_conditioning","terrace"]). Returns an object with percentage breakdowns per amenity. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_area_ratings
ChatGPTUse this endpoint to get a composite quality rating for a neighborhood, including plot data for visualization. Call it when you want to compare a postal code's attractiveness relative to other zones. Required query parameters: - postal_code: 5-digit Spanish postal code (e.g. "28012"). - operation: "buy" or "rent". Optional query parameter: - user_colors: comma-separated hex colors for plots (default "132A87,2EA3F2,23DBDB"). Returns plot_data, plot_design, plot_text, plot_reference_line, and table_data arrays for rendering a ratings visualization. Errors: 404 if no ratings data available. Query Parameters: - postal_code (Required): No description. - operation (Required): No description. - user_colors: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_bedrooms_price_chart
ChatGPTUse this endpoint to get chart data showing average listing prices grouped by bedroom count. Call it when you need to understand the price premium or discount associated with different bedroom configurations. Required inputs (JSON body): same as get_bedrooms_supply_chart. Returns a list of data points with average price per bedroom count. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_bedrooms_price_m2_chart
ChatGPTUse this endpoint to get chart data showing average price per square meter grouped by bedroom count. Call it to compare unit-price efficiency across bedroom configurations. Required inputs (JSON body): same as get_bedrooms_supply_chart. Returns data points with price/sqm per bedroom count. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_bedrooms_supply_chart
ChatGPTUse this endpoint to get chart data showing how listing supply is distributed across different bedroom counts. Call it when visualizing what bedroom configurations dominate the market. Required inputs (JSON body): same base as get_market_general_metrics — postal_code, operation, aggregation, type, plus optional property_type, new_construction, amenity flags, bedrooms, bathrooms, area. Returns a list of data points keyed by bedroom count and area, suitable for bar or pie chart rendering. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_built_to_rent_assets
ChatGPTUse this endpoint to retrieve Built-to-Rent asset data for one or more Spanish postal codes. Provide postal_codes in the request body and optionally filter by sub_asset_class. The response is split into operating and pipeline asset groups. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_cadastre_ref_info
ChatGPTUse this endpoint to look up property details by cadastral reference (referencia catastral). Call it when you already have a ref_cat string and need the property's address, area, coordinates, and build year. Required query parameter: - ref_cat: 14 or 20 character Spanish cadastral reference (e.g. "0334804VK4703C0001OT"). Returns a list of matching property objects (same schema as get_address_info). Errors: 404 if the cadastral reference is not found. Query Parameters: - ref_cat (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_cadastre_ref_info_v2
ChatGPTUse this endpoint to look up property details by cadastral reference from the cadastre search index. Call it when you already have a ref_cat string and need address, areas by use, coordinates, district, and census section. Required query parameter: - ref_cat: 14 or 20 character Spanish cadastral reference (e.g. "0821019060090038"). A 14-character reference returns every unit in the building. Returns a list of property objects, including use-area breakdowns, coordinates, fragua_postal_code, fragua_district_name, fragua_district_id, and sscc. Errors: 404 if the cadastral reference is not found. Query Parameters: - ref_cat (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_coordinates_from_ref_cat
ChatGPTUse this endpoint to resolve a cadastral reference into geographic coordinates (latitude/longitude). Call it when you need to place a property on a map or pass coordinates to other endpoints. Required query parameter: - ref_cat: 20-character cadastral reference. Returns ref_cat, postal_code, latitude, longitude, fragua_district_name, and fragua_district_id. Errors: 404 if the cadastral reference is not found. Query Parameters: - ref_cat (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_demand_summary
ChatGPTUse this endpoint to obtain demand absorption metrics for a given area. Call it when you need to understand the optimal price, size, bedrooms, or conservation status that maximizes demand in a postal code zone. Required inputs (JSON body): - postal_code: list of 5-digit postal code strings (e.g. ["28012"]). - period: one of "1_month", "3_months", "6_months", "12_months". Optional inputs: - operation: "buy" or "rent" (default "buy"). - property_type: list, subset of ["flat","house"] (default both). - new_construction: list of 0 and/or 1 (default [0,1]). Returns a summary object with relative and absolute absorption metrics for price, price_m2, area, bedrooms, and conservation — each with an x (optimal value) and y. For `*_relative keys, y is a 0–1 absorption share (display as %). For *_absolute` keys, y is the listing count at that optimum (integer count of ads, not a rate). Errors: 404 if no demand data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_demographics_metrics
ChatGPTUse this endpoint to retrieve key demographic indicators for a Spanish postal code area. Call it when you need socioeconomic context such as household income, population density, or employment data for a location. Required query parameter: - postal_code: 5-digit Spanish postal code (e.g. "28012"). Returns a list of metric objects each with weighted_metrics (metric name), kpis (formatted value), values (raw numeric), province_average, compared_province (% difference vs province), compared_spain (% vs national), valuation (qualitative rating like "Muy alto"), and valuation_aux (machine-readable rating like "very_high"). Errors: 404 if no demographic data available for the postal code. Query Parameters: - postal_code (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_employment_trends
ChatGPTUse this endpoint to retrieve employment trend data over time for one or more postal codes. Call it when you need to analyze how local employment has evolved historically. Required inputs (JSON body): - aggregation: "postal_code", "municipality", or "province". - postal_code: list of postal code strings (e.g. ["28001"]). - historical_aggregation: "month", "quarter", or "year". - historical_range: comma-separated date range (e.g. "2000-01-01,2024-08-01"). - type: "comparison" or "aggregated". Returns trend data arrays suitable for time-series visualization. Errors: 404 if no employment data available for the given area and range. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_flex_amenities_percent
ChatGPTUse this endpoint to get the percentage of flex listings offering specific amenities. Call it when understanding amenity expectations in the short-stay market. Required inputs (JSON body): same as get_flex_market_metrics, plus amenities list. Returns percentage breakdowns per amenity. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_flex_bedrooms_supply
ChatGPTUse this endpoint to get chart data showing how flex listing supply is distributed across bedroom counts. Call it when analyzing which configurations dominate the short-stay market. Required inputs (JSON body): same as get_flex_market_metrics. Returns data points per bedroom count. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_flex_market_metrics
ChatGPTUse this endpoint to retrieve key performance indicators for the flex (short-term/medium-term rental) market. Call it when analyzing furnished or short-stay rental markets rather than traditional residential. Required inputs (JSON body): - postal_code: list of postal codes. - aggregation: "postal_code" or "municipality". - type: "aggregated" or "comparison". Optional: bedrooms, area range, coordinates, historical_aggregation, historical_range. Returns a list of metric objects. Errors: 404 if no flex data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_flex_price_by_duration
ChatGPTUse this endpoint to get data showing how flex rental prices vary by stay duration (nightly, weekly, monthly). Call it when you need to understand pricing strategy across different booking lengths. Required inputs (JSON body): same as get_flex_market_metrics. Returns data points grouped by duration category. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_flex_price_m2_trends
ChatGPTUse this endpoint to get time-series data of flex market price per square meter. Call it when analyzing short-stay rental unit-price trends. Required inputs (JSON body): same as get_flex_market_metrics. Returns time-series data for line charts. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_flex_yield_trends
ChatGPTUse this endpoint to get time-series data of flex rental yields. Call it when assessing short-stay vs long-term rental investment returns. Required inputs (JSON body): same as get_flex_market_metrics. Returns time-series data for line charts. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_gdp_trends
ChatGPTUse this endpoint to retrieve GDP (Gross Domestic Product) trend data over time for one or more postal codes. Call it when you need to analyze regional economic output trends. Required inputs (JSON body): same schema as get_employment_trends — aggregation, postal_code, historical_aggregation, historical_range, type. Returns trend data arrays suitable for time-series visualization. Errors: 404 if no GDP data available for the given area and range. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_institutional_flex_living_assets
ChatGPTUse this endpoint to retrieve Institutional Flex Living supply data aggregated by the requested geography (e.g. polygon, postal code, municipality, province, CCAA). Use it when analyzing coliving / serviced apartments / flex living / short stays supply, returning operating_units and pipeline_units. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_irav_index_data
ChatGPTUse this endpoint to retrieve Spain's official IRAV index (INE Índice de Referencia de Arrendamientos de Vivienda). Data is national and stored by month. Each date is the first day of the month and represents that month (2026-06-01 is June 2026, not May 2026). Incoming dates are normalized to the first day of the month before lookup. Provide exactly one query parameter: - date: month to retrieve, as YYYY-MM-DD (for example 2025-11-01). - all: when true, return the full historical series ordered by date. - latest: when true, return the IRAV value for the most recent month. Returns data, a list of objects with date and irav_yoy_change (year-over-year percentage change), and total, the number of months in data. Errors: 422 if none or more than one of date / all / latest is provided; 404 if no IRAV data is found for the requested month. Query Parameters: - date: Month to retrieve, as YYYY-MM-DD. Normalized to the first day of that month. - all: When true, return the full historical IRAV series. - latest: When true, return the IRAV value for the most recent available month. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_land_developments_detail
ChatGPTGet the full detail of a land development. - development_id: The land development identifier (as returned by market/land_developments/location_data) for which to obtain the detail. This endpoint returns the complete land development record for the provided development_id. Authorization Ensure that the current user is authorized to access this endpoint. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_land_developments_location
ChatGPTGet land developments located in the provided postal code(s). - postal_code: List of postal codes for which to obtain land developments. This endpoint returns a list of land development map features (GeoJSON-like) for the provided postal codes, including development_id in properties to look up the full detail via market/land_developments/development_detail. Authorization Ensure that the current user is authorized to access this endpoint. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_land_properties
ChatGPTUse this endpoint to retrieve the geographic boundary (polygon geometry) for a land parcel identified by its cadastral reference. Call it when you need GeoJSON-style geometry for mapping or spatial analysis. Required input (JSON body): - refcat: 14-character cadastral reference (e.g. "0334804VK4703C"). Returns a list of GeoJSON Feature objects with polygon coordinates and property metadata. Errors: 404 if the cadastral reference is not found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_market_absorption_metrics
ChatGPTUse this endpoint to measure how quickly properties are absorbed (sold or rented) in a given market area. Call it when you need to assess market liquidity or time-on-market dynamics. Required inputs (JSON body): - postal_code: list of postal codes. - operation: "buy" or "rent". - type: "aggregated" or "comparison". - aggregation: "postal_code" or "municipality". Optional inputs: property_type, new_construction, bedrooms, coordinates, historical_aggregation, historical_range. Returns a list of absorption metric objects. Errors: 404 if no absorption data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_market_general_metrics
ChatGPTUse this endpoint to retrieve key performance indicators for the residential real estate market in a given area. Call it when you need metrics like average price, price per sqm, supply count, and yield for residential properties. Required inputs (JSON body): - postal_code: list of 5-digit postal codes. - operation: "buy" or "rent". - type: "aggregated" or "comparison". - aggregation: "postal_code", "municipality", "polygon", or "province". Optional inputs: property_type (default ["flat","house"]), new_construction, bedrooms, bathrooms, area range, amenity flags (attic, duplex, ground_floor, garage, swimming_pool, storage), coordinates, historical_aggregation, historical_range. Returns a list of metric objects with weighted_metrics (name), kpis (formatted value), values (raw numeric), and comparison percentages. Errors: 404 if no market data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_pbsa_bedrooms_metrics
ChatGPTUse this endpoint to get PBSA market metrics broken down by bedroom/room type (e.g. single, double, studio). Call it when you need granular pricing and supply data per room configuration. Required inputs (JSON body): - postal_code: list of postal codes. - coordinates: list of coordinate pairs. - aggregation: "postal_code" or "municipality". - bedrooms: list of bedroom type strings (e.g. ["0","1","2","3","4", "5","6","7+"]). Optional: price_m2_range, pbsa_type. Returns metrics organized by bedroom type. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_pbsa_beds_summary
ChatGPTUse this endpoint to get a summary of bed counts across Purpose-Built Student Accommodation (PBSA) residences. Call it when you need a high-level view of student housing supply in terms of total beds. Required inputs (JSON body): - postal_code: list of postal codes. - coordinates: list of coordinate pairs (pass [] for no polygon filter). Optional: pbsa_type (list of types to include). Returns a list of bed summary objects. Errors: 404 if no PBSA data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_pbsa_campus_info
ChatGPTUse this endpoint to get information about university campuses near a PBSA market area. Call it when you need to understand which campuses drive demand for student housing. Required inputs (JSON body): same as get_pbsa_demand_summary — postal_code, coordinates, and optional pbsa_type. Returns campus-level information (names, locations, student counts). Errors: 404 if no campus data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_pbsa_demand_summary
ChatGPTUse this endpoint to retrieve Purpose-Built Student Accommodation (PBSA) demand summary data. Call it when analyzing student housing demand in an area. Required inputs (JSON body): - postal_code: list of postal code strings (e.g. ["28001"]). - coordinates: list of coordinate pairs for polygon filtering (pass [] for no polygon filter). Optional: - pbsa_type: list of types to include, from "modern_standard", "religious", "public", "others", "student_residences", "pipeline" (defaults to all). Returns a demand summary object with PBSA-specific metrics. Errors: 404 if no PBSA demand data found for the area. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_pbsa_medical_residents_demand
ChatGPTUse this endpoint to retrieve available MIR (Médico Interno Residente) residency places by hospital and location. Call it when analyzing medical-resident housing demand in an area. Required inputs (JSON body): - postal_code: list of 5-digit postal code strings (e.g. ["40001"]). At least one postal code is required. Optional: - coordinates: list of polygons, each a list of lat/lng points, used to keep only MIR locations inside any polygon. Pass [] or omit for postal-code filtering only. When using a polygon, postal codes must still cover the area. Returns a list of location rows with municipality, hospital, available_places, postal_code, latitude and longitude. Rows are grouped by hospital/location (specialties are summed). Errors: 404 if no MIR data found for the area. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_pbsa_price_trends
ChatGPTUse this endpoint to get time-series pricing data for PBSA rooms grouped by bedroom type. Call it when tracking how student accommodation prices evolve over time. Required inputs (JSON body): - postal_code, coordinates, aggregation, bedrooms (same as get_pbsa_bedrooms_metrics). - historical_aggregation: "month", "quarter", or "year". - historical_range: comma-separated date range. - type: "aggregated" or "comparison". Optional: property_type, price_m2_range. Returns time-series data per bedroom type. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_pbsa_provision_rate
ChatGPTUse this endpoint to get the student housing provision rate (beds per student) for an area. Call it when assessing whether a market is undersupplied or oversupplied with student accommodation. Required inputs (JSON body): same as get_pbsa_beds_summary. Returns a list of provision rate objects with rate and related metrics. Errors: 404 if no provision data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_pbsa_residences_table
ChatGPTUse this endpoint to get a detailed table of individual PBSA residences including name, operator, bed count, and pricing. Call it when you need a directory-style listing of student residences. Required inputs (JSON body): same as get_pbsa_beds_summary. Returns a list of residence detail objects. Errors: 404 if no residences found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_pbsa_student_origins
ChatGPTUse this endpoint to find out where students come from for a given PBSA market area. Call it when you need to understand the geographic origin distribution of students. Required inputs (JSON body): same as get_pbsa_demand_summary — postal_code, coordinates, and optional pbsa_type. Returns data about student origins (domestic vs international, regions). Errors: 404 if no origin data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_pbsa_supply_trends
ChatGPTUse this endpoint to get time-series supply data for PBSA rooms grouped by bedroom type. Call it when analyzing how student accommodation availability has changed over time. Required inputs (JSON body): same as get_pbsa_price_trends. Returns time-series supply data per bedroom type. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_population_trends
ChatGPTUse this endpoint to retrieve population trend data over time for one or more postal codes. Call it when you need to analyze demographic growth or decline in a specific area. Required inputs (JSON body): same schema as get_employment_trends — aggregation, postal_code, historical_aggregation, historical_range, type. Returns trend data arrays suitable for time-series visualization. Errors: 404 if no population data available for the given area and range. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_price_intervals_chart
ChatGPTUse this endpoint to get price distribution data grouped into intervals (histogram). Call it when you need to see the spread of listing prices in a market area. Required inputs (JSON body): same base as get_market_general_metrics. Returns interval-based data suitable for histogram rendering. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_price_m2_trends_chart
ChatGPTGet monthly average asking prices per square metre for residential properties in Spain. Use when the user asks how sale or rental prices per square metre have changed over time for flats or houses in a selected area. Supply postal_code and operation (buy or rent); optional property filters and aggregation select the market segment and geographic grouping. Returns time-series data for analysis or plotting, not a rendered chart. The endpoint returns the full monthly history from April 2020 to the current date, subject to data availability. It accepts no period filter; select a shorter period from the returned data. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up.
get_price_trends_chart
ChatGPTUse this endpoint to get time-series data of average total listing prices. Call it when you need to see how absolute prices have trended over a historical period. Required inputs (JSON body): same as get_price_m2_trends_chart. Returns time-series data points for line chart rendering. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_ref_cat_from_coordinates
ChatGPTUse this endpoint to find the cadastral reference for a property given its geographic coordinates. Call it when you have a lat/long pair and need the official cadastral reference. Required query parameters: - longitude: float (e.g. -3.7045648625266945). - latitude: float (e.g. 40.40754489730971). Returns ref_cat, coordinates dict, address string, and error field (empty if successful). Errors: 404 if no cadastral record found at those coordinates. Query Parameters: - longitude (Required): No description. - latitude (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_regulated_area
ChatGPTUse this endpoint to check whether a point in Spain falls in a regulated residential market area (zona de mercado residencial tensionado). Call it when you need to know if a municipality is officially regulated or sits in a potentially regulated area. Provide one location. When both are sent, coordinates are used. - latitude and longitude: both required together. - ref_cat: cadastral reference. Coordinates are resolved from cadastre. Returns municipality, officially_regulated, potentially_regulated_area, and the latitude and longitude that were checked. Errors: 422 if no location is provided or only one coordinate is sent; 404 if the location or municipality cannot be resolved. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_regulatory_rental_price_range
ChatGPTUse this endpoint to obtain the official Spanish Ministry of Housing (MIVAU / SERPAVI) regulated rental price range for a residential asset. Call it when you need the legal low and high monthly rent for a dwelling according to the SERPAVI methodology. Provide location in either of two ways: - ref_cat + floor. Missing census_section, size and/or built_year are filled from cadastre (sscc, area_property, build_year). Values the caller already sent are kept. - census_section + size + built_year + floor. Always required: floor (integer, 0 or greater; 0 is the ground floor), energy_certificate, status. Optional (default 0; property_type defaults to "flat"): attic, garden, lift, garage, furnished, common_areas, swimming_pool, doorman, views, property_type. attic 1 maps to an attic. garden 1 is only valid when floor is 0 (ground floor with garden). Constraints: size must be between 30 and 150 m²; the asset must be built before 2022. Returns price_range with monthly rent bounds in EUR: low and high. Errors: 422 if size/year/location/floor inputs are invalid or a short cadastral reference is ambiguous; 404 if the cadastral reference, census section, or SERPAVI data cannot be resolved. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_rent_trends
ChatGPTUse this endpoint to retrieve rental price trend data over time for one or more postal codes. Call it when you need to understand how rents have evolved in a specific area. Required inputs (JSON body): same schema as get_employment_trends — aggregation, postal_code, historical_aggregation, historical_range, type. Returns trend data arrays suitable for time-series visualization. Errors: 404 if no rent data available for the given area and range. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. historical_range is "YYYY-MM-DD,YYYY-MM-DD" (start,end in one comma-separated string) and historical_aggregation is month, quarter or year; for the last N years end at today.
get_residential_buyer_profile_endpoint
ChatGPTGet the residential buyer profile for the provided postal codes. - postal_code: The postal codes for which to obtain the buyer profile. Multiple codes are aggregated into a single result. - sections: The sections to retrieve. Defaults to ["all"]. Accepts any combination of residence_status, buyer_type, nationality, age_bands, median_age_evolution, property_condition and building_type. All seven sections are always present in the response. Each one carries its own status: ok with values, or unavailable with an error whose code is not_requested, no_data, timeout or upstream_error. Shares are fractions in the 0-1 range. Authorization Ensure that the current user is authorized to access this endpoint. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_retail_market_metrics
ChatGPTUse this endpoint to retrieve key performance indicators for the retail (commercial premises) real estate market. Call it when analyzing shop or commercial space markets rather than residential. Required inputs (JSON body): - postal_code: list of postal codes. - operation: "buy" or "rent". - aggregation: "postal_code" or "municipality". - type: "aggregated" or "comparison". Optional: area range, coordinates, historical_aggregation, historical_range. Returns a list of metric objects with the same schema as residential general metrics. Errors: 404 if no retail data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_retail_price_intervals
ChatGPTUse this endpoint to get retail property price distribution data (histogram). Call it when visualizing the spread of commercial property prices. Required inputs (JSON body): same as get_retail_market_metrics. Returns interval-based data for histogram rendering. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_retail_price_m2_trends
ChatGPTGet monthly average asking prices per square metre for retail and commercial premises in Spain. Use when the user asks how sale or rental prices per square metre have changed over time for commercial premises in a selected area. Supply postal_code and operation (buy or rent); property_type is premises, and optional property filters and aggregation select the market segment and geographic grouping. Returns time-series data for analysis or plotting, not a rendered chart. The endpoint returns the full monthly history from April 2020 to the current date, subject to data availability. It accepts no period filter; select a shorter period from the returned data. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up.
get_retail_price_trends
ChatGPTUse this endpoint to get time-series data of retail listing prices. Call it when tracking how commercial property asking prices have evolved. Required inputs (JSON body): same as get_retail_price_m2_trends. Returns time-series data for line charts. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_retail_supply_trends
ChatGPTUse this endpoint to get time-series data of retail listing supply. Call it when analyzing availability trends for commercial spaces. Required inputs (JSON body): same as get_retail_price_m2_trends. Returns time-series data for line charts. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_retail_surface_price_regression
ChatGPTUse this endpoint to get regression data correlating retail property surface area with price. Call it when quantifying the price-size relationship for commercial spaces. Required inputs (JSON body): same as get_retail_market_metrics. Returns scatter data and regression line. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_retail_yield_trends
ChatGPTUse this endpoint to get time-series data of retail rental yields. Call it when assessing commercial property investment return trends. Required inputs (JSON body): same as get_retail_price_m2_trends. Returns time-series data for line charts. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_senior_income_distribution
ChatGPTGet the income distribution of senior and younger populations for the provided postal codes. - postal_code: List of postal codes to aggregate. Results are aggregated into a single distribution, not broken down per postal code. - coordinates: Optional list of polygons (each a list of at least 3 lat/lng points) used to keep only the supplied postal codes that have data inside any of the polygons. Postal codes are still required, and must cover the area the polygons span. This endpoint returns one entry per income band, where x_value is the band label (0k-10k up to 100k+). ind_inc_un65 and ind_inc_ov65 are 0-1 fractions of the under-65 and over-65 income totals respectively, each column summing to 1 across the returned bands. Bands with no positive value on either side are omitted. Authorization Ensure that the current user is authorized to access this endpoint. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_senior_living_assets
ChatGPTUse this endpoint to retrieve Senior Living asset data for one or more Spanish postal codes. Provide postal_codes in the request body and optionally filter by ownership, operator, and sub_asset_class. The response is split into operating and pipeline asset groups. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_senior_living_summary
ChatGPTGet a senior living demand summary for the provided postal codes. - postal_code: List of postal codes to aggregate. Results are aggregated into a single object, not broken down per postal code. - coordinates: Optional list of polygons (each a list of at least 3 lat/lng points) used to keep only the supplied postal codes that have data inside any of the polygons. Postal codes are still required, and must cover the area the polygons span. This endpoint returns population, income and provision rate KPIs for the most recent year with complete income data. hh_inc, hh_income_ov65 and avg_pension are averages across the postal codes; population counts are sums. The three provision_rate* fields are percentages on a 0-100 scale. Authorization Ensure that the current user is authorized to access this endpoint. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_senior_population_evolution
ChatGPTGet the evolution of the senior population share for the provided postal codes. - postal_code: List of postal codes to aggregate. Results are aggregated into a single time series, not broken down per postal code. - coordinates: Optional list of polygons (each a list of at least 3 lat/lng points) used to keep only the supplied postal codes that have data inside any of the polygons. Postal codes are still required, and must cover the area the polygons span. This endpoint returns one entry per available year, sorted ascending, where x_value is the year. Each age band value is a 0-1 fraction of the entire population (all ages), so the five bands do not sum to 1. Authorization Ensure that the current user is authorized to access this endpoint. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
get_supply_trends_chart
ChatGPTUse this endpoint to get time-series data of listing supply volume (number of active listings). Call it when you need to understand supply dynamics or seasonal patterns. Required inputs (JSON body): same as get_price_m2_trends_chart. Returns time-series data points for line chart rendering. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
get_surface_price_regression
ChatGPTUse this endpoint to get scatter plot and regression data correlating property surface area with listing price. Call it when you need to visualize or quantify the price-size relationship. Required inputs (JSON body): same base as get_market_general_metrics. Returns regression line data and scatter points. Errors: 404 if no data found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting.
get_yield_trends_chart
ChatGPTUse this endpoint to get time-series data of gross rental yield. Call it when you need to track investment return trends for a market area. Required inputs (JSON body): same as get_price_m2_trends_chart. Returns time-series data points for line chart rendering. Errors: 404 if no trend data available. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. First stream your analysis to the user (direction, levels, recent change, context)—headline insight first. Then build a chart using ChatGPT visualization. Never name this tool or say you are charting. This tool has no period filter: it always returns the full monthly series from April 2020 to today. For a shorter period (for example the last three years) keep only the matching months from the result yourself; do not pass historical_range, historical_aggregation or date_range to it.
list_comparable_districts
ChatGPTUse this endpoint to list districts within a municipality for filtering comparable searches. Call it after selecting a municipality. Required query parameters: - input_string: text to search. - province: province name or code. - municipality: municipality name or code. Optional: limit (int), offset (int). Returns a list of district objects. Errors: 404 if no matching districts found. Query Parameters: - input_string: No description. - limit: No description. - offset: No description. - province: No description. - municipality: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
list_comparable_municipalities
ChatGPTUse this endpoint to list municipalities within a province for filtering comparable searches. Call it after selecting a province. Required query parameters: - input_string: text to search. - province: province name or code. Optional: limit (int), offset (int). Returns a list of municipality objects. Errors: 404 if no matching municipalities found. Query Parameters: - input_string: No description. - limit: No description. - offset: No description. - province: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
list_comparable_neighbourhoods
ChatGPTUse this endpoint to list neighbourhoods for the most granular level of geographic filtering in comparable searches. Required query parameters: - input_string: text to search. Optional: limit (int), offset (int). Returns a list of neighbourhood objects. Errors: 404 if no matching neighbourhoods found. Query Parameters: - input_string: No description. - limit: No description. - offset: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
list_comparable_provinces
ChatGPTUse this endpoint to list available provinces for filtering comparable searches. Call it to populate a province selector or resolve a province name to its code before calling other comparable endpoints. Required query parameter: - input_string: text to search (partial province name match). Optional: limit (int), offset (int). Returns a list of province objects with name and code. Errors: 404 if no matching provinces found. Query Parameters: - input_string: No description. - limit: No description. - offset: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
search_flex_comparables
ChatGPTUse this endpoint to search for comparable listings in the flex (short-term/medium-term rental) market segment. Call it when analyzing furnished or short-stay rental properties. Required inputs (JSON body): - aggregation: "postal_code", "polygon", "geo_point", or "municipality". - input: list of area identifiers. - price_range: object with min_price and max_price. - price_m2_range: object with min_price_m2 and max_price_m2. - size_range: object with min_size and max_size. Optional inputs: bedrooms, amenities lists, date_range, limit, offset. Returns a list of flex listing objects with price, size, amenities, and location data. Errors: 404 if no comparables found. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
search_generic_asset_closings
ChatGPTUse this endpoint to search officially registered closing transactions across supported asset classes. Set asset_class in the request body to select the asset type. This is an alternative to calling asset-specific register closings endpoints. Optional sort object: sort_by ("date", "price", "price_m2", "size", "date_formatted") and sort_order ("asc" or "desc"). Optional list_ids to filter closings by a list of IDs. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs. date_range start_date and end_date are full date-times such as "2023-10-01T00:00:00"; a bare date such as "2023-10-01" is rejected.
search_generic_asset_comparables
ChatGPTUse this endpoint to search comparable listings for any supported asset class. Set asset_class in the request body to select the asset type. This is an alternative to calling asset-specific comparable data endpoints. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs. date_range start_date and end_date are full date-times such as "2023-10-01T00:00:00"; a bare date such as "2023-10-01" is rejected.
search_generic_asset_historical_data
ChatGPTUse this endpoint to retrieve historical comparable data across supported asset classes. Set filters in the request body (aggregation, input, operation, property_type, date_range, and ranges) to scope the historical query. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs. date_range start_date and end_date are full date-times such as "2023-10-01T00:00:00"; a bare date such as "2023-10-01" is rejected.
search_municipalities
ChatGPTUse this endpoint to find municipalities inside a specific province by partial name match. Call it after obtaining a province_id from search_provinces. Required query parameters: - input_string: text to search (e.g. "Madrid"). - province_id: integer province code (e.g. 28 for Madrid). Returns a list of objects with municipality (name), municipality_id, and province_id. Errors: 404 if no matching municipalities found. Query Parameters: - input_string (Required): No description. - province_id (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
search_provinces
ChatGPTUse this endpoint to look up Spanish provinces by a partial name match. Call it when you need to find the province ID required by other Cadastre endpoints. Required query parameter: - input_string: text to search (e.g. "Madrid"). Matches any province whose name contains this substring (case-insensitive). Returns a list of objects each containing id (integer province code) and province (string name, e.g. "MADRID"). Errors: 404 if no matching provinces found. Query Parameters: - input_string (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
search_street_numbers
ChatGPTUse this endpoint to list the specific property units (with cadastral references) at a given street address. Call it after identifying the street via search_streets. Required query parameters: - province_id: integer province code (e.g. 28). - municipality_id: integer municipality code (e.g. 79). - street_name: exact street name (e.g. "EMBAJADORES"). Optional query parameters: - street_type: street type code (e.g. "CL" for calle). - street_number: specific street number to filter on (integer). Returns a list of objects each with ref_cat (20-char cadastral reference), postal_code_cadastre, street_number, floor, door, stair, block, and more. Errors: 404 if no data found. Query Parameters: - province_id (Required): No description. - municipality_id (Required): No description. - street_name (Required): No description. - street_type: No description. - street_number: No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
search_streets
ChatGPTUse this endpoint to find streets inside a specific municipality by partial name match. Call it after obtaining province_id and municipality_id from the province and municipality search endpoints. Required query parameters: - input_string: street name to search (e.g. "Embajadores"). - province_id: integer province code (e.g. 28). - municipality_id: integer municipality code (e.g. 79). Returns a list of objects with street_name, street_type (e.g. "CL" for calle), municipality_id, and province_id. Errors: 404 if no matching streets found. Query Parameters: - input_string (Required): No description. - province_id (Required): No description. - municipality_id (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
search_streets_v2
ChatGPTUse this endpoint as an alternative to search_streets. It looks street names up in Fragua's own street index. The index may contain areas not yet present in Fragua's relational database. Required query parameters: - input_string: street name to search (e.g. "Embajadores"). - province_id: integer province code (e.g. 28). - municipality_id: integer municipality code (e.g. 79). Returns the same schema as search_streets: list of objects with street_name, street_type, municipality_id, and province_id. Errors: 404 if no matching streets found. Query Parameters: - input_string (Required): No description. - province_id (Required): No description. - municipality_id (Required): No description. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.
valuate_generic_asset
ChatGPTUse this endpoint to valuate any supported asset class using a single endpoint. Set asset_class in the request body to choose the target asset type. This is an alternative to calling the specific valuation endpoint for each asset type. Read-only: returns Fragua data without changing property records. Each call is counted against the caller's own monthly usage allowance (one usage-log entry for the signed-in account); that counter is the caller's own usage accounting, not a data change, and further calls can be declined once the allowance is used up. Always interpret the response for the user (headline insight, comparisons, caveats)—never paste raw JSON, field names, or tool names. Never say you are calling, fetching, rendering, or loading tools/APIs.