{"files":{"SKILL.md":"---\nname: idealspot-geodata\ndescription: \"IdealSpot GeoData API skill. Use when working with IdealSpot GeoData for data, geometries, traffic. Covers 7 endpoints.\"\nversion: 1.0.0\ngenerator: lapsh\n---\n\n# IdealSpot GeoData\nAPI version: 1.0\n\n## Auth\nApiKey X-RapidAPI-Key in header\n\n## Base URL\nhttps://idealspot-geodata.p.rapidapi.com/api/v1\n\n## Setup\n1. Set your API key in the appropriate header\n2. GET /data/insights -- fetch available insights\n3. Explore available endpoints below\n\n## Endpoints\n7 endpoints across 3 groups. See references/api-spec.lap for full details.\n\n### Data\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /data/insights | Fetch Available Insights |\n| GET | /data/insights/{insight_id:} | Fetch Insight Query Parameters |\n| GET | /data/insights/{insight_id:}/query | Query Insight at Location |\n\n### Geometries\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /geometries/regions/intersecting/{latitude}/{longitude} | Fetch Administrative Regions using Lat/Lng |\n| GET | /geometries/geometry | Fetch Geometries |\n\n### Traffic\n| Method | Path | Description |\n|--------|------|-------------|\n| GET | /traffic/roads/nearest/{latitude}/{longitude} | Fetch Nearest Road Segments |\n| GET | /traffic/counts/{segment_id} | Vehicle Traffic Counts for Road Segment |\n\n## Common Questions\nMatch user requests to endpoints in references/api-spec.lap. Key patterns:\n- \"List all insights?\" -> GET /data/insights\n- \"Get insight details?\" -> GET /data/insights/{insight_id:}\n- \"List all query?\" -> GET /data/insights/{insight_id:}/query\n- \"Get intersecting details?\" -> GET /geometries/regions/intersecting/{latitude}/{longitude}\n- \"List all geometry?\" -> GET /geometries/geometry\n- \"Get nearest details?\" -> GET /traffic/roads/nearest/{latitude}/{longitude}\n- \"Get count details?\" -> GET /traffic/counts/{segment_id}\n- \"How to authenticate?\" -> See Auth section above\n\n## Response Tips\n- Check response schemas in references/api-spec.lap for field details\n\n## References\n- Full spec: See references/api-spec.lap for complete endpoint details, parameter tables, and response schemas\n\n> Generated from the official API spec by [LAP](https://lap.sh)\n","references/api-spec.lap":"@lap v0.3\n# Machine-readable API spec. Each @endpoint block is one API call.\n@api IdealSpot GeoData\n@base https://idealspot-geodata.p.rapidapi.com/api/v1\n@version 1.0\n@auth ApiKey X-RapidAPI-Key in header\n@common_fields {X-RapidAPI-Key: any # (Required) Rapid API Key. See https://rapidapi.com/idealspot-inc-idealspot-inc-default/api/idealspot-geodata, X-RapidAPI-Host: any}\n@endpoints 7\n@toc data(3), geometries(2), traffic(2)\n\n@group data\n@endpoint GET /data/insights\n@desc Fetch Available Insights\n@returns(200)\n\n@endpoint GET /data/insights/{insight_id:}\n@desc Fetch Insight Query Parameters\n@required {insight_id:: any # Insight ID. See developer documentation for full list.}\n@returns(200)\n\n@endpoint GET /data/insights/{insight_id:}/query\n@desc Query Insight at Location\n@required {version: any # (Required) Insight version. Insight versions are incremented when a response format changes in any way, including the addition of new groups. Old versions are retained, unmodified, for backwards compatibility., location[]: any # (Required) Represents a buffer, region, or custom polygon specification. Accepts the `Location` model (as a `Buffer`, `Region`, or `Custom Polygon`) formatted as a JSON string. Multiple `location` query parameters are allowed. NOTE: When requesting multiple locations, you must include brackets(i.e. `?location[]=...&location[]=...`). If not included, only the last location will be used. For more detail, see https://idealspot.gitlab.io/developer-docs/#location, insight_id:: any # Insight ID. See https://developer.idealspot.com/data for full list.}\n@returns(200)\n\n@endgroup\n\n@group geometries\n@endpoint GET /geometries/regions/intersecting/{latitude}/{longitude}\n@desc Fetch Administrative Regions using Lat/Lng\n@required {latitude: any # (Required) Search coordinate latitude, longitude: any # (Required) Search coordinate longitude}\n@returns(200)\n\n@endpoint GET /geometries/geometry\n@desc Fetch Geometries\n@required {location[]: any: any # (Required) Represents a buffer, region, or custom polygon specification. Accepts the `Location` model (as a `Buffer`, `Region`, or `Custom Polygon`) formatted as a JSON string. Multiple `location` query parameters are allowed. NOTE: When requesting multiple locations, you must include brackets(i.e. `?location[]=...&location[]=...`). If not included, only the last location will be used.}\n@returns(200)\n\n@endgroup\n\n@group traffic\n@endpoint GET /traffic/roads/nearest/{latitude}/{longitude}\n@desc Fetch Nearest Road Segments\n@required {n: any # Number of road segments to return (between 1 and 20), latitude: any # (Required) Search coordinate latitude, longitude: any # (Required) Search coordinate longitude}\n@returns(200)\n\n@endpoint GET /traffic/counts/{segment_id}\n@desc Vehicle Traffic Counts for Road Segment\n@required {segment_id: any # (Required) Road segment ID. Fetched from Search Road Segments}\n@returns(200)\n\n@endgroup\n\n@end\n"}}