geospatial.openverbs.com
https://geospatial.openverbs.com/v1/to-dmsPaid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
x402 readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 64.9/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 10/10 | Payment requirements carry a payee, a mainnet network and a price. |
| Live 402 challenge | 25/25 | Paid endpoint answers with an HTTP 402 challenge (229 ms). |
| x402 version | n/a | x402 version not observed yet. |
| Signed descriptor | n/a | No x402 standard defines a signed descriptor. |
| Uptime (30 days) | 15/15 | 32/32 probes succeeded over 30 days (100%). |
| Resource declaration | 10/10 | Declares 15 paid resource(s). |
| Verified identity | 5/10 | Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control. |
| Freshness + modern flags | 1/5 | not seen in a source for over 30 days; declares x402. |
| Security declaration | n/a | Payment is the access control for an x402 resource. |
Compared with peers
Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 88 · peer median 78
- Latency
- Faster than 45% of peers
- This listing 229 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
- Freshness + modern flags −4
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402.
Paid endpoints
15 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
https://geospatial.openverbs.com/v1/to-dms
Convert a decimal-degree latitude/longitude to degrees-minutes-seconds, with hemisphere letters and a formatted string for each axis.
https://geospatial.openverbs.com/v1/parse
Parse a coordinate string into decimal lat/lon. Accepts a plain decimal pair ('40.4462, -79.9822') or DMS with hemisphere letters ('40°26'46"N 79°58'56"W'). Anything unrecognized is a clean 400.
https://geospatial.openverbs.com/v1/utm
Convert decimal lat/lon to a UTM coordinate (zone, latitude band, hemisphere, easting, northing) on WGS84, including the Norway/Svalbard zone exceptions. Defined for latitudes -80..84.
https://geospatial.openverbs.com/v1/from-utm
Convert a UTM coordinate (zone, hemisphere, easting, northing) back to decimal lat/lon on WGS84.
https://geospatial.openverbs.com/v1/mgrs
Convert decimal lat/lon to a Military Grid Reference System (MGRS) string on WGS84. Precision is the number of digits per axis (1–5; 5 = 1-metre resolution, default 5).
https://geospatial.openverbs.com/v1/from-mgrs
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 400.
https://geospatial.openverbs.com/v1/forward
Project WGS84 longitude/latitude (degrees) to Web Mercator (EPSG:3857) easting/northing in metres. Latitude is clamped to ±85.0511° (the projection's valid extent).
https://geospatial.openverbs.com/v1/inverse
Un-project Web Mercator (EPSG:3857) easting/northing in metres back to WGS84 longitude/latitude in degrees.
https://geospatial.openverbs.com/v1/tile
Map a WGS84 coordinate at a given zoom (0..30) to its slippy-map (XYZ / Google / OSM) tile x,y and its Bing quadkey.
https://geospatial.openverbs.com/v1/tile-bounds
Compute the geographic bounding box (west/south/east/north in degrees) of a slippy-map tile z/x/y, plus its Bing quadkey.
https://geospatial.openverbs.com/v1/resolution
Report the ground resolution (metres per pixel, for 256-px tiles) and the OGC map scale denominator at a zoom level, optionally adjusted for latitude (default equator).
https://geospatial.openverbs.com/v1/distance
Distance and initial bearing between two coordinates.
https://geospatial.openverbs.com/v1/geohash
Encode a coordinate to a geohash and return its bounding box and 8 neighbors.
https://geospatial.openverbs.com/v1/timezone
Resolve the timezone for a latitude/longitude.
https://geospatial.openverbs.com/v1/point-in-polygon
Test whether a coordinate falls inside a polygon.
How to call
curl -sS -i -X POST https://geospatial.openverbs.com/v1/to-dms # expect HTTP 402 Payment Required (about 0.002 USDC/call)
Listed in
Directories this entry was found in.