# Astro Agents - verifiable planetary timing data and astrology (remote · astro-agent.dev) Verifiable market-timing data for trading bots: Gann lines, events, analogues. Pay per call in MCP. - Trust score: 87/100 (high trust) - Change this week: +2 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-07 ## Components - remote · `astro-agent.dev`: 87/100 (this document), [markdown](https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent.md), [page](https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent) ## Channel facts - Endpoint: `https://astro-agent.dev/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `1.8.4` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-07. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 71/100 - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 11691 tokens (~449/item across 26 items; 24 tools + 2 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 100/100 - No destabilizing schema changes in the last 30 days. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 26 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the Astro Agents - verifiable planetary timing data and… MCP server? Astro Agents - verifiable planetary timing data and… is a hosted endpoint at https://astro-agent.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add --transport http aidatatools-dev-astro-agents 'https://astro-agent.dev/mcp' ``` ### Cursor ```json { "mcpServers": { "aidatatools-dev-astro-agents": { "url": "https://astro-agent.dev/mcp" } } } ``` ### VS Code ```json { "servers": { "aidatatools-dev-astro-agents": { "type": "http", "url": "https://astro-agent.dev/mcp" } } } ``` ### Codex ```toml [mcp_servers.aidatatools-dev-astro-agents] url = "https://astro-agent.dev/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "aidatatools-dev-astro-agents": { "type": "remote", "url": "https://astro-agent.dev/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add aidatatools-dev-astro-agents --url 'https://astro-agent.dev/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: aidatatools-dev-astro-agents: url: "https://astro-agent.dev/mcp" ``` ### Netclaw ```json { "McpServers": { "aidatatools-dev-astro-agents": { "Transport": "http", "Url": "https://astro-agent.dev/mcp" } } } ``` ### Vellum ```bash assistant mcp add aidatatools-dev-astro-agents -t streamable-http -u 'https://astro-agent.dev/mcp' ``` ### Other ```json { "mcpServers": { "aidatatools-dev-astro-agents": { "type": "http", "url": "https://astro-agent.dev/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-07 (score 87, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [functional] Server version: 1.8.5 → 1.8.6 ### 2026-11-06 (score 87, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-11-03 (score 87, +1) - [security] Stability: 0.97 → pass - [security] The server rewrote its instructions, which are the text every model session reads - [functional] Server version: 1.8.3 → 1.8.4 ### 2026-11-01 (score 86, +1) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “token_synastry” rewrote its description, which is the text the model reads - [functional] Server version: 1.8.2 → 1.8.3 - [functional] Server version: 1.8.0 → 1.8.2 ### 2026-10-30 (score 85, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “astro_catalog” rewrote its description, which is the text the model reads - [security] Tool “astro_event_calendar” rewrote its description, which is the text the model reads - [security] Tool “planet_positions” rewrote its description, which is the text the model reads - [security] Tool “planetary_lines” rewrote its description, which is the text the model reads - [security] Tool “sky_analogues” rewrote its description, which is the text the model reads - [functional regression] Schema quality: 392 → 443 - [functional regression] Schema quality: 9021 → 9955 - [functional] Server version: 1.6.0 → 1.8.0 - [functional] Server version: 1.5.0 → 1.6.0 - [functional] New tool “token_chart” - [functional] New tool “token_synastry” - [functional] New tool “sky_analogues” - [cosmetic] “sky_analogues” reworded the description of “direction” - [cosmetic] “sky_analogues” reworded the description of “range” - [cosmetic] “sky_analogues” reworded the description of “reference” - [cosmetic] Tool “astro_event_calendar” changed its title: Astro event calendar → Eclipse & Mercury retrograde calendar (market timing) - [cosmetic] Tool “natal_chart” changed its title: Western natal chart → Natal chart (birth chart) - [cosmetic] Tool “planet_positions” changed its title: Planetary positions → Planetary positions for any date (ephemeris) - [cosmetic] Tool “sky_today” changed its title: Sky today → Sky today: retrogrades, Moon phase, next events ### 2026-10-29 (score 85, +1) - [security] The server rewrote its instructions, which are the text every model session reads - [security] Tool “aspects” rewrote its description, which is the text the model reads - [security] Tool “doshas” rewrote its description, which is the text the model reads - [security] Tool “gun_milan” rewrote its description, which is the text the model reads - [security] Tool “kp_chart” rewrote its description, which is the text the model reads - [security] Tool “kundli” rewrote its description, which is the text the model reads - [security] Tool “kundli_full” rewrote its description, which is the text the model reads - [security] Tool “nakshatras” rewrote its description, which is the text the model reads - [security] Tool “natal_chart” rewrote its description, which is the text the model reads - [security] Tool “panchang” rewrote its description, which is the text the model reads - [security] Tool “planet_positions” rewrote its description, which is the text the model reads - [security] Tool “resolve_birth_time” rewrote its description, which is the text the model reads - [security] Tool “synastry” rewrote its description, which is the text the model reads - [security] Tool “transits” rewrote its description, which is the text the model reads - [security] Tool “vedic_report” rewrote its description, which is the text the model reads - [security] Tool “vimshottari_dasha” rewrote its description, which is the text the model reads - [security] Tool “yogas” rewrote its description, which is the text the model reads - [functional regression] Schema quality: 348 → 392 - [functional regression] Schema quality: 348 → 389 - [functional] Schema quality: excellent → good - [functional] Server version: 1.3.0 → 1.5.0 - [functional] New tool “astro_event_calendar” - [functional] New tool “planetary_lines” - [functional] New tool “sky_today” - [cosmetic] “aspects” reworded the description of “longitudes” ### 2026-10-27 (score 84, 0) - [security] The server rewrote its instructions, which are the text every model session reads - [functional regression] Schema quality: 5874 → 6960 - [functional] Server version: 1.0.3 → 1.3.0 - [functional] New tool “kp_chart” - [functional] New tool “yogas” ### 2026-10-26 (score 84, +1) No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes. ## MCP tools (24) ### `resolve_birth_time` (~448 tokens) Birth time resolver Astrology birth time to UTC conversion: convert a local birth date, time and place into exact Universal Time, with the historical time zone and UTC offset, Delta T, Local Mean Time and true solar time. The step LLMs most often get wrong. Resolves the IANA time zone from coordinates, applies the offset in force on that date (historical DST, Local Mean Time before standard time), flags ambiguous or non-existent local times instead of guessing, and returns Julian Days (UT/TT), Delta T, Local Mean Time, true (apparent) solar time and the equation of time. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/time/resolve (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number): Decimal degrees, north positive. - `longitude` (number): Decimal degrees, east positive. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `planet_positions` (~491 tokens) Planetary positions for any date (ephemeris) Western astrology planet positions and ephemeris API: the zodiac sign, longitude, latitude, speed and retrograde flag of the Sun, Moon, planets, lunar nodes and Lilith at any moment, geocentric or heliocentric, ecliptic or equatorial (declination, out-of-bounds). Geocentric apparent positions from NASA/JPL DE440 for any moment 1800-2200, with sign, degree, element, modality, daily speed and retrograde status. Location is optional (only used to interpret a local time). Options: perspective 'heliocentric' (seen from the Sun) and coordinates 'equatorial' (right ascension, declination, out-of-bounds). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/western/positions (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number): Decimal degrees, north positive. - `longitude` (number): Decimal degrees, east positive. - `options` (object): Optional calculation settings; every default is the common Western convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `sky_today` (~499 tokens) Sky today: retrogrades, Moon phase, next events Astrology sky today (no birth data): planet positions, retrogrades and the Moon phase now, plus the exact times of the next ingresses, Mercury retrograde and other stations, new and full moons and planetary aspects over the coming days. For agents and bots that follow the sky itself (market timing, daily content, alerts): positions with retrograde flags and the Moon's phase and illumination at a moment (default: now, UTC), then every sign ingress, retrograde/direct station, lunation (new, quarter, full) and major aspect between the planets over the next 1-90 days, each to the minute. Tropical or sidereal. Pass 'datetime' for a reproducible call. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.01 per call via REST POST https://astro-agent.dev/v1/western/sky (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `days` (integer): How many days ahead to list events. Example: 30. - `latitude` (number): Decimal degrees, north positive. - `longitude` (number): Decimal degrees, east positive. - `options` (object): Optional zodiac settings. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `aspects` (~477 tokens) Aspects Western astrology aspects: find the aspects between planets at a moment, or between longitudes you supply, with orb, exactness and applying or separating. Either give a moment (datetime, optional place) and get the aspects among all planets, or give 'longitudes' {name: degrees} and get the pure geometry. Orbs are explicit and overridable. With options.declination: declinations and the parallels / contra-parallels too. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.02 per call via REST POST https://astro-agent.dev/v1/western/aspects (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number): Decimal degrees, north positive. - `longitude` (number): Decimal degrees, east positive. - `longitudes` (object): Optional {name: degrees} or {name: {longitude, speed, declination?, declination_speed?}}; when given, no ephemeris is used. - `options` (object): Optional calculation settings; every default is the common Western convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `natal_chart` (~455 tokens) Natal chart (birth chart) Western astrology natal chart (birth chart, horoscope): planets in zodiac signs and houses, sun sign, moon sign and rising sign (ascendant), MC, aspects and a summary. Everything a natal reading needs, computed exactly: positions, house cusps (Placidus by default; Koch, Whole Sign, Equal, Porphyry, Regiomontanus, Campanus, Topocentric, Alcabitius, Morinus, Meridian), ascendant/MC/DSC/IC, aspects with orbs and applying/separating state, element and modality balance, chart ruler, sect and Part of Fortune. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.06 per call via REST POST https://astro-agent.dev/v1/western/natal (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `options` (object): Optional calculation settings; every default is the common Western convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `transits` (~230 tokens) Transits Western astrology transits: the transits to a natal chart at a moment, and the exact dates transiting aspects perfect over a window of up to a year. 'transit': aspects from the sky at a moment to every natal point, with the natal house each transiting planet occupies. 'window': the exact UTC minute every transiting planet perfects each aspect to each natal point over up to 366 days (62 with the Moon), retrograde passes included. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.08 per call via REST POST https://astro-agent.dev/v1/western/transits (x402 or MPP); always paid, never a free call. Input parameters: - `natal` (object, required): Birth data. - `options` (object): Optional calculation settings; every default is the common Western convention. - `transit` (object): The transit moment. A bare local time is read in the natal place's zone. - `window` (object): UTC dates YYYY-MM-DD, at most 366 days apart. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `synastry` (~177 tokens) Synastry Western astrology synastry (relationship compatibility): compare two birth charts with cross-aspects, house overlays both ways and composite midpoints. Two natal charts compared: every cross-aspect with orbs, where each person's planets fall in the other's houses, harmonious/challenging counts, and composite (midpoint) positions and angles. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.12 per call via REST POST https://astro-agent.dev/v1/western/synastry (x402 or MPP); always paid, never a free call. Input parameters: - `options` (object): Optional calculation settings; every default is the common Western convention. - `person_a` (object, required): First person's birth data. - `person_b` (object, required): Second person's birth data. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `planetary_lines` (~835 tokens) Gann planetary lines Financial astrology Gann planetary lines for trading bots and backtests (stocks, crypto, BTC, forex): planet degrees seen from the Earth and from the Sun (geocentric and heliocentric) at a moment or as an hourly-to-weekly time series keyed by unix timestamp, with aspect offsets, Mean of 5 / Circle of 8 and price levels (degree + 360k) x unit. E.g. {start: '2024-01-01', end: '2024-12-31', interval: '1d', bodies: ['jupiter', 'saturn']}. Financial-astrology DATA for charting and backtests, not signals: the longitude of each planet, seen from the Earth and from the Sun in one call, plus the aspect offsets you ask for (+/-90, 120...), the Optuma averages Mean of 5 and Circle of 8, speeds, retrograde flags and declinations. Snapshot ('datetime') or series ('start', 'end', 'interval' 1h..1w, up to 1000 samples, optionally unwrapped for plotting) in columns ready for pandas. With 'price_unit' and 'price_range': every price level (degree + 360 k) x unit. Each result is hashed, so a backtest can cite and replay it. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.20 per call via REST POST https://astro-agent.dev/v1/finance/planetary-lines (x402 or MPP); always paid, never a free call. Input parameters: - `aspects`: Aspect offsets added to every line (+angle and -angle). Default: the planet's own line only (conjunction). - `average_method` (string): 'arithmetic' mean of the 0-360 longitudes (Optuma's rule) or 'circular' (vector) mean. - `averages` (array): Optuma averages: mean_of_5 = (Jupiter+Saturn+Uranus+Neptune+Pluto)/5, circle_of_8 = (Mercury..Pluto)/8, in each perspective. - `bodies` (array): Bodies to draw. Default: Sun..Pluto (geo), Mercury..Pluto with Earth (helio). - `datetime` (string): A moment (snapshot): ISO 8601 with Z or an offset, e.g. '2024-01-01T00:00Z'. A local time needs 'timezone' or coordinates. Omit when giving start/end. - `end` (string): Series: last UTC date, YYYY-MM-DD (at most 1000 samples). - `format` (string): Series layout: 'columns' (pandas.DataFrame(result['series'])) or 'rows' (one object per sample). - `include_declination` (boolean): Series: also a declination column per body. - `interval` (string): Series sampling step, in candle-timeframe notation. - `options` (object): Optional zodiac settings. - `perspective` (string): Geocentric, heliocentric, or both in one call (default). - `price_range` (object): The price window in which to list levels, e.g. {min: 30000, max: 80000}. - `price_unit` (number): Price per degree. With price_range: levels = (degree + 360 k) x price_unit. - `start` (string): Series: first UTC date, YYYY-MM-DD. Example: '2024-01-01'. - `time_utc` (string): Series: UTC time of day of the first sample, HH:MM. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. - `unwrap` (boolean): Series: continuous degrees (no 360 -> 0 jump), for plotting lines across a chart. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `astro_event_calendar` (~492 tokens) Eclipse & Mercury retrograde calendar (market timing) Financial astrology event calendar for backtesting and trading bots (stocks, crypto, forex): the exact UTC minute and unix timestamp of every eclipse, Mercury retrograde and other station, ingress, new and full moon, planetary aspect, declination parallel and out-of-bounds between two dates, 1800-2200, each with a stable key to join on candles. E.g. {start: '2024-01-01', end: '2024-12-31', include: ['eclipse', 'station']}. A reproducible calendar of celestial events for backtests and alerts, historical or future: sign ingresses, retrograde/direct stations, new/full/quarter moons, solar eclipses (total, annular, hybrid, partial, with gamma) and lunar eclipses (with magnitudes), aspects between planets, declination parallels / contra-parallels and out-of-bounds crossings. Up to 366 days per call, geocentric or heliocentric, tropical or sidereal, Moon optional. Each event has exact_utc, a unix 'timestamp' to join on candle times and a stable 'key' for de-duplication across pages. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/finance/events (x402 or MPP); always paid, never a free call. Input parameters: - `aspects`: Aspects timed between planets. Default: the 5 majors. - `bodies` (array): Planets searched. Default: Sun..Pluto (geo), Mercury..Pluto with Earth (helio). - `end` (string, required): Last UTC date, YYYY-MM-DD, at most 366 days after start (inclusive). - `include` (array): Event types to return. Default: all that apply to the perspective. - `include_moon` (boolean): Also the Moon's ingresses, aspects, parallels and out-of-bounds (geocentric; many events). - `options` (object): Optional zodiac settings. - `perspective` (string): Heliocentric gives ingresses and aspects only (no stations, lunations, eclipses). - `start` (string, required): First UTC date, YYYY-MM-DD, 1800..2199. Example: '2024-01-01'. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `sky_analogues` (~1137 tokens) Sky analogues (matching skies) Financial astrology sky analogues (matching skies, planetary cycle analogues): find the past or future dates whose planetary positions best match a reference sky (a moment, now, positions you give, or a birth sky: compare a birth sky to past/future dates), ranked by a stated angular distance, to line up market history (stocks, crypto) with similar skies in a backtest. E.g. {reference: '2026-10-29T00:00Z', direction: 'past', bodies: ['jupiter', 'saturn'], min_separation_days: 3650}. Data only. Matching skies by geometry, data only: give a reference (a UTC moment, 'now', your own positions, or a birth sky: compare a birth sky to past/future dates — data only) and get the dates in a range (past, future or both, 1800-2200, 1h..1w grid) whose sky is closest, ranked by a weighted mean of circular longitude differences (geocentric and/or heliocentric), pair angles (aspects), declination differences and retrograde-flag mismatches, in degrees. Each match gives its date, unix timestamp, score, every body's exact longitude and retrograde flag and each feature's distance, in columns ready for pandas. The metric formula is in the response; the same request returns the same bytes and hash, future dates included. Up to 100 matches and 36,600 candidate dates per call; no market data. Data for your own analysis — never a signal or forecast. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/finance/analogues (x402 or MPP); always paid, never a free call. Input parameters: - `bodies` (array): Bodies to match. Default: Sun..Pluto (geo), Mercury..Pluto with Earth (helio). - `direction` (string): Search before the reference (a birth: before the birth moment), after it, or both (default; the only choice with reference.values without 'datetime'). - `features` (array): What to compare: 'longitude' (default), 'aspects' (the angle between every pair of bodies), 'declination', 'retrograde' (geocentric flags, Mercury..Pluto). - `format` (string): 'columns' (pandas.DataFrame(result['matches'])) or 'rows' (one object per match). - `max_distance` (number): Optional: only matches whose score (degrees) is at most this. - `min_separation_days` (number): Minimum gap between two matches and between a match and the reference time, so one passage gives one match. Raise it (e.g. 3650) to skip the current cycle of slow planets. - `options` (object): Optional zodiac settings. - `perspective` (string): Positions seen from the Earth, from the Sun, or both. - `range` (object): Candidate dates. Default (a reference with a time): the longest window the caps allow, up to 100 years in the chosen direction (50 on each side for 'both'). - `reference`: The sky to match: 'now' (default; the current UTC hour or day, echoed in result.reference.date_utc), a UTC moment ('2026-10-29T00:00Z' or 'YYYY-MM-DD'), {datetime: ...}, your own configuration {value… - `require_same_retrograde` (boolean): Keep only dates whose retrograde flags equal the reference's. - `resolution` (string): Step of the candidate grid. At most 36,600 candidate dates per call, and at most 660,000 dates x ephemeris series (one per body and perspective, plus one per retrograde-flagged body). - `top_n` (integer): How many matches. - `weights` (object): Optional {feature id: weight}, default 1 each, e.g. {'geo.jupiter': 2}. Feature ids: '.' (longitude, 0-360), '.-:angle' (separation, 0-180), '.:decl… Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `token_chart` (~565 tokens) Token launch sky (crypto token chart) Crypto token launch sky (token astrology chart, data only): the planets' signs, degrees, retrogrades and aspects at a token's launch moment (block time of its deployment or mint), plus the exact UTC dates ahead when planets return to or aspect those positions (key astronomical dates, unix timestamps for backtests) and a shareable SVG card. E.g. {launch_datetime: '2018-08-03T19:28:24Z', token: {symbol: 'USDC'}, from: '2026-11-01'}. Give a token's launch moment (the block time of its contract deployment or mint, UTC, to the second) and get the geocentric sky at that instant: each planet's sign, degree, longitude and retrograde flag, the major aspects between them, element and modality balance (no houses: a token has no place). Then the key dates: the exact UTC minute, over up to 366 days from 'from', at which each transiting planet returns to its launch position or aspects a launch position, each with a unix timestamp and a stable key, in rows ready for pandas. result.card.svg is a server-rendered 1200x675 card (wheel, positions, next key dates) ready to post. Key astronomical dates, data only — never a signal or forecast. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/finance/token-chart (x402 or MPP); always paid, never a free call. Input parameters: - `card` (boolean): Include the shareable SVG card (result.card.svg). - `days` (integer): How many days of key dates from 'from'. - `from` (string): First UTC date of the key dates, YYYY-MM-DD. Default: today (UTC); pass it for a reproducible call. Example: '2026-11-01'. - `launch_datetime` (required): The token's launch moment in UTC: ISO 8601 with Z or an offset, to the second ('2018-08-03T19:28:24Z'), or unix seconds (an on-chain block time). Use the block time of the contract deployment or of t… - `limit` (integer): Maximum key dates returned (counts.key_dates gives the total). - `options` (object): Optional zodiac and aspect settings. - `token` (object): Optional label drawn on the card and echoed in the result. On-chain resolution of the launch time is not available yet: give launch_datetime. - `transit_bodies` (array): Transiting bodies timed against the launch positions (default all nine). Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `token_synastry` (~514 tokens) Token synastry (two launch skies compared) Crypto token synastry (compatibility by sky geometry of two tokens, data only): the cross-aspects between two launch skies with orbs, harmonious / tense counts, the tightest aspects and a geometry score defined in the response, plus a shareable SVG card. E.g. {token_a: {launch_datetime: '2018-08-03T19:28:24Z', symbol: 'USDC'}, token_b: {launch_datetime: '2020-09-14T18:11:26Z', symbol: 'UNI'}}. Two launch moments (UTC block times) compared like a synastry, without houses: every major cross-aspect between token A's and token B's planets with its orb and exactness, harmonious (trine, sextile) / tense (square, opposition) / conjunction counts, the five tightest aspects as readable labels, and geometry_score = 100 x H / (H + T) where H and T sum the exactness (1 - orb / orb allowed) of harmonious and tense aspects -- an aggregate of geometry, defined in the response, not a rating. Next to it, 'substance' says how much geometry the score stands on: aspects_total, counts (harmonious, tense, conjunction), tight_aspects (orb <= 1 deg), the tightest aspect with its orb, the orb threshold, the summed exactness and a confidence label by tight aspects (rich >= 7, moderate 3-6, thin <= 2; the rule is in the response). Rows ready for pandas; result.card.svg is a server-rendered card naming both tokens, with the substance under the score. Data only — never a signal or forecast. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/finance/token-synastry (x402 or MPP); always paid, never a free call. Input parameters: - `card` (boolean): Include the shareable SVG card (result.card.svg). - `options` (object): Optional zodiac and aspect settings. - `token_a` (required): A token: its launch_datetime (string or unix seconds), or {launch_datetime, chain?, address?, symbol?, name?}. - `token_b` (required): A token: its launch_datetime (string or unix seconds), or {launch_datetime, chain?, address?, symbol?, name?}. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `nakshatras` (~464 tokens) Nakshatras Vedic astrology nakshatras: the sidereal nakshatra, pada and lord of every graha, plus the janma nakshatra with gana, yoni, nadi and varna. The 27 lunar mansions for each of the 9 grahas at a moment (Lahiri by default, 6 ayanamsas), with the birth star's attributes used in matching. Or pass 'longitude_sidereal' for a direct lookup. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.02 per call via REST POST https://astro-agent.dev/v1/vedic/nakshatra (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number): Decimal degrees, north positive. - `longitude` (number): Decimal degrees, east positive. - `longitude_sidereal` (number): Optional direct lookup, degrees 0-360. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `panchang` (~438 tokens) Panchang Vedic astrology panchang (Hindu calendar) for a day and place: tithi, vara, nakshatra, yoga and karana with their exact end times, plus sunrise and sunset. The Hindu almanac for any moment and place: the five limbs with their end times (to the minute), paksha, Moon and Sun rashi, sunrise/sunset, and the vara by the sunrise-to-sunrise rule. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.02 per call via REST POST https://astro-agent.dev/v1/vedic/panchang (x402 or MPP); each client gets 1 free call on the $0.01-0.02 tools, this one included. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `kundli` (~474 tokens) Kundli (Vedic birth chart) Vedic astrology birth chart (kundli, Jyotish horoscope, D1 and D9): lagna and the nine grahas with rashi, nakshatra, pada, house, dignity and combustion. The Jyotish birth chart: ayanamsa (Lahiri default; Raman, KP, Yukteshwar, Fagan-Bradley, True Chitrapaksha), lagna, grahas with rashi, nakshatra/pada/lord, bhava, dignity (exalted, debilitated, moolatrikona, own sign), retrograde and combustion, house table with lords and occupants, and the Navamsa (D9). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.15 per call via REST POST https://astro-agent.dev/v1/vedic/kundli (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `kundli_full` (~441 tokens) Kundli with all 16 vargas Vedic astrology full kundli: all 16 Shodashavarga divisional charts, D1 to D60 (navamsa, dasamsa...), by Parashara's rules. Everything in /vedic/kundli plus D1, D2, D3, D4, D7, D9, D10, D12, D16, D20, D24, D27, D30, D40, D45 and D60, each with its lagna, placements and house table. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.32 per call via REST POST https://astro-agent.dev/v1/vedic/kundli-full (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `vimshottari_dasha` (~447 tokens) Vimshottari dashas Vedic astrology dasha periods: the Vimshottari maha, antar and pratyantar dashas with exact dates, the balance at birth and the periods running now. The 120-year Vimshottari sequence from the Moon's exact nakshatra position: balance at birth, all 9 mahadashas with sub-periods down to 4 levels, and (with on_date) the periods running on a date. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.10 per call via REST POST https://astro-agent.dev/v1/vedic/dashas (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `on_date` (string): YYYY-MM-DD (UTC): also report what is active on this date. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `doshas` (~448 tokens) Doshas Vedic astrology doshas: check Manglik (Kuja), Kaal Sarp and Sade Sati / Dhaiya, each with the rule applied and the relevant dates. Manglik from lagna, Moon and Venus with severity and commonly cited cancellations; Kaal Sarp with type and direction (partial cases flagged); Sade Sati cycles and Dhaiya phases with start/end dates over 100 years, plus the status on a given date. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.15 per call via REST POST https://astro-agent.dev/v1/vedic/doshas (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `on_date` (string): YYYY-MM-DD (UTC): also report what is active on this date. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `gun_milan` (~229 tokens) Gun Milan (Ashtakoota matching) Vedic astrology kundli matching (horoscope matching, marriage compatibility): 36-point Ashtakoota Gun Milan with all 8 kootas and reasons, plus dosha and Manglik checks. Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot and Nadi scored from both Moons, each with the attributes and rule behind the score, Nadi/Bhakoot dosha flags with commonly cited cancellations, and both partners' Manglik status. Boy = person_a, girl = person_b by convention. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.25 per call via REST POST https://astro-agent.dev/v1/vedic/gun-milan (x402 or MPP); always paid, never a free call. Input parameters: - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `person_a` (object, required): Groom / boy (traditional convention). - `person_b` (object, required): Bride / girl. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `vedic_report` (~432 tokens) Complete Vedic report Vedic astrology report in one call: kundli, Vimshottari dashas, doshas and the birth panchang. The full Jyotish dossier for one person in a single deterministic call: everything in /vedic/kundli, /vedic/dashas (2 levels, running periods with on_date), /vedic/doshas and the panchang at birth. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.50 per call via REST POST https://astro-agent.dev/v1/vedic/report (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `on_date` (string): YYYY-MM-DD (UTC): also report what is active on this date. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `kp_chart` (~506 tokens) KP chart (Krishnamurti Paddhati) KP astrology (Krishnamurti Paddhati) chart: the star lord, sub-lord and sub-sub-lord of every planet and house cusp, cuspal sub-lords and the A/B/C/D house significators. Krishnamurti Paddhati on the KP ayanamsa with Placidus cusps: for each of the 9 grahas and 12 cusps the sign lord, star (nakshatra) lord, sub-lord, sub-sub-lord and number among the 249 KP subs; the cuspal sub-lords; house significators at the four levels A (in the star of occupants), B (occupants), C (in the star of the lord), D (lord); and each planet's significations. The sub-division rule is stated in the response. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.15 per call via REST POST https://astro-agent.dev/v1/vedic/kp (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `options` (object): Optional KP settings. Cusps are always Placidus (the KP convention). - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `yogas` (~526 tokens) Yogas Vedic astrology yogas: detect Raj yoga, Dhana yoga, Gaja-Kesari, Budha-Aditya, Chandra-Mangala, the five Pancha Mahapurusha yogas, Neecha Bhanga Raja yoga, Kemadruma and Kaal Sarp, each with the rule applied. Deterministic yoga detection on the sidereal chart, houses counted by sign: the five Pancha Mahapurusha yogas (Ruchaka, Bhadra, Hamsa, Malavya, Sasa), Gaja-Kesari, Budha-Aditya, Chandra-Mangala, Dhana (lords of 2, 5, 9, 11), Raja (kendra and trikona lords, yogakarakas), Neecha Bhanga Raja, Kemadruma and Kaal Sarp. Each yoga gives the rule applied, the grahas and houses involved and whether it is present; no predictive interpretation. Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.10 per call via REST POST https://astro-agent.dev/v1/vedic/yogas (x402 or MPP); always paid, never a free call. Input parameters: - `ambiguous_time` (string): Which occurrence to use when a local time happens twice (DST fall-back). - `date` (string): YYYY-MM-DD (use with 'time' instead of 'datetime'). - `datetime` (string): Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. - `latitude` (number, required): Decimal degrees, north positive. - `longitude` (number, required): Decimal degrees, east positive. - `options` (object): Optional calculation settings; every default is the common Parashari convention. - `time` (string): HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). - `time_basis` (string): What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time. - `timezone` (string): IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. Output parameters: - `accepts` (array): x402 offer only: the payment options (scheme, network, amount, asset, payTo, ...). - `endpoint` (string): The REST route that computed it, e.g. 'western/natal'. - `error` (string): x402 offer only: why payment is required. - `extensions` (object): x402 offer only: protocol extensions (bazaar). - `meta` (object): Provenance of the result. - `resource` (object): x402 offer only: the resource being paid for. - `result` (object): The calculation result. - `x402Version` (integer): x402 offer only: protocol version (2). ### `astro_catalog` (~78 tokens) Catalog (free) List every astrology, ephemeris and financial-astrology (trading backtest) tool with its price, input schema and an example request: planet positions, event calendar (eclipses, Mercury retrograde), Gann planetary lines, sky analogues, natal and Vedic charts. Free; call it first to pick the right tool. Output parameters: - `accuracy` (object): Headline of the accuracy benchmark against NASA/JPL Horizons (largest deviations in arcseconds) with links to the details. - `calls` (array): The $0.01-0.02 tools: MCP tool name, price, REST route, what it computes and an example request (input schemas are in tools/list). - `discovery` (object): Discovery documents: OpenAPI, MCP server card, A2A agent card. - `engine_version` (string): Calculation engine version. - `free_endpoints` (object): Endpoints that are always free (catalog, verify, health, benchmark). - `payment` (object): Free calls, payment protocols (x402, MPP) and networks. - `premium` (array): The full-chart tools, same fields as 'calls'. - `service` (string): Service name. - `start_here` (string): Which tool to call first for common questions. - `support` (object): Contact, documentation and policies. - `tagline` (string): One-line summary of the service. - `whats_new` (object): What the current release added (version, date, and each new tool or proof with its route, price and summary). - `why_use_this_instead_of_computing_it_yourself` (array): Reasons to prefer these tools over computing a chart yourself. ### `verify_result_hash` (~95 tokens) Verify a result hash (free) Verify that an astrology result was not altered: recompute the SHA-256 of a 'result' object returned by any tool and compare it with the result_sha256 you hold. Free. Input parameters: - `result` (object, required): The 'result' object exactly as a tool returned it. - `result_sha256` (string): The meta.result_sha256 returned with it (64 hex characters). Omit to only recompute the hash. Output parameters: - `matches` (boolean): Whether it equals the result_sha256 you sent. Absent if you sent none. - `result_sha256` (string): SHA-256 recomputed from the 'result' you sent. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent#diagnostics ## Score history - 2026-11-07: 87 - 2026-11-06: 87 - 2026-11-05: 87 - 2026-11-04: 87 - 2026-11-03: 87 - 2026-11-02: 86 - 2026-11-01: 86 - 2026-10-31: 85 - 2026-10-30: 85 - 2026-10-29: 85 - 2026-10-28: 84 - 2026-10-27: 84 - 2026-10-26: 84 - 2026-10-25: 83 - 2026-10-24: 83 - 2026-10-23: 82 - 2026-10-22: 82 - 2026-10-21: 81 - 2026-10-20: 81 - 2026-10-19: 80 - 2026-10-18: 80 - 2026-10-17: 79 - 2026-10-16: 79 - 2026-10-15: 79 - 2026-10-14: 78 - 2026-10-13: 78 - 2026-10-12: 77 - 2026-10-11: 77 - 2026-10-10: 76 - 2026-10-07: 75 ## Common questions ### What is the Astro Agents - verifiable planetary timing data and… MCP server? Astro Agents - verifiable planetary timing data and… is an MCP server listed in the public MCP registry as io.github.aidatatools-dev/astro-agents. Verifiable market-timing data for trading bots: Gann lines, events, analogues. Pay per call in MCP. This page covers its hosted endpoint (https://astro-agent.dev/mcp). ### Is the Astro Agents - verifiable planetary timing data and… MCP server safe to use? Astro Agents - verifiable planetary timing data and… scores 87 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the Astro Agents - verifiable planetary timing data and… MCP server expose? Astro Agents - verifiable planetary timing data and… exposes 24 tools: resolve_birth_time, planet_positions, sky_today, aspects, natal_chart, and 19 more. Their descriptions and schemas cost roughly 10,898 tokens of context every time the server is loaded. ### Does the Astro Agents - verifiable planetary timing data and… MCP server require authentication? No. We connected to Astro Agents - verifiable planetary timing data and… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the Astro Agents - verifiable planetary timing data and… MCP server still maintained? Astro Agents - verifiable planetary timing data and… is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What did VerifyMCP test on the Astro Agents - verifiable planetary timing data and… MCP server? VerifyMCP ran 13 checks on Astro Agents - verifiable planetary timing data and…, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out. ## Links - Remote endpoint: https://astro-agent.dev/mcp - Repository: https://github.com/aidatatools-dev/astro-agents-mcp - Website: https://astro-agent.dev/llms.txt - Changelog RSS feed: https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent.xml - Changelog JSON feed: https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent/changelog.json - Trust report (JSON): https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent.json - HTML version of this page: https://verifymcp.io/servers/aidatatools-dev-astro-agents/astro-agent