Vedic Astrology and Kundli MCP Server by RoxyAPI
REMOTE · ROXYAPI.COM · SCANNED AUG 4
Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.
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 Security63
- 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 54 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 37128 tokens (~687/item across 54 items; 54 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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 · roxyapi.com
claude mcp add --transport http com-roxyapi-vedic-astrology https://roxyapi.com/mcp/vedic-astrology
[mcp_servers.com-roxyapi-vedic-astrology] url = "https://roxyapi.com/mcp/vedic-astrology"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-roxyapi-vedic-astrology": {
"type": "remote",
"url": "https://roxyapi.com/mcp/vedic-astrology",
"enabled": true
}
}
} openclaw mcp add com-roxyapi-vedic-astrology --url https://roxyapi.com/mcp/vedic-astrology --transport streamable-http
mcp_servers:
com-roxyapi-vedic-astrology:
url: "https://roxyapi.com/mcp/vedic-astrology" {
"mcpServers": {
"com-roxyapi-vedic-astrology": {
"type": "http",
"url": "https://roxyapi.com/mcp/vedic-astrology"
}
}
} 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.
- 3 Aug 26 +1
- Tool “get_vedic_astrology_yoga_id” rewrote its description, which is the text the model reads security
- Schema quality: 596 → 687 ▼ functional
- New tool “post_vedic_astrology_bhav_chalit” functional
- New tool “post_vedic_astrology_bhava_bala” functional
- New tool “post_vedic_astrology_heliacal” functional
- New tool “post_vedic_astrology_kp_horary” functional
- “post_vedic_astrology_dosha_kalsarpa” added an optional parameter “lang” cosmetic
- “post_vedic_astrology_dosha_manglik” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_dosha_manglik” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_dosha_manglik” added an optional parameter “lang” cosmetic
- “post_vedic_astrology_dosha_sadhesati” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_dosha_sadhesati” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_dosha_sadhesati” added an optional parameter “lang” cosmetic
- “post_vedic_astrology_navamsa” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_navamsa” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_planetary_positions” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_planetary_positions” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_shadbala” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_shadbala” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_shadbala” added an optional parameter “lang” cosmetic
- “post_vedic_astrology_upagraha” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_upagraha” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_yoga_detect” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_yoga_detect” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_arudha” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_arudha” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_ashtakavarga” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_ashtakavarga” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_birth_chart” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_birth_chart” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_birth_chart” added an optional parameter “modernPlanets” cosmetic
- “post_vedic_astrology_chara_karakas” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_chara_karakas” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_compatibility” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_compatibility” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_divisional_chart” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_divisional_chart” added an optional parameter “ayanamsaValue” cosmetic
- “post_vedic_astrology_dosha_kalsarpa” added an optional parameter “ayanamsa” cosmetic
- “post_vedic_astrology_dosha_kalsarpa” added an optional parameter “ayanamsaValue” cosmetic
- 2 Aug 26 −1
- “get_vedic_astrology_yoga” added an optional parameter “family” cosmetic
- “post_vedic_astrology_birth_chart” added an optional parameter “avasthaInfo” cosmetic
- “post_vedic_astrology_kp_sublord_changes” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_kp_planets_interval” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_kp_rasi_changes” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_kp_ruling_planets_interval” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_dasha_current” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_dasha_major” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_kp_chart” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_kp_cusps” reworded the description of “ayanamsa” cosmetic
- “post_vedic_astrology_kp_planets” reworded the description of “ayanamsa” cosmetic
15 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 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
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 58
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 4 Aug 2026 · Probed https://roxyapi.com/mcp/vedic-astrology
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=roxyapi.com | CN=WE1,O=Google Trust Services,C=US | 26 Jul 2026 | 24 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | fb04ac30ca01abb60e3558bdfadfe2f4 |
| SANs: roxyapi.com, *.roxyapi.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of roxyapi.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| roxyapi.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' https://fonts.scalar.com; connect-src 'self' https://api.scalar.com https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=() |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://roxyapi.com/mcp/vedic-astrology | Verified | 200 | |
| http (plaintext) | http://roxyapi.com/mcp/vedic-astrology | HTTPS enforced | 301 | https://roxyapi.com/mcp/vedic-astrology |
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.
post_vedic_astrology_kp_ruling_planets_interval Get KP ruling planets with significators at intervals ~942
Calculate ruling planets and their KP significators at regular time intervals using Krishnamurti Paddhati prashna (horary) astrology. For each interval, a full Placidus house chart is erected and significators are computed using the 4-level KP hierarchy: Level 1 (strongest) planets in star of house occupant, Level 2 occupants, Level 3 planets in star of house owner, Level 4 house owner. Returns Day Lord (sunrise-based Hindu Vara), Moon Sign/Star/Sub/Sub-Sub Lords, Lagna Sign/Star/Sub/Sub-Sub Lords, unique ruling planets set, and per-ruling-planet house significations. No birth data needed, significators come from each moments sky chart. Use for birth time rectification, muhurta selection, and KP horary number analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with… |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| endDatetime | string | yes | End of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC. |
| focus | string | — | Which signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same… |
| intervalMinutes | integer | yes | Interval between calculations in minutes (1-1440). Use 1-5 for birth time rectification. |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Observer latitude in decimal degrees |
| longitude | number | yes | Observer longitude in decimal degrees |
| nodeType | string | — | Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1… |
| startDatetime | string | yes | Start of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC. |
| timezone | — | — | Timezone offset from UTC in decimal hours. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to… |
No output schema declared.
No examples provided.
post_vedic_astrology_kp_sublord_changes Find KP sublord changes ~559
Track when planets cross KP sublord boundaries (1-249 divisions) for precise Krishnamurti Paddhati event timing. Returns exact timestamps when a planet transitions between sublords, essential for prashna kundali analysis and dasha predictions. Use this to find favorable windows when benefic sublords are active. Supports Sun, Moon, Mars, Mercury, Jupiter, Venus, and Saturn tracking over any date range.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with… |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| endDate | string | yes | End date for sublord change search (YYYY-MM-DD format) |
| nodeType | string | — | Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1… |
| planet | string | yes | Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn |
| startDate | string | yes | Start date for sublord change search (YYYY-MM-DD format) |
| timezone | — | — | IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC). |
No output schema declared.
No examples provided.
post_vedic_astrology_navamsa Get Navamsa chart (D9) - Marriage Compatibility Calculator ~797
Calculate Navamsa (D9 divisional chart) for marriage compatibility analysis, spouse prediction, and spiritual life assessment. Navamsa calculator API reveals planetary strength in married life. Each planetary position is divided into 9 parts for accurate marriage astrology. Detects Vargottama planets (exalted status). Essential for matrimonial matching, relationship prediction, and marital harmony analysis in Vedic astrology.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | — | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | — | — | Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you c… |
No output schema declared.
No examples provided.
post_vedic_astrology_panchang_basic Get basic Panchang - Tithi Nakshatra Yoga Karana Calculator ~419
Calculate Panchang elements (Hindu calendar) for any date: Tithi (lunar day), Nakshatra (lunar mansion), Yoga, and Karana. Daily panchang API for determining auspicious timings (muhurta), festival dates, and planetary influences. Tithi calculator with Shukla/Krishna paksha. Accurate nakshatra today with ruling planet. Essential for Hindu calendar integration, muhurta selection, and Vedic timekeeping in astrology apps.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Date in YYYY-MM-DD format. Panchang elements (Tithi, Nakshatra, Yoga, Karana) are calculated for this date. |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Observer latitude in decimal degrees. Determines sunrise/sunset times which define the Vara (weekday) and muhurta boundaries. |
| longitude | number | yes | Observer longitude in decimal degrees. Affects local time calculations for sunrise/sunset-dependent panchang elements. |
| time | string | yes | Time in HH:MM:SS format (24-hour). Determines the exact Moon and Sun positions for tithi and nakshatra calculation. |
| timezone | — | — | Timezone offset from UTC in decimal hours. Defaults to 5.5 (IST). |
No output schema declared.
No examples provided.
post_vedic_astrology_panchang_choghadiya Get Choghadiya - 8 Muhurta divisions of day and night ~423
Calculate Choghadiya (Chaughadia) muhurta timings for any date and location. Divides day (sunrise to sunset) and night (sunset to next sunrise) into 8 equal auspicious/inauspicious periods. Each period ruled by a planet: Udveg (Sun, bad), Amrit (Moon, good), Rog (Mars, bad), Labh (Mercury, good), Shubh (Jupiter, good), Char (Venus, good), Kaal (Saturn, bad). Essential for muhurta selection, daily planning, and traditional Hindu timekeeping. Choghadiya calculator API, daily muhurat timings, auspicious time finder.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. |
| latitude | number | yes | Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations. |
| longitude | number | yes | Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries. |
| timezone | — | — | Timezone offset from UTC in decimal hours. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Choghadiya periods outside IST. Defaults to 5.5 (IST). |
No output schema declared.
No examples provided.
post_vedic_astrology_panchang_detailed Get detailed Panchang with Rahu Kaal, Yamaganda, Gulika ~495
Complete daily panchang with all five limbs (Tithi, Nakshatra, Yoga, Karana, Vara) plus sunrise, sunset, moonrise, moonset times. Includes inauspicious periods (Rahu Kaal, Yamaganda, Gulika Kaal) and auspicious windows (Abhijit Muhurta, Brahma Muhurta). Current planetary hora with start/end times. Essential for muhurta selection, daily horoscope apps, Hindu calendar integration, and electional astrology. Accurate calculations based on observer location.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations. |
| longitude | number | yes | Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries. |
| timezone | — | — | Timezone offset from UTC in decimal hours, for example -5 for New York or 9 for Tokyo. Send the offset that matches the coordinates: sunrise, sunset and every muhurta boundary are found by searching… |
No output schema declared.
No examples provided.
post_vedic_astrology_panchang_hora Get Hora - 24 Planetary Hours (12 day + 12 night) ~355
Calculate all 24 Hora (planetary hour) periods for any date and location. Day is divided into 12 equal horas from sunrise to sunset, night into 12 equal horas from sunset to next sunrise. Each hora is ruled by a planet in the Chaldean sequence starting from the day lord. Hora timings API, planetary hours calculator, Vedic hora chart, electional astrology timing.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. |
| latitude | number | yes | Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations. |
| longitude | number | yes | Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries. |
| timezone | — | — | Timezone offset from UTC in decimal hours. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Hora periods outside IST. Defaults to 5.5 (IST). |
No output schema declared.
No examples provided.
post_vedic_astrology_parallels Declination Parallels - Planets at same or opposite declination ~353
Calculate planetary declinations and find parallels (same declination) and contraparallels (opposite declination). Parallels are considered equivalent to conjunctions in strength, contraparallels to oppositions. Returns declination for each planet and all parallel/contraparallel aspects. Declination parallels API, planetary declination calculator, contraparallel aspects.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Date in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects. |
| latitude | number | yes | Observer latitude in decimal degrees. Used for topocentric declination corrections. |
| longitude | number | yes | Observer longitude in decimal degrees. Affects local time context for declination calculations. |
| orb | number | — | Orb in degrees for parallel/contraparallel detection. Defaults to 1.5°. |
| time | string | yes | Time in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon. |
| timezone | — | — | Timezone offset from UTC in hours. Defaults to 5.5 (IST). |
No output schema declared.
No examples provided.
post_vedic_astrology_parallels_monthly Monthly Declination Parallels - Parallel and contraparallel events for a month ~284
Find all declination parallel and contraparallel events between the 7 visible planets for a given month. Parallels occur when two planets share the same celestial declination (equivalent to conjunction in strength). Contraparallels occur at opposite declinations (equivalent to opposition). Scanned daily at noon UTC. Essential for advanced transit analysis and hidden aspect discovery. Monthly declination parallels API, planetary parallel ephemeris, contraparallel event calendar.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| month | integer | yes | Month number (1-12) for parallel analysis. |
| timezone | — | — | Timezone offset from UTC in hours. Output times are converted to this timezone. Defaults to 0 (UTC). |
| year | integer | yes | Year for monthly parallel analysis (1900-2100). |
No output schema declared.
No examples provided.
post_vedic_astrology_planetary_positions Get planetary positions - Graha Positions API ~811
Get simplified planetary positions (graha positions) for all 9 planets (Sun through Ketu) plus Ascendant (Lagna). Real-time planet transit calculator for Vedic astrology. Navagraha positions API with nakshatra, pada, and rashi details. Includes house number placement using Whole Sign house system from Lagna. Faster response for basic planetary data without full chart structure. Perfect for planetary alignment tracking, daily transit updates, and astrology widgets.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | — | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | — | — | Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you c… |
No output schema declared.
No examples provided.
post_vedic_astrology_planetary_positions_monthly Monthly Ephemeris - Daily sidereal planetary positions for a month ~321
Get daily sidereal ecliptic positions for all 9 Vedic planets (Navagraha) for an entire month. Returns longitude, zodiac sign, degree within sign, and retrograde status for each planet on each day. Calculated at noon UTC. Essential for ephemeris generation, transit tracking, and planetary movement visualization. Monthly planetary ephemeris API, sidereal position table, daily graha gochara positions, ecliptic longitude calculator.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| coordinateSystem | string | — | Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa - standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults… |
| month | integer | yes | Month number (1-12) for ephemeris. |
| year | integer | yes | Year for monthly ephemeris (1900-2100). |
No output schema declared.
No examples provided.
post_vedic_astrology_shadbala Get Shadbala (six-fold planetary strength) analysis - Shadbala Calculator API ~854
Calculate complete Shadbala (six-fold planetary strength) per Brihat Parashara Hora Shastra (BPHS) and BV Raman Graha and Bhava Balas. Returns all 6 strength components (Sthana Bala, Dig Bala, Kala Bala, Chesta Bala, Naisargika Bala, Drik Bala) plus Ishta Phala, Kashta Phala, strength ratio, and relative ranking for all 7 classical planets. Essential for evaluating planetary strength in Vedic birth chart analysis, dasha prediction, transit interpretation, and yoga assessment. Shadbala calculator API, planetary strength Vedic astrology, graha bala, Ishta Kashta Phala.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | — | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | — | — | Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you c… |
No output schema declared.
No examples provided.
post_vedic_astrology_transit Transit Analysis - Compare current planets to natal chart (Gochar) ~464
Analyze planetary transits (Gochar) over natal chart positions. Returns transiting planets with their natal house positions, aspects to natal planets, and highlights key transits from slow-moving planets (Jupiter, Saturn, Rahu, Ketu). Essential for timing predictions, event forecasting, and understanding current planetary influences. Transit analysis API, gochar calculator, vedic transit predictions.
| Name | Type | Req | Description |
|---|---|---|---|
| birthDate | string | yes | Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed. |
| birthTime | string | yes | Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements. |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| coordinateSystem | string | — | Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa - standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults… |
| latitude | number | yes | Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments. |
| longitude | number | yes | Observer longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations. |
| timezone | — | — | Timezone offset from UTC in hours. Defaults to 5.5 (IST). |
| transitDate | string | yes | Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart. |
| transitTime | string | — | Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon. |
No output schema declared.
No examples provided.
post_vedic_astrology_transit_monthly Monthly Transit - Planetary sign changes for an entire month ~346
Get all planetary sign (rashi) changes for a given month. Shows when each planet transitions from one zodiac sign to another. Covers all 9 Vedic planets: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Includes starting positions at the beginning of the month. Essential for transit prediction, monthly horoscope generation, and muhurta planning. Monthly planetary transit API, gochar calendar, rashi parivartan dates.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| coordinateSystem | string | — | Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa - standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults… |
| month | integer | yes | Month number (1-12) for transit analysis. |
| timezone | — | — | Timezone offset from UTC in hours. Output times are converted to this timezone. Defaults to 0 (UTC). |
| year | integer | yes | Year for monthly transit analysis (1900-2100). |
No output schema declared.
No examples provided.
post_vedic_astrology_upagraha Get upagraha (sub-planet) positions - Upagraha Calculator API ~811
Calculate all 11 Vedic upagraha (sub-planet) positions per Brihat Parashara Hora Shastra (BPHS). Returns 6 time-based upagrahas (Gulika, Mandi, Kala, Mrityu, Ardhaprahara, Yamaghantaka) derived from the 8-part day/night division, plus 5 Sun-longitude-based upagrahas (Dhuma, Vyatipata, Parivesha, Indra Chapa, Upaketu). Essential for complete kundli analysis, dosha assessment, and advanced chart interpretation. Upagraha calculator API, Gulika Mandi position, sub-planet Vedic astrology.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | — | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | — | — | Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you c… |
No output schema declared.
No examples provided.
post_vedic_astrology_yoga_detect Detect classical Vedic yogas in a birth chart ~1,184
Chart-driven detection of 44 classical Vedic yogas. Twelve conjunction and dignity yogas: Gajakesari (parashara three-rule definition), Sunapha, Anapha, Dhurdhura, Kemadruma, Chandra Mangala, Budha-Aditya, and the five Pancha Mahapurusha yogas (Ruchaka, Bhadra, Hamsa, Malavya, Sasa). Plus all 32 Nabhasa distribution yogas, which describe how the seven visible grahas are spread across the whole chart rather than any single conjunction, across four families: Asraya (Rajju, Musala, Nala), Dala (Mala, Sarpa), Akriti (Gada, Shakata, Vihaga, Shringataka, Hala, Vajra, Yava, Kamala, Vapi, Yupa, Shara, Shakti, Danda, Nauka, Kuta, Chhatra, Dhanusha, Ardhachandra, Chakra, Samudra) and Sankhya (Gola, Yuga, Shoola, Kedara, Pasa, Damini, Veena). Each yoga is returned with an `id`, `name`, a `present` boolean, a `quality` (Positive, Negative, or Both, i.e. auspicious, inauspicious, or context-dependent), and a classical-text `evidence` string naming the rule that triggered or failed (kendra position, dignity, malefic drishti, lordship, retrograde state, sign modality, bhava distribution). Nabhasa results also apply the four classical precedence norms, so a yoga that matched its own rule but was outranked by a stronger family is returned as absent with evidence naming the norm that silenced it, letting you explain a verdict rather than only report it. There is no separate major/minor flag; `quality` is the auspiciousness axis. Unlike GET /yoga and GET /yoga/{id} which are dictionary lookups, this endpoint computes the kundli from birth data and runs the detection rules. Sources: BPHS ch. 35 and ch. 75, Mantreswara Phaladeepika ch. 6, B.V. Raman Three Hundred Important Combinations.
| Name | Type | Req | Description |
|---|---|---|---|
| ayanamsa | string | — | Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hind… |
| ayanamsaValue | number | — | Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source. |
| compact | boolean | — | Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie… |
| date | string | yes | Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and div… |
| lang | string | — | Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English. |
| latitude | number | yes | Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172. |
| longitude | number | yes | Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240. |
| time | string | yes | Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and… |
| timezone | — | — | Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you c… |
No output schema declared.
No examples provided.