geo.nearby

Everything around a coordinate in one call: nearby airports (IATA/ICAO, type, distance), public K-12 schools (name, district, enrollment, distance), NOAA climate stations (for chaining into /api/climate/station-history), and earthquakes from the past week (magnitude, depth, time). Pass lat/lon plus optional radiusKm (default 25, max 200) and per-category limit (default 5). Each category returns an independent found/error block, so one slow source never empties the rest. Site assessment, relocation research, travel planning, and risk screening. Each category is also a standalone endpoint (/api/airport/near, /api/edu/school-lookup, /api/climate/station-near, /api/quakes/recent).

price
$0.0036 USDC per call
method
GET/api/geo/nearby
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The nearby API is a pay-per-call geo endpoint built for AI agents and autonomous software. Everything around a coordinate in one call: nearby airports (IATA/ICAO, type, distance), public K-12 schools (name, district, enrollment, distance), NOAA climate stations (for chaining into /api/climate/station-history), and earthquakes from the past week (magnitude, depth, time).

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in nearby data source for an agent tool-use loop, an MCP host, or a backend that needs geo data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
latrequirednumber
min -90 · max 90
lonrequirednumber
min -180 · max 180
radiusKmnumber
min 1 · max 200
limitinteger
min 1 · max 20

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/geo/nearby?lat=-90&lon=-180&radiusKm=25&limit=5'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/geo/nearby?lat=-90&lon=-180&radiusKm=25&limit=5' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/geo/nearby?lat=-90&lon=-180&radiusKm=25&limit=5'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.geo.nearby({
  "lat": -90,
  "lon": -180,
  "radiusKm": 25,
  "limit": 5
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.geo.nearby(lat=-90, lon=-180, radiusKm=25, limit=5)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "geo.nearby",
    "arguments": {
      "lat": -90,
      "lon": -180,
      "radiusKm": 25,
      "limit": 5
    }
  }
}

Response

FieldTypeDescription
latnumber
lonnumber
radiusKmnumber
airportsobject
schoolsobject
climateStationsobject
quakesobjectEarthquakes within radiusKm (min 50km search radius) from the past 7 days, magnitude ≥ 2.
sourcesarray
Example response datajson
{
  "lat": 1,
  "lon": 1,
  "radiusKm": 1,
  "airports": {
    "found": false,
    "error": "example",
    "count": 1,
    "items": [
      {}
    ]
  },
  "schools": {
    "found": false,
    "error": "example",
    "count": 1,
    "items": [
      {}
    ]
  },
  "climateStations": {
    "found": false,
    "error": "example",
    "count": 1,
    "items": [
      {}
    ]
  },
  "quakes": {
    "found": false,
    "error": "example",
    "count": 1,
    "items": [
      {}
    ]
  },
  "sources": [
    {
      "provider": "example",
      "url": "example",
      "license": "example"
    }
  ]
}

FAQ

Do I need an API key to use the nearby API?
No. geo.nearby is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the nearby API cost?
$0.0036 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the nearby API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call geo.nearby from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: nearby api · geo nearby api · nearby api for ai agents · x402 geo api · nearby api no api key · pay per call nearby api · geo api