Arcsecond Astronomy API
54
AI ReadinessFoundational (C)54/100
Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey12 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look up exoplanets, observing sites, telescopes, satellites, and astronomical objects from a unified astronomy data API.
Use for: Look up the exoplanet Kepler-22b on Arcsecond, List all known exoplanets in the Arcsecond catalogue, Find an observing site by name or UUID, Get the details of a specific telescope
Not supported: Does not handle live telescope control, image processing, or weather forecasting - use for astronomy catalogue lookups only.
Jentic publishes the only available OpenAPI specification for Arcsecond Astronomy API, keeping it validated and agent-ready. Arcsecond is a unified REST API for world-wide astronomy data spanning exoplanets, observing sites, telescopes, instruments, observations, satellites, and astronomical objects. The API is used by amateur and professional astronomy tooling, planetarium software, and research dashboards. Authentication is via a token-based scheme, with separate registration and login endpoints for issuing tokens.
Install Jentic One Beta
Connect the Arcsecond Astronomy API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Arcsecond Astronomy 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.
1
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%2Farcsecond.io%2Farcsecond" | sh2
Step 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%2Farcsecond.io%2Farcsecond" | 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.
Capabilities
What an agent can do with Arcsecond Astronomy API.
Look up exoplanets by name and list known planetary systems
Resolve an astronomical object by name and return its catalogued properties
List worldwide observing sites and fetch site detail by UUID
List telescopes and pair them with their host observing site
Register a user and exchange credentials for a token used on subsequent calls
Use Cases
Patterns agents use Arcsecond Astronomy API for, with concrete tasks.
★ Exoplanet Lookup for Educational Tools
Surface known exoplanets and their host-star data inside an educational app or planetarium-style tool. Schools and amateur astronomy products use Arcsecond as a single source for exoplanet catalogues without scraping multiple research databases. GET /exoplanets/ lists the catalogue and GET /exoplanets/{name}/ returns the detail record for a specific planet.
Call GET /exoplanets/{name}/ with the user's planet name and return the host star, orbital period, and discovery year.
Observing-Site Directory for Trip Planning
Plan an astronomy trip by looking up observing sites, their coordinates, and their associated telescopes. Astronomy tour operators and dark-sky tools use Arcsecond to render maps and pick a site that matches the user's altitude or hemisphere preferences. The observing-sites and telescopes endpoints expose this directory.
Call GET /observingsites/ and filter by the user's hemisphere, then return the matching sites and their telescopes.
Astronomical Object Resolution
Resolve a free-text astronomical object name into a catalogued record with coordinates and metadata. Stargazing apps use this to translate a user's typed query into a record they can render in a sky chart. GET /objects/{name}/ accepts the canonical or common name and returns the resolved object.
Call GET /objects/{name}/ with the user's typed name and return the resolved object's coordinates and catalogue identifier.
AI Agent Astronomy Assistant via Jentic
An assistant agent answering 'what is Kepler-22b' or 'where is the largest telescope in Chile' can call Arcsecond through Jentic to ground its answers in real catalogue data. The agent searches for the lookup operation, loads the schema, and executes the call without managing the token. Jentic resolves the token from its credential vault.
Use Jentic search 'look up an exoplanet', load the schema for GET /exoplanets/{name}/, then execute with the user's planet name and return the catalogued properties.
Key Endpoints
12 endpoints — jentic publishes the only available openapi specification for arcsecond astronomy api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/auth/login/
Log in and receive an auth token
POST
/auth/register/
Register a new user
GET
/exoplanets/
List all exoplanets
GET
/exoplanets/{name}/
Get a specific exoplanet
GET
/objects/{name}/
Resolve an astronomical object by name
GET
/observingsites/
List observing sites worldwide
GET
/observingsites/{uuid}/
Get a specific observing site
GET
/telescopes/
List telescopes
POST
/auth/login/
Log in and receive an auth token
POST
/auth/register/
Register a new user
GET
/exoplanets/
List all exoplanets
GET
/exoplanets/{name}/
Get a specific exoplanet
GET
/objects/{name}/
Resolve an astronomical object by name
GET
/observingsites/
List observing sites worldwide
GET
/observingsites/{uuid}/
Get a specific observing site
GET
/telescopes/
List telescopes
Jentic AI Readiness Score
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.
A
Arcsecond Astronomy API
- Foundational (C)54/100
56
Foundational Compliance59
Developer Experience & Jentic Compatibility45
AI-Readiness & Agent Experience62
Agent Usability50
Security59
AI DiscoverabilityPowered by JenticScoring Framework 0.2.0 | Scoring Engine 0.3.10
Show dimension breakdown
56
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: CSignals: 4
89%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
35%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
59
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
38%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
45
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
30%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
62
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: B-Signals: 1
62%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
59
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: C+Signals: 1
59%
Descriptive Richness
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>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Arcsecond by hand means exchanging credentials at its login endpoint for an auth token and then paging its exoplanet, object, and observing-site catalogues yourself. Through Jentic you install once, import the Arcsecond Astronomy API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Arcsecond puts the object name or site uuid in the URL path (/exoplanets/{name}/, /observingsites/{uuid}/), so a rule can pin your agent to reading specific catalogue entries. You choose the operations it may call, so account operations like register are not included unless you add them.
Credential isolation
Your Arcsecond auth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up an exoplanet', and Jentic returns the matching Arcsecond operation with its input schema so the agent calls the right endpoint without browsing docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Arcsecond Astronomy API through Jentic.
Why is there no official OpenAPI spec for Arcsecond Astronomy API?
Arcsecond does not publish an OpenAPI specification on api.arcsecond.io. Jentic generates and maintains this spec so that AI agents and developers can call Arcsecond Astronomy API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Arcsecond API use?
Arcsecond uses token-based authentication. Register via POST /auth/register/ or log in via POST /auth/login/ to receive a token, then send it on subsequent requests. Through Jentic, the token is stored encrypted in the vault and never enters the agent's context.
Can I list every exoplanet catalogued in Arcsecond?
Yes. Call GET /exoplanets/ to list the catalogue, and GET /exoplanets/{name}/ to fetch the detail record for a specific exoplanet including its host star and orbital characteristics.
How do I find a telescope or observing site?
Use GET /telescopes/ to list telescopes and GET /observingsites/ or GET /observingsites/{uuid}/ to look up a specific site. Telescopes carry a reference to their host site so you can resolve the pair in two calls.
What are the rate limits for the Arcsecond API?
The OpenAPI spec does not declare explicit rate limits. Arcsecond applies per-token fair-use limits - sustained traffic above a few requests per second can be throttled. Contact Arcsecond for higher quotas in production workloads.
How do I look up an exoplanet through Jentic?
Install Jentic with pip install jentic, search for 'look up an exoplanet', load the schema for GET /exoplanets/{name}/, then execute with the planet name. Jentic injects the auth token automatically.
Can I limit what my agent is allowed to do with the Arcsecond Astronomy API?
Yes. Jentic One is self-hosted, so your own rules decide which Arcsecond operations and credentials your agent may use. You can restrict it to read-only catalogue lookups such as GET /exoplanets/{name}/ and GET /observingsites/{uuid}/, pinning it to specific entries because the object name or site UUID sits in the URL path. Account operations like POST /auth/register/ stay out of reach unless you explicitly grant them.
GET STARTED