# NASA Near Earth Asteroids and Planetary Hazard Radar (`adaptive_nightmare/nasa-neo-asteroids-radar`) Actor

Extract NASA Near Earth Asteroids and Planetary Hazard data in clean JSON or CSV. Query by daysRange, hazardousOnly for records, engagement metrics, and metadata. Export datasets, run via API or Python/Node.js SDK, schedule runs, or integrate with webhooks with zero proxy fees.

- **URL**: https://apify.com/adaptive_nightmare/nasa-neo-asteroids-radar.md
- **Developed by:** [Darim Quraishi](https://apify.com/adaptive_nightmare) (community)
- **Categories:** Education, News, AI
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.15 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## NASA Near Earth Asteroids and Planetary Hazard Radar

Track near-Earth asteroid approaches, estimated diameters, relative velocities, close approach miss distances, and hazard flags from the NASA Near Earth Object program.

### Features

- Scrapes the official NASA Jet Propulsion Laboratory (JPL) Near Earth Object Web Service (NeoWs).
- Tracks upcoming asteroid close approaches within a 1 to 7 day observation window.
- Gathers estimated minimum and maximum physical diameters in kilometers.
- Captures relative encounter velocities in kilometers per hour and exact miss distances.
- Filters asteroids by NASA potential hazard classification.
- Operates via public NASA endpoints with zero proxy overhead.
- Delivers clean structured records formatted for export to JSON, CSV, Excel, or astronomy dashboards.

### Input parameters

- Days Range Window: Number of observation days to query (1 to 7 days). Default is 3.
- Potentially Hazardous Only: Boolean flag to restrict results solely to hazardous bodies. Default is false.

### Output dataset fields

Each dataset record contains:

- neoId: Unique NASA Near Earth Object reference identifier.
- name: Astronomical catalog name (such as (2026 AB) or 99942 Apophis).
- closeApproachDate: Calendar date of closest orbital approach.
- isPotentiallyHazardous: Boolean indicator flagging potential planetary hazard.
- absoluteMagnitudeH: Intrinsic visual magnitude brightness.
- estimatedDiameterMinKm: Estimated lower bound diameter in kilometers.
- estimatedDiameterMaxKm: Estimated upper bound diameter in kilometers.
- relativeVelocityKmh: Encounter velocity relative to Earth in km/h.
- missDistanceKm: Minimum distance between Earth and asteroid center in kilometers.
- orbitingBody: Celestial body being passed (Earth).
- nasaJplUrl: Direct link to the JPL Small-Body Database orbital viewer.
- scrapedAt: UTC timestamp when the data was extracted.

### Use cases

- Astronomy education: Power interactive celestial trackers and classroom orbital models.
- Science journalism: Retrieve verified flyby distances and sizes when asteroids pass Earth.
- Planetary defense research: Compile orbital trajectory telemetry for scientific catalogs.

# Actor input Schema

## `daysRange` (type: `integer`):

Number of upcoming observation days to retrieve (1 to 7 days).

## `hazardousOnly` (type: `boolean`):

Filter solely for asteroids flagged as potentially hazardous.

## Actor input object example

```json
{
  "daysRange": 3,
  "hazardousOnly": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("adaptive_nightmare/nasa-neo-asteroids-radar").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("adaptive_nightmare/nasa-neo-asteroids-radar").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call adaptive_nightmare/nasa-neo-asteroids-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,adaptive_nightmare/nasa-neo-asteroids-radar"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/BChnuoVgzREbu5sr9/builds/Xq8fBS6pIhrxHCS0D/openapi.json