CATEGORY

Location And Travel x402 offerings

Browse indexable location and travel x402 offerings, including provider, method, and service details.

1007 indexable offerings in this category.

Offerings

Page 13 of 42

Creates or inspects H3 cells and optionally returns neighbors or changes resolution. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age.

Api EndpointProvider: geo.halowerk.com

Converts WGS84 latitude and longitude to MGRS using the open mgrs library. Missing facts are returned as null and named in unavailable_fields where applicable. Derived values disclose their method; source-backed values disclose source, time window and age.

Api EndpointProvider: geo.halowerk.com

Forward-geocode a street address or place name (WORLDWIDE) to coordinates + parsed address components via OpenStreetMap Nominatim (public, keyless).

Api EndpointProvider: payai.agentstools.dev

Forward-geocode a street address or place name (WORLDWIDE) to coordinates + parsed address components via OpenStreetMap Nominatim (public, keyless).

Api EndpointProvider: api.agentstools.dev

Turn a Spanish address, street, town or place into coordinates with the official CartoCiudad geocoder (IGN): normalized address, municipality and INE code, province, region, postcode and lat/lon.

Api EndpointProvider: api.vextorium.com

Reverse-geocode coordinates (WORLDWIDE) to a street address + parsed components via OpenStreetMap Nominatim; enriched with the nearest NWS city/state when the point is in the US.

Api EndpointProvider: api.agentstools.dev

Reverse-geocode coordinates (WORLDWIDE) to a street address + parsed components via OpenStreetMap Nominatim; enriched with the nearest NWS city/state when the point is in the US.

Api EndpointProvider: payai.agentstools.dev

Forward and reverse geocoding on OpenStreetMap data: turn place names, addresses, and landmarks into coordinates with structured address components (forward), or turn lat/lon into the nearest address (reverse). Global coverage, up to 10 ranked results. ODbL attribution included in every response. POST a JSON body like: {"query":"eiffel tower, paris","limit":1}

Api EndpointProvider: keyronne.com

Geocoding and reverse geocoding from GeoNames: city, town or postal code to lat/lon, and lat/lon to the nearest place and postal code. Covers 170,000 places with 1000+ inhabitants and 1.8 million postal codes worldwide, answered from our own database in milliseconds. Not street level: house numbers and streets are skipped and reported in ignored_parts. Provide address (e.g. 'Paris, Texas', '10115 Berlin') or lat + lon.

Api EndpointProvider: agentsvc.io

Geohash encoder and decoder: encode a WGS-84 latitude and longitude to a geohash at a chosen precision, or decode a geohash back to its bounding box, centre point and error bounds in metres. Encoding also returns the eight neighbouring cells, which is what a caller needs to do proximity search over a geohash-indexed store without a spatial database.

Api EndpointProvider: api.duoleads.com

Give it a longitude and latitude inside the United States and it answers with the Census FIPS codes for that point: the 2-digit state code, the 5-digit county GEOID, and the GEOID of the congressional district. Parameters go in the query string: this is a GET, there is no body. The codes are the product and the names are a courtesy. A county GEOID is the join key to essentially every geography-keyed federal dataset -- the American Community Survey, BLS Local Area Unemployment Statistics, BEA regional accounts, CDC WONDER, HUD, USDA, FEMA -- and the state code is its first two digits, so one call gives you both keys already in the form those tables expect. County GEOID is also the first five digits of a tract GEOID (11 digits) and of a block group GEOID (12), so it is the prefix you would filter a tract-level extract down with. COVERAGE, stated up front because the shortfall is the point: this endpoint answers state, county and congressional district, and it does NOT answer tract, block group, place or ZCTA. That is a size limit, not an oversight, and it was measured rather than guessed. A national compacted H3 index of tracts is 3196 KiB gzipped and of block groups 5335 KiB, at a resolution already too coarse for either; the whole Worker has 3 MiB compressed to spend and most of that was gone before this route existed. Those four tiers need an object store behind the Worker and will arrive with one. Every response repeats this under `coverage`, so an agent never has to infer it from a missing field. In the meantime geocoding.geo.census.gov answers all seven tiers, free, authoritative, at the cost of a round trip and a dependency. VINTAGE: TIGER/Line 2025, congressional districts for the 119th Congress. It is on every response under `vintage` and it matters more here than almost anywhere else in this catalog, because TIGER is re-cut annually and districts move with redistricting, so a stale district code is a wrong answer a caller cannot detect from the outside. Noth

Api EndpointProvider: api.geoprimitives.dev

Geospatial computation. op=distance (lat1,lon1,lat2,lon2 -> km and miles) or op=geohash (lat,lon,precision? -> geohash string). Inputs as query params.

Api EndpointProvider: x402.shizu.me

Convert an MGRS grid reference back to decimal lat/lon on WGS84 (the coordinate of the grid cell's south-west corner at the given precision). Whitespace is ignored; a malformed reference is a clean 4…

Api EndpointProvider: geospatial.openverbs.com