CycleCalcs Astronomy
REMOTE · WWW.CYCLECALCS.COM · SCANNED AUG 18
Astronomy: sun, moon, planet, eclipse, twilight and star position calculations.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 5758 tokens (~523/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · www.cyclecalcs.com
claude mcp add --transport http com-cyclecalcs-astronomy https://www.cyclecalcs.com/mcp
[mcp_servers.com-cyclecalcs-astronomy] url = "https://www.cyclecalcs.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-cyclecalcs-astronomy": {
"type": "remote",
"url": "https://www.cyclecalcs.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-cyclecalcs-astronomy --url https://www.cyclecalcs.com/mcp --transport streamable-http
mcp_servers:
com-cyclecalcs-astronomy:
url: "https://www.cyclecalcs.com/mcp" {
"mcpServers": {
"com-cyclecalcs-astronomy": {
"type": "http",
"url": "https://www.cyclecalcs.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- Tool “astro_dark_window” now declares an output schema ▲ functional
- Tool “astro_eclipses” now declares an output schema ▲ functional
- Tool “astro_find_place” now declares an output schema ▲ functional
- Tool “astro_moon” now declares an output schema ▲ functional
- Tool “astro_moon_phases” now declares an output schema ▲ functional
- Tool “astro_planet_board” now declares an output schema ▲ functional
- Tool “astro_planet_events” now declares an output schema ▲ functional
- Tool “astro_positions” now declares an output schema ▲ functional
- Tool “astro_rise_set” now declares an output schema ▲ functional
- Tool “astro_sky_today” now declares an output schema ▲ functional
- Tool “astro_sun” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- 9 Aug 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Aug 2026 · Probed https://www.cyclecalcs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.cyclecalcs.com | CN=YE1,O=Let's Encrypt,C=US | 13 Aug 2026 | 11 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 67c70b8b582bd7d1ecffa6e39e9abc989cb |
| SANs: cyclecalcs.com, www.cyclecalcs.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of www.cyclecalcs.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cyclecalcs.com. | present | 27182 | 8 | Verified |
| www.cyclecalcs.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.cyclecalcs.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.cyclecalcs.com/mcp | HTTPS enforced | 301 | https://www.cyclecalcs.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
astro_dark_window Dark moonless observing window ~364
The genuinely dark, moonless observing window for a night: astronomical night intersected with the Moon being down, ranked across up to 62 nights with a trend. The right tool for "when should I stargaze / photograph the Milky Way / observe deep-sky objects". Location required. For plain twilight times use astro_sun.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Night to start from. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| moon_illumination_max | number | – | Treat the Moon as tolerable below this illuminated fraction (0..1) even when up. |
| nights | integer | – | How many nights to evaluate and rank. Default 1. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | The best genuinely dark observing windows across a range of nights. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_eclipses Solar and lunar eclipses ~619
Solar and lunar eclipses: the next or previous from a date, or all in a range, with type, magnitude, obscuration, Saros series and global geometry. With a location it adds local circumstances, contact times, and an explicit visible-from-here answer; set visible_only to true to keep only eclipses visible there. NOTE: count applies per type, so count=3 with type "both" can return six events.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many eclipses PER TYPE to return. |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Anchor date to search from. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with D… |
| direction | string | – | Search direction from the anchor date. Default "next". |
| end | string | – | Last day of an explicit window. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses wi… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| start | string | – | First day of an explicit window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range th… |
| type | string | – | Which kind of eclipse to report. Default "both". |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| visible_only | boolean | – | true keeps only eclipses visible from the supplied location (requires a location). |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Solar and lunar eclipses in a date range, optionally filtered to one location. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_find_place Place name to coordinates and timezone ~228
Resolve a place name to coordinates, region, country, IANA timezone and a stable place_id, or reverse-look-up the nearest places to a lat/lon. Results are GeoNames data (CC BY 4.0); the response carries the required credit in its attribution field, which must be preserved when results are shown. Note the other tools accept a place argument directly, so this is only needed to disambiguate a name, filter by country, or reverse-geocode.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter ISO country code filter, e.g. "US". |
| id | string | – | A place_id from an earlier result, to fetch that exact place. |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| limit | integer | – | Maximum matches to return. Default 5. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| query | string | – | Place name to search for, e.g. "Springfield". |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Coordinates for a place name, or the nearest named places to coordinates. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_moon Moon state and appearance ~534
The Moon at an instant or as a daily series: phase name and angle, illuminated fraction, distance, apparent size, libration, bright limb, and the next quarter phases. A location adds rise/set and altitude. For a calendar of new and full moons use astro_moon_phases; for the Moon's exact coordinates use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of daily rows from start (alternative to end). |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the… |
| end | string | – | Last day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with D… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| start | string | – | First day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | The Moon's state and appearance, or a sampled series in range mode. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_moon_phases Lunar phase calendar ~586
Every new moon, quarter and full moon in a window (or the next few from a date): each with its exact instant, distance, apparent size, supermoon classification under both competing definitions, traditional full-moon name, and any eclipse falling on it. Use for "when is the next full moon" and phase calendars. For the Moon's state right now use astro_moon.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many phase events to return from the anchor date. |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Anchor date; the next phases follow it. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API re… |
| end | string | – | Last day of a window. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OU… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| phases | array | – | Optional filter of phase kinds. Omit for all four. Example: ["full_moon"] for full moons only. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| start | string | – | First day of a window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refu… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | New, first quarter, full and last quarter moons in a date range. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_planet_board All planets at a glance ~365
All eight planets in one call for a date and optional location: constellation, magnitude, apparent size, elongation from the Sun, morning or evening sky, retrograde state with the next station, rise/set, and a worth-looking-tonight assessment. The right tool for "which planets are visible tonight". For exact coordinates of specific bodies use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | – | Optional subset of planets: mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| sort | string | – | Optional result ordering. Default is by distance from the Sun. |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Which planets are worth looking at right now, and where. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_planet_events Mercury and Venus apparition events ~683
The apparition cycle of the inferior planets as dated events: inferior and superior conjunctions, greatest eastern and western elongations, peak brightness (a Venus-only event: Mercury's brightness peaks behind the Sun where it cannot be seen), and the rare transits across the Sun. With no dates it also reports where each body is in its cycle right now: morning star or evening star, the conjunctions bounding the current apparition, and the live elongation, phase, magnitude and apparent size. The right tool for "when does Venus become the morning star", "when is Venus brightest", or "Mercury's next greatest elongation". For tonight's visibility of all eight planets use astro_planet_board. Conjunction instants use the classical heliocentric convention, named on each event.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | – | Which inferior planets to report. Default both. |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Anchor instant; with no start/end the response covers the next full synodic cycle from here. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Y… |
| end | string | – | Last day of an explicit window, exclusive. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API… |
| kinds | array | – | Optional filter of event kinds. Omit for all. peak_magnitude only ever fires for venus; the transit kinds are body-specific and genuinely rare. |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| start | string | – | First day of an explicit window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range th… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Apparition events per planet in a date range: conjunctions, elongations, stations. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_positions Precise positions of bodies ~661
Exact positions for up to 20 bodies at an instant or over a time grid: right ascension and declination in both J2000 and of-date frames, ecliptic longitude and latitude, distance, and, with a location, altitude and azimuth with refraction stated per field. Use for "where exactly is X". Do not pass earth. For rise and set TIMES use astro_rise_set; for a visibility overview of all planets use astro_planet_board.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | yes | Bodies to report. Each entry: One of sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, or a fixed J2000 target as "radec:RA,DEC" with RA in hours (0-24) and DEC in degrees (-9… |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the… |
| end | string | – | Grid end. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE b… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| start | string | – | Grid start (use with end and step). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuse… |
| step | string | – | Grid stride, e.g. "1h", "10min", "1d". |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Where each requested body is, at an instant or sampled across a range. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_rise_set Rise, transit and set times ~633
Rise, upper transit, set and lower transit for one body at one location, with an explicit status at extreme latitudes (circumpolar, never rises) instead of missing values. Accepts fixed radec targets. For the Sun specifically, astro_sun returns richer twilight structure; for positions between events use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | One of sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, or a fixed J2000 target as "radec:RA,DEC" with RA in hours (0-24) and DEC in degrees (-90..90), e.g. "radec:5.6,-5.4"… |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the… |
| end | string | – | Last day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with D… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| search_horizon_days | integer | – | How many days ahead to search when an event does not occur on the requested day (high latitudes). |
| start | string | – | First day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Rise, transit and set for one body, for a day or across a range. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_sky_today Sky snapshot for a place and moment ~332
One-call snapshot of the whole sky for a place and moment: moon phase and illumination, which planets are up and worth looking at, the next eclipse, and (with a location) sun times. Reach for this first when the question is broad, like "what is in the sky tonight". For solar-day detail use astro_sun; for choosing an observing night use astro_dark_window; for one planet's exact position use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT_OF_RANGE because the… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | A whole-sky snapshot for one place and moment. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_sun Sunrise, sunset and twilight ~580
The complete solar day for one location: sunrise, sunset, solar noon, day length, civil, nautical and astronomical twilight boundaries, and explicit polar day/night status at high latitudes. Location required. For a series, send start and end (step is whole days, e.g. "1d" or "7d"). For "is it dark enough to observe" prefer astro_dark_window; for a broad snapshot prefer astro_sky_today.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Single day to report, ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OU… |
| end | string | – | Last day of a range. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that range the API refuses with DATE_OUT… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | Place name instead of lat/lon, as "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Resolved server-side; the response then carries a required GeoNames CC BY 4.0 credit in its attributi… |
| start | string | – | First day of a range (use with end instead of date). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". Omit for the current moment. Years 1700 to 2200 only; outside that ran… |
| step | string | – | Range stride in whole days, e.g. "1d", "7d", "30d". Default "1d". |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | The complete solar day for one location, or one row per day in range mode. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.