space.satellites

Search the catalog of every cataloged Earth-orbiting object — ~69,000 satellites, rocket bodies, and debris tracked by US Space Force / 18 SDS (via CelesTrak SATCAT). Filter by name (q, e.g. "starlink"), owner/launching country (owner — code like US/PRC/CIS or a name like "china"), object type (type = payload | rocket body | debris | unknown), launch-year range (launchYearFrom/launchYearTo), international/COSPAR designator prefix (intlDesignator, e.g. "2024-"), on-orbit vs decayed (onOrbit), or exact NORAD number (noradId). Each result carries the NORAD id, name, international designator, object type, owner + resolved country, launch date + site, decay date (null = still in orbit), and orbital parameters (period, inclination, apogee, perigee). The envelope total is the full count matching your filter — so onOrbit=true&type=payload answers "how many active satellites are up there", and owner=PRC tells you who launched them. For a satellite's live sub-point position, pass its noradId to /api/space/satellite.

price
$0.0012 USDC per call
method
GET/api/space/satellites
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The satellites API is a pay-per-call space endpoint built for AI agents and autonomous software. Search the catalog of every cataloged Earth-orbiting object — ~69,000 satellites, rocket bodies, and debris tracked by US Space Force / 18 SDS (via CelesTrak SATCAT).

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 satellites 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.

Use cases

Parameters

NameTypeDescription
qstring
min 1 chars · max 120 chars
ownerstring
min 1 chars · max 40 chars
typestring
min 1 chars · max 20 chars
noradIdinteger
min 1 · max 999999
intlDesignatorstring
min 1 chars · max 20 chars
launchYearFrominteger
min 1957 · max 2100
launchYearTointeger
min 1957 · max 2100
onOrbitstring
one of: true | false
limitinteger
min 1 · max 100
offsetinteger
min 0 · max 100000

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/space/satellites?q=example&owner=example&type=example&noradId=1&intlDesignator=example&launchYearFrom=1957&launchYearTo=1957&onOrbit=true&limit=25&offset=0'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/space/satellites?q=example&owner=example&type=example&noradId=1&intlDesignator=example&launchYearFrom=1957&launchYearTo=1957&onOrbit=true&limit=25&offset=0' \
  -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/satellites?q=example&owner=example&type=example&noradId=1&intlDesignator=example&launchYearFrom=1957&launchYearTo=1957&onOrbit=true&limit=25&offset=0'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.space.satellites({
  "q": "example",
  "owner": "example",
  "type": "example",
  "noradId": 1,
  "intlDesignator": "example",
  "launchYearFrom": 1957,
  "launchYearTo": 1957,
  "onOrbit": "true",
  "limit": 25,
  "offset": 0
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.space.satellites(q="example", owner="example", type="example", noradId=1, intlDesignator="example", launchYearFrom=1957, launchYearTo=1957, onOrbit="true", limit=25, offset=0)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 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.satellites",
    "arguments": {
      "q": "example",
      "owner": "example",
      "type": "example",
      "noradId": 1,
      "intlDesignator": "example",
      "launchYearFrom": 1957,
      "launchYearTo": 1957,
      "onOrbit": "true",
      "limit": 25,
      "offset": 0
    }
  }
}

Response

FieldTypeDescription
okboolean
one of: true
itemsarray
totalintegerTotal matching rows upstream; null when unknown.
sourceobject
Example response datajson
{
  "ok": true,
  "items": [
    {
      "noradId": 1,
      "name": "example",
      "intlDesignator": "example",
      "objectType": "example",
      "opsStatus": "example",
      "owner": "example",
      "ownerName": "example",
      "launchDate": "example",
      "launchSite": "example",
      "decayDate": "example",
      "onOrbit": false,
      "orbit": {
        "periodMin": 1,
        "inclinationDeg": 1,
        "apogeeKm": 1,
        "perigeeKm": 1,
        "orbitType": "example"
      },
      "rcsM2": 1
    }
  ],
  "total": 1,
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  }
}

FAQ

Do I need an API key to use the satellites API?
No. space.satellites is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the satellites API cost?
$0.0012 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the satellites API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call space.satellites from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: satellites api · space satellites api · satellites api for ai agents · x402 space api · satellites api no api key · pay per call satellites api · space api