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.