Asterwise

Computes the full sidereal natal chart from BirthData and returns planet rows, houses, aspects, arudhas, upapada, bhava cusps, and avakhada metadata. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: RECOMMENDED — asterwise_get_yogas — layer classical combinations after the base chart exists. INPUT CONTRACT: BirthData enforces date YYYY-MM-DD, time HH:MM, lat -90..90, lon -180..180,

Computes divisional (varga) charts from BirthData; pass chart_type for one varga, or omit chart_type for all sixteen. Each planet in each varga comes with its dignity there and whether it is vargottama; with a known birth time, each chart also has its own lagna, every planet's whole-sign house from that lagna, and a houses table. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — anc

Aggregates the chart's strength measures from BirthData: Shadbala, Bhavbala and Vimshopaka (with per-varga contributions). Also returns the sixteen vargas, Ashtakavarga, karaka maps and graha yuddha pairs. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises houses before reading bala tables. AFTER: asterwise_get_yogas — optional configuration pass after strength revie

Calls atmakaraka and ishta-devata endpoints sequentially and merges their payloads into top-level atmakaraka and ishta_devata objects for one BirthData. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — understand chart basics before devotional pointers. AFTER: None. INPUT CONTRACT: Wrapper returns { atmakaraka: <upstream dict>, ishta_devata: <upstream dict> } — not a flat data.*

Looks up static metadata for one of twenty-seven nakshatras by name and returns interpretive, professional, activity, and body-map reference data. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: None. INPUT CONTRACT: nakshatra_name is sent as given; the API ignores case, spaces, hyphens and common romanisation differences ('uttarashadha', 'Aswini', 'Moola' and 'Krithika' all match). A

Evaluates Saturn's seven-and-a-half-year Sade Sati cycle against the natal Moon sign for the current day. Returns intensity, upcoming cycles, and historical rows. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm Moon sign context. AFTER: asterwise_get_gochar — broader transit canvas if needed. INPUT CONTRACT: No explicit query date — API pins to current day. BirthData

Casts a Prashna chart for the query instant from the supplied date, time, place and a single-topic keyword. Returns houses, Moon diagnostics, a verdict, and cusps. WORKFLOW: BEFORE: None — standalone for horary. AFTER: None. INPUT CONTRACT: question must be exactly one of: self, wealth, siblings, property, children, health, marriage, death, travel, career, gains, loss. Full sentences are not v

Produces a Lal Kitab chart from BirthData following the 1952 Lal Kitab: houses counted from the Vedic lagna, the lagna house read as house 1 (Aries). Returns planets with pakka ghar, uchcha/neecha, fixed or doubtful effect and malefic reasons, the twelve houses, and the nine Lal Kitab debts (rin). WORKFLOW: BEFORE: None — standalone for Lal Kitab queries. AFTER: asterwise_get_lal_kitab_remedies

Lists Lal Kitab remedies (from the 1952 Lal Kitab) for the planets that need them, plus remedies for any indicated debts (rin). WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_lal_kitab_chart — see the chart and malefic reasons first. AFTER: None. INPUT CONTRACT: BirthData only. ayanamsa: lahiri (default), raman or kp is used as sent; tropical is refused (INVALID_PARAMS) because Lal Kitab star

Builds a KP natal chart with sub-lords on grahas and twelve cusps from BirthData using the KP ayanamsa in the response. WORKFLOW: BEFORE: RECOMMENDED — cross-check birth record before trusting sub-lords. AFTER: asterwise_get_kp_significators — house-level significator chains. INPUT CONTRACT: ayanamsa is accepted but ignored (always KP). Birth time is required: this tool has no sunrise fallba

Computes KP significator chains for all houses or one optional house from BirthData and returns house tables plus planet-tier reverse indexes. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_kp_chart — establish cusps before significators. AFTER: None. INPUT CONTRACT: house_number optional int 1..12; omit for all twelve. DO NOT CONFUSE WITH: asterwise_get_kp_chart — cusps and sub-lords, not

Computes KP ruling planets at a latitude and longitude for the current instant or a given local date and time, with no birth data. Returns the day lord, Moon and Ascendant lord chains, and a deduplicated ruling_planets list. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_kp_chart — if natal confirmation is needed afterwards. INPUT CONTRACT: lat and lon required. Optio

Computes full Ashtakavarga bindu matrices, trikona and ekadhipatya reductions, and sarva totals from BirthData for transit support analysis. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before AVK study. AFTER: asterwise_get_gochar — uses AVK scores in transit rows. INPUT CONTRACT: BirthData only. DO NOT CONFUSE WITH: asterwise_get_chart_strength — primary p

Computes the annual Tajika-style solar return for a four-digit civil year and returns Muntha, Pancha Adhikari metrics, Tajika aspects, and varshaphal positions. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — baseline radix before annual overlay. AFTER: None. INPUT CONTRACT: year is a plain int sent as target_year upstream; callers must supply the true Gregorian return year, not

