List near-Earth asteroid/comet close approaches to Earth within a date window and maximum distance, from NASA JPL's Close-Approach Data API. Filter by dateMin / dateMax (YYYY-MM-DD) and distMaxAu (max approach distance in AU; default 0.05 AU ≈ 19.5 lunar distances). Each approach: object designation, close-approach date (UTC), nominal + minimum distance in AU and lunar distances, relative velocity (km/s), and absolute magnitude H (a size proxy). Sorted nearest-first. Planetary-defense, observation planning, and "what's passing by this month" queries. Public-domain NASA/JPL data; for full physical/orbital params of a listed object see /api/space/body.
/api/space/close-approachesPAYMENT-SIGNATURE.The close approaches API is a pay-per-call space endpoint built for AI agents and autonomous software. List near-Earth asteroid/comet close approaches to Earth within a date window and maximum distance, from NASA JPL's Close-Approach Data API.
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 close approaches data source for an agent tool-use loop, an MCP host, or a backend that needs space data on demand without onboarding to yet another vendor portal.
| Name | Type | Description |
|---|---|---|
dateMin | string | match ^\d{4}-\d{2}-\d{2}$ |
dateMax | string | match ^\d{4}-\d{2}-\d{2}$ |
distMaxAu | number | min 0.0001 · max 1 |
limit | integer | min 1 · max 200 |
# 1. Probe with no auth → 402 envelope with PaymentRequirements curl -sS 'https://2s.io/api/space/close-approaches?dateMin=2024-01-01&dateMax=2024-01-01&distMaxAu=0.05&limit=50' # 2. Sign + retry with PAYMENT-SIGNATURE: curl -sS 'https://2s.io/api/space/close-approaches?dateMin=2024-01-01&dateMax=2024-01-01&distMaxAu=0.05&limit=50' \ -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/space/close-approaches?dateMin=2024-01-01&dateMax=2024-01-01&distMaxAu=0.05&limit=50'
import { TwoS } from '@2sio/sdk'
const client = new TwoS({
privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})
const result = await client.space.closeApproaches({
"dateMin": "2024-01-01",
"dateMax": "2024-01-01",
"distMaxAu": 0.05,
"limit": 50
})
console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)import os
from twosio import TwoS
client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])
result = client.space.close_approaches(dateMin="2024-01-01", dateMax="2024-01-01", distMaxAu=0.05, limit=50)
print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)// 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": "space.close-approaches",
"arguments": {
"dateMin": "2024-01-01",
"dateMax": "2024-01-01",
"distMaxAu": 0.05,
"limit": 50
}
}
}| Field | Type | Description |
|---|---|---|
ok | boolean | one of: true |
items | array | |
total | integer | Total matching rows upstream; null when unknown. |
source | object |
{
"ok": true,
"items": [
{
"designation": "example",
"date": "example",
"julianDate": 1,
"distanceAu": 1,
"distanceMinAu": 1,
"distanceLd": 1,
"relativeVelocityKmS": 1,
"absoluteMagnitudeH": 1
}
],
"total": 1,
"source": {
"provider": "example",
"url": "example",
"license": "example"
}
}