Impact Risk Table
by Space Objects in Security & trust
JPL Sentry impact-monitoring objects above a Palermo-scale threshold: probability, Torino level, size and impact years.
https://space-objects.x402tookit.com/impact-risk-table- Price
- $0.02
- per call in USDC
- Uptime
- 63.2%
- last 30 days
- Response time
- 544 ms
- 1.1 s slowest 5%
- Last check
- Passed
- 7 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://space-objects.x402tookit.com/impact-risk-table
Each call costs $0.02 in USDC on Polygon, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
GET https://space-objects.x402tookit.com/impact-risk-table?limit=10&maxH=24&minPalermo=-3Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | No | Objects returned, 1 to 50 (default 20) |
maxH | number | No | Only objects with absolute magnitude H at or below this (larger objects), 10 to 35 |
minPalermo | number | No | Minimum cumulative Palermo scale, -12 to 2 (default -3; lower values list many more objects) |
Example response
The provider's example. We can't check it without paying.
Example response, 55 lines
{
"asOf": "2026-10-11T08:41:44.122Z",
"degraded": false,
"disclaimer": "Screening signal computed from the named public source. Not financial, legal or investment advice; provided as is. Verify at the source before acting.",
"maxH": 24,
"minPalermo": -3,
"notChecked": [
"objects JPL's Sentry does not list, including those tracked by ESA's NEOCC risk list",
"removed objects: Sentry drops objects once new data rules out impact",
"…2 more"
],
"objects": [
{
"absoluteMagnitudeH": 17.94,
"designation": "29075",
"diameterKm": 1.3,
"impactProbability": 0.0003633,
"impactSpeedKmS": 14.1,
"impactYears": "2880-2880",
"lastObservation": "2026-10-05",
"name": "29075 (1950 DA)",
"oneIn": 2753,
"palermoCumulative": -0.95,
"palermoMax": -0.95,
"potentialImpacts": 1,
"torinoMax": null
},
{
"absoluteMagnitudeH": 20.63,
"designation": "101955",
"diameterKm": 0.49,
"impactProbability": 0.000571699999999996,
"impactSpeedKmS": 5.99,
"impactYears": "2178-2290",
"lastObservation": "2020-10-3.80160",
"name": "101955 Bennu (1999 RQ36)",
"oneIn": 1749,
"palermoCumulative": -1.4,
"palermoMax": -1.58,
"potentialImpacts": 157,
"torinoMax": null
}
],
"reasons": [
"Every listed object has Torino level 0 (no unusual hazard).",
"A Palermo value below -2 means the risk is far below the background risk from all other objects of that size.",
"…1 more"
],
"returned": 4,
"source": "NASA JPL Solar System Dynamics",
"sourceUrl": "https://ssd-api.jpl.nasa.gov",
"summary": "4 Sentry object(s) with Palermo -3 or higher and H 24 or lower; 4 listed. Highest cumulative Palermo: 29075 (1950 DA) at -0.95 (Merits careful monitoring), impact probability 1 in 2,753.",
"totalMatches": 4,
"verdict": "OBJECTS_LISTED"
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://space-objects.x402tookit.com/impact-risk-table?limit=10&maxH=24&minPalermo=-3'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://space-objects.x402tookit.com/impact-risk-table?limit=10&maxH=24&minPalermo=-3' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fspace-objects.x402tookit.com%2Fimpact-risk-table
const res = await pay("https://space-objects.x402tookit.com/impact-risk-table?limit=10&maxH=24&minPalermo=-3");
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://space-objects.x402tookit.com/impact-risk-table?limit=10&maxH=24&minPalermo=-3")
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 7 h ago | Passed | 402 | 563 ms | $0.02 |
| 20 h ago | Expected HTTP 402, got 530 | 530 | 108 ms | - |
| 32 h ago | Passed | 402 | 576 ms | $0.02 |
| 44 h ago | Expected HTTP 402, got 530 | 530 | 111 ms | - |
| 2 days ago | Passed | 402 | 518 ms | $0.02 |
Show 10 older checks
| 3 days ago | Passed | 402 | 544 ms | $0.02 |
| 4 days ago | Expected HTTP 402, got 530 | 530 | 94 ms | - |
| 4 days ago | Expected HTTP 402, got 530 | 530 | 94 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 131 ms | - |
| 5 days ago | Passed | 402 | 548 ms | $0.02 |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 164 ms | - |
| 5 days ago | Expected HTTP 402, got 530 | 530 | 175 ms | - |
| 5 days ago | Passed | 402 | 548 ms | $0.02 |
| 5 days ago | Passed | 402 | 516 ms | $0.02 |
| 6 days ago | Passed | 402 | 544 ms | $0.02 |