Computes all 10 Tajika Saham (sensitive points) for a Varshaphal solar return chart. Sahams are the Tajika equivalent of Arabic Parts — mathematically derived zodiac points that focus the annual horoscope on specific life themes. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_varshaphal — understand the base solar return chart (Varsha Pati, Muntha, Varsha Ascendant) before interpreting Saham

Computes Harsha Bala (positional happiness score) for all 7 classical planets in a Varshaphal solar return chart. Maximum 20 per planet (4 components × 5 points each). WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_varshaphal — identify the Year Lord (Varsha Pati) before interpreting Harsha Bala. The Year Lord's Harsha Bala is the most actionable number in this response. AFTER: asterwise_get_

Computes Vimshottari Dasha from birth data and returns hierarchical period trees plus current Maha/Antar interpretation blocks. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes chart and Moon context before interpreting Dasha lords. AFTER: asterwise_get_dasha_transits — correlates active Dasha lords with transits for the same birth data. INPUT CONTRACT: levels (int,

Combines active Vimshottari lords with transits on one date and returns scored correlations plus transit longitudes and houses from Moon and Lagna. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — same birth data should be understood before interpreting houses and lords. AFTER: asterwise_get_gochar — optional broader transit snapshot without dasha scoring. INPUT CONTRACT: target

Computes Char Dasha from birth data and returns sign lords as period rulers with ISO-dated Maha and Antar sequences plus karaka mappings. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — contextualises the chart before interpreting sign-based lords. AFTER: asterwise_get_dasha — optional Vimshottari cross-check for the same native. INPUT CONTRACT: cycles (optional int 1–3, defa

Computes the eight-Yogini, 36-year Yogini Dasha cycle with two-level period trees and DD/MM/YYYY boundaries from birth data. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes birth context for interpreting Yogini lords. AFTER: asterwise_get_dasha — optional Vimshottari comparison for the same native. INPUT CONTRACT: Tree lives at data.periods.root[] — agents must no

Computes the Ashtottari Dasha tree (108-year cycle) with configurable depth, levels 1–5. The timeline continues into the next cycle until it reaches at least age 120 (usually 9–11 mahadashas); periods are under data.periods.root with DD/MM/YYYY dates. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart context before choosing between Ashtottari and Vimshottari. AFTER: asterw

Scores North Indian Ashtakoota (36-point Guna Milan) for two charts. Returns the koota breakdown, dosha flags, classical vetoes, a Mangal cross-check and narrative guidance. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per person — understand charts before interpreting scores. AFTER: asterwise_get_papasamyam — optional malefic balance overlay. INPUT CONTRACT: Two BirthData obj

Computes the ten-koota Dashakoot grid for two charts and converts it to a ten-point score with percentage. Also returns boolean dosha flags and supplementary diagnostics. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart for each native — context before regional scoring. AFTER: asterwise_get_papasamyam — optional malefic differential. INPUT CONTRACT: Two BirthData objects per globa

Measures malefic stress from Lagna, Moon, and Venus references for each partner, compares totals, and labels compatibility level against a threshold. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_compatibility — establish baseline match quality. AFTER: None. INPUT CONTRACT: Two BirthData objects per global contract. DO NOT CONFUSE WITH: asterwise_get_doshas — twelve natal dosha buckets fo

Runs the Kerala ten-porutham checklist for two charts and counts passes out of ten. Also returns Rajju and Vedha condition booleans and per-porutham evidence objects. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart per native. AFTER: asterwise_get_thirumana_porutham — extended twelve-koota read if needed. INPUT CONTRACT: Two BirthData objects per global contract. DO NOT CONFUSE WI

Evaluates twelve Tamil Thirumana poruthams for two charts, tracks veto severity for Rajju, and returns an expanded breakdown map with tradition metadata. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_porutham — quick ten-koota pass before twelve-koota depth. AFTER: None. INPUT CONTRACT: Two BirthData objects per global contract. DO NOT CONFUSE WITH: asterwise_get_porutham — ten poruthams

Panchanga for one date at a location: the limbs at sunrise plus every tithi, nakshatra, yoga and karana of the panchanga day (sunrise to next sunrise). Each comes with ISO start and end times and kshaya/vriddhi flags. Also returns sunrise, sunset, moonrise and moonset; Sun and Moon rashi; lunar month (amanta and purnimanta, with Adhik months); Vikram, Shaka and Gujarati samvat; ritu and ayana; and

Splits a solar day into sixteen Choghadiya segments from sunrise/sunset at a location and labels each slot's quality, ruler, and local clock bounds. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_rahu_kaal — optional inauspicious band overlay for the same date. INPUT CONTRACT: LocationInput enforces YYYY-MM-DD date and lat/lon ranges locally. All parameters are define

Builds the twenty-four planetary Horas between successive sunrises for a location date and tags each hour with ruler, quality text, and whether it is current. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_choghadiya — alternative same-day slot system. INPUT CONTRACT: LocationInput date/coordinate rules apply locally (YYYY-MM-DD, bounded lat/lon). DO NOT CONFUSE WITH

Computes Rahu Kaal, Gulika Kaal, and Yamaganda Kaal intervals from diurnal length at a location and marks whether Rahu Kaal is active now in local time. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_choghadiya — broader auspicious/inauspicious grid for the day. INPUT CONTRACT: LocationInput validates date pattern and coordinates locally. DO NOT CONFUSE WITH: asterwi

Finds auspicious time windows for an activity between two dates (up to a year) at a location, with exact ISO start and end times. Activities: marriage, griha_pravesh, business, travel, naming_ceremony, vehicle_purchase, property_purchase, mundan, annaprashan, upanayana, vidyarambha. Applies each activity's nakshatra, tithi and weekday rules, seasonal bans (Chaturmas, Adhik Maas, Pitru Paksha, Khar

Panchanga for every day of a month at a location, one entry per day. Each day has its sunrise tithi, vara, nakshatra, yoga, karana and Rahu Kaal, plus sunrise, sunset, moonrise, moonset, paksha, lunar month (amanta and purnimanta, with Adhik months), Bhadra windows, and every tithi, nakshatra, yoga and karana active that day with ISO start and end times. WORKFLOW: BEFORE: asterwise_geocode — wh

Tamil Panchanga for a date and location: Rahu Kalam, Yamagandam, Kuligai (Gulika), Nalla Neram and the Tamil solar month. Nalla Neram is the daytime windows free of those periods; the month comes from the Sun's sidereal sign at sunrise. WORKFLOW: BEFORE: asterwise_geocode — when you only have a place name. AFTER: asterwise_get_panchanga — the day's limbs and other timings. INPUT CONTRACT: da

Hindu festivals, vrats, sankrantis, eclipses and periods for a year at a location. Each lunar festival is fixed by its lunar month (amanta, with Adhik months found from new moons and sankrantis), its tithi, and the part of the day the tithi must hold (sunrise, forenoon, Madhyahna, Aparahna, Pradosh, Nishita, moonrise), with the classical tie-breaks when a tithi spans two days, Bhadra rules for Hol

Turns a place name into latitude, longitude and IANA timezone for the other tools, which all take lat, lon and timezone. WORKFLOW: BEFORE: None. AFTER: any tool that takes lat, lon and timezone — asterwise_get_natal_chart, asterwise_get_panchanga, asterwise_get_muhurta, asterwise_get_festival_calendar and others. INPUT CONTRACT: query: place name, at least 2 characters (required). limit: 1-10

Returns classical graha (planet) properties for all nine planets or a single planet per classical Vedic tradition. WORKFLOW: BEFORE: None — standalone reference. AFTER: asterwise_get_puja_suggestions — propitiation for a specific graha. INPUT CONTRACT: planet (optional): One of Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Omit to get all nine planets. DO NOT CONFUSE WITH: a

Returns puja (ritual worship) recommendations for planetary propitiation per graha. WORKFLOW: BEFORE: asterwise_get_natal_chart — identify afflicted planets before recommending pujas. AFTER: asterwise_get_rudraksha — complementary bead-based remedy. INPUT CONTRACT: planet (optional): One of Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Omit to get all nine planets. DO NOT CO

Returns Rudraksha bead recommendations per planet. WORKFLOW: BEFORE: asterwise_get_natal_chart — identify planets needing support. AFTER: None. INPUT CONTRACT: planet (optional): One of Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu, Ketu. Omit to get all nine planets. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — Ratna-style gemstones from natal chart. asterwise_get

Returns ayanamsha values for all four supported systems (Lahiri, Raman, KP, Tropical) for a given date. WORKFLOW: BEFORE: None — standalone reference. AFTER: None. INPUT CONTRACT: date (optional): Date in YYYY-MM-DD format. Defaults to today. DO NOT CONFUSE WITH: asterwise_get_natal_chart — applies Lahiri ayanamsha automatically to natal positions. asterwise_get_western_natal — uses tropi

Computes physical (23-day), emotional (28-day), and intellectual (33-day) biorhythm cycles for a birth date. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_nakshatra_prediction — for the Vedic personalized daily prediction. INPUT CONTRACT: birth_date (required): Date of birth in YYYY-MM-DD format. target_date (optional): Date to compute for. Defaults to today. days (optional int 1

Personal daily prediction from Tarabala and Chandrabala for the day at the birth place (sunrise to next sunrise). WORKFLOW: BEFORE: None — birth data computes everything needed. AFTER: asterwise_get_panchanga — the day's full panchanga; asterwise_get_muhurta — Tarabala-aware windows for an activity. INPUT CONTRACT: birth: BirthData (date, time, lat, lon, timezone). Unknown birth time: omit

Detects and analyses Pitru Dosha (Pitru Shapa — Ancestral Curse) using all five classical Pitru Dosha combinations. WORKFLOW: BEFORE: None — birth data computes everything needed. AFTER: asterwise_get_puja_suggestions — recommend remedial pujas for Sun/Mars. INPUT CONTRACT: birth — BirthData (date, time, lat, lon, timezone). DO NOT CONFUSE WITH: asterwise_get_doshas — returns pitru_do

Returns the four Ghatak (inauspicious) timing parameters for a native based on their Janma Rasi (natal Moon sign). WORKFLOW: BEFORE: None — birth data computes everything needed. AFTER: asterwise_get_nakshatra_prediction — for today's personalized daily auspiciousness score. INPUT CONTRACT: birth — BirthData (date, time, lat, lon, timezone). Moon sign is computed from birth data. DO NOT C

Evaluates the natal chart for named classical yogas. Each hit returns its category, formation text, the classical texts it is drawn from (classical_sources), a modern summary, and keywords. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — same birth tuple should be understood before interpreting yoga names. AFTER: asterwise_get_doshas — complementary affliction scan on the same c

Scores twelve fixed dosha buckets from birth data and returns presence flags, typed detail objects, optional summaries, and remedy lines per dosha. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart familiarity before dosha interpretation. AFTER: asterwise_get_remedies — classical remedial suggestions after dosha review. INPUT CONTRACT: BirthData follows the global contract.

Derives classical remedial prescriptions from planetary weakness, dusthana lordship or placement, and combustion. Returns mantra, lifestyle, charity, and dignity tables. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — chart context before choosing remedies. AFTER: asterwise_get_gemstone_recommendations — optional focused gem briefing. INPUT CONTRACT: BirthData follows the globa

Computes Ratna-style gemstone picks and cautions from the natal chart. Returns the primary and role-based stones, secondary options, contraindications and a safety note. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — confirm chart before wearing advice. AFTER: asterwise_get_remedies — broader remedial programme if needed. INPUT CONTRACT: BirthData follows the global contract.

Builds a Pythagorean numerology profile from a legal name and birth date and returns core numbers, cycles, lucky digits, and summary copy. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_personal_year — fills Personal Year when needed. INPUT CONTRACT: name and date strings are forwarded without extra local validation; malformed payloads fail upstream. DO NOT CONFUSE W

Compares two people on their Pythagorean Life Path numbers, worked out from their birth dates. Returns a score, tier label, narrative, strengths, challenges, and advice. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile per person — sanity-check Life Paths before comparing. AFTER: None. INPUT CONTRACT: Four strings (two names, two dates) are passed through without local guards

Reduces a name and birth date through the Chaldean letter-value system and returns name, birth, and combined compound analyses with themes and keywords. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — compare against Pythagorean cores if needed. INPUT CONTRACT: name and date forwarded as-is; no local validation. DO NOT CONFUSE WITH: asterwise_get_numerology_pr

Derives a Lo Shu three-by-three frequency grid from birth-date digits and annotates planes, missing or repeated digits, and per-digit traits. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: date string only; validated upstream. DO NOT CONFUSE WITH: asterwise_get_numerology_profile — letter-based Western numbers, not digit-frequency Lo Shu. asterwise_get_name_correction —

Scores the current spelling of a personal name against the birth-date Life Path and suggests alternate spellings with harmony metrics. Names the best alternative when one scores higher. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — baseline numbers before renaming advice. AFTER: None. INPUT CONTRACT: name and date strings only; upstream validates. DO NOT CONFUSE WITH: a

Fetches condensed lucky-number guidance for a name and birth date including primary and secondary picks, power number, interpretation, and a date_specific flag. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — if deeper context is required. INPUT CONTRACT: name and date forwarded upstream without local checks. DO NOT CONFUSE WITH: asterwise_get_numerology_profi

Looks up the Personal Year theme for the current calendar year from a birth date (its month and day). WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — see other core numbers first. AFTER: None. INPUT CONTRACT: Only the birth date is sent; name is optional and not used. The active calendar year is chosen upstream automatically. DO NOT CONFUSE WITH: asterwise_get_numerology_

Returns dictionary-style numerology copy for a single integer, including interpretation, keywords, and stubbed extended fields. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: number must pass local guard: one of 1-9, 11, 22 or 33; any other value raises MCP INVALID_PARAMS before the HTTP call. DO NOT CONFUSE WITH: asterwise_get_numerology_profile — computes personal numbe

Sums the digits of the national number (country code left out), reduces them to a single number, and returns harmonic scoring plus interpretive copy. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — anchor Life Path before judging the line. AFTER: None. INPUT CONTRACT: Only digits count; the country calling code is never counted. Numbers written with '+' or '00' use the nat

Strips non-digits from a vehicle registration token, reduces the numeric run to a single number, and returns the same harmony schema as mobile analysis. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — owner baseline. AFTER: None. INPUT CONTRACT: Letters and separators are ignored; reduction uses numeric digits only. Owner name and birth date are optional and not used. DO

Reduces a business name to Expression and root digits and returns thematic suitability lists plus a harmony score. Uses the name only; no founder birth date is involved. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_name_correction — if the entity is a person, not a brand. INPUT CONTRACT: business_name (required): special characters and digits are acceptable; reduction strips non

Calculates the Expression (Destiny) number from the full name using Pythagorean letter values. Reduces each name part separately before summing (Decoz per-part method), keeping master numbers 11, 22, 33 at every step. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_soul_urge_number — complete the core trinity (Expression, Soul Urge, Personality). INPUT CONTRACT: name â

Calculates the Soul Urge (Heart's Desire) number from vowels in the full name. Only A, E, I, O, U are treated as vowels — Y is always a consonant in this system. Reduces each name part separately before summing, preserving master numbers 11, 22, 33. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_personality_number — complete the name number trinity. INPUT CONTRACT: name — Full

Calculates the Personality number from consonants in the full name. All non-vowels (BCDFGHJKLMNPQRSTVWXYZ) contribute — Y is always a consonant. Reduces each name part separately, preserving master numbers 11, 22, 33. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — see all five core numbers together. INPUT CONTRACT: name — Full legal name as used at birth.

Calculates the Maturity number as the sum of Life Path and Expression numbers, reduced to a single digit or master number. Represents the underlying wish or true desire that becomes conscious around age 35 and fully emerges by midlife. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — confirm Life Path and Expression before interpreting their sum. AFTER: None. INPUT CONTRACT

Calculates the Balance number from the first letter of each name part, using Pythagorean values. A three-part name yields three initials summed and reduced. The Balance number describes how a person handles emotional crises and unresolved inner conflict. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: name — Full legal name as used at birth. The first letter of each space-s

Identifies karmic lessons by scanning all letter values in the full name and finding which digits 1–9 are absent. Each missing digit represents an area where experience is thin and development is needed in this lifetime. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — see karmic lessons alongside all core numbers. INPUT CONTRACT: name — Full legal name as u

Returns the Personal Year, Personal Month, and Personal Day numbers for a given birth date and optional target date. All three cycle numbers are derived from the birth month, birth day, and the target calendar date. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_numerology_profile — see personal cycles alongside core numbers. INPUT CONTRACT: date — Birth date in YYYY-MM-DD forma

Returns the angel number for today (UTC, or the caller's timezone) or for a given date. All digits of the date are summed and reduced to a single digit (1-9), then the triple sequence of that digit is returned (e.g. digit 9 → angel number 999). WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_angel_number_personal — for a personalised angel number from birth date. INPUT CONTRACT:

Lookup the meaning of a specific angel number by its sequence. Supported: 000, 111–999 (single repeating digit), 911, 1010, 1111, 1122, 1212, 1234, 2222–9999 (double repeating digit). WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: number: string — the angel number sequence to look up. Examples: '111', '444', '1111', '911'. DO NOT CONFUSE WITH: asterwise_get_angel_numb

Computes a personal angel number from a birth date using the Pythagorean Life Path as the base. Life Path 1-9 maps to the triple sequence (LP 4 → 444). Master numbers 11, 22, 33 map to 1111, 2222, 3333 respectively. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — confirm Life Path before calling. AFTER: None. INPUT CONTRACT: date: Birth date in YYYY-MM-DD format. Example

Returns all 54 crystals in the database sorted alphabetically. Each entry includes chakra associations, elemental correspondences, Vedic and Western planetary assignments, physical/emotional/spiritual healing properties, geographic origins, affirmations, and safety cautions. WORKFLOW: BEFORE: None — standalone catalogue. AFTER: asterwise_get_crystal_by_planet — filter by Vedic planet for reme

Lookup a specific crystal by slug or name (case-insensitive). Returns full detail including dual Vedic/Western planetary assignments, all healing properties, and any safety cautions. WORKFLOW: BEFORE: None — standalone or after asterwise_get_gemstone_recommendations. AFTER: None. INPUT CONTRACT: name: Crystal slug or display name. Examples: 'amethyst', 'blue-sapphire', 'Cat's Eye Chrysoberyl'

Returns all crystals associated with a specific Vedic planet. Results are sorted with primary Navaratna gems first, then Uparatna substitutes. Only Navaratna and Uparatna Vedic assignments are returned — crystals with no Vedic planetary correspondence are excluded. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — identify the planet needing remediation. AFTER: asterwise_get_gemst

Recommends crystals based on zodiac sign, chakra, or intention keyword. At least one filter is required. Returns crystals that match the most criteria first. WORKFLOW: BEFORE: None — standalone for consumer apps. AFTER: asterwise_get_crystal — get full detail on any recommended crystal. INPUT CONTRACT: At least one of: zodiac_sign, chakra, intention must be provided. zodiac_sign (optional):

Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, or

Returns dream symbols from the database with dual-tradition interpretation: Jungian/Western psychological analysis and traditional Vedic dream-symbol meaning. 500 symbols across 8 categories. Optionally filter by category. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_dream_symbol — get full detail for a specific symbol. INPUT CONTRACT: category (optional): One of animals, nature

Lookup a specific dream symbol by slug or name (case-insensitive). Returns full dual-tradition interpretation including Jungian archetype, Vedic dream meaning with auspiciousness, context variants, and related symbols. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: name: Symbol slug or display name. Examples: 'snake', 'eagle', 'childhood-home', 'lotus', 'black-dog' DO NOT C

Fetches an AI-synthesised Moon-sign horoscope for a chosen horizon and returns structured guidance fields plus metadata about the model and period. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_natal_chart — if the user needs a personalised chart beyond sign-general copy. INPUT CONTRACT: period is constrained to the tool schema enum (daily, weekly, monthly, yearly).

Fetches an AI-synthesised Western sun-sign horoscope for a chosen horizon and returns structured guidance fields plus metadata about the model and period. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_western_natal — if the user needs a personalised tropical chart beyond sign-general copy. INPUT CONTRACT: period is constrained to the tool schema enum (daily, weekly,

Computes Gochar against the natal Moon and Lagna and returns per-planet transit longitudes, houses, AVK scores, vedha flags, and a roll-up summary. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — anchors what "natal" means for the same birth record. AFTER: asterwise_get_dasha_transits — adds dasha-lord correlation for today. INPUT CONTRACT: target_date (string, optional — YYY

Lists sign ingresses and retrograde/direct stations for all planets between two dates against the natal context and returns chronological astronomical events. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — clarifies the natal reference for the same birth data. AFTER: asterwise_get_gochar — optional current snapshot after scanning the range. INPUT CONTRACT: from_date and to_dat

Calculate a complete Western natal chart using the tropical zodiac and Swiss Ephemeris. Returns 10 planet positions with Placidus (or chosen) house placements, sign-level dignities plus Lilly essential-dignity scores, all active aspects, and element/modality/hemisphere balance statistics. WORKFLOW: BEFORE: None — this tool is standalone. AFTER: asterwise_get_western_transits_daily — layer cur

Calculates the tropical lunar phase for any date using Swiss Ephemeris. Returns the phase name, phase angle, illumination percentage, Moon age in days, and the next major phase transition. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_western_moon_calendar — get the full month's phase data. INPUT CONTRACT: date (optional string YYYY-MM-DD, years 1-3000) — Date to compute phase

Returns lunar phase data for every day in a calendar month as a structured array. Each element is a complete daily phase object identical to asterwise_get_western_moon_phase. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: year (optional int, 1-3000) — Target year. Defaults to the current year (UTC). Example: 2026 month (optional int 1–12) — Target month. Defaults to th

Calculates all active aspects between a supplied set of planetary longitudes. Accepts a dictionary of body name to tropical ecliptic longitude and returns every aspect within standard natal orbs. WORKFLOW: BEFORE: None — standalone; or use asterwise_get_western_natal to get positions first. AFTER: None. INPUT CONTRACT: positions — dict mapping planet/body name (string) to tropical longitude

Current sky positions vs natal chart for a single day. Returns all 10 planets with tropical longitudes and active aspects to natal positions using transit orbs: major 3°, sextile 2°, minor 1°. Provide start_date for a specific day; defaults to today. WORKFLOW: BEFORE: asterwise_get_western_natal — establish natal chart first. AFTER: asterwise_get_western_transits_weekly — for week view. I

7-day transit window vs natal chart. Returns day-by-day transit snapshots plus peak aspects (active 4+ days in the window). Use start_date to set the week start; defaults to today. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: asterwise_get_western_transits_monthly — for full month. INPUT CONTRACT: birth — WesternBirthData. house_system picks the natal houses used for natal_house on

30-day transit window vs natal chart. Returns day-by-day transit snapshots plus peak aspects (active 10+ days in the window). Use start_date to set the month start; defaults to today. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: None. INPUT CONTRACT: birth — WesternBirthData. house_system picks the natal houses used for natal_house on each transiting planet (default placidus). start_d

Aspect grid between two natal charts using the tropical zodiac. Returns all inter-chart aspects using standard inter-chart orbs. Useful for relationship compatibility analysis. WORKFLOW: BEFORE: asterwise_get_western_natal per person — understand charts individually first. AFTER: asterwise_get_western_composite — midpoint chart for the relationship itself. INPUT CONTRACT: person1, person2 â€

Midpoint composite chart for two people. Each composite planet is the midpoint of the two natal positions. Returns composite planets with dignities and internal aspects. WORKFLOW: BEFORE: asterwise_get_western_synastry — examine inter-chart aspects before composite. AFTER: None. INPUT CONTRACT: person1, person2 — WesternBirthData each. house_system ignored. DO NOT CONFUSE WITH: asterwise_ge

Overall compatibility score (0–100) between two natal charts. Scores element affinity, synastry aspects between personal planets (Sun, Moon, Venus, Mars), and Sun/Moon/rising sign comparisons. WORKFLOW: BEFORE: asterwise_get_western_natal per person optional. AFTER: asterwise_get_western_synastry — drill into raw aspects if score needs detail. INPUT CONTRACT: person1, person2 — WesternBirt

Sign-to-sign compatibility without birth data. Based on element and modality affinity. Fast — no ephemeris calculation required. WORKFLOW: BEFORE: None — no birth data needed. AFTER: asterwise_get_western_compatibility — when full charts are available. INPUT CONTRACT: sign1, sign2 — English zodiac names (Aries … Pisces). DO NOT CONFUSE WITH: asterwise_get_western_compatibility — req

Western solar return chart for a given year, cast for the exact moment the Sun returns to its natal tropical longitude. The chart is a complete Western natal chart for that moment at the birth location. Provide the year as an integer (e.g. 2026). WORKFLOW: BEFORE: asterwise_get_western_natal — understand natal chart before reading return. AFTER: None. INPUT CONTRACT: birth — WesternBirthData

Western lunar return chart: the next moment after a given date that the Moon returns to its natal tropical longitude (approximately every 27.3 days). Builds a complete Western natal chart for that moment at the birth location. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: None. INPUT CONTRACT: birth — WesternBirthData. after_date (optional YYYY-MM-DD) — find next return after this da

Next return chart for any planet after a given date. Finds the exact moment the specified planet returns to its natal tropical longitude and builds a complete Western natal chart for that moment at the birth location. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: None. INPUT CONTRACT: birth — WesternBirthData. planet — one of Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus,

Secondary progressed chart using the day-for-a-year method. Each day after birth symbolises one year of life (1 ephemeris day = 1 tropical year = 365.2421904 days). Returns all 10 progressed planet positions, progressed Ascendant and MC, and the solar arc. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: asterwise_get_western_solar_arc — compare uniform arc vs individual motion. INPUT CON

Western Solar Arc Directions for a target date: the solar arc (progressed Sun minus natal Sun) is added to every natal planet and angle. It is approximately 1° per year; unlike secondary progressions, all planets advance at the same rate. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: None. INPUT CONTRACT: birth — WesternBirthData. target_date (optional YYYY-MM-DD) — defaults to toda

Lists void-of-course Moon periods in a date range (UTC), each with start, end, duration, the Moon's sign, the next sign and the last exact aspect. Rule: traditional — the Moon is void from its last exact Ptolemaic aspect (conjunction, sextile, square, trine, opposition) to the Sun, Mercury, Venus, Mars, Jupiter or Saturn until it enters the next sign (Lilly, Christian Astrology 1647, p. 112). Ou

The 24 planetary hours for a date and place, with the planet ruling each hour and local plus UTC start and end times. Day (sunrise to sunset) and night (sunset to next sunrise) are each split into 12 equal parts; the first hour after sunrise belongs to the weekday's planet and the rest follow the Chaldean order (Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon). WORKFLOW: BEFORE: None — standal

Annual profections for a birth chart and a date: the activated whole-sign house, its sign and the lord of the year. Also gives where the year lord sits natally and the next twelve profection years. Rule: the Ascendant sign is the 1st house at age 0 and the activated sign moves one sign forward every birthday, so at age N the house is (N mod 12) + 1. WORKFLOW: BEFORE: asterwise_get_western_natal â

Solar and lunar eclipses in a date range, past or future, up to 10 years. Each gives the type, time of greatest eclipse, start and end (UTC) and the eclipse degree in the tropical zodiac. With birth data, each eclipse also lists the natal planets and angles within 3° of the eclipse degree by conjunction or opposition. WORKFLOW: BEFORE: None — standalone; add birth for personal contacts. AFTER:

One calendar day at a place, Western style: planetary hours, void-of-course Moon periods, Moon sign changes and the Moon phase. The day runs from local midnight to midnight; every planetary hour that falls in it is listed with the void-of-course periods that overlap it. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_western_daily_factors — the personal picture for the same day. IN

Every Western factor for one person on one day, in one shape, with no weighting. Each factor carries its raw value and range, its frame, the verdict Lilly's rules give, the rule's source, signification ids, the time it holds and whether it depends on the birth time. WORKFLOW: BEFORE: asterwise_get_western_natal. AFTER: asterwise_get_western_events — the same over a range, as a timeline. INPUT

One timeline of everything that happens to a chart over 1 to 31 days, each event with its exact time. It holds the exact major aspects from the transiting planets to the natal planets and angles with Lilly's verdicts, tropical sign ingresses and stations, Moon sign changes, void-of-course periods, New and Full Moons and quarters, eclipses with their contacts, and the profection year turning on the

The chart of a question's moment with the facts Lilly's horary method reads, each rule named. It gives the house rulers, the significators (lord of the 1st and the Moon for the querent, lord of the quesited house), their aspects with Lilly's orbs and whether an applying aspect perfects before a sign change, the Moon's last and next aspects and void-of-course state, combustion, and the consideratio

What each house and planet signifies in William Lilly's Christian Astrology (1647), as a fixed list with stable ids: the twelve houses (pp. 50-56) and the seven planets (pp. 57-83: kinds of people, professions, manners when well and ill dignified). WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_western_daily_factors — factors cite these ids. INPUT CONTRACT: No inputs beyond respon

Tarabala and Chandrabala for any date, with the Moon's star and sign change times. For 1 to 31 civil days, every Moon nakshatra and Moon sign with exact start and end (local and UTC), the tara counted from the birth nakshatra with its name and verdict, and the Moon's house from the natal Moon with the chandrabala verdict (Muhurta Chintamani). WORKFLOW: BEFORE: asterwise_get_natal_chart — the bi

Every classical factor for one person on one day, in one shape, with no weighting. Each factor carries its raw value and range, its frame (from the Moon, from the Lagna, a natal planet, none), the verdict its own rule gives or null, the rule's source, signification ids, the time it holds and whether it depends on the birth time. WORKFLOW: BEFORE: asterwise_get_natal_chart. AFTER: asterwise_get_ve

One timeline of everything that happens to a chart over 1 to 31 days, each event with its exact time. Sidereal sign ingresses with the new sign's house from the natal Moon, stations, Moon nakshatra changes with Tarabala, Moon sign changes with Chandrabala, exact degree conjunctions with natal planets, eclipses with their contacts, Purnima and Amavasya (exact full and new Moon, with the tithi's sta

What each house and planet signifies in Brihat Parashara Hora Shastra, as a fixed list with stable ids. Houses from chapter 11, verses 2-13; planets from chapter 3, verses 12-13 and the karaka verses of chapters 8 and 14. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_vedic_daily_factors — factors cite these ids. INPUT CONTRACT: No inputs beyond response_format. DO NOT CONFUSE WI

Published test charts with reference values from an independent source, so anyone can check the maths. They cover the 25 edge cases of the verification harness (clock changes, southern hemisphere, polar night and day, the date line, 45-minute zones, historical offsets, leap day, range limits), a sample of random charts, a Moon-on-a-nakshatra-boundary case and an unknown-birth-time case. WORKFLOW:

Returns the complete 78-card Rider-Waite-Smith deck with full metadata. Each card includes id (slug), name, arcana_type (major/minor), suit, number, element, astrology_correspondence, upright and reversed meanings, keywords for both orientations, yes/no polarity, and visual description. WORKFLOW: BEFORE: None — standalone catalogue endpoint. AFTER: asterwise_draw_tarot_cards or asterwise_get_ta

Returns full structured data for a single card identified by its slug ID. Useful for card detail pages, single-card lookups, and displaying a specific card after the user selects one by name. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: card_id — Slug identifier for the card. Must be exact. Major Arcana examples: 'the-fool', 'the-magician', 'the-high-priestess', 'the-e

Returns all 22 Major Arcana cards (The Fool through The World) as a structured array. Major Arcana represent universal archetypes and major life themes. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_draw_tarot_cards — draw from this subset by filtering by arcana_type. INPUT CONTRACT: response_format (optional): markdown (default) | json. DO NOT CONFUSE WITH: asterwise_get_tarot_card

Returns all 14 cards in a given Minor Arcana suit as a structured array. WORKFLOW: BEFORE: None — standalone. AFTER: None. INPUT CONTRACT: suit — One of exactly: 'wands', 'cups', 'swords', 'pentacles'. Case-insensitive. Any other value is rejected locally with MCP INVALID_PARAMS. DO NOT CONFUSE WITH: asterwise_get_tarot_major_arcana — 22 Major Arcana, not suit-based. asterwise_get_tarot

Returns a deterministic daily tarot card seeded by SHA-256 hash of the date string. The same card is returned for all callers on the same date — this is intentional. The daily card is not a reading for an individual but a collective daily energy. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_tarot_three_card_spread — for deeper daily reading context. INPUT CONTRACT: date (optio

Draws N unique random cards from the 78-card deck using cryptographic randomness (Python secrets.SystemRandom). Every call is independent — there is no session state. WORKFLOW: BEFORE: None — standalone. AFTER: None — interpret drawn cards using their active_meaning and active_keywords fields. INPUT CONTRACT: count (int 1–78, default 1) — Number of unique cards to draw. Example: 1 (d

Past / Present / Future spread. Draws 3 unique cards using cryptographic randomness and assigns each to a named positional slot with an interpretive context. WORKFLOW: BEFORE: None — standalone reading. AFTER: asterwise_get_tarot_celtic_cross — for deeper 10-position analysis of same question. INPUT CONTRACT: allow_reversed (bool, default false) — Each card independently has 50% reversal c

Ten-card Celtic Cross spread — traditional ten-position tarot layout. Draws 10 unique cards using cryptographic randomness and assigns each to one of the 10 classical Celtic Cross positions. WORKFLOW: BEFORE: None — standalone reading, or follow asterwise_get_tarot_three_card_spread when a more detailed examination of the same question is needed. AFTER: None. INPUT CONTRACT: allow_reversed (

Draws one card and returns a yes, no, or maybe answer with confidence level. The answer is derived from the card's built-in yes_no polarity and its orientation. WORKFLOW: BEFORE: None — standalone. AFTER: asterwise_get_tarot_three_card_spread — for more context when the yes/no answer is 'maybe' or the situation needs elaboration. INPUT CONTRACT: allow_reversed (bool, default true) — Recomm