@roxyapi/ui 1.1.2 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +21 -1
- package/README.md +43 -1
- package/THEMING.md +32 -13
- package/components-catalog.json +1 -11247
- package/dist/cdn/components/almanac-day.js +3 -4
- package/dist/cdn/components/angel-number-card.js +3 -4
- package/dist/cdn/components/angel-number-lookup.js +3 -4
- package/dist/cdn/components/arudha-padas.js +3 -4
- package/dist/cdn/components/ashtakavarga-grid.js +3 -4
- package/dist/cdn/components/aspects-table.js +3 -4
- package/dist/cdn/components/astrocartography-map.js +9 -10
- package/dist/cdn/components/bazi-chart.js +3 -4
- package/dist/cdn/components/bhav-chalit-table.js +3 -4
- package/dist/cdn/components/bhava-bala-table.js +3 -4
- package/dist/cdn/components/biorhythm-chart.js +3 -4
- package/dist/cdn/components/bodygraph.js +14 -13
- package/dist/cdn/components/chara-karakas.js +3 -4
- package/dist/cdn/components/choghadiya-grid.js +3 -4
- package/dist/cdn/components/compatibility-card.js +3 -4
- package/dist/cdn/components/compound-number.js +3 -4
- package/dist/cdn/components/crystal-card.js +3 -4
- package/dist/cdn/components/crystal-grid.js +3 -4
- package/dist/cdn/components/dasha-timeline.js +3 -4
- package/dist/cdn/components/data.js +3 -4
- package/dist/cdn/components/divisional-chart.js +50 -49
- package/dist/cdn/components/dosha-card.js +3 -4
- package/dist/cdn/components/dosha-constitution.js +3 -4
- package/dist/cdn/components/dream-card.js +3 -4
- package/dist/cdn/components/dream-search.js +3 -4
- package/dist/cdn/components/endpoint-form.js +3 -4
- package/dist/cdn/components/ephemeris-table.js +3 -4
- package/dist/cdn/components/fixed-stars.js +3 -4
- package/dist/cdn/components/flying-star-chart.js +3 -4
- package/dist/cdn/components/forecast-digest.js +3 -4
- package/dist/cdn/components/forecast-timeline.js +3 -4
- package/dist/cdn/components/gematria.js +3 -4
- package/dist/cdn/components/gochara-table.js +3 -4
- package/dist/cdn/components/guna-milan.js +3 -4
- package/dist/cdn/components/hd-connection.js +13 -12
- package/dist/cdn/components/hd-penta.js +16 -17
- package/dist/cdn/components/hd-type-card.js +3 -4
- package/dist/cdn/components/hd-variables.js +3 -4
- package/dist/cdn/components/heliacal-table.js +3 -4
- package/dist/cdn/components/hexagram.js +3 -4
- package/dist/cdn/components/hora-table.js +3 -4
- package/dist/cdn/components/horoscope-card.js +3 -4
- package/dist/cdn/components/kp-chart.js +3 -4
- package/dist/cdn/components/kp-finance-card.js +3 -4
- package/dist/cdn/components/kp-planets-table.js +3 -4
- package/dist/cdn/components/kp-ruling-planets.js +3 -4
- package/dist/cdn/components/kua-card.js +3 -4
- package/dist/cdn/components/local-space-compass.js +6 -7
- package/dist/cdn/components/location-search.js +3 -4
- package/dist/cdn/components/luck-pillars.js +3 -4
- package/dist/cdn/components/mayan-day-sign.js +3 -4
- package/dist/cdn/components/moon-phase.js +3 -4
- package/dist/cdn/components/nakshatra-card.js +3 -4
- package/dist/cdn/components/natal-chart.js +24 -14
- package/dist/cdn/components/numerology-card.js +3 -4
- package/dist/cdn/components/panchang-table.js +3 -4
- package/dist/cdn/components/positions-table.js +3 -4
- package/dist/cdn/components/profection-card.js +3 -4
- package/dist/cdn/components/reference-card.js +3 -4
- package/dist/cdn/components/relocation-wheel.js +24 -14
- package/dist/cdn/components/shadbala-table.js +3 -4
- package/dist/cdn/components/synastry-chart.js +21 -12
- package/dist/cdn/components/tarot-card.js +3 -4
- package/dist/cdn/components/tarot-catalog.js +3 -4
- package/dist/cdn/components/tarot-spread.js +3 -4
- package/dist/cdn/components/transit-wheel.js +10 -11
- package/dist/cdn/components/transits-table.js +3 -4
- package/dist/cdn/components/upagraha-table.js +3 -4
- package/dist/cdn/components/vastu-mandala.js +10 -11
- package/dist/cdn/components/vedic-aspects.js +3 -4
- package/dist/cdn/components/vedic-daily.js +3 -4
- package/dist/cdn/components/vedic-kundli.js +62 -61
- package/dist/cdn/components/vedic-planets-table.js +3 -4
- package/dist/cdn/components/western-planets-table.js +3 -4
- package/dist/cdn/components/yoga-list.js +3 -4
- package/dist/cdn/components/zodiac-card.js +3 -4
- package/dist/cdn/locales/de.js +1 -1
- package/dist/cdn/locales/es.js +1 -1
- package/dist/cdn/locales/fr.js +1 -1
- package/dist/cdn/locales/hi.js +1 -1
- package/dist/cdn/locales/pt.js +1 -1
- package/dist/cdn/locales/ru.js +1 -1
- package/dist/cdn/locales/tr.js +1 -1
- package/dist/cdn/roxy-ui.js +113 -96
- package/dist/cdn/widgets.js +1 -1
- package/dist/charts.cjs +111 -0
- package/dist/charts.d.ts +8 -0
- package/dist/charts.js +111 -0
- package/dist/components/almanac-day.js +1 -1
- package/dist/components/angel-number-card.js +1 -1
- package/dist/components/angel-number-lookup.js +1 -1
- package/dist/components/arudha-padas.js +1 -1
- package/dist/components/ashtakavarga-grid.js +1 -1
- package/dist/components/aspects-table.js +1 -1
- package/dist/components/astrocartography-map.js +5 -5
- package/dist/components/bazi-chart.js +1 -1
- package/dist/components/bhav-chalit-table.js +1 -1
- package/dist/components/bhava-bala-table.js +1 -1
- package/dist/components/biorhythm-chart.js +1 -1
- package/dist/components/bodygraph.d.ts +0 -4
- package/dist/components/bodygraph.js +10 -10
- package/dist/components/chara-karakas.js +1 -1
- package/dist/components/choghadiya-grid.js +1 -1
- package/dist/components/compatibility-card.js +1 -1
- package/dist/components/compound-number.js +1 -1
- package/dist/components/crystal-card.js +1 -1
- package/dist/components/crystal-grid.js +1 -1
- package/dist/components/dasha-timeline.js +1 -1
- package/dist/components/data.js +1 -1
- package/dist/components/divisional-chart.js +60 -60
- package/dist/components/dosha-card.js +1 -1
- package/dist/components/dosha-constitution.js +1 -1
- package/dist/components/dream-card.js +1 -1
- package/dist/components/dream-search.js +1 -1
- package/dist/components/endpoint-form.d.ts +3 -1
- package/dist/components/endpoint-form.js +1 -1
- package/dist/components/ephemeris-table.js +1 -1
- package/dist/components/fixed-stars.js +1 -1
- package/dist/components/flying-star-chart.js +1 -1
- package/dist/components/forecast-digest.js +1 -1
- package/dist/components/forecast-timeline.js +1 -1
- package/dist/components/gematria.js +1 -1
- package/dist/components/gochara-table.js +1 -1
- package/dist/components/guna-milan.js +1 -1
- package/dist/components/hd-connection.js +10 -10
- package/dist/components/hd-penta.js +16 -16
- package/dist/components/hd-type-card.js +1 -1
- package/dist/components/hd-variables.js +1 -1
- package/dist/components/heliacal-table.js +1 -1
- package/dist/components/hexagram.js +1 -1
- package/dist/components/hora-table.js +1 -1
- package/dist/components/horoscope-card.js +1 -1
- package/dist/components/kp-chart.js +1 -1
- package/dist/components/kp-finance-card.js +1 -1
- package/dist/components/kp-planets-table.js +1 -1
- package/dist/components/kp-ruling-planets.js +1 -1
- package/dist/components/kua-card.js +1 -1
- package/dist/components/local-space-compass.js +5 -5
- package/dist/components/location-search.d.ts +1 -0
- package/dist/components/location-search.js +1 -1
- package/dist/components/luck-pillars.js +1 -1
- package/dist/components/mayan-day-sign.js +1 -1
- package/dist/components/moon-phase.js +1 -1
- package/dist/components/nakshatra-card.js +1 -1
- package/dist/components/natal-chart.d.ts +3 -82
- package/dist/components/natal-chart.js +20 -11
- package/dist/components/numerology-card.js +1 -1
- package/dist/components/panchang-table.js +1 -1
- package/dist/components/positions-table.js +1 -1
- package/dist/components/profection-card.js +1 -1
- package/dist/components/reference-card.js +1 -1
- package/dist/components/relocation-wheel.js +20 -11
- package/dist/components/shadbala-table.js +1 -1
- package/dist/components/synastry-chart.d.ts +2 -34
- package/dist/components/synastry-chart.js +17 -9
- package/dist/components/tarot-card.js +1 -1
- package/dist/components/tarot-catalog.js +1 -1
- package/dist/components/tarot-spread.js +1 -1
- package/dist/components/transit-wheel.js +7 -7
- package/dist/components/transits-table.js +1 -1
- package/dist/components/upagraha-table.js +1 -1
- package/dist/components/vastu-mandala.js +9 -9
- package/dist/components/vedic-aspects.js +1 -1
- package/dist/components/vedic-daily.js +1 -1
- package/dist/components/vedic-kundli.js +54 -54
- package/dist/components/vedic-planets-table.js +1 -1
- package/dist/components/western-planets-table.js +1 -1
- package/dist/components/yoga-list.js +1 -1
- package/dist/components/zodiac-card.js +1 -1
- package/dist/forms/labels/de.json +1 -1
- package/dist/forms/labels/en.json +1 -1
- package/dist/forms/labels/es.json +1 -1
- package/dist/forms/labels/fr.json +1 -1
- package/dist/forms/labels/hi.json +1 -1
- package/dist/forms/labels/pt.json +1 -1
- package/dist/forms/labels/ru.json +1 -1
- package/dist/forms/labels/tr.json +1 -1
- package/dist/forms.json +1 -1
- package/dist/generated/field-labels-en.d.ts +1 -1
- package/dist/i18n/chrome-strings.d.ts +1 -1
- package/dist/i18n/lang.d.ts +3 -1
- package/dist/i18n/localized-element.d.ts +4 -0
- package/dist/i18n/registry.d.ts +7 -0
- package/dist/index.cjs +111 -94
- package/dist/index.js +110 -93
- package/dist/locales/de.js +1 -1
- package/dist/locales/es.js +1 -1
- package/dist/locales/field-labels/de.d.ts +1 -1
- package/dist/locales/field-labels/es.d.ts +1 -1
- package/dist/locales/field-labels/fr.d.ts +1 -1
- package/dist/locales/field-labels/hi.d.ts +1 -1
- package/dist/locales/field-labels/pt.d.ts +1 -1
- package/dist/locales/field-labels/ru.d.ts +1 -1
- package/dist/locales/field-labels/tr.d.ts +1 -1
- package/dist/locales/fr.js +1 -1
- package/dist/locales/hi.js +1 -1
- package/dist/locales/pt.js +1 -1
- package/dist/locales/ru.js +1 -1
- package/dist/locales/tr.js +1 -1
- package/dist/manifest.d.ts +3 -5
- package/dist/manifest.json +1 -89
- package/dist/schemas/get--angel-numbers-lookup.json +1 -1
- package/dist/schemas/get--angel-numbers-numbers-number.json +1 -1
- package/dist/schemas/get--angel-numbers-numbers.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-daily.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-monthly.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-weekly.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-yearly.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-calendar-year-month.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-current.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-upcoming.json +1 -1
- package/dist/schemas/get--astrology-planet-meanings-id.json +1 -1
- package/dist/schemas/get--astrology-planet-meanings.json +1 -1
- package/dist/schemas/get--astrology-signs-id.json +1 -1
- package/dist/schemas/get--astrology-signs.json +1 -1
- package/dist/schemas/get--ayurveda-daily.json +1 -1
- package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
- package/dist/schemas/get--ayurveda-doshas.json +1 -1
- package/dist/schemas/get--ayurveda-qualities.json +1 -1
- package/dist/schemas/get--ayurveda-tastes.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-day-date.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-monthly.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-solar-terms-year.json +1 -1
- package/dist/schemas/get--chinese-astrology-elements.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-compatibility-sign1-sign2.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
- package/dist/schemas/get--crystals-birthstone-month.json +1 -1
- package/dist/schemas/get--crystals-chakra-chakra.json +1 -1
- package/dist/schemas/get--crystals-colors.json +1 -1
- package/dist/schemas/get--crystals-element-element.json +1 -1
- package/dist/schemas/get--crystals-id.json +1 -1
- package/dist/schemas/get--crystals-pairings-id.json +1 -1
- package/dist/schemas/get--crystals-planets.json +1 -1
- package/dist/schemas/get--crystals-random.json +1 -1
- package/dist/schemas/get--crystals-search.json +1 -1
- package/dist/schemas/get--crystals-zodiac-sign.json +1 -1
- package/dist/schemas/get--crystals.json +1 -1
- package/dist/schemas/get--dreams-symbols-id.json +1 -1
- package/dist/schemas/get--dreams-symbols-letters.json +1 -1
- package/dist/schemas/get--dreams-symbols-random.json +1 -1
- package/dist/schemas/get--dreams-symbols.json +1 -1
- package/dist/schemas/get--feng-shui-afflictions-year.json +1 -1
- package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
- package/dist/schemas/get--feng-shui-bagua.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-annual-year.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-monthly.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-stars.json +1 -1
- package/dist/schemas/get--feng-shui-kua-number.json +1 -1
- package/dist/schemas/get--feng-shui-periods.json +1 -1
- package/dist/schemas/get--human-design-centers-id.json +1 -1
- package/dist/schemas/get--human-design-gates-number.json +1 -1
- package/dist/schemas/get--iching-cast.json +1 -1
- package/dist/schemas/get--iching-hexagrams-lookup.json +1 -1
- package/dist/schemas/get--iching-hexagrams-number.json +1 -1
- package/dist/schemas/get--iching-hexagrams-random.json +1 -1
- package/dist/schemas/get--iching-hexagrams.json +1 -1
- package/dist/schemas/get--iching-trigrams-id.json +1 -1
- package/dist/schemas/get--iching-trigrams.json +1 -1
- package/dist/schemas/get--kabbalah-ciphers.json +1 -1
- package/dist/schemas/get--kabbalah-daily.json +1 -1
- package/dist/schemas/get--kabbalah-letters-id.json +1 -1
- package/dist/schemas/get--kabbalah-letters.json +1 -1
- package/dist/schemas/get--kabbalah-names-number.json +1 -1
- package/dist/schemas/get--kabbalah-names.json +1 -1
- package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
- package/dist/schemas/get--kabbalah-tree.json +1 -1
- package/dist/schemas/get--languages-field-labels.json +1 -1
- package/dist/schemas/get--languages.json +1 -1
- package/dist/schemas/get--location-countries-iso2.json +1 -1
- package/dist/schemas/get--location-countries.json +1 -1
- package/dist/schemas/get--location-search.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-daily.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas-number.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-calendar-monthly.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-daily.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas-number.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas.json +1 -1
- package/dist/schemas/get--numerology-compound-number-number.json +1 -1
- package/dist/schemas/get--numerology-meanings-number.json +1 -1
- package/dist/schemas/get--tarot-cards-id.json +1 -1
- package/dist/schemas/get--tarot-cards.json +1 -1
- package/dist/schemas/get--usage.json +1 -1
- package/dist/schemas/get--vastu-devatas-id.json +1 -1
- package/dist/schemas/get--vastu-devatas.json +1 -1
- package/dist/schemas/get--vastu-directions-id.json +1 -1
- package/dist/schemas/get--vastu-directions.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas.json +1 -1
- package/dist/schemas/get--vedic-astrology-kp-ayanamsa.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga.json +1 -1
- package/dist/schemas/post--angel-numbers-daily.json +1 -1
- package/dist/schemas/post--astrology-arabic-lots.json +1 -1
- package/dist/schemas/post--astrology-aspect-patterns.json +1 -1
- package/dist/schemas/post--astrology-aspects-monthly.json +1 -1
- package/dist/schemas/post--astrology-aspects.json +1 -1
- package/dist/schemas/post--astrology-asteroids.json +1 -1
- package/dist/schemas/post--astrology-astrocartography.json +1 -1
- package/dist/schemas/post--astrology-compatibility-score.json +1 -1
- package/dist/schemas/post--astrology-composite-chart.json +1 -1
- package/dist/schemas/post--astrology-ecliptic-crossings.json +1 -1
- package/dist/schemas/post--astrology-fixed-stars.json +1 -1
- package/dist/schemas/post--astrology-houses.json +1 -1
- package/dist/schemas/post--astrology-lilith.json +1 -1
- package/dist/schemas/post--astrology-local-space.json +1 -1
- package/dist/schemas/post--astrology-lunar-return.json +1 -1
- package/dist/schemas/post--astrology-natal-chart.json +1 -1
- package/dist/schemas/post--astrology-parallels-monthly.json +1 -1
- package/dist/schemas/post--astrology-planetary-returns.json +1 -1
- package/dist/schemas/post--astrology-planets-monthly.json +1 -1
- package/dist/schemas/post--astrology-planets.json +1 -1
- package/dist/schemas/post--astrology-profections.json +1 -1
- package/dist/schemas/post--astrology-progressions.json +1 -1
- package/dist/schemas/post--astrology-relocation-chart.json +1 -1
- package/dist/schemas/post--astrology-solar-arc.json +1 -1
- package/dist/schemas/post--astrology-solar-return.json +1 -1
- package/dist/schemas/post--astrology-synastry.json +1 -1
- package/dist/schemas/post--astrology-transit-aspects.json +1 -1
- package/dist/schemas/post--astrology-transits-monthly.json +1 -1
- package/dist/schemas/post--astrology-transits.json +1 -1
- package/dist/schemas/post--ayurveda-constitution.json +1 -1
- package/dist/schemas/post--ayurveda-dinacharya.json +1 -1
- package/dist/schemas/post--ayurveda-ritucharya.json +1 -1
- package/dist/schemas/post--biorhythm-compatibility.json +1 -1
- package/dist/schemas/post--biorhythm-critical-days.json +1 -1
- package/dist/schemas/post--biorhythm-daily.json +1 -1
- package/dist/schemas/post--biorhythm-forecast.json +1 -1
- package/dist/schemas/post--biorhythm-phases.json +1 -1
- package/dist/schemas/post--biorhythm-reading.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-annual-forecast.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-chart.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-day-master.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-luck-pillars.json +1 -1
- package/dist/schemas/post--chinese-astrology-calendar-auspicious-days.json +1 -1
- package/dist/schemas/post--chinese-astrology-calendar-lunar-date.json +1 -1
- package/dist/schemas/post--chinese-astrology-zodiac-sign.json +1 -1
- package/dist/schemas/post--crystals-daily.json +1 -1
- package/dist/schemas/post--dreams-daily.json +1 -1
- package/dist/schemas/post--feng-shui-eight-mansions.json +1 -1
- package/dist/schemas/post--feng-shui-flying-stars-natal.json +1 -1
- package/dist/schemas/post--feng-shui-kua.json +1 -1
- package/dist/schemas/post--forecast-digest.json +1 -1
- package/dist/schemas/post--forecast-significant-dates.json +1 -1
- package/dist/schemas/post--forecast-solar-return.json +1 -1
- package/dist/schemas/post--forecast-timeline.json +1 -1
- package/dist/schemas/post--forecast-transits.json +1 -1
- package/dist/schemas/post--human-design-bodygraph.json +1 -1
- package/dist/schemas/post--human-design-centers.json +1 -1
- package/dist/schemas/post--human-design-channels.json +1 -1
- package/dist/schemas/post--human-design-connection.json +1 -1
- package/dist/schemas/post--human-design-gates.json +1 -1
- package/dist/schemas/post--human-design-penta.json +1 -1
- package/dist/schemas/post--human-design-profile.json +1 -1
- package/dist/schemas/post--human-design-transit.json +1 -1
- package/dist/schemas/post--human-design-type.json +1 -1
- package/dist/schemas/post--human-design-variables.json +1 -1
- package/dist/schemas/post--iching-daily-cast.json +1 -1
- package/dist/schemas/post--iching-daily.json +1 -1
- package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
- package/dist/schemas/post--kabbalah-compatibility.json +1 -1
- package/dist/schemas/post--kabbalah-gematria.json +1 -1
- package/dist/schemas/post--kabbalah-name-profile.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-aztec-tonalpohualli.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-chart.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-long-count-convert.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-tzolkin.json +1 -1
- package/dist/schemas/post--numerology-birth-day.json +1 -1
- package/dist/schemas/post--numerology-bridge.json +1 -1
- package/dist/schemas/post--numerology-business-name.json +1 -1
- package/dist/schemas/post--numerology-chaldean.json +1 -1
- package/dist/schemas/post--numerology-chart.json +1 -1
- package/dist/schemas/post--numerology-compatibility.json +1 -1
- package/dist/schemas/post--numerology-daily.json +1 -1
- package/dist/schemas/post--numerology-dual.json +1 -1
- package/dist/schemas/post--numerology-expression.json +1 -1
- package/dist/schemas/post--numerology-karmic-debt.json +1 -1
- package/dist/schemas/post--numerology-karmic-lessons.json +1 -1
- package/dist/schemas/post--numerology-life-path.json +1 -1
- package/dist/schemas/post--numerology-maturity.json +1 -1
- package/dist/schemas/post--numerology-personal-day.json +1 -1
- package/dist/schemas/post--numerology-personal-month.json +1 -1
- package/dist/schemas/post--numerology-personal-year.json +1 -1
- package/dist/schemas/post--numerology-personality.json +1 -1
- package/dist/schemas/post--numerology-soul-urge.json +1 -1
- package/dist/schemas/post--tarot-daily.json +1 -1
- package/dist/schemas/post--tarot-draw.json +1 -1
- package/dist/schemas/post--tarot-spreads-career.json +1 -1
- package/dist/schemas/post--tarot-spreads-celtic-cross.json +1 -1
- package/dist/schemas/post--tarot-spreads-custom.json +1 -1
- package/dist/schemas/post--tarot-spreads-love.json +1 -1
- package/dist/schemas/post--tarot-spreads-three-card.json +1 -1
- package/dist/schemas/post--tarot-yes-no.json +1 -1
- package/dist/schemas/post--vastu-ayadi.json +1 -1
- package/dist/schemas/post--vastu-entrance.json +1 -1
- package/dist/schemas/post--vastu-mandala.json +1 -1
- package/dist/schemas/post--vastu-plot.json +1 -1
- package/dist/schemas/post--vastu-rooms.json +1 -1
- package/dist/schemas/post--vastu-timing-griha-pravesh.json +1 -1
- package/dist/schemas/post--vedic-astrology-arudha.json +1 -1
- package/dist/schemas/post--vedic-astrology-ashtakavarga.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects-lunar.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects.json +1 -1
- package/dist/schemas/post--vedic-astrology-bhav-chalit.json +1 -1
- package/dist/schemas/post--vedic-astrology-bhava-bala.json +1 -1
- package/dist/schemas/post--vedic-astrology-birth-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-chara-karakas.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
- package/dist/schemas/post--vedic-astrology-daily.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-divisional-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-kalsarpa.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-manglik.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-sadhesati.json +1 -1
- package/dist/schemas/post--vedic-astrology-ecliptic-crossings.json +1 -1
- package/dist/schemas/post--vedic-astrology-heliacal.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-rasi-changes.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-sublord-changes.json +1 -1
- package/dist/schemas/post--vedic-astrology-navamsa.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-basic.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-choghadiya.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-detailed.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-hora.json +1 -1
- package/dist/schemas/post--vedic-astrology-parallels-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-parallels.json +1 -1
- package/dist/schemas/post--vedic-astrology-planetary-positions-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-planetary-positions.json +1 -1
- package/dist/schemas/post--vedic-astrology-shadbala.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit.json +1 -1
- package/dist/schemas/post--vedic-astrology-upagraha.json +1 -1
- package/dist/schemas/post--vedic-astrology-yoga-detect.json +1 -1
- package/dist/styles/charts/bodygraph.css +1 -0
- package/dist/styles/charts/kundli.css +1 -0
- package/dist/styles/charts/natal-wheel.css +1 -0
- package/dist/styles/charts/synastry-wheel.css +1 -0
- package/dist/styles/fonts/fraunces-jost.css +1 -0
- package/dist/styles/fonts/geist/OFL.txt +93 -0
- package/dist/styles/fonts/geist/geist-cyrillic.woff2 +0 -0
- package/dist/styles/fonts/geist/geist-latin-ext.woff2 +0 -0
- package/dist/styles/fonts/geist/geist-latin.woff2 +0 -0
- package/dist/styles/fonts/geist.css +1 -0
- package/dist/styles/fonts/jost.css +1 -0
- package/dist/styles/fonts.d.ts +23 -0
- package/dist/styles/palette-names.d.ts +3 -0
- package/dist/styles/palettes.d.ts +6 -19
- package/dist/styles/themes/celeste.css +1 -1
- package/dist/styles/themes/eucalyptus.css +1 -1
- package/dist/styles/themes/kiln.css +1 -1
- package/dist/styles/themes/moonlit.css +1 -1
- package/dist/styles/themes/practitioner.css +1 -1
- package/dist/styles/tokens-css.d.ts +1 -1
- package/dist/styles/tokens.css +1 -1
- package/dist/tool-component.cjs +1 -1
- package/dist/tool-component.js +1 -1
- package/dist/utils/angel-sections.d.ts +1 -1
- package/dist/utils/aspect-line.d.ts +1 -10
- package/dist/utils/aspect-styles.d.ts +4 -0
- package/dist/utils/base-element.d.ts +15 -2
- package/dist/utils/bodygraph-render.d.ts +18 -2
- package/dist/utils/bodygraph-styles.d.ts +1 -6
- package/dist/utils/brand.d.ts +22 -0
- package/dist/utils/chart-styles.d.ts +9 -0
- package/dist/utils/chart-viewport.d.ts +1 -1
- package/dist/utils/degree.d.ts +7 -0
- package/dist/utils/dist-base.d.ts +2 -0
- package/dist/utils/fetch-controller.d.ts +9 -2
- package/dist/utils/field-schema.d.ts +10 -4
- package/dist/utils/frame.d.ts +1 -1
- package/dist/utils/hd-reading.d.ts +1 -14
- package/dist/utils/interp-accordion.d.ts +1 -1
- package/dist/utils/kundli-chrome.d.ts +22 -0
- package/dist/utils/kundli-render.d.ts +17 -28
- package/dist/utils/natal-wheel.d.ts +32 -0
- package/dist/utils/reference-table.d.ts +7 -0
- package/dist/utils/stacked-table.d.ts +1 -1
- package/dist/utils/svg-string.d.ts +20 -0
- package/dist/utils/synastry-wheel.d.ts +15 -0
- package/dist/version.d.ts +1 -1
- package/package.json +10 -2
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Ayadi shadvarga","fields":[{"key":"length","name":"length","kind":"number","required":true,"description":"Length of the building or room, in the unit given. Under the Manasara family this is the measure the aya and rksha formulas multiply; under the perimeter family it only feeds the perimeter.","min":0,"example":11},{"key":"breadth","name":"breadth","kind":"number","required":true,"description":"Breadth of the building or room, in the unit given. Under the Manasara family this is the measure the vyaya and yoni formulas multiply.","min":0,"example":11},{"key":"perimeter","name":"perimeter","kind":"number","required":false,"description":"Perimeter of the plan, if it is not simply twice the length plus twice the breadth. The perimeter family runs every formula on this one measure, so it is the number that decides all six remainders there.","min":0,"example":11,"fold":true},{"key":"circumference","name":"circumference","kind":"number","required":false,"description":"Circumference or height, if the Manasara vara and tithi formulas should read something other than the perimeter. Defaults to the perimeter, which is what a rectangular plan supplies.","min":0,"example":11,"fold":true},{"key":"unit","name":"unit","kind":"tiles","required":false,"description":"Unit the Ayadi dimensions are given in. Every remainder is unit sensitive, so this is an input and never assumed: the same building measured in cubits and in feet gives different remainders. hasta is the classical cubit and needs no conversion; feet and metres are converted using hastaInches and rounded to whole cubits, and the rounded figures are returned. Defaults to hasta.","enum":["hasta","feet","metres"],"default":"hasta","example":"hasta","fold":true},{"key":"hastaInches","name":"hastaInches","kind":"number","required":false,"description":"Length of one hasta, the classical cubit, in inches. Defaults to 18, which is 24 angula at three quarters of an inch each and is the value three independent sources agree on. Raise it if your lineage measures the cubit differently; the value used is echoed on the response so a stored reading can be reproduced years later. Only used when unit is feet or metres.","min":0,"default":18,"example":18,"fold":true},{"key":"ayadiText","name":"ayadiText","kind":"tiles","required":false,"description":"Which family of Ayadi formulas to apply. manasara takes length, breadth and circumference separately and is double sourced. perimeter-texts runs every formula on the perimeter alone and is the family the usual worked example is printed for. utpala supplies a yoni formula from the length times the breadth and nothing else, so the other five vargas fall back to the perimeter family and the response says so. Defaults to manasara.","enum":["manasara","perimeter-texts","utpala"],"default":"manasara","example":"manasara","fold":true},{"key":"vyayaFormula","name":"vyayaFormula","kind":"tiles","required":false,"description":"Which vyaya formula the perimeter family uses. The printed table gives two joined by the word or and states no rule for choosing. p9-10 multiplies by nine and divides by ten, which is the only divisor consistent with the ten member vyaya group, so its remainder can be placed in that group and it is the default. p3-14 multiplies by three and divides by fourteen, and its remainder maps to no group any source enumerates. Ignored when ayadiText is manasara, which has one vyaya formula.","enum":["p9-10","p3-14"],"default":"p9-10","example":"p9-10","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Ayadi shadvarga","fields":[{"key":"length","name":"length","kind":"number","required":true,"description":"Length of the building or room, in the unit given. Under the Manasara family this is the measure the aya and rksha formulas multiply; under the perimeter family it only feeds the perimeter.","min":0,"example":11},{"key":"breadth","name":"breadth","kind":"number","required":true,"description":"Breadth of the building or room, in the unit given. Under the Manasara family this is the measure the vyaya and yoni formulas multiply.","min":0,"example":11},{"key":"perimeter","name":"perimeter","kind":"number","required":false,"description":"Perimeter of the plan, if it is not simply twice the length plus twice the breadth. The perimeter family runs every formula on this one measure, so it is the number that decides all six remainders there.","min":0,"example":11,"fold":true},{"key":"circumference","name":"circumference","kind":"number","required":false,"description":"Circumference or height, if the Manasara vara and tithi formulas should read something other than the perimeter. Defaults to the perimeter, which is what a rectangular plan supplies.","min":0,"example":11,"fold":true},{"key":"unit","name":"unit","kind":"tiles","required":false,"description":"Unit the Ayadi dimensions are given in. Every remainder is unit sensitive, so this is an input and never assumed: the same building measured in cubits and in feet gives different remainders. hasta is the classical cubit and needs no conversion; feet and metres are converted using hastaInches and rounded to whole cubits, and the rounded figures are returned. Defaults to hasta.","enum":["hasta","feet","metres"],"default":"hasta","example":"hasta","fold":true},{"key":"hastaInches","name":"hastaInches","kind":"number","required":false,"description":"Length of one hasta, the classical cubit, in inches. Defaults to 18, which is 24 angula at three quarters of an inch each and is the value three independent sources agree on. Raise it if your lineage measures the cubit differently; the value used is echoed on the response so a stored reading can be reproduced years later. Only used when unit is feet or metres.","min":0,"default":18,"example":18,"fold":true},{"key":"ayadiText","name":"ayadiText","kind":"tiles","required":false,"description":"Which family of Ayadi formulas to apply. manasara takes length, breadth and circumference separately and is double sourced. perimeter-texts runs every formula on the perimeter alone and is the family the usual worked example is printed for. utpala supplies a yoni formula from the length times the breadth and nothing else, so the other five vargas fall back to the perimeter family and the response says so. Defaults to manasara.","enum":["manasara","perimeter-texts","utpala"],"default":"manasara","example":"manasara","fold":true},{"key":"vyayaFormula","name":"vyayaFormula","kind":"tiles","required":false,"description":"Which vyaya formula the perimeter family uses. The printed table gives two joined by the word or and states no rule for choosing. p9-10 multiplies by nine and divides by ten, which is the only divisor consistent with the ten member vyaya group, so its remainder can be placed in that group and it is the default. p3-14 multiplies by three and divides by fourteen, and its remainder maps to no group any source enumerates. Ignored when ayadiText is manasara, which has one vyaya formula.","enum":["p9-10","p3-14"],"default":"p9-10","example":"p9-10","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate entrance pada","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":true,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"door.x","name":"x","group":"door","kind":"number","required":false,"description":"Distance east of the plot origin, in the same unit as the plot. The x axis runs east.","example":15,"fold":true},{"key":"door.y","name":"y","group":"door","kind":"number","required":false,"description":"Distance north of the plot origin, in the same unit as the plot. The y axis runs north.","example":0,"fold":true},{"key":"doorPosition","name":"doorPosition","kind":"number","required":true,"description":"Where the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facing, the south-west for a west facing and the north-west for a north facing. The side carries 8 padas, so to aim at pada n of 8 send its midpoint, (n - 0.5) / 8: 0.0625 for the first pada, 0.4375 for the fourth, 0.9375 for the eighth. The response names the pada the fraction resolved to in ordinalOnSide. Requires a cardinal facing, since an intercardinal facing names no single side. Send this or door, never both.","min":0,"max":1,"example":0.4},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"requiredAnyOf":[["facing","doorPosition"],["facing","door"],["facingDegrees","doorPosition"],["facingDegrees","door"]],"groups":[{"key":"plot","label":"Plot"},{},{"key":"door","label":"Door","fold":true}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate entrance pada","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":true,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"door.x","name":"x","group":"door","kind":"number","required":false,"description":"Distance east of the plot origin, in the same unit as the plot. The x axis runs east.","example":15,"fold":true},{"key":"door.y","name":"y","group":"door","kind":"number","required":false,"description":"Distance north of the plot origin, in the same unit as the plot. The y axis runs north.","example":0,"fold":true},{"key":"doorPosition","name":"doorPosition","kind":"number","required":true,"description":"Where the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facing, the south-west for a west facing and the north-west for a north facing. The side carries 8 padas, so to aim at pada n of 8 send its midpoint, (n - 0.5) / 8: 0.0625 for the first pada, 0.4375 for the fourth, 0.9375 for the eighth. The response names the pada the fraction resolved to in ordinalOnSide. Requires a cardinal facing, since an intercardinal facing names no single side. Send this or door, never both.","min":0,"max":1,"example":0.4},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["facing","doorPosition"],["facing","door"],["facingDegrees","doorPosition"],["facingDegrees","door"]],"groups":[{"key":"plot","label":"Plot"},{},{"key":"door","label":"Door","fold":true}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Generate Vastu Purusha Mandala","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"groups":[{"key":"plot","label":"Plot"},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate Vastu Purusha Mandala","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"plot","label":"Plot"},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Analyse a plot","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":true,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"slopeLowDirection","name":"slopeLowDirection","kind":"tiles","required":false,"description":"Which quarter of the plot the ground falls toward, that is where the LOW point is. The chapter states its rules in terms of the side that stands HIGHER, so the opposite of this value is what the verses are read against, and both are returned. Omit it if the ground is level.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","fold":true},{"key":"road","name":"road","kind":"tiles","required":false,"description":"Which side a road runs along. The verdict is convention: the chapter states no rule for the side a road is on, only that an obstruction facing the gate brings misery unless it lies beyond twice the height of the house.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","fold":true},{"key":"extensions","name":"extensions","kind":"array","required":false,"description":"Quarters where the plot bulges out beyond a rectangle. Every extension verdict is convention: the chapter states no rule for a named corner and the nearest verses speak of a figure with a limb wanting.","example":["Northeast"],"fold":true},{"key":"cuts","name":"cuts","kind":"array","required":false,"description":"Quarters where a corner is missing from the rectangle. Every cut verdict is convention, for the same reason as the extensions.","example":["Southwest"],"fold":true},{"key":"water","name":"water","kind":"tiles","required":false,"description":"Which quarter holds standing water, a well, a tank or a sump. This one IS sourced: 53.119 gives a distinct effect for each of the eight directions and calls only the north and the north-east favourable.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","fold":true},{"key":"slopeSchool","name":"slopeSchool","kind":"tiles","required":false,"description":"Which reading of the ground level to lead with. brihat-samhita applies verses 115 to 117 as written, where a higher north-east is a loss, a higher east or north is permitted when level ground is unavoidable and still carries its stated cost, and a higher south or west carries its cost with no allowance. modern applies the widely taught rule that the north-east must be the lowest point, which agrees with verse 115 and contradicts the verse 116 allowance. Both readings are returned whichever you choose, so the disagreement is visible rather than hidden. Defaults to brihat-samhita.","enum":["brihat-samhita","modern"],"default":"brihat-samhita","example":"brihat-samhita","fold":true}],"hasLang":true,"requiredAnyOf":[["facing"],["facingDegrees"]],"groups":[{"key":"plot","label":"Plot"},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Analyse a plot","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":true,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"slopeLowDirection","name":"slopeLowDirection","kind":"tiles","required":false,"description":"Which quarter of the plot the ground falls toward, that is where the LOW point is. The chapter states its rules in terms of the side that stands HIGHER, so the opposite of this value is what the verses are read against, and both are returned. Omit it if the ground is level.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","fold":true},{"key":"road","name":"road","kind":"tiles","required":false,"description":"Which side a road runs along. The verdict is convention: the chapter states no rule for the side a road is on, only that an obstruction facing the gate brings misery unless it lies beyond twice the height of the house.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","fold":true},{"key":"extensions","name":"extensions","kind":"array","required":false,"description":"Quarters where the plot bulges out beyond a rectangle. Every extension verdict is convention: the chapter states no rule for a named corner and the nearest verses speak of a figure with a limb wanting.","example":["Northeast"],"fold":true},{"key":"cuts","name":"cuts","kind":"array","required":false,"description":"Quarters where a corner is missing from the rectangle. Every cut verdict is convention, for the same reason as the extensions.","example":["Southwest"],"fold":true},{"key":"water","name":"water","kind":"tiles","required":false,"description":"Which quarter holds standing water, a well, a tank or a sump. This one IS sourced: 53.119 gives a distinct effect for each of the eight directions and calls only the north and the north-east favourable.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast","fold":true},{"key":"slopeSchool","name":"slopeSchool","kind":"tiles","required":false,"description":"Which reading of the ground level to lead with. brihat-samhita applies verses 115 to 117 as written, where a higher north-east is a loss, a higher east or north is permitted when level ground is unavoidable and still carries its stated cost, and a higher south or west carries its cost with no allowance. modern applies the widely taught rule that the north-east must be the lowest point, which agrees with verse 115 and contradicts the verse 116 allowance. Both readings are returned whichever you choose, so the disagreement is visible rather than hidden. Defaults to brihat-samhita.","enum":["brihat-samhita","modern"],"default":"brihat-samhita","example":"brihat-samhita","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["facing"],["facingDegrees"]],"groups":[{"key":"plot","label":"Plot"},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Check room placement","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":true,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"rooms.0.type","name":"type","group":"rooms.0","kind":"tiles","required":true,"description":"What the room is, one of puja, kitchen, master-bedroom, bedroom, living, dining, study, toilet, store, staircase, water-storage, entrance. Case and punctuation are folded, so Master Bedroom and master_bedroom both resolve. Four of the twelve carry a verse and the rest carry convention, and the response says which.","enum":["puja","kitchen","master-bedroom","bedroom","living","dining","study","toilet","store","staircase","water-storage","entrance"],"example":"kitchen"},{"key":"rooms.0.direction","name":"direction","group":"rooms.0","kind":"tiles","required":true,"description":"Which quarter of the plot the room sits in, if you already know it. Send this or polygon, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast"},{"key":"rooms.0.polygon","name":"polygon","group":"rooms.0","kind":"array","required":false,"description":"The room outline in plot coordinates, 3 to 16 vertices. The quarter is read from the area centroid against thirds of the plot, so an L-shaped room lands where its mass is rather than where its corners are. Send this or direction, never both.","example":[{"x":20,"y":2},{"x":28,"y":2},{"x":28,"y":12},{"x":20,"y":12}]}],"hasLang":true,"repeats":[{"key":"rooms","min":1,"max":24}],"requiredAnyOf":[["facing"],["facingDegrees"]],"groups":[{"key":"plot","label":"Plot"},{},{"key":"rooms.0","label":"Rooms 1"}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Check room placement","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":true,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":true,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":true,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"rooms.0.type","name":"type","group":"rooms.0","kind":"tiles","required":true,"description":"What the room is, one of puja, kitchen, master-bedroom, bedroom, living, dining, study, toilet, store, staircase, water-storage, entrance. Case and punctuation are folded, so Master Bedroom and master_bedroom both resolve. Four of the twelve carry a verse and the rest carry convention, and the response says which.","enum":["puja","kitchen","master-bedroom","bedroom","living","dining","study","toilet","store","staircase","water-storage","entrance"],"example":"kitchen"},{"key":"rooms.0.direction","name":"direction","group":"rooms.0","kind":"tiles","required":true,"description":"Which quarter of the plot the room sits in, if you already know it. Send this or polygon, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast"},{"key":"rooms.0.polygon","name":"polygon","group":"rooms.0","kind":"array","required":false,"description":"The room outline in plot coordinates, 3 to 16 vertices. The quarter is read from the area centroid against thirds of the plot, so an L-shaped room lands where its mass is rather than where its corners are. Send this or direction, never both.","example":[{"x":20,"y":2},{"x":28,"y":2},{"x":28,"y":12},{"x":20,"y":12}]}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"repeats":[{"key":"rooms","min":1,"max":24}],"requiredAnyOf":[["facing"],["facingDegrees"]],"groups":[{"key":"plot","label":"Plot"},{},{"key":"rooms.0","label":"Rooms 1"}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Find griha pravesh dates","fields":[{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search window, in YYYY-MM-DD. Every limb is read at sunrise of the local day, because the Hindu day begins at sunrise rather than at midnight.","example":"2027-01-20"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search window, in YYYY-MM-DD, inclusive. The window is capped at 93 days, which is a full season and the same cap the Vedic auspicious day search carries.","example":"2027-03-20"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the house, in decimal degrees, positive north. Sunrise decides where one day ends and the next begins, so a nakshatra running out during the morning changes which day it counts for.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the house, in decimal degrees, positive east.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"muhurtaText","name":"muhurtaText","kind":"tiles","required":false,"description":"Which Muhurta text supplies the admissible nakshatras for entering a new house. muhurta-chintamani admits eight and kalaprakasika admits twelve; seven overlap and are the high confidence core, one is unique to the first and five to the second. The two texts are independent witnesses, which is what makes the overlap strong and the difference worth exposing. Defaults to muhurta-chintamani.","enum":["muhurta-chintamani","kalaprakasika"],"default":"muhurta-chintamani","example":"muhurta-chintamani","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Find griha pravesh dates","fields":[{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search window, in YYYY-MM-DD. Every limb is read at sunrise of the local day, because the Hindu day begins at sunrise rather than at midnight.","example":"2027-01-20"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search window, in YYYY-MM-DD, inclusive. The window is capped at 93 days, which is a full season and the same cap the Vedic auspicious day search carries.","example":"2027-03-20"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the house, in decimal degrees, positive north. Sunrise decides where one day ends and the next begins, so a nakshatra running out during the morning changes which day it counts for.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the house, in decimal degrees, positive east.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"muhurtaText","name":"muhurtaText","kind":"tiles","required":false,"description":"Which Muhurta text supplies the admissible nakshatras for entering a new house. muhurta-chintamani admits eight and kalaprakasika admits twelve; seven overlap and are the high confidence core, one is unique to the first and five to the second. The two texts are independent witnesses, which is what makes the overlap strong and the difference worth exposing. Defaults to muhurta-chintamani.","enum":["muhurta-chintamani","kalaprakasika"],"default":"muhurta-chintamani","example":"muhurta-chintamani","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get the twelve Arudha padas","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get the twelve Arudha padas","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get Ashtakavarga (planetary strength) analysis","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Ashtakavarga (planetary strength) analysis","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Monthly Lunar Aspects","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly analysis (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":2},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Monthly Lunar Aspects","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly analysis (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":2},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Monthly Planetary Aspects","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly analysis (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":2},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Monthly Planetary Aspects","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly analysis (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":2},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 once, at the start of the window, and that offset applies to every time in the response. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get planetary aspects (Drishti)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. Planetary positions are calculated for this date to determine mutual aspects (drishti).","example":"2026-02-03"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in HH:MM:SS format (24-hour). Exact time affects fast-moving planets (Moon, Mercury) and aspect orbs.","example":"12:00:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Used for Lagna calculation which affects house-based aspect analysis.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local sidereal time for positional calculations.","min":-180,"max":180,"example":78.486671,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get planetary aspects (Drishti)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. Planetary positions are calculated for this date to determine mutual aspects (drishti).","example":"2026-02-03"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in HH:MM:SS format (24-hour). Exact time affects fast-moving planets (Moon, Mercury) and aspect orbs.","example":"12:00:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Used for Lagna calculation which affects house-based aspect analysis.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local sidereal time for positional calculations.","min":-180,"max":180,"example":78.486671,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get the Bhav Chalit (Chalit Kundli) cusp-based house chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get the Bhav Chalit (Chalit Kundli) cusp-based house chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get Bhava Bala (house strength) for all twelve houses","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Bhava Bala (house strength) for all twelve houses","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get birth chart (D1 Rashi chart)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"avasthaInfo","name":"avasthaInfo","kind":"toggle","required":false,"description":"Set true to include a localized meaning and one-sentence classical interpretation beside each graha avastha state, under avasthaInfo on that graha in meta. Defaults to false, so an existing integration is byte-identical until it opts in. Saves a second call to GET /avasthas and the client-side join that would otherwise be needed to turn Yuva or Swapna into readable text.","default":false,"example":true,"fold":true},{"key":"modernPlanets","name":"modernPlanets","kind":"toggle","required":false,"description":"Set true to also return Uranus, Neptune and Pluto, under the Sanskrit names Arun, Varun and Yam that Indian software prints for them. They arrive in a separate modernPlanets array, NOT inside meta, because classical Jyotish is defined over nine grahas: the moderns rule no sign, so they have no dignity, avastha, combustion or aspect strength and it would be fabrication to report one. Each carries longitude, rashi, degree in sign, nakshatra with pada and lord, and retrograde status. Defaults to false, so an existing integration is byte-identical until it opts in.","default":false,"example":true,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get birth chart (D1 Rashi chart)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"avasthaInfo","name":"avasthaInfo","kind":"toggle","required":false,"description":"Set true to include a localized meaning and one-sentence classical interpretation beside each graha avastha state, under avasthaInfo on that graha in meta. Defaults to false, so an existing integration is byte-identical until it opts in. Saves a second call to GET /avasthas and the client-side join that would otherwise be needed to turn Yuva or Swapna into readable text.","default":false,"example":true,"fold":true},{"key":"modernPlanets","name":"modernPlanets","kind":"toggle","required":false,"description":"Set true to also return Uranus, Neptune and Pluto, under the Sanskrit names Arun, Varun and Yam that Indian software prints for them. They arrive in a separate modernPlanets array, NOT inside meta, because classical Jyotish is defined over nine grahas: the moderns rule no sign, so they have no dignity, avastha, combustion or aspect strength and it would be fabrication to report one. Each carries longitude, rashi, degree in sign, nakshatra with pada and lord, and retrograde status. Defaults to false, so an existing integration is byte-identical until it opts in.","default":false,"example":true,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get Chara Karakas including Atmakaraka","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"scheme","name":"scheme","kind":"tiles","required":false,"description":"Which Chara Karaka scheme to rank. \"eight\" includes Rahu, counting its degree in reverse because it moves retrograde, and returns eight offices including Pitrikaraka. \"seven\" ranks only the seven classical grahas and drops Pitrikaraka. Ketu is excluded from both, since it always mirrors the Rahu degree exactly. The two schemes can produce a different Atmakaraka for the same chart, so select the one your reference software uses. Defaults to \"eight\".","enum":["seven","eight"],"default":"eight","example":"eight","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Chara Karakas including Atmakaraka","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"scheme","name":"scheme","kind":"tiles","required":false,"description":"Which Chara Karaka scheme to rank. \"eight\" includes Rahu, counting its degree in reverse because it moves retrograde, and returns eight offices including Pitrikaraka. \"seven\" ranks only the seven classical grahas and drops Pitrikaraka. Ketu is excluded from both, since it always mirrors the Rahu degree exactly. The two schemes can produce a different Atmakaraka for the same chart, so select the one your reference software uses. Defaults to \"eight\".","enum":["seven","eight"],"default":"eight","example":"eight","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate ten porutham match","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate ten porutham match","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Compare malefic affliction","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Compare malefic affliction","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"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 Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Daily Reading","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Fixes the Janma Rashi and Janma Nakshatra every part of this reading is counted from, and the natal Ashtakavarga the bindu gate reads.","example":"1984-11-03"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). The Moon moves about half a degree an hour, so an error here moves the Janma Rashi and Janma Nakshatra and therefore every gochara house count, the tarabala and the chandrabala in this response.","example":"01:35:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Sets the natal house cusps behind the Ashtakavarga scorecard and the KP significators, and the sunrise that opens the panchanga day.","min":-90,"max":90,"example":28.8944,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local sidereal time for the natal cusps and the sunrise the reading is composed at.","min":-180,"max":180,"example":76.5894,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\") OR decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). IANA strings are resolved twice, each to the DST-correct offset of its own moment: at the birth date and time for the birth chart, and on the date being read for the reading day. A decimal is applied to both as sent. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, in YYYY-MM-DD format. Defaults to today (UTC). The panchanga day it names runs from sunrise at the birth coordinates to the next sunrise, not from midnight, so a reading for this date covers the night that follows it.","example":"2026-06-21","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu. \"mean\" uses the smooth mean node, which is the traditional Vedic default and what printed panchangs use. \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean and can therefore move a node into a different rashi and change its gochara house. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Daily Reading","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Fixes the Janma Rashi and Janma Nakshatra every part of this reading is counted from, and the natal Ashtakavarga the bindu gate reads.","example":"1984-11-03"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). The Moon moves about half a degree an hour, so an error here moves the Janma Rashi and Janma Nakshatra and therefore every gochara house count, the tarabala and the chandrabala in this response.","example":"01:35:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Sets the natal house cusps behind the Ashtakavarga scorecard and the KP significators, and the sunrise that opens the panchanga day.","min":-90,"max":90,"example":28.8944,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local sidereal time for the natal cusps and the sunrise the reading is composed at.","min":-180,"max":180,"example":76.5894,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\") OR decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). IANA strings are resolved twice, each to the DST-correct offset of its own moment: at the birth date and time for the birth chart, and on the date being read for the reading day. A decimal is applied to both as sent. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, in YYYY-MM-DD format. Defaults to today (UTC). The panchanga day it names runs from sunrise at the birth coordinates to the next sunrise, not from midnight, so a reading for this date covers the night that follows it.","example":"2026-06-21","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu. \"mean\" uses the smooth mean node, which is the traditional Vedic default and what printed panchangs use. \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean and can therefore move a node into a different rashi and change its gochara house. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. 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.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone, an IANA name resolved at this datetime rather than at the birth (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-08-23T13:47:46Z","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. 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.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone, an IANA name resolved at this datetime rather than at the birth (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-08-23T13:47:46Z","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get all 9 Mahadasha periods (120-year cycle)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. 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.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get all 9 Mahadasha periods (120-year cycle)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"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 the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"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.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. 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.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"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 twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|