Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Space-Track Satellite Tracking API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspace-track.org%2Fspace-track" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fspace-track.org%2Fspace-track" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Space-Track Satellite Tracking API.
Authenticate and get session
Get current UTC time
Query General Perturbations data
Query and filter Space-Track Satellite Tracking API records by parameters
Monitor Space-Track Satellite Tracking API operational status and events
GET STARTED
Patterns agents use Space-Track Satellite Tracking API for, with concrete tasks.
★ Communications Operations
Use the Space-Track Satellite Tracking API to perform communications operations programmatically. The API provides 11 endpoints covering core functionality including authenticate and get session, get current utc time, query general perturbations data.
Call POST /ajaxauth/login to authenticate and get session
Automated Authentication Management
Automate authentication operations by combining multiple Space-Track Satellite Tracking API endpoints. Agents can get current utc time and then query general perturbations data in a single workflow.
Call GET /time/getTime to get current utc time, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Space-Track Satellite Tracking API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.
Search Jentic for 'authenticate and get session', load the operation schema, and execute with Jentic-managed credentials
11 endpoints — space-track.
METHOD
PATH
DESCRIPTION
/ajaxauth/login
Authenticate and get session
/time/getTime
Get current UTC time
/basicspacedata/query/class/gp
Query General Perturbations data
/basicspacedata/query/class/gp_history
Query GP history data
/basicspacedata/query/class/satcat
Query satellite catalog
/basicspacedata/query/class/satcat_debut
Query recently cataloged objects
/basicspacedata/query/class/decay
Query decay/reentry data
/basicspacedata/query/class/tip
Query reentry predictions
/ajaxauth/login
Authenticate and get session
/time/getTime
Get current UTC time
/basicspacedata/query/class/gp
Query General Perturbations data
/basicspacedata/query/class/gp_history
Query GP history data
/basicspacedata/query/class/satcat
Query satellite catalog
/basicspacedata/query/class/satcat_debut
Query recently cataloged objects
/basicspacedata/query/class/decay
Query decay/reentry data
/basicspacedata/query/class/tip
Query reentry predictions
What agents get from Jentic-routed access to this vendor.
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Space-Track Satellite Tracking API through Jentic.
What authentication does the Space-Track Satellite Tracking API use?
The Space-Track Satellite Tracking API uses an API key passed in the `chocolatechip` cookie. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I authenticate and get session with the Space-Track Satellite Tracking API?
Yes. Use the POST /ajaxauth/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Space-Track Satellite Tracking API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I authenticate and get session through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'authenticate and get session'. Jentic returns the matching Space-Track Satellite Tracking API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Space-Track Satellite Tracking API have?
The Space-Track Satellite Tracking API exposes 11 endpoints covering authentication, space data, utilities operations.
Can I limit what my agent is allowed to do with the Space-Track Satellite Tracking API?
Yes. Because Jentic One is self-hosted, you set the rules that decide which Space-Track operations your agent may call, and it can only use the ones you allow. The Space-Track surface is read-only data retrieval, so you can restrict the agent to just the classes it needs, such as querying the gp catalog, reading the satellite catalog, or looking up decay predictions, while leaving the rest off limits. Credentials are stored once by your own instance and injected only for the operations you permit, so the agent reads the space-object data you approve and nothing more.
For Agents
Programmatically authenticate and get session, get current utc time. Covers 11 operations with apiKey authentication.
Use for: I need to authenticate and get session, I want to current utc time, Search for query general perturbations data, Find all query gp history data
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
Space-Track.org API for accessing satellite tracking data including general perturbations, satellite catalog, decay predictions, conjunction data messages, and more. The API exposes 11 endpoints secured with apiKey authentication.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>