# Geospatial OpenVerbs Coordinate Parser

> Geospatial OpenVerbs Coordinate Parser is a paid API for AI agents from geospatial.openverbs.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-15).

Parses a coordinate string in decimal or DMS format into normalized decimal latitude and longitude values

## Facts

- Endpoint: POST https://geospatial.openverbs.com/v1/parse
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/geospatial-openverbs-coordinate-parser-952d3909
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bzDmGH-SgG7H84E_zx3bH

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability geospatial-openverbs-coordinate-parser-952d3909 -d '<json body>'
```

Example prompt: Parse this coordinate string for me — '40°26'46"N 79°58'56"W' — and give me the decimal lat/lon.

## When to prefer this

Use this endpoint when you need to reliably parse and normalize coordinate strings that may arrive in either plain decimal (e.g. '40.4462, -79.9822') or DMS-with-hemisphere format (e.g. '40°26'46"N 79°58'56"W'). Prefer it over manual parsing when input format is unpredictable and you need a guaranteed clean decimal output or a well-defined error. It complements sibling endpoints on the same platform for downstream operations like geohashing, timezone lookup, or UTM conversion.

## Known failure modes

- Unrecognized coordinate format returns 400 Bad Request
- Input outside valid lat/lon range may return 400
- Missing or empty coordinate field returns 400 validation error
- Ambiguous coordinate strings (missing hemisphere, malformed DMS) return 400

## How this service works

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.

## Output

Returns the parsed decimal latitude and longitude values extracted from the input coordinate string. Invalid or unrecognized coordinate formats result in a clean 400 error response.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "coordinate"
     ],
     "properties": {
      "coordinate": {
       "type": "string",
       "maxLength": 256,
       "minLength": 1,
       "description": "Coordinate string (decimal pair or DMS)."
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/geospatial-openverbs-coordinate-parser-952d3909/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from geospatial.openverbs.com](https://www.zero.xyz/host/geospatial.openverbs.com/llms.txt)