# MolCloud Reverse Geocoding API

> MolCloud Reverse Geocoding API is a paid API for AI agents from api.molcloud.net, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-17).

Converts latitude/longitude coordinates into a human-readable location name and country code

## Facts

- Endpoint: GET https://api.molcloud.net/api/geo/reverse?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/molcloud-reverse-geocoding-api-7094433e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Sg7Z5rxqabaCT72aIdm6d

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 molcloud-reverse-geocoding-api-7094433e
```

Example prompt: What city and country are at coordinates latitude 52.3676 and longitude 4.9041?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call reverse geocoding lookup that returns a city-level display name and country code without a subscription. Ideal for AI agents that sporadically need to humanize GPS coordinates and want to settle micro-payments in USDC via x402 rather than managing API keys or monthly billing.

## Known failure modes

- Missing lat or lon parameter returns an error
- Out-of-range coordinates (e.g. lat > 90) may return an error or empty result
- Coordinates in remote ocean areas may return no displayName
- Network timeout or upstream geocoding provider failure

## How this service works

40 pay-per-request AI, search, headless browser, crypto alpha & memory APIs for autonomous agents settling in USDC on Base via x402 v2.

## Output

Returns a JSON object containing a 'displayName' field (e.g. 'Amsterdam, Netherlands') and a 'countryCode' field (e.g. 'NL'), along with a status field indicating success and the endpoint path.

## 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",
    "queryParams"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "lat",
      "lon"
     ],
     "properties": {
      "lat": {
       "type": "number",
       "description": "Latitude coordinate"
      },
      "lon": {
       "type": "number",
       "description": "Longitude coordinate"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "status",
      "endpoint"
     ],
     "properties": {
      "data": {
       "type": "object"
      },
      "payer": {
       "type": "string"
      },
      "status": {
       "enum": [
        "success"
       ],
       "type": "string"
      },
      "endpoint": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "countryCode": "NL",
   "displayName": "Amsterdam, Netherlands"
  },
  "status": "success",
  "endpoint": "/api/geo/reverse"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/molcloud-reverse-geocoding-api-7094433e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.molcloud.net](https://www.zero.xyz/host/api.molcloud.net/llms.txt)