Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vedic Astrology and Kundli MCP Server by RoxyAPI

REMOTE · ROXYAPI.COM

Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.

Available components

0 this week 87 Trust /100

Last scanned (11 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 42024 tokens (~724/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (95% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 58 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 58 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 29 Oct 26 0
    • Tool “post_vedic_astrology_kp_chart” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_kp_cusps” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_kp_daily_finance” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_kp_horary” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_kp_ruling_planets_interval” rewrote its description, which is the text the model reads security
    • “post_vedic_astrology_daily” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_current” reworded the description of “datetime” cosmetic
    • “post_vedic_astrology_dasha_current” reworded the description of “significators” cosmetic
    • “post_vedic_astrology_dasha_major” reworded the description of “significators” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha” reworded the description of “significators” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha_antardasha” reworded the description of “significators” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha” reworded the description of “significators” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma” reworded the description of “significators” cosmetic
    • “post_vedic_astrology_kp_chart” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_kp_cusps” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_kp_daily_finance” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_kp_daily_finance” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_horary” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_kp_planets” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_kp_ruling_planets” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_kp_ruling_planets” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_ruling_planets_interval” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_transit” reworded the description of “timezone” cosmetic
  • 10 Oct 26 0
    • Tool “post_vedic_astrology_birth_chart” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_planetary_positions” rewrote its description, which is the text the model reads security
    • Tool “post_vedic_astrology_planetary_positions_monthly” rewrote its description, which is the text the model reads security
  • 3 Oct 26 87
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 1 Oct 26 0
    • “post_vedic_astrology_aspects_lunar” reworded the description of “year” cosmetic
    • “post_vedic_astrology_aspects_monthly” reworded the description of “year” cosmetic
    • “post_vedic_astrology_ecliptic_crossings” reworded the description of “year” cosmetic
    • “post_vedic_astrology_panchang_choghadiya” reworded the description of “date” cosmetic
    • “post_vedic_astrology_panchang_detailed” reworded the description of “date” cosmetic
    • “post_vedic_astrology_panchang_hora” reworded the description of “date” cosmetic
    • “post_vedic_astrology_parallels_monthly” reworded the description of “year” cosmetic
    • “post_vedic_astrology_planetary_positions_monthly” reworded the description of “year” cosmetic
    • “post_vedic_astrology_transit_monthly” reworded the description of “year” cosmetic

    9 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 30 Sept 26 0
    • “post_vedic_astrology_panchang_choghadiya” reworded the description of “date” cosmetic
    • “post_vedic_astrology_panchang_detailed” reworded the description of “date” cosmetic
    • “post_vedic_astrology_panchang_hora” reworded the description of “date” cosmetic
    • “post_vedic_astrology_parallels” reworded the description of “latitude” cosmetic
    • “post_vedic_astrology_parallels” reworded the description of “longitude” cosmetic

    5 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0
    • “post_vedic_astrology_ecliptic_crossings” added an optional parameter “lang” cosmetic
    • “post_vedic_astrology_arudha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_ashtakavarga” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_aspects” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_aspects_lunar” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_aspects_monthly” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_bhav_chalit” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_bhava_bala” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_birth_chart” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_chara_karakas” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_current” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_major” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha_antardasha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dasha_sub_mahadasha_antardasha_pratyantardasha_sookshma” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_divisional_chart” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dosha_kalsarpa” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dosha_manglik” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_dosha_sadhesati” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_ecliptic_crossings” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_chart” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_cusps” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_planets” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_kp_ruling_planets_interval” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_navamsa” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_panchang_basic” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_panchang_choghadiya” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_panchang_detailed” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_panchang_hora” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_parallels” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_parallels_monthly” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_planetary_positions” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_shadbala” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_transit” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_transit_monthly” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_upagraha” reworded the description of “timezone” cosmetic
    • “post_vedic_astrology_yoga_detect” reworded the description of “timezone” cosmetic

    38 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

Diagnostics

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 5 Nov 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 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 b253589252f3f4620e758a7554771c71
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

Background: What to check on a remote MCP endpoint →

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'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 'self' 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=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

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
MCP tools · 58 exposed · ~42,024 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
post_vedic_astrology_divisional_chart ~1,008

Calculate any Vedic divisional chart (Varga) from D2 Hora to D60 Shashtiamsa. Divisional charts divide each zodiac sign into smaller segments to reveal detailed insights about specific life areas: wealth (D2), siblings (D3), property (D4), children (D7), marriage (D9), career (D10), parents (D12), vehicles (D16), spirituality (D20), education (D24), strength (D27), misfortunes (D30), merit (D40), character (D45), and past life karma (D60). Based on Brihat Parashara Hora Shastra (BPHS) Shodasha Varga system. Detects Vargottama planets (same sign in D1 and selected chart).

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
divisionintegeryesDivisional chart number. Each division reveals a specific life area. Supported: 2 (Hora, wealth), 3 (Drekkana, siblings), 4 (Chaturthamsa, property), 7 (Saptamsa, children), 9 (Navamsa, marriage), 10…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
chartobjectyes–
divisionobjectyes–
frameobjectyes–
vargottamaarrayyes–
{"date":"1990-07-04","division":10,"latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_dosha_kalsarpa ~804

Detect Kalsarpa dosha (Kalsarpa yoga) when all 7 planets are hemmed between Rahu-Ketu axis. Accurate kalsarpa dosha calculator identifying 12 types (Ananta, Kulik, Vasuki, Shankhapala, Padma, Mahapadma, Takshak, Karkotak, Shankhachud, Ghatak, Vishdhar, Sheshnag). Returns severity and effects based on Rahu house position. Essential for Vedic astrology dosha analysis, birth chart evaluation, and matrimonial compatibility. Considered significant dosha affecting life obstacles and spiritual growth.

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
descriptionstringyes–
effectsobject––
frameobjectyes–
presentbooleanyes–
remediesarray––
severitystring––
typestring––
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_dosha_manglik ~785

Detect Manglik dosha (Kuja dosha, Mars dosha) based on Mars position in inauspicious houses (1, 2, 4, 7, 8, 12) from Lagna. Accurate mangal dosha calculator for matrimonial compatibility checks in Vedic astrology. Returns severity levels (Mild/Moderate/Severe) and cancellation factors. Essential for kundli matching for marriage, manglik compatibility, and marriage astrology in matrimonial sites. Includes exceptions that reduce manglik dosha effects.

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
descriptionstringyes–
effectsobject––
exceptionsarray––
frameobjectyes–
presentbooleanyes–
remediesarray––
severitystring––
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_dosha_sadhesati ~782

Calculate Sadhesati (Sade Sati) periods when Saturn transits 12th, 1st, and 2nd houses from natal Moon. Accurate sade sati calculator with current status and phase identification (Rising/Peak/Setting). Shani sadhesati 7.5 year period tracker. Returns Saturn transit dates and effects on life. Essential for Saturn transit analysis, sadhesati remedies timing, and understanding challenging Saturn periods in Vedic astrology. Important for timing major life decisions.

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
descriptionstringyes–
effectsobject––
frameobjectyes–
presentbooleanyes–
remediesarray––
severitystring––
typestring––
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_ecliptic_crossings ~439

Find all ecliptic plane crossings for visible planets during a given year. An ecliptic crossing occurs when a planetary celestial latitude passes through 0 degrees, crossing from one side of the ecliptic to the other. Ascending crossings (south to north) correspond to the ascending node, descending crossings (north to south) to the descending node. Moon crosses ~2 times per month, outer planets cross less frequently. Returns exact date, time, direction, longitude and zodiac sign in the requested coordinateSystem, sidereal by default. Ecliptic crossing API, planetary node crossing, ascending descending node ephemeris.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
coordinateSystemstring–Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved onc…
yearintegeryesYear to scan for ecliptic crossings (1551 to 2649).
NameTypeReqDescription
eventsarrayyes–
timezonenumberyes–
yearnumberyes–
{"year":2026}
post_vedic_astrology_heliacal ~472

Calculate heliacal rising (udaya) and setting (asta) of the six visible grahas for any date and place, by the Surya Siddhanta rule. Returns whether each graha currently clears the solar glare, its separation from the Sun in classical degrees of time, and the dates its visibility last changed and next changes. This is the calculation behind Guru Asta and Shukra Asta, the periods classical muhurta withholds marriage and other auspicious ceremonies. Unlike a birth chart combustion flag it is location aware, because the angle the ecliptic makes with the local horizon decides how long a graha lingers after the Sun. Graha asta API, Guru Asta Shukra Asta dates, heliacal rising calculator, planetary combustion muhurta.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesLocal calendar date to judge, in YYYY-MM-DD format. There is deliberately no time field: heliacal visibility is a once-a-day verdict read at that day sunrise or sunset, so a clock time could only pic…
latitudenumberyesObserver latitude in decimal degrees, restricted to -60 to 60. Visibility depends on the observer, unlike the longitude orb every chart API reports, because the angle the ecliptic makes with the hori…
longitudenumberyesObserver longitude in decimal degrees. Sets local sunrise and sunset, which are the instants the verdict is read at. Example: Mumbai 72.8777, Delhi 77.2090, London -0.1278.
timezone––Timezone: IANA name (e.g. "Asia/Kolkata", "Europe/London") OR decimal hours from UTC. Fixes which local day the date refers to, and every datetime in the response is returned in it. Defaults to 5.5.
NameTypeReqDescription
datestringyes–
grahasarrayyes–
{"date":"2026-07-25","latitude":19.076,"longitude":72.8777}
post_vedic_astrology_kp_chart ~997

Generate authentic Krishnamurti Paddhati birth charts with Placidus house cusps, star-lord and sub-lord calculations. Supports custom ayanamsa and dynamic KP-Newcomb ayanamsa calculation. Returns complete chart with all 9 planets (Sun through Ketu), Ascendant, 12 Placidus house cusps, nakshatra details, star-lords, sub-lords, and KP horary numbers (1-249). Perfect for KP astrology software, horary prediction apps, and event timing analysis. One call is a complete Krishnamurti Paddhati chart generator, returning the Placidus cusps and the planets with their sub lords together. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.

NameTypeReqDescription
ayanamsastring–Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanam…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format
focusstring–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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth location latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar la…
longitudenumberyesBirth location longitude in decimal degrees
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format. CRITICAL for accurate Lagna and house calculations.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
ascendantobjectyes–
cuspsarrayyes–
focusstringyes–
houseThemesobjectyes–
metaobjectyes–
nodesobjectyes–
planetsarrayyes–
significatorsobjectyes–
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_kp_cusps ~812

Calculate unequal Placidus house cusps with ruling sign-lord, nakshatra-lord, and sub-lord for each cusp. Dynamic KP-Newcomb or custom ayanamsa support. Used in KP horary astrology, cusp sub-lord analysis, and birth chart rectification. Returns all 12 house cusps with KP sub-division details. Use it as a Placidus house cusp calculator that also carries the star lord and sub lord of each cusp, which is what Krishnamurti Paddhati horary work reads first. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.

NameTypeReqDescription
ayanamsastring–Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanam…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format
focusstring–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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth location latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar la…
longitudenumberyesBirth location longitude in decimal degrees
timestringyesBirth time in 24-hour HH:MM:SS format
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
ayanamsanumberyes–
cuspsarrayyes–
focusstringyes–
houseSystemstringyes–
houseThemesobjectyes–
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_kp_daily_finance ~1,283

A Krishnamurti Paddhati daily finance reading for one native on one date. Four KP layers are each scored against the money houses and weighed into one number: the cusp sub lords of the gain and loss houses (structural promise), the four running Vimshottari lords at the reading moment (timing), the ruling planets of that moment (the pulse), and the sub lord windows the Moon passes through across the civil day (the hour hand), with the best and worst windows named. Weights cusps 30, dasha 40, rulingPlanets 15, moonWindows 15. Every input is the shipped KP arithmetic: Placidus cusps, the 249 sub lord table, the four tier significator rule, the Vimshottari chain to the sookshma level, all in the one ayanamsa you choose. Every row prints its planet, its standing against the two sets and its score, so the number can be audited rather than trusted. The house groups, the classification, the inversion on the loss cusps, the retrograde penalty, the level weights and the layer weights are a KP practitioner convention adopted as the published convention of this route: no classical KP text weighs these four layers against each other, and every table behind the number is printed so the result can be checked line by line rather than trusted. The score measures what the method outputs for the day, never the probability of a gain or a loss. Override the two house groups to run your own school. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.

NameTypeReqDescription
ayanamsastring–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…
birthDatestringyesBirth date, YYYY-MM-DD. Fixes the Placidus cusps, the four tier significators and the Vimshottari balance every layer reads.
birthTimestringyesBirth time, HH:MM:SS, 24 hour, local to the birth place. The cusp sub lords move about one sub every four minutes of clock time, so this is the input the whole reading is most sensitive to.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestring–Civil date to read, YYYY-MM-DD in the request timezone. Defaults to today (UTC). The Moon windows cover this date from midnight to midnight.
gainHousesarray–Houses whose significators count as gain, 1 to 12. Defaults to the convention, 2 and 11. Override it to run your own school: the two lists may not share a house.
latitudenumberyesBirth latitude in decimal degrees. Sets the Placidus cusps; also the place the ruling planets and the Moon windows are read at. The latitude must lie below 66.56 degrees north or south, inside the po…
longitudenumberyesBirth longitude in decimal degrees, east positive.
lossHousesarray–Houses whose significators count as loss, 1 to 12. Defaults to the convention, 6 and 8 and 12. Override it to run your own school: the two lists may not share a house.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestring–Reading moment on that date, HH:MM:SS local. The ruling planets and the running sookshma lord are read at this instant. Defaults to 12:00:00; pass a market open or any hour for an intraday read.
timezone––Timezone as an IANA name (Asia/Kolkata) or decimal hours from UTC. Applies to the birth time, to the reading date and time, and to every local timestamp in the response. An IANA name is resolved twic…
weightsobject–Layer weights in percent, all four required, summing to 100. Defaults to the convention, cusps 30, dasha 40, rulingPlanets 15, moonWindows 15. Seventy percent of the default sits on the cusps and the…
NameTypeReqDescription
ayanamsastring––
ayanamsaDegreesnumberyes–
bandstringyes–
bestWindowobject|nullyes–
datestringyes–
housesobjectyes–
layersobjectyes–
readingAtstringyes–
scorenumberyes–
significatorsobjectyes–
worstWindowsarrayyes–
{"birthDate":"1990-06-15","birthTime":"07:30:00","latitude":28.6139,"longitude":77.209}
post_vedic_astrology_kp_horary ~1,210

Cast a Krishnamurti Paddhati horary chart, also called Prashna, from a number between 1 and 249 given by the querent plus the moment and place the question is judged. NO BIRTH DETAILS ARE NEEDED, which is what makes horary the KP answer when birth time is unknown or unreliable. The number maps to one of the 249 KP sub divisions and sets the Ascendant; the twelve Placidus cusps follow from that Ascendant at the given latitude, and every planetary position comes from the real sky at the moment of the question. Returns the Ascendant with its sub lord, all twelve cusps with star lord and sub lord, the nine grahas placed against those cusps, the five ruling planets for validating the chart, and four-level significators for judging which houses each graha supports. KP horary API, Prashna kundali calculator, 249 horary number chart, Krishnamurti Paddhati horary, cusp sub lord question answering. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.

NameTypeReqDescription
ayanamsastring–Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanam…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesDate the question was taken up for judgment, YYYY-MM-DD. Not a birth date: a horary chart needs no birth details at all, which is the point of the method.
focusstring–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…
horaryNumberintegeryesHorary number from 1 to 249, given by the querent while focused on their question. It maps to one of the 249 KP sub divisions of the zodiac, and that division sets the Ascendant of the chart. The que…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesLatitude where the question is judged, decimal degrees. The house cusps are Placidus and therefore latitude dependent, so this is the place of judgment, not the querent birthplace. The latitude must…
longitudenumberyesLongitude where the question is judged, decimal degrees.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesTime the question was taken up for judgment, 24-hour HH:MM:SS. In KP practice this is the moment the astrologer receives and understands the question, not the moment the querent first thought of it.…
timezone––Timezone: IANA name (e.g. "Asia/Kolkata") OR decimal hours from UTC. Defaults to 5.5.
NameTypeReqDescription
ascendantobjectyes–
ayanamsaDegreesnumberyes–
ayanamsaTypestringyes–
cuspsarrayyes–
focusstringyes–
horaryNumberintegeryes–
houseThemesobjectyes–
planetsarrayyes–
questionTimestringyes–
rulingPlanetsobjectyes–
significatorsobjectyes–
{"date":"2026-03-08","horaryNumber":108,"latitude":19.076,"longitude":72.8777,"time":"14:30:00"}
post_vedic_astrology_kp_planets ~667

Get planetary positions with detailed KP star-lord and sub-lord calculations for precise event timing and significator analysis. Returns all 9 planets (Sun through Ketu) with nakshatra, star-lord, sub-lord, and KP horary numbers (1-249). Essential for KP astrology software, significator analysis, and event prediction. Use it as a star lord and sub lord calculator wherever Krishnamurti Paddhati planet positions drive the reading.

NameTypeReqDescription
ayanamsastring–Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanam…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format
latitudenumberyesBirth location latitude in decimal degrees. Accepted at any latitude, polar included: planet longitudes are geocentric and the star and sub lords are divisions of longitude, so no house cusp is invol…
longitudenumberyesBirth location longitude in decimal degrees
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestringyesBirth time in 24-hour HH:MM:SS format
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
ayanamsanumberyes–
planetsarrayyes–
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_kp_planets_interval ~714

Calculate positions of all 9 planets (Sun through Saturn, Rahu, Ketu) at regular time intervals with full KP hierarchy: sign lord, star lord, sublord, and sub-sublord. Returns longitude, zodiac sign, nakshatra, sublord, sub-sublord, and KP number (1-249) for each planet at each timestamp. Ideal for tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables. Maximum range of 7 days with 15-minute to 24-hour intervals.

NameTypeReqDescription
ayanamsastring–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…
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
endDatetimestringyesEnd datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Maximum 7 days from start. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is…
intervalMinutesnumberyesTime between calculations in minutes. Range: 15 (quarter-hourly) to 1440 (daily).
latitudenumberyesObserver latitude in decimal degrees (for future Lagna calculations)
longitudenumberyesObserver longitude in decimal degrees (for future Lagna calculations)
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
startDatetimestringyesStart datetime 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––IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local t…
NameTypeReqDescription
ayanamsastringyes–
ayanamsaValuenumberyes–
endDatetimestringyes–
intervalMinutesnumberyes–
intervalsarrayyes–
startDatetimestringyes–
totalIntervalsnumberyes–
{"endDatetime":"2025-01-15T23:59:00Z","intervalMinutes":60,"latitude":28.6139,"longitude":77.209,"startDatetime":"2025-01-15T00:00:00Z"}
post_vedic_astrology_kp_rasi_changes ~643

Track when planets enter new zodiac signs (rasi) with precise ingress timestamps. Essential for Vedic astrology transit analysis, muhurta selection, and predictive horoscope readings. Returns exact times when planets cross sign boundaries (0, 30, 60 degrees etc). Use for tracking Sun sankranti dates, Moon sign changes for panchang, or outer planet transits for yearly predictions.

NameTypeReqDescription
ayanamsastring–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…
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
endDatestringyesLast day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
planetstringyesPlanet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn
startDatestringyesFirst day of the search (YYYY-MM-DD), a calendar day in `timezone`.
timezone––IANA name (e.g. "America/New_York", "Europe/London"), a fixed offset like "+05:30", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole ra…
NameTypeReqDescription
changesarrayyes–
endDatestringyes–
planetstringyes–
startDatestringyes–
totalChangesnumberyes–
{"endDate":"2025-12-31","planet":"Sun","startDate":"2025-01-01"}
post_vedic_astrology_kp_ruling_planets ~789

Calculate the 5 ruling planets at any moment using Krishnamurti Paddhati horary astrology. Returns Day Lord, Moon Sign/Star/Sub Lord, Lagna Sign/Star/Sub Lord. Optionally provide birth data (birthDate, birthTime) to include significators showing which houses each ruling planet signifies in the birth chart, which is essential for KP prediction.

NameTypeReqDescription
birthDatestring–Birth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.
birthTimestring–Birth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datetimestring–ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timez…
focusstring–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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesObserver latitude in decimal degrees. Any latitude for the ruling planets alone; with birthDate and birthTime the significators read Placidus cusps, so the latitude must lie below 66.56 degrees north…
longitudenumberyesObserver longitude in decimal degrees
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timezone––Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. An IANA name is resolved to the DST-correct offset of each moment separately: at datetime for the ruling plan…
NameTypeReqDescription
datetimestringyes–
dayLordstringyes–
focusstring––
houseThemesobject––
lagnaSignLordstringyes–
lagnaStarLordstringyes–
lagnaSubSublordstringyes–
lagnaSublordstringyes–
locationobjectyes–
moonSignLordstringyes–
moonStarLordstringyes–
moonSubSublordstringyes–
moonSublordstringyes–
rulingPlanetsarrayyes–
significatorsarray––
{"latitude":28.6139,"longitude":77.209}
post_vedic_astrology_kp_ruling_planets_interval ~1,118

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. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.

NameTypeReqDescription
ayanamsastring–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…
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
endDatetimestringyesEnd 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.
focusstring–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…
intervalMinutesintegeryesInterval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesObserver latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude…
longitudenumberyesObserver longitude in decimal degrees
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
startDatetimestringyesStart 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved onc…
NameTypeReqDescription
endDatetimestringyes–
focusstringyes–
houseThemesobjectyes–
intervalMinutesnumberyes–
intervalsarrayyes–
locationobjectyes–
startDatetimestringyes–
totalIntervalsnumberyes–
{"endDatetime":"2026-02-03T01:00:00Z","intervalMinutes":5,"latitude":17.385044,"longitude":78.486671,"startDatetime":"2026-02-03T00:00:00Z"}
post_vedic_astrology_kp_sublord_changes ~656

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 window up to 365 days.

NameTypeReqDescription
ayanamsastring–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…
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
endDatestringyesLast day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
planetstringyesPlanet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn
startDatestringyesFirst day of the search (YYYY-MM-DD), a calendar day in `timezone`.
timezone––IANA name (e.g. "America/New_York", "Europe/London"), a fixed offset like "+05:30", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole ra…
NameTypeReqDescription
changesarrayyes–
endDatestringyes–
planetstringyes–
startDatestringyes–
totalChangesnumberyes–
{"endDate":"2025-01-31","planet":"Moon","startDate":"2025-01-01"}
post_vedic_astrology_navamsa ~754

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.

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
chartobjectyes–
frameobjectyes–
vargottamaarrayyes–
vargottamaExplanationstringyes–
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_panchang_basic ~440

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.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesDate in YYYY-MM-DD format. Panchang elements (Tithi, Nakshatra, Yoga, Karana) are calculated for this date.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise/sunset times which define the Vara (weekday) and muhurta boundaries.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise/sunset-dependent panchang elements.
timestringyesTime in HH:MM:SS format (24-hour). Determines the exact Moon and Sun positions for tithi and nakshatra calculation.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
karanaobjectyes–
moonLongitudenumberyes–
nakshatraobjectyes–
sunLongitudenumberyes–
tithiobjectyes–
yogaobjectyes–
{"date":"2025-12-17","latitude":28.6139,"longitude":77.209,"time":"12:00:00"}
post_vedic_astrology_panchang_choghadiya ~500

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.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesDate 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. Calculations that read planetary positions su…
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
datestringyes–
dayChoghadiyaarrayyes–
nightChoghadiyaarrayyes–
{"date":"2026-02-03","latitude":17.385044,"longitude":78.486671}
post_vedic_astrology_panchang_detailed ~577

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.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesDate 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. Calculations that read planetary positions su…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
abhijitMuhurtaobject|nullyes–
amritKalamarrayyes–
bhadraobjectyes–
brahmaMuhurtaobjectyes–
chandrabalamobjectyes–
datestringyes–
durMuhurtaarrayyes–
godhuliMuhurtaobject|nullyes–
gulikaobjectyes–
horaobjectyes–
karanaobjectyes–
locationobjectyes–
moonSignobjectyes–
moonrisestring|nullyes–
moonsetstring|nullyes–
nakshatraobjectyes–
nishitaMuhurtaobjectyes–
panchakaobjectyes–
pratahSandhyaobject|nullyes–
rahuKaalobjectyes–
sayahnaSandhyaobject|nullyes–
sunNakshatraobjectyes–
sunSignobjectyes–
sunrisestringyes–
sunsetstringyes–
tarabalamobjectyes–
tithiobjectyes–
transitionsobjectyes–
varaobjectyes–
varjyamarrayyes–
vijayaMuhurtaobjectyes–
yamagandaobjectyes–
yogaobjectyes–
{"date":"2026-02-03","latitude":28.6139,"longitude":77.209}
post_vedic_astrology_panchang_hora ~432

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.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesDate 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. Calculations that read planetary positions su…
latitudenumberyesObserver latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.
longitudenumberyesObserver longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
datestringyes–
dayHorasarrayyes–
nightHorasarrayyes–
{"date":"2026-02-03","latitude":17.385044,"longitude":78.486671}
post_vedic_astrology_parallels ~397

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.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesDate in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects.
latitudenumberyesBirth latitude in decimal degrees, part of the birth record. Declinations are geocentric, as every published ephemeris prints them, so it does not move them.
longitudenumberyesBirth longitude in decimal degrees, part of the birth record. Declinations are geocentric, so it does not move them; the instant comes from date, time and timezone.
orbnumber–Orb in degrees for parallel/contraparallel detection. Defaults to 1.5°.
timestringyesTime in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
datetimestringyes–
parallelsarrayyes–
planetsarrayyes–
{"date":"2026-02-03","latitude":17.385044,"longitude":78.486671,"time":"12:00:00"}
post_vedic_astrology_parallels_monthly ~399

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. Omit year and month to get the month in progress, so a published parallel calendar stays current without a redeploy. Essential for advanced transit analysis and hidden aspect discovery. Monthly declination parallels API, planetary parallel ephemeris, contraparallel event calendar.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
monthinteger–Month number (1-12) for parallel analysis. Defaults to the current month (UTC).
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved onc…
yearinteger–Year for monthly parallel analysis (1551 to 2649). Defaults to the current year (UTC).
NameTypeReqDescription
eventsarrayyes–
monthnumberyes–
yearnumberyes–
{}
post_vedic_astrology_planetary_positions ~796

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. Rahu and Ketu are the mean lunar node, referred to the true equinox of date, with Ketu exactly opposite Rahu.

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…

Structured output declared, but exposes no named fields.

{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_planetary_positions_monthly ~393

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. Omit year and month to get the month in progress, so a published ephemeris page stays current without a redeploy. Essential for ephemeris generation, transit tracking, and planetary movement visualization. Monthly planetary ephemeris API, sidereal position table, daily graha gochara positions, ecliptic longitude calculator. Rahu and Ketu are the mean lunar node, referred to the true equinox of date, with Ketu exactly opposite Rahu.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
coordinateSystemstring–Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
monthinteger–Month number (1-12) for ephemeris. Defaults to the current month (UTC).
yearinteger–Year for monthly ephemeris (1551 to 2649). Defaults to the current year (UTC).
NameTypeReqDescription
daysarrayyes–
monthnumberyes–
yearnumberyes–
{}
post_vedic_astrology_shadbala ~811

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.

NameTypeReqDescription
ayanamsastring–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…
ayanamsaValuenumber–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.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth 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…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth 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.
longitudenumberyesBirth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
timestringyesBirth 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: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
balaThemesobjectyes–
frameobjectyes–
planetsarrayyes–
{"date":"1990-07-04","latitude":28.6139,"longitude":77.209,"time":"10:12:00"}
post_vedic_astrology_transit ~608

Analyze planetary transits (Gochar) over natal chart positions. Each transiting graha comes back with TWO whole-sign house numbers, because the two readings answer different questions: houseFromMoon is counted from the natal Moon sign (Janma Rashi), which is the reference classical Gochara uses, and natalHouse is counted from the Lagna. Also returns graha drishti onto the natal grahas (7th for every graha, plus Mars 4th and 8th, Jupiter 5th and 9th, Saturn 3rd and 10th), degree-based angular aspects with orbs, the Gochara Kaksha verdict, and highlighted transits from the slow-moving grahas (Jupiter, Saturn, Rahu, Ketu). Essential for timing predictions, event forecasting, and understanding current planetary influences. Transit analysis API, gochar calculator, vedic transit predictions, Chandra Lagna gochara, graha drishti.

NameTypeReqDescription
birthDatestringyesBirth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.
birthTimestringyesBirth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
coordinateSystemstring–Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
latitudenumberyesObserver latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.
longitudenumberyesObserver longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations.
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
transitDatestringyesTransit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.
transitTimestring–Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.
NameTypeReqDescription
birthDatetimestringyes–
frameobjectyes–
keyTransitsarrayyes–
natalPlanetsarrayyes–
transitDatetimestringyes–
transitingPlanetsarrayyes–
{"birthDate":"1990-07-04","birthTime":"10:12:00","latitude":17.385044,"longitude":78.486671,"transitDate":"2026-02-03"}
post_vedic_astrology_transit_monthly ~463

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. Omit year and month to get the month in progress, so a published gochar calendar stays current without a redeploy. Essential for transit prediction, monthly horoscope generation, and muhurta planning. Monthly planetary transit API, gochar calendar, rashi parivartan dates.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
coordinateSystemstring–Coordinate system for longitude output. "sidereal" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. "tropical" (Sayana) uses raw ecliptic longitude matching Western astrology. Defau…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
monthinteger–Month number (1-12) for transit analysis. Defaults to the current month (UTC).
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved onc…
yearinteger–Year for monthly transit analysis (1551 to 2649). Defaults to the current year (UTC).
NameTypeReqDescription
monthnumberyes–
startingPositionsarrayyes–
timezonenumberyes–
transitEventsarrayyes–
yearnumberyes–
{}
Install

How do I install the Vedic Astrology and Kundli MCP Server by RoxyAPI server?

Vedic Astrology and Kundli MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/vedic-astrology, 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.

remote · roxyapi.com

# add to Claude Code
claude mcp add --transport http com-roxyapi-vedic-astrology 'https://roxyapi.com/mcp/vedic-astrology'
Common questions

What is the Vedic Astrology and Kundli MCP Server by RoxyAPI server?

Vedic Astrology and Kundli MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/vedic-astrology. Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key. This page covers its hosted endpoint (https://roxyapi.com/mcp/vedic-astrology).

Is the Vedic Astrology and Kundli MCP Server by RoxyAPI server safe to use?

Vedic Astrology and Kundli MCP Server by RoxyAPI 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 Vedic Astrology and Kundli MCP Server by RoxyAPI server expose?

Vedic Astrology and Kundli MCP Server by RoxyAPI exposes 58 tools: post_vedic_astrology_birth_chart, post_vedic_astrology_navamsa, post_vedic_astrology_divisional_chart, post_vedic_astrology_compatibility, post_vedic_astrology_compatibility_dashakoot, and 53 more. Their descriptions and schemas cost roughly 42,024 tokens of context every time the server is loaded.

Does the Vedic Astrology and Kundli MCP Server by RoxyAPI server require authentication?

No. We connected to Vedic Astrology and Kundli MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vedic Astrology and Kundli MCP Server by RoxyAPI server still maintained?

Vedic Astrology and Kundli MCP Server by RoxyAPI is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.