birth_chart_compatibility

Use this when someone asks whether two people are compatible in Vedic astrology, for synastry, or to compare two birth charts ("are we compatible", "compare my chart with my partner’s", "Vedic compatibility for me and my husband"). Returns each person’s Moon, Venus and Mars signs (and rising sign with a time), how the two Moon signs sit to each other, where each person’s Sun, Moon, Mars and Venus land in the other’s houses, and the strongest links between their planets. It gives no score and no verdict, and it is not the 36-point guna milan of kundli matching: say so if asked for gunas. Needs both dates and towns of birth; times make it exact. The first person is usually the one asking.

read-only

Argument	Type	Description
person_a_birth_date*	string	The first person’s date of birth, YYYY-MM-DD.
person_a_birth_time	string	The first person’s local clock time of birth, 24-hour HH:MM, if known.
person_b_birth_date*	string	The second person’s date of birth, YYYY-MM-DD.
person_b_birth_time	string	The second person’s local clock time of birth, 24-hour HH:MM, if known.
person_a_birth_place*	string	The first person’s town or city of birth, with region or country if known.
person_b_birth_place*	string	The second person’s town or city of birth, with region or country if known.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "person_a_birth_date",
    "person_a_birth_place",
    "person_b_birth_date",
    "person_b_birth_place"
  ],
  "properties": {
    "person_a_birth_date": {
      "type": "string",
      "description": "The first person’s date of birth, YYYY-MM-DD."
    },
    "person_a_birth_time": {
      "type": "string",
      "description": "The first person’s local clock time of birth, 24-hour HH:MM, if known."
    },
    "person_b_birth_date": {
      "type": "string",
      "description": "The second person’s date of birth, YYYY-MM-DD."
    },
    "person_b_birth_time": {
      "type": "string",
      "description": "The second person’s local clock time of birth, 24-hour HH:MM, if known."
    },
    "person_a_birth_place": {
      "type": "string",
      "description": "The first person’s town or city of birth, with region or country if known."
    },
    "person_b_birth_place": {
      "type": "string",
      "description": "The second person’s town or city of birth, with region or country if known."
    }
  },
  "additionalProperties": false
}

chara_karakas

Use this when someone asks for their atmakaraka (soul planet), amatyakaraka (career planet), darakaraka (spouse or partner planet) or their seven chara karakas in Jaimini or Vedic astrology ("what is my atmakaraka", "my darakaraka", "darakaraka in navamsa", "which planet is my career planet"). Set "which" to the karaka asked about. Returns all seven karakas in order with sign, degree, nakshatra and navamsa sign, and with a birth time the house. Works from the birth date and town; without the time the answer can change during the birth day, and then each possibility comes with the hours it holds for.

read-only

Argument	Type	Description
which	string	The karaka asked about. Leave out for the atmakaraka.
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "which": {
      "enum": [
        "atmakaraka",
        "amatyakaraka",
        "darakaraka"
      ],
      "type": "string",
      "description": "The karaka asked about. Leave out for the atmakaraka."
    },
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

current_dasha

Use this when someone asks which mahadasha or antardasha they are running, their Vimshottari dasha timeline, when their next dasha begins, or when a dasha ends ("when does my Rahu dasha end", "my current dasha lord", "which dasha was I in during 2019", "when is my Venus antardasha"). Returns every mahadasha with dates, and the antardasha, pratyantar and sookshma running now. Set on_date for what was or will be running on another day; set mahadasha to list all nine antardashas of one mahadasha with dates. For what a dasha means in general, without birth details, use mahadasha_meaning. Needs birth date, time and town.

read-only

Argument	Type	Description
on_date	string	Optional: a day as YYYY-MM-DD, to see which periods were or will be running then. Leave out for today.
mahadasha	string	Optional: one mahadasha lord, to list all nine antardashas of that mahadasha with dates, past, now or ahead.
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time*	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

daily_panchang

Use this when someone asks for today’s panchang or the Hindu calendar for a place: the tithi, nakshatra, yoga, karana, Rahu kaal (rahu kalam), Yamaganda, Gulika, Abhijit muhurat, choghadiya, sunrise and sunset, or which festival or vrat falls today ("aaj ka panchang", "what is today’s tithi", "Rahu kaal today in Pune", "is today Ekadashi", "good time to start today"). Also answers for another date. Needs no birth details. Send the town if the person has said it; without one the answer is for New Delhi. Do not use for a person’s birth chart or birth star.

read-only

