Space-Track Satellite Tracking API

Setup

Wiring Space-Track by hand means running its cookie-session login flow to get a chocolatechip session, then querying the basicspacedata classes like gp, satcat, and decay against a single host while you manage session refresh yourself. Through Jentic you install once, import the Space-Track Satellite Tracking API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

The Space-Track query surface is read-only data retrieval, so limit the agent to the operations it needs, such as querying the gp catalog or reading decay predictions. You choose the operations it may call, so it only reads the space-object data classes you allow and nothing more.

Credential isolation

Your Space-Track credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get current TLE data for a satellite' or 'look up a decay prediction', and Jentic returns the matching Space-Track operation with its input schema so the agent calls the right endpoint without browsing the reference docs.