Inteligencia de ubicaciones para empresas y expansión | Pickgeo

Account / Get Current User

Get Current User

Account / Get Monthly Usage

Get Monthly Usage

Usage / Get Account Limits

Get Account Limits

Usage / Get Endpoint Usage Monthly

Get Endpoint Usage Monthly

Usage / Get Current Month Endpoint Usage

Get Current Month Endpoint Usage

Usage / Get Current Month Total Usage

Get Current Month Total Usage

Usage / Get Request History Monthly Route

Get Request History Monthly Route

Usage / Get Recent History

Get Recent History

Billing / List Payments

List Payments

Geo Datasets / List Geo datasets

Returns the full catalog of public Geo datasets accepted by `/v2/geo/datasets/{dataset}/query`. Use this endpoint to discover the dataset identifier, migration path from v1, supported area selectors, supported response formats, and the metric families each dataset returns. Use this catalog before querying `/v2/geo/datasets/{dataset}/query`; it lists dataset IDs, supported area selectors, response formats, and metric-family notes.

Geo Datasets / Query a Geo dataset

Queries one Pickgeo dataset for a typed geography. Authenticate with `X-API-Key` or `Authorization: Bearer <token>`. The request body selects the country, area, and response format. The backend never infers country from coordinates or polygons. Single-area responses use `data.metrics`; multi-row responses use `data.results`. Metric keys are dataset-specific and keep the existing Pickgeo metric naming. Call `GET /v2/geo/datasets` for the dataset catalog, supported area selectors, supported respon

Geo POIs / Query points of interest

Queries grouped points of interest from the selected provider. The response always uses `data.pois` as a flat list of category group objects for both OSM and Overture. Each POI group has `name`, `count`, `brands`, and optional `marker_type` / `category` fields. Each brand contains coordinate objects with explicit `latitude` and `longitude` fields. Use the tool input schema country_code enum for currently accepted countries. Spain remains the default when country_code is omitted, and the backend

Geo Similar Zones / Find similar zones

Finds spatially supported zones similar to a source area. The source area uses the same typed v2 `area` object as Geo dataset queries. The backend builds a feature vector from census-section data, scores candidate sections, applies spatial smoothing and clustering so isolated matching sections are not returned as zones, and optionally re-scores shortlisted clusters with POI category mix. No analytical tables are required; all similarity features are computed from existing country-specific Pickge

Geo Business Rules / List business-rule features

Returns the feature identifiers accepted by `/v2/geo/business-rules/query`. Business-rule queries combine these features with percentile ranges, resolved server-side for the requested country from country-specific Pickgeo tables. Use this catalog before querying `/v2/geo/business-rules/query`.

Geo Business Rules / Filter sections by business rules

Finds spatially supported census sections that satisfy AND-combined percentile rules. Provide a typed v2 `area` or exactly one province or municipality filter; unbounded country-wide queries are rejected. The backend resolves percentiles to country-specific thresholds and never infers country from coordinates or polygons. Send percentile ranges, not raw thresholds. Bound each query with a typed v2 `area` or one province/municipality filter. Default `limit` is compact for LLM context; raise it o

Geo Reverse Geocoding / Resolve location fields from coordinates

Resolves a lat/lon point to separate location fields: street, district, neighborhood, municipality, province, and census section. The administrative fields are resolved locally from country-specific Pickgeo section and municipality tables; coordinates are never used to infer country, so provide `country_code` for non-Spain points. The street field is a local nearest-street match where Pickgeo has a street/traffic segment source, not a full Google-style postal address. Neighborhoods currently com

Pedestrian Traffic / Query pedestrian traffic

Returns pedestrian traffic metrics for a provider segment identifier, or resolves the nearest Spain traffic segment from an address or lat/lon point. Use the GET segment resource when a known segment id is available and a body is unnecessary. Spain-only pedestrian traffic lookup. Provide either `segment_id` when known, or `area` as a direct JSON object with `type=point` plus lat/lon or `type=address`; the API resolves the nearest traffic segment within `max_distance_meters`.

Pedestrian Traffic / Get pedestrian traffic segment

Returns pedestrian traffic metrics for one segment identifier.

Commercial Premises / Search commercial premises listings

Searches individual commercial-premises listings from shared listing sources. This is separate from Geo datasets `rental-premises` and `sale-premises`, which return only aggregated market indicators. Sources currently include `portals`, `brickbro`, and `cassandra`; client-scoped `Propios` listings are not included. Listings expose a normalized `url` when the source provides a viewable listing or opportunity URL. Searches individual Spain-only commercial-premises listings from shared sources (`p

BORME Companies / Search BORME companies

Searches GSRAW BORME/company records around a Spanish point and activity text. Use it to discover nearby legal entities, company identifiers, activity, address, administration, status, and distance fields. Returned row coordinates can be approximate because GSRAW may fall back from address geocoding to postal-code or municipality geocoding. Spain-only GSRAW BORME company search. Coordinates are used as the search center, not for country inference. Returned row lat/lon values can be approximate:

BORME Companies / Search BORME company positions

Searches GSRAW BORME company officer/position records around a Spanish point, activity text, and person-name fragment. Use it to link people, roles, dates, and company details. Returned row coordinates can be approximate because GSRAW may fall back from address geocoding to postal-code or municipality geocoding. Spain-only GSRAW BORME person/company-position search. Use employee for the person-name fragment. Company lat/lon values can be approximate geocoding references rather than exact compan