Argument	Type	Description
date	string	The date wanted, as YYYY-MM-DD. Leave out for today at that place.
place	string	Town or city, with region or country if known, e.g. "Pune, India" or "Austin, Texas".

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "date": {
      "type": "string",
      "description": "The date wanted, as YYYY-MM-DD. Leave out for today at that place."
    },
    "place": {
      "type": "string",
      "description": "Town or city, with region or country if known, e.g. \"Pune, India\" or \"Austin, Texas\"."
    }
  },
  "additionalProperties": false
}

divisional_chart

Use this when someone asks for their navamsa (D9) chart, read for marriage and inner strength, or their dashamsha (D10) chart, read for career ("my navamsa chart", "D9 chart", "Venus in my navamsa", "D10 career chart", "my ishta devata"). Set "chart" to d9 or d10. Returns the rising sign and every planet with its sign and house in that chart; the D9 adds the ishta and palana deities read from the karakamsha, the D10 the deity of each planet’s part. Needs birth date, time and town: the D9 rising sign moves on about every 13 minutes of birth time, the D10’s about every 12.

read-only

Argument	Type	Description
chart*	string	d9 for the navamsa, d10 for the dashamsha (career).
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time*	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place",
    "chart"
  ],
  "properties": {
    "chart": {
      "enum": [
        "d9",
        "d10"
      ],
      "type": "string",
      "description": "d9 for the navamsa, d10 for the dashamsha (career)."
    },
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

festival_and_vrat_dates

Use this when someone asks when a Hindu festival, vrat or observance falls, or what is coming up: "when is Diwali", "next Ekadashi", "Karwa Chauth date", "Pradosh vrat this month", "festivals in November", "when is Pongal in Chennai". Returns the dated list for a place, from a start date (today if left out), for up to 120 days. For a festival in a later year, set "from" to about a month before its usual season. Dates can differ from city to city, so send the town if known; without one the list is for New Delhi. Needs no birth details.

read-only

Argument	Type	Description
days	integer	How many days to list, 1 to 120. Default 45.
from	string	First day of the list, as YYYY-MM-DD. Leave out for today.
name	string	Optional: only days whose name contains this word, e.g. "Ekadashi", "Diwali", "Pradosh".
place	string	Town or city, with region or country if known, e.g. "Pune, India" or "Austin, Texas".

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 120,
      "minimum": 1,
      "description": "How many days to list, 1 to 120. Default 45."
    },
    "from": {
      "type": "string",
      "description": "First day of the list, as YYYY-MM-DD. Leave out for today."
    },
    "name": {
      "type": "string",
      "description": "Optional: only days whose name contains this word, e.g. \"Ekadashi\", \"Diwali\", \"Pradosh\"."
    },
    "place": {
      "type": "string",
      "description": "Town or city, with region or country if known, e.g. \"Pune, India\" or \"Austin, Texas\"."
    }
  },
  "additionalProperties": false
}

indu_lagna_money_sign

Use this when someone asks for their Indu Lagna, their money or wealth sign, or which planet is key for money in their Vedic chart ("indu lagna calculator", "my wealth sign in astrology", "which planet brings me money"). Returns the money sign and its house, how it is counted (the 9th lords and their kalas), the planets in it and aspecting it, the money point’s nakshatra and the key planet for money. It is a Jaimini method used widely by astrologers today, not in the classical texts our readings are checked against: call it a method. Never promise wealth or a sum. Needs birth date, time and town.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time*	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

mahadasha_meaning

Use this when someone asks what a mahadasha or antardasha means in Vedic astrology in general, or how long one lasts, without asking for their own dates: "what does Rahu mahadasha mean", "Saturn mahadasha effects", "Jupiter mahadasha Venus antardasha", "how long is Ketu dasha". Returns the length of the period, what the planet stands for, what its years tend to bring in daily life, when they tend to work and when they strain, every antardasha in order with its length, and for an antardasha asked about, its note. For the person’s own dates use current_dasha. Read a period by where the planet sits in the chart, never as good or bad in itself; no fear.

read-only

Argument	Type	Description
planet*	string	The mahadasha lord.
antardasha	string	Optional: the antardasha lord inside it.

Input schema (JSON)

{
  "type": "object",
  "required": [
    "planet"
  ],
  "properties": {
    "planet": {
      "enum": [
        "sun",
        "moon",
        "mars",
        "mercury",
        "jupiter",
        "venus",
        "saturn",
        "rahu",
        "ketu"
      ],
      "type": "string",
      "description": "The mahadasha lord."
    },
    "antardasha": {
      "enum": [
        "sun",
        "moon",
        "mars",
        "mercury",
        "jupiter",
        "venus",
        "saturn",
        "rahu",
        "ketu"
      ],
      "type": "string",
      "description": "Optional: the antardasha lord inside it."
    }
  },
  "additionalProperties": false
}

