Near-Earth Asteroids (NASA)
Upcoming near-earth object close approaches from NASA's official NeoWs API: names, estimated diameters, miss distances in kilometers, relative velocities and the hazard classification. Live planetary-defense data — the kind of fact agents cannot invent.
Worked examples
Next 3 days
GET /api/v1/live/nasa-neo?days=3
Result: 30 object(s) approaching within 3d — closest: (2017 UX7) at 6,500,634 km (Ø ~45 m)
This week, hazardous only
GET /api/v1/live/nasa-neo?days=7&hazardousOnly=true
Result: 5 object(s) approaching within 7d — closest: 518810 (2010 CF19) at 22,895,177 km (Ø ~254 m)
Tomorrow
GET /api/v1/live/nasa-neo?days=1
Result: 17 object(s) approaching within 1d — closest: (2017 UX7) at 6,500,634 km (Ø ~45 m)
Machine API (x402)
$0.02 / callThis tool is also a JSON API for AI agents. Requests without payment receive 402 Payment Required plus instructions; agents pay USDC on Base via the x402 protocol — no accounts, no API keys.
GET /api/v1/live/nasa-neo?days=3 HTTP/1.1
Host: agentstoolshub.com
→ 402 (payment required, instructions in headers)
→ 200 (after X-PAYMENT header; JSON body below)
{
"tool": "live/nasa-neo",
"input": {"days":3},
"result": { "value": 30, "answer": "30 object(s) approaching within 3d — closest: (2017 UX7) at 6,500,634 km (Ø ~45 m)" }
}Agent docs: /llms.txt · OpenAPI spec · integration guide
About this tool
NASA's near-earth-object feed, live: every asteroid closing in over the next 1-7 days with estimated diameter, miss distance and relative velocity, sorted by closest approach and filterable to potentially-hazardous objects. The definitive source — NASA JPL's own data, cached 30 minutes.
Frequently asked questions
What does 'potentially hazardous' actually mean?
A NASA classification: magnitude bright enough and an orbit passing within ~19.5 lunar distances. It's a long-term monitoring flag — none of the listed objects threaten an imminent impact.
Why does it sometimes fail?
The tool uses NASA's public DEMO_KEY (30 requests/hour/IP, no signup). Under heavy shared use the rate limit can bite; responses are cached 30 minutes to stretch the quota.