How to Use JPL asteroid close approaches in Muse Code
Returns predicted encounter dates, distances, relative speeds, and uncertainties from JPL's Small-Body Database. Use it to build an approach calendar or examine Apophis in 2029; impact probabilities come from Sentry.
Prompts to try with JPL asteroid close approaches in Muse Code
Copy an example into Muse Code, or ask in your own words.
Use JPL asteroid close approaches to fetch Apophis encounters during 2029 and add a table of dates, distances, and uncertainties to this project's astronomy page.
Use JPL asteroid close approaches to look this up and give me the result as a table. Save the result in ./assets.
Pull the latest numbers from JPL asteroid close approaches and tell me what changed since last week.
Check JPL asteroid close approaches and summarize what you find in three bullet points.
Pull the newest data from JPL asteroid close approaches and give me the result as a table.
How to set up JPL asteroid close approaches in Muse Code
Pick the way that suits you. Each takes about two minutes.
Use Spiral's MCP server
- Install Muse Code
curl -fsSL https://dev.meta.ai/install.sh | bash
- Ask Muse to add the server
Start muse and ask:
Add the Spiral MCP server at https://api.spiral.ai/mcp
- Sign in
In your terminal, run:
muse mcp login spiral
Use the Spiral skill
- Send Muse Code this message
Your agent reads Spiral's skill and sets itself up.
set up https://spiral.ai/SKILL.md
- Sign in or paste a key
Approve Spiral in the browser, or give the agent a key from the console.
Use the Spiral CLI
- Install and sign in
Installs the Spiral CLI, signs you in and adds its skill to your coding agents.
npx -y spiral-cli@latest init
Call the Spiral API
- Create an API key
In the console, under API keys.
- Run JPL asteroid close approaches
One request; the result comes back by polling or a webhook.
curl https://api.spiral.ai/v1/runs \ -H "Authorization: Bearer $SPIRAL_API_KEY" \ -H "Content-Type: application/json" \ -H "Idempotency-Key: $(uuidgen)" \ -d '{ "provider": "alexandria", "model": "ssd-api-jpl-nasa-gov/small-bodies/close_approaches", "input": { "body": "earth" } }'
Then paste one of the prompts above: Muse Code finds JPL asteroid close approaches on Spiral, shows the price and runs it.
JPL asteroid close approaches providers and prices
Spiral runs JPL asteroid close approaches through Alexandria. Open a card for today's price, with every fee included.
Settings you can ask for
Ask Muse Code for any of these in your prompt.
| Setting | Allowed values | Default | Description |
|---|---|---|---|
| Body | earth, moon, mercury, venus, mars, jupiter, saturn, uranus and 3 more | Body approached (default earth). | |
| Sort | date, -date, dist, -dist, v_rel, -v_rel, h, or -h | date | Sort key; prefix - for descending. |
| H max | a number | Only objects with H at most this (larger objects; H 22 is roughly 140 m). | |
| H min | a number | Only objects with H at least this (smaller objects). | |
| Limit | 1 to 200 | 50 | Approaches per page. |
| Pha only | on or off | Only potentially hazardous asteroids. | |
| Max distance au | a number | Maximum nominal distance in au (default 0.05, or 0.2 with a designation). | |
| Max distance ld | a number | Maximum nominal distance in lunar distances, instead of max_distance_au. | |
| Min distance au | a number | Minimum nominal distance in au. |
Every API field of JPL Small-Body and CNEOS Data · Close approaches is on its tool page: open its card above.
What can you do with JPL asteroid close approaches in Muse Code?
Build an astronomy feature using JPL encounter records, asteroid and comet properties, or atmospheric event data. Keep encounter predictions, Sentry scenarios, and observed fireballs distinct in the project's data model.
Prepare a planetarium news brief
Combine upcoming encounters, reported fireballs, Sentry summaries, individual risk scenarios, and asteroid or comet background tables into a weekly astronomy briefing.
Check an astronomy article
Check flyby predictions, atmospheric event records, impact probabilities, and object properties against the corresponding JPL records before publication.
Build a classroom evidence workbook
Give students separate exercises on predicted encounters, observed atmospheric events, possible impact scenarios, and differences among asteroid or comet populations.
Create an asteroid encounter calendar
List predicted encounter dates and distances, then add orbital and physical context for selected objects.
Study orbital uncertainty
Compare orbital records across selected asteroids and inspect the uncertainty information attached to their predicted encounters.
More on JPL asteroid close approaches and Muse Code
Overview
JPL asteroid close approaches in other agents
Questions about JPL asteroid close approaches in Muse Code
Can Muse Code use JPL asteroid close approaches?
Yes. Add Spiral to Muse Code as an MCP server, and Muse Code can find and run JPL asteroid close approaches like any built-in tool.
How much does JPL asteroid close approaches cost in Muse Code?
$0.00873 per call. You pay from your Spiral balance as you go, with no subscription, and a failed run is not charged. Your Muse Code plan is separate.
Do I need an Alexandria account to use JPL asteroid close approaches in Muse Code?
No. Spiral runs JPL asteroid close approaches on its own Alexandria account. You sign in to Spiral once and never paste a key.
How long does it take to set up JPL asteroid close approaches in Muse Code?
About two minutes: install Muse Code, then ask Muse to add the server, then sign in.
Does Muse Code wait while JPL asteroid close approaches runs?
JPL asteroid close approaches runs in the background. Muse Code starts the run, checks on it and gives you the json when it's ready.
Which objects does JPL's Small-Body Database cover?
It covers all known asteroids and comets within the solar system. Identification and orbital data are included, while physical properties are selected data rather than a complete set of measurements for every object.
How quickly do JPL orbital records change?
JPL typically computes new small-body orbits within an hour or two after new discoveries or astrometric observations become available. That timing applies to orbital processing, not to publication of fireball detections.
How far back and forward do the Earth close-approach tables extend?
The published tables exclude dates before 1900 and after 2200. They also exclude encounters whose uncertainty is too large, so that date range does not guarantee a complete encounter history for every asteroid.
What does Sentry's cumulative impact probability mean?
It adds the probabilities of all detected potential impacts for an asteroid. An individual scenario's probability and the object's cumulative probability describe different quantities.
Can a search change while I retrieve multiple pages?
Yes. JPL explicitly warns that the SBDB database can change between calls used to page through search results.
Start using JPL asteroid close approaches in Muse Code
One Spiral account for every tool your agent needs. No subscription; you pay per run.
Paste this into Muse Code:
set up https://spiral.ai/SKILL.md