manglik_check

Use this when someone asks if they are Manglik or have Mangal dosha. Returns where Mars falls counted from the rising sign, the Moon and Venus, and which of those counts show it. Present it honestly: about half of all charts count as Manglik by the common rule, so it is common, not a danger. Works from the birth date and town; the birth time adds the main count, from the rising sign.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

mercury_retrograde

Use this when someone asks whether Mercury is retrograde now, when the next Mercury retrograde starts or ends, or for the Mercury retrograde dates of a year ("is Mercury in retrograde", "when does Mercury retrograde end", "Mercury retrograde 2027 dates"). Returns the period running now or the next one, with its shadow dates and signs, and the ones after it. Needs no birth details and no place. Say it without fear: it is a stretch of the calendar, not a warning.

read-only

Argument	Type	Description
year	integer	Optional: list every Mercury retrograde of this year.

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2031,
      "minimum": 2024,
      "description": "Optional: list every Mercury retrograde of this year."
    }
  },
  "additionalProperties": false
}

moon_sign_nakshatra

Use this when someone asks for their Moon sign (rashi), birth star or nakshatra and pada in Vedic astrology. Also use for "birth star", "janma nakshatra", "what is my rashi", "my zodiac sign in Vedic astrology". Works from the birth date and town; the time makes it exact when the Moon changes sign that day. Do not use for Western sun signs, horoscopes or the rising sign.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

moon_today

Use this when someone asks where the Moon is right now, today or on another date: its sign (Vedic and Western), its nakshatra, its phase, or when the next full moon or new moon comes ("what sign is the Moon in today", "moon phase today", "next full moon", "today’s nakshatra", "what sign is the Moon in on 3 November"). Needs no birth details. Send the town to get the times as local clock times there; without one they are in UTC. Do not use for a person’s own Moon sign at birth: use moon_sign_nakshatra for that.

read-only

Argument	Type	Description
date	string	Optional: a date as YYYY-MM-DD, for the Moon at midday that day. Leave out for right now.
place	string	Optional: the town, so the times come as local clock times there.

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "date": {
      "type": "string",
      "description": "Optional: a date as YYYY-MM-DD, for the Moon at midday that day. Leave out for right now."
    },
    "place": {
      "type": "string",
      "description": "Optional: the town, so the times come as local clock times there."
    }
  },
  "additionalProperties": false
}

planet_in_house_meaning

Use this when someone asks what a planet in a house means in Vedic astrology, e.g. "Venus in the 8th house", "Saturn in 12th house meaning", "Sun in my 12th house". Use this instead of vedic_birth_chart when the person names a planet and a house, even in the first person ("my Venus is in my 8th"); do not ask for birth details. Returns what the house holds, what the planet brings, our line for that planet in that house, how each tends to show in daily life, when it tends to work and when it strains, and our article when one exists. None of these tools cover daily horoscopes, gemstones, tarot or predictions.

read-only

Argument	Type	Description
house*	integer	House number, 1 to 12.
planet*	string

Input schema (JSON)

{
  "type": "object",
  "required": [
    "planet",
    "house"
  ],
  "properties": {
    "house": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "House number, 1 to 12."
    },
    "planet": {
      "enum": [
        "sun",
        "moon",
        "mars",
        "mercury",
        "jupiter",
        "venus",
        "saturn",
        "rahu",
        "ketu"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}

planetary_hours

Use this when someone asks for the planetary hours or hora of a day and place, which planet rules the hour now, or when a planet’s hour comes ("planetary hours today in London", "what planetary hour is it", "when is the Venus hour today", "hora today"). Returns the twelve day hours and twelve night hours counted from sunrise, with clock times for that place, and the hour running now. Needs the town: ask if the person has not said it. Needs no birth details.

read-only

Argument	Type	Description
date	string	The date wanted, as YYYY-MM-DD. Leave out for today at that place.
place*	string	Town or city, with region or country if known, e.g. "Pune, India" or "Austin, Texas".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "place"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "The date wanted, as YYYY-MM-DD. Leave out for today at that place."
    },
    "place": {
      "type": "string",
      "description": "Town or city, with region or country if known, e.g. \"Pune, India\" or \"Austin, Texas\"."
    }
  },
  "additionalProperties": false
}

raj_yoga

