Developer Data
Use OrbitSmith public AI data from static JSON and the public MCP bridge. No OrbitSmith API key is required.
Public No-Key Data
OrbitSmith publishes static JSON snapshots for AI assistants and lightweight public reuse. No OrbitSmith API key is required for these files.
Public MCP toolsThe public bridge can read summaries, reentry data, statistics, catalog metadata, SATCAT basic metadata, and GP/TLE element snapshots.
AttributionPublic outputs carry citation requirements and upstream attribution for OrbitSmith, Space-Track.org / 18 SDS / USSPACECOM, CelesTrak where indicated, and GCAT where indicated.
How To Use
There are two paths. The public JSON path works anywhere an AI assistant can read web URLs. The MCP bridge path is currently for local validation.
1. Public JSONGive Claude, Codex, or another AI assistant the manifest URL and ask it to read only the listed public JSON files.
2. Claude Code MCPFor local validation, register the repo-local bridge script as an MCP server, then start a fresh Claude session.
3. Codex MCPFor local validation, add this MCP server entry to your Codex config and start a fresh Codex session.
Current statusThe static JSON files are public. The MCP bridge is still a small local helper script, not a packaged public installer yet.
Recommended Prompt Note
When asking an AI assistant to use OrbitSmith MCP, add this note to reduce over-interpretation.
Public Scope
Can doSummarize aggregate conjunction activity, check a user-provided NORAD ID list, review reentry-watch summaries, and return OrbitSmith statistics.
Cannot doIt does not issue official warnings, guarantee safety, provide operational maneuver decisions, or assess ground impact.
Public dataCatalog lookup, SATCAT lookup, and GP/TLE lookup are available as public static data with attribution and non-operational limitations.
Held backRaw CDM documents, covariance, state vectors, restricted folders, credentials, and operational decision products are not included.
Questions / Feedback
At this stage, OrbitSmith is not issuing public user keys. The intended public path is static JSON plus the public MCP bridge, both reading the same no-key public data.