Use this when someone asks whether they have raj yoga (raja yoga) or another yoga in their kundli or birth chart, how strong a yoga is, or when it will activate ("do I have raj yoga", "raj yoga calculator", "Gaja Kesari yoga in my chart", "vipreet raj yoga", "neecha bhanga raja yoga", "Malavya yoga", "when will my raj yoga give results"). Returns each classical yoga the chart holds: raja yogas from the lords of the angles and trines, Maha Raja yoga, the yogakaraka, Gaja Kesari, the five Mahapurusha yogas (Ruchaka, Bhadra, Hamsa, Malavya, Sasa), Lakshmi, Neecha Bhanga and Vipreet (Harsha, Sarala, Vimala), plus Budhaditya marked as a modern yoga. For each: how it forms in this chart, its strength on the classical scale (full, half or a quarter, from each planet’s shadbala against the strength the classical texts ask), whether its planets’ period is running now or the next dated window, and how common it is in our sample of 20,000 charts. Needs birth date, time and town.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time*	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

sade_sati_check

Use this when someone asks whether they are in Sade Sati, when their Sade Sati starts or ends, or about Saturn’s seven and a half years. Also use for Shani sade sati and "Saturn’s 7.5 years". Returns whether it is running now, its three phases with dates, and the next one. Needs birth date and town.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

saturn_return_dates

Use this when someone asks when their Saturn return is (in Vedic, sidereal reckoning), whether they are in it now, or at what ages it comes. Also use for "Saturn return at 28/29" and Shani return. Returns every Saturn return with dates and ages. Needs birth date and town; ask if missing.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

vedic_and_western_signs

Use this when someone asks what their sign is in Vedic (sidereal) astrology compared with Western (tropical) astrology, why their sign is different in Vedic astrology, or for their "real" or sidereal zodiac sign ("I am a Leo, what am I in Vedic astrology", "my sidereal sun sign", "why does my Vedic chart show different signs"). Returns the Sun, the Moon and every planet counted both ways, the gap between the two zodiacs (the ayanamsa), and with a birth time the rising sign both ways. Works from the birth date and town.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

vedic_birth_chart

Use this when someone asks for their Vedic birth chart, kundli, janam kundali, sidereal chart, or where their planets are in Vedic astrology (signs, houses, nakshatras, rising sign). Returns all nine planets with sign, degree, house (needs birth time), nakshatra and pada, and each one’s navamsa (D9) sign. If the person asks for only one thing (rising sign, Moon sign, dasha, Manglik), use the narrower tool. Needs birth date and town, and the time for houses; ask if missing. Do not use for Western/tropical charts or daily horoscopes.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

vedic_rising_sign

Use this when someone asks for their rising sign, ascendant or lagna in Vedic astrology, or why their Vedic rising sign differs from a Western app. Returns the Vedic rising sign, its ruler, and the Western rising sign for comparison. Needs the birth time.

read-only

Argument	Type	Description
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time*	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

{
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}

vehicle_purchase_dates

Use this when someone asks for a good day or muhurat to buy a car, bike or other vehicle from their birth details ("vehicle purchase muhurat", "best day to buy a car as per my chart", "car muhurat next month"). Returns the next 60 days, each with its weekday, nakshatra and tithi and how it counts from the person’s birth star (tarabala) and birth Moon (chandrabala), each marked favoured or not by the common muhurta custom, and the planet their chart links to vehicles. The day rules are a custom, not in the classical texts our readings are checked against: say so. Needs birth date and town; town_now sets the time zone of the days.

read-only

Argument	Type	Description
from	string	Optional: the first of the 60 days, as YYYY-MM-DD. Leave out for today.
town_now	string	Optional: where they live now, for the time zone of the days. Leave out to use the town of birth.
birth_date*	string	Date of birth, YYYY-MM-DD, e.g. 1993-03-17.
birth_time	string	Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate).
birth_place*	string	Town or city of birth, with region or country if known, e.g. "Chicago, Illinois, US" or "Pune, India".

Input schema (JSON)

venus_retrograde

Use this when someone asks whether Venus is retrograde now, when Venus retrograde starts or ends, or for the Venus retrograde dates of a year ("is Venus retrograde", "Venus retrograde 2026", "when does Venus go direct", "Venus retrograde in Libra"). Returns the period running now or the next one, with its shadow dates, its signs in both zodiacs, the day Venus meets the Sun, and the ones after it. Venus turns retrograde about every 19 months, for about six weeks. Needs no birth details and no place. Say it without fear: it is a stretch of the calendar, not a warning.

read-only

Argument	Type	Description
year	integer	Optional: list every Venus retrograde touching this year.

Input schema (JSON)

{
  "type": "object",
  "required": [],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2039,
      "minimum": 2020,
      "description": "Optional: list every Venus retrograde touching this year."
    }
  },
  "additionalProperties": false
}

Cosmic Chemistry

Try it

birth_chart_compatibility Read-only

Cosmic Chemistry

Try it

birth_chart_compatibility Read-only

Tools (22)