@roxyapi/ui 1.1.3 → 1.3.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 +39 -1
- package/README.md +82 -1
- package/THEMING.md +34 -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 +18 -19
- 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/report.js +50 -0
- 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 +9 -10
- 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 +49 -48
- 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/report.d.ts +61 -0
- package/dist/components/report.js +1 -0
- 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/endpoint-defaults.d.ts +1 -0
- 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.d.ts +1 -0
- package/dist/index.js +111 -94
- 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--reports-bazi.json +1 -0
- package/dist/schemas/post--reports-human-design.json +1 -0
- package/dist/schemas/post--reports-kundli.json +1 -0
- package/dist/schemas/post--reports-matchmaking.json +1 -0
- package/dist/schemas/post--reports-natal.json +1 -0
- package/dist/schemas/post--reports-numerology.json +1 -0
- package/dist/schemas/post--reports-synastry.json +1 -0
- package/dist/schemas/post--reports-tarot.json +1 -0
- package/dist/schemas/post--reports-yearly-forecast.json +1 -0
- 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/types/index.d.ts +1 -1
- package/dist/types/types.gen.d.ts +17614 -15166
- 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 +25 -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/object-url.d.ts +17 -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":"Get KP planetary positions with sub-lords","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Accepted at any latitude, polar included: planet longitudes are geocentric and the star and sub lords are divisions of longitude, so no house cusp is involved.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","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 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","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":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get KP planetary positions with sub-lords","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Accepted at any latitude, polar included: planet longitudes are geocentric and the star and sub lords are divisions of longitude, so no house cusp is involved.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","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 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","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":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Find KP rasi ingress times","fields":[{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Sun"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-12-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Find KP rasi ingress times","fields":[{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Sun"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-12-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get KP ruling planets with significators at intervals","fields":[{"key":"startDatetime","name":"startDatetime","kind":"datetime","required":true,"description":"Start of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T00:00:00Z"},{"key":"endDatetime","name":"endDatetime","kind":"datetime","required":true,"description":"End of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T01:00:00Z"},{"key":"intervalMinutes","name":"intervalMinutes","kind":"number","required":true,"description":"Interval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.","min":1,"max":1440,"example":5},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","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 once, at the start of the window, and that offset applies to every time in the response. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. 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 KP ruling planets with significators at intervals","fields":[{"key":"startDatetime","name":"startDatetime","kind":"datetime","required":true,"description":"Start of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T00:00:00Z"},{"key":"endDatetime","name":"endDatetime","kind":"datetime","required":true,"description":"End of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T01:00:00Z"},{"key":"intervalMinutes","name":"intervalMinutes","kind":"number","required":true,"description":"Interval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.","min":1,"max":1440,"example":5},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","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 once, at the start of the window, and that offset applies to every time in the response. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. 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 KP ruling planets with optional significators","fields":[{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Any latitude for the ruling planets alone; with birthDate and birthTime the significators read Placidus cusps, so the latitude must lie below 66.56 degrees north or south and a polar latitude returns 400.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. An IANA name is resolved to the DST-correct offset of each moment separately: at datetime for the ruling planets, and at birthDate and birthTime for the significators. 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":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T10:30:00Z","fold":true},{"key":"birthDate","name":"birthDate","kind":"date","required":false,"description":"Birth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.","example":"1990-07-04","fold":true},{"key":"birthTime","name":"birthTime","kind":"time","required":false,"description":"Birth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.","example":"10:12:00","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. 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 KP ruling planets with optional significators","fields":[{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Any latitude for the ruling planets alone; with birthDate and birthTime the significators read Placidus cusps, so the latitude must lie below 66.56 degrees north or south and a polar latitude returns 400.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. An IANA name is resolved to the DST-correct offset of each moment separately: at datetime for the ruling planets, and at birthDate and birthTime for the significators. 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":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T10:30:00Z","fold":true},{"key":"birthDate","name":"birthDate","kind":"date","required":false,"description":"Birth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.","example":"1990-07-04","fold":true},{"key":"birthTime","name":"birthTime","kind":"time","required":false,"description":"Birth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.","example":"10:12:00","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. 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":"Find KP sublord changes","fields":[{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Moon"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-01-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Find KP sublord changes","fields":[{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet to track (case-insensitive). Valid values: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn","enum":["Sun","Moon","Mars","Mercury","Jupiter","Venus","Saturn"],"example":"Moon"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First day of the search (YYYY-MM-DD), a calendar day in `timezone`.","example":"2025-01-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last day of the search, inclusive (YYYY-MM-DD), a calendar day in `timezone`. Not before startDate, at most 365 days after it.","example":"2025-01-31"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\"), a fixed offset like \"+05:30\", OR decimal hours from UTC. One offset is taken from startDate (DST-correct for that date) and used for the whole range, so a window crossing a daylight-saving change is read on the earlier offset throughout; send a fixed offset if you need that explicit. The two dates are read as calendar days in this timezone and output times are converted to it, so one date with 5.5 is that whole Indian day. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get Navamsa chart (D9)","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 Navamsa chart (D9)","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 basic Panchang","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. Panchang elements (Tithi, Nakshatra, Yoga, Karana) are calculated for this date.","example":"2025-12-17"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in HH:MM:SS format (24-hour). Determines the exact Moon and Sun positions for tithi and nakshatra calculation.","example":"12:00:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise/sunset times which define the Vara (weekday) and muhurta boundaries.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise/sunset-dependent panchang elements.","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 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get basic Panchang","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. Panchang elements (Tithi, Nakshatra, Yoga, Karana) are calculated for this date.","example":"2025-12-17"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in HH:MM:SS format (24-hour). Determines the exact Moon and Sun positions for tithi and nakshatra calculation.","example":"12:00:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise/sunset times which define the Vara (weekday) and muhurta boundaries.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise/sunset-dependent panchang elements.","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 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"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 Choghadiya","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","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 time calculations for sunrise, sunset, and muhurta period boundaries.","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. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Choghadiya periods outside IST. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Choghadiya","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","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 time calculations for sunrise, sunset, and muhurta period boundaries.","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. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Choghadiya periods outside IST. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get detailed Panchang with Rahu Kaal, Yamaganda, Gulika","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.","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. Send the timezone that matches the coordinates: sunrise, sunset and every muhurta boundary are found by searching forward from local midnight, so the default anchors the search to an Indian day. Omitting it for a location outside IST returns a correctly ordered set of periods for the wrong window, shifted by the difference between 5.5 and the real offset. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get detailed Panchang with Rahu Kaal, Yamaganda, Gulika","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local time calculations for sunrise, sunset, and muhurta period boundaries.","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. Send the timezone that matches the coordinates: sunrise, sunset and every muhurta boundary are found by searching forward from local midnight, so the default anchors the search to an Indian day. Omitting it for a location outside IST returns a correctly ordered set of periods for the wrong window, shifted by the difference between 5.5 and the real offset. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"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 Hora","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","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 time calculations for sunrise, sunset, and muhurta period boundaries.","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. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Hora periods outside IST. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Hora","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. A single-digit month or day is accepted and zero-padded (2026-3-5 becomes 2026-03-05). Impossible calendar dates are rejected. Calculations that read planetary positions support 1550-01-02 to 2650-01-22; outside that span they answer 400 with code date_out_of_range, and a calculation that reads a window around the date (a sunrise search, a run of days) may answer the same 400 for a date within a few days of either end.","example":"2026-02-03"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines sunrise and sunset times which define day/night boundaries for muhurta calculations.","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 time calculations for sunrise, sunset, and muhurta period boundaries.","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. Used for accurate sunrise/sunset calculation and output time formatting. Essential for correct Hora periods outside IST. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Monthly Declination Parallels","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly parallel 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) for parallel analysis. 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}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Monthly Declination Parallels","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly parallel 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) for parallel analysis. 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}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Declination Parallels","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects.","example":"2026-02-03"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon.","example":"12:00:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees, part of the birth record. Declinations are geocentric, as every published ephemeris prints them, so it does not move them.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees, part of the birth record. Declinations are geocentric, so it does not move them; the instant comes from date, time and timezone.","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":"orb","name":"orb","kind":"number","required":false,"description":"Orb in degrees for parallel/contraparallel detection. Defaults to 1.5°.","min":0.5,"max":3,"default":1.5,"example":1.5,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Declination Parallels","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format. Planetary declinations are calculated for this date to find parallel and contraparallel aspects.","example":"2026-02-03"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in HH:MM:SS format (24-hour). Exact time affects declination values, especially for the fast-moving Moon.","example":"12:00:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees, part of the birth record. Declinations are geocentric, as every published ephemeris prints them, so it does not move them.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees, part of the birth record. Declinations are geocentric, so it does not move them; the instant comes from date, time and timezone.","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":"orb","name":"orb","kind":"number","required":false,"description":"Orb in degrees for parallel/contraparallel detection. Defaults to 1.5°.","min":0.5,"max":3,"default":1.5,"example":1.5,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Monthly Ephemeris","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly ephemeris (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) for ephemeris. Defaults to the current month (UTC).","min":1,"max":12,"example":2},{"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 Ephemeris","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly ephemeris (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) for ephemeris. Defaults to the current month (UTC).","min":1,"max":12,"example":2},{"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 positions","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 planetary positions","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 Shadbala (six-fold 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":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get Shadbala (six-fold 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":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":"Monthly Transit","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly transit 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) for transit analysis. 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 Transit","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for monthly transit 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) for transit analysis. 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":"Transit Analysis","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.","example":"1990-07-04"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.","example":"10:12:00"},{"key":"transitDate","name":"transitDate","kind":"date","required":true,"description":"Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.","example":"2026-02-03"},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.","example":"12:00:00","fold":true},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.","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 Lagna and house 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. The birth moment and the transit moment are each resolved at their own 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":"Transit Analysis","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.","example":"1990-07-04"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.","example":"10:12:00"},{"key":"transitDate","name":"transitDate","kind":"date","required":true,"description":"Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.","example":"2026-02-03"},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.","example":"12:00:00","fold":true},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.","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 Lagna and house 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. The birth moment and the transit moment are each resolved at their own 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 upagraha (sub-planet) positions","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 upagraha (sub-planet) positions","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":"Detect classical Vedic yogas in a birth 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}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Detect classical Vedic yogas in a birth 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}],"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}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
:where(.bodygraph) .bg-body{fill:color-mix(in srgb,var(--roxy-secondary) 8%,transparent);stroke:var(--roxy-border);stroke-width:1}:where(.bodygraph) .bg-channel{stroke:var(--roxy-border);stroke-width:5;stroke-linecap:round}:where(.bodygraph) .bg-half{stroke-width:5;stroke-linecap:round}:where(.bodygraph) .bg-half.stripe{stroke-linecap:butt;stroke-dasharray:7 7}:where(.bodygraph) .bg-center{fill:var(--_mask, var(--roxy-bg));stroke:var(--roxy-secondary);stroke-width:1.8}:where(.bodygraph) .bg-center.defined{stroke:color-mix(in srgb,var(--roxy-fg) 45%,transparent)}:where(.bodygraph){--_gold: color-mix(in oklch, var(--roxy-warning) 60%, var(--roxy-success));--_gold-ink: color-mix(in oklch, var(--roxy-warning-fg) 60%, var(--roxy-success-fg));--_center-gold: light-dark( color-mix(in oklab, var(--_gold) 40%, var(--roxy-bg)), color-mix(in oklab, var(--_gold) 50%, var(--_gold-ink)) );--_center-green: light-dark( color-mix(in oklab, var(--roxy-success) 40%, var(--roxy-bg)), color-mix(in oklab, var(--roxy-success) 50%, var(--roxy-success-fg)) );--_center-red: light-dark( color-mix(in oklab, var(--roxy-danger) 40%, var(--roxy-bg)), color-mix(in oklab, var(--roxy-danger) 50%, var(--roxy-danger-fg)) );--_center-brown: light-dark( color-mix(in oklab, color-mix(in oklab, var(--roxy-warning-fg) 75%, var(--roxy-fg)) 45%, var(--roxy-bg)), color-mix(in oklab, var(--roxy-warning-fg) 50%, var(--roxy-secondary)) )}:where(.bodygraph) .bg-center.bg-gold.defined,:where(.bodygraph) .legend .swatch.bg-gold{fill:var(--_center-gold);background:var(--_center-gold)}:where(.bodygraph) .bg-center.bg-green.defined,:where(.bodygraph) .legend .swatch.bg-green{fill:var(--_center-green);background:var(--_center-green)}:where(.bodygraph) .bg-center.bg-red.defined,:where(.bodygraph) .legend .swatch.bg-red{fill:var(--_center-red);background:var(--_center-red)}:where(.bodygraph) .bg-center.bg-brown.defined,:where(.bodygraph) .legend .swatch.bg-brown{fill:var(--_center-brown);background:var(--_center-brown)}:where(.bodygraph) .bg-gate-dot{fill:var(--_mask, var(--roxy-bg));stroke:var(--roxy-border);stroke-width:1}:where(.bodygraph) .bg-gate-dot.on{stroke:var(--_mask, var(--roxy-bg))}:where(.bodygraph) .bg-center-name{color:var(--roxy-muted);fill:currentColor;font-weight:var(--roxy-weight-bold);text-transform:uppercase;pointer-events:none}:where(.bodygraph) .bg-center-name.defined{color:light-dark(var(--roxy-fg),var(--roxy-bg))}:where(.bodygraph) .bg-gate{fill:var(--roxy-muted);font-size:calc(var(--roxy-text-base) * 0.50625);font-weight:var(--roxy-weight-bold);font-family:var(--roxy-font-sans)}:where(.bodygraph) .bg-gate.on{fill:var(--src-ink, var(--_mask, var(--roxy-bg)))}:where(.bodygraph) .bg-half.src-left{stroke:var(--src-left, var(--roxy-danger))}:where(.bodygraph) .bg-half.src-right{stroke:var(--src-right, var(--roxy-fg))}:where(.bodygraph) .bg-gate-dot.on.src-left{fill:var(--src-left, var(--roxy-danger))}:where(.bodygraph) .bg-gate-dot.on.src-right{fill:var(--src-right, var(--roxy-fg))}:where(.bodygraph) .legend .swatch.src-left{background:var(--src-left, var(--roxy-danger))}:where(.bodygraph) .legend .swatch.src-right{background:var(--src-right, var(--roxy-fg))}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
:where(.kundli) .line{fill:transparent;stroke:var(--roxy-border)}:where(.kundli) .sign-text{fill:var(--roxy-muted);font-size:calc(var(--roxy-text-base) * 0.6875);font-weight:var(--roxy-weight-normal);font-family:var(--roxy-font-sans);text-transform:uppercase}:where(.kundli) .rashi-num{fill:var(--roxy-muted);font-size:calc(var(--roxy-text-base) * 0.75);font-weight:var(--roxy-weight-normal);font-family:var(--roxy-font-sans)}:where(.kundli) .house-num{fill:var(--roxy-accent-ink);font-size:calc(var(--roxy-text-base) * 0.6875);font-weight:var(--roxy-weight-bold);font-family:var(--roxy-font-sans)}:where(.kundli) .planet-text{fill:var(--roxy-fg);font-size:calc(var(--roxy-text-base) * 0.8125);font-weight:var(--roxy-weight-bold);font-family:var(--roxy-font-sans)}:where(.kundli) .centre-label{fill:var(--roxy-muted);font-size:calc(var(--roxy-text-base) * 0.875);font-weight:var(--roxy-weight-bold);font-family:var(--roxy-font-sans)}:where(.kundli) .lagna-marker{fill:var(--roxy-accent-ink);font-size:calc(var(--roxy-text-base) * 0.625);font-weight:var(--roxy-weight-bold);font-family:var(--roxy-font-sans);text-transform:uppercase}:where(.kundli) .lagna-bg{fill:color-mix(in srgb,var(--roxy-accent) 14%,transparent)}:where(.kundli) .lagna-slash{stroke:var(--roxy-accent);stroke-linecap:round;opacity:0.7}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
.aspect{stroke:var(--_aspect, var(--roxy-muted));stroke-width:0.8;fill:none;opacity:0.55;stroke-opacity:0.7}.aspect-trine,.aspect-sextile{--_aspect: var(--roxy-info);--_aspect-ink: var(--roxy-info-fg)}.aspect-square,.aspect-opposition{--_aspect: var(--roxy-danger);--_aspect-ink: var(--roxy-danger-fg)}.aspect-quincunx,.aspect-semi-sextile{--_aspect: var(--roxy-success);--_aspect-ink: var(--roxy-success-fg)}.aspect-conjunction{--_aspect: var(--roxy-accent-ink);--_aspect-ink: var(--roxy-accent-ink)}:is(.aspect-trine,.aspect-sextile,.aspect-square,.aspect-opposition,.aspect-quincunx,.aspect-semi-sextile,.aspect-conjunction){color:var(--_aspect-ink);stroke-opacity:1}.aspect-swatch{display:inline-block;inline-size:var(--roxy-space-sm);block-size:var(--roxy-space-sm);margin-inline-end:var(--roxy-space-xs);border-radius:var(--roxy-radius-full);background:var(--_aspect);vertical-align:middle}:where(.natal-wheel) .wheel-line,:where(.natal-wheel) .tick{fill:none;stroke:var(--roxy-border)}:where(.natal-wheel) .tick-major{stroke:var(--roxy-secondary)}:where(.natal-wheel) .sign-glyph{fill:var(--roxy-secondary);font-size:calc(var(--roxy-text-base) * 0.875)}:where(.natal-wheel) .planet-glyph{fill:var(--roxy-accent-ink);font-size:calc(var(--roxy-text-base) * 0.875);font-weight:var(--roxy-weight-bold)}:where(.natal-wheel) .planet-deg{fill:var(--roxy-fg);font-size:calc(var(--roxy-text-base) * 0.4375)}:where(.natal-wheel) .planet-deg .retro{fill:var(--roxy-danger-fg)}:where(.natal-wheel) .planet-leader{stroke:var(--roxy-accent);stroke-width:0.5;opacity:0.55}:where(.natal-wheel) .house-num{fill:var(--roxy-muted);font-size:calc(var(--roxy-text-base) * 0.5625)}:where(.natal-wheel) .cusp-deg{fill:var(--roxy-muted);font-size:calc(var(--roxy-text-base) * 0.375)}:where(.natal-wheel) .angle-marker{fill:var(--roxy-accent-ink);font-size:calc(var(--roxy-text-base) * 0.8125);font-weight:var(--roxy-weight-bold)}:where(.natal-wheel) .angle-tick{stroke:var(--roxy-accent-ink);stroke-width:1.5}@container (max-width: 480px){:where(.natal-wheel) .sign-glyph,:where(.natal-wheel) .planet-glyph{font-size:calc(var(--roxy-text-base) * 1.5)}:where(.natal-wheel) .planet-deg{font-size:calc(var(--roxy-text-base) * 0.8125)}:where(.natal-wheel) .house-num{font-size:calc(var(--roxy-text-base) * 0.75)}}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
.aspect{stroke:var(--_aspect, var(--roxy-muted));stroke-width:0.8;fill:none;opacity:0.55;stroke-opacity:0.7}.aspect-trine,.aspect-sextile{--_aspect: var(--roxy-info);--_aspect-ink: var(--roxy-info-fg)}.aspect-square,.aspect-opposition{--_aspect: var(--roxy-danger);--_aspect-ink: var(--roxy-danger-fg)}.aspect-quincunx,.aspect-semi-sextile{--_aspect: var(--roxy-success);--_aspect-ink: var(--roxy-success-fg)}.aspect-conjunction{--_aspect: var(--roxy-accent-ink);--_aspect-ink: var(--roxy-accent-ink)}:is(.aspect-trine,.aspect-sextile,.aspect-square,.aspect-opposition,.aspect-quincunx,.aspect-semi-sextile,.aspect-conjunction){color:var(--_aspect-ink);stroke-opacity:1}.aspect-swatch{display:inline-block;inline-size:var(--roxy-space-sm);block-size:var(--roxy-space-sm);margin-inline-end:var(--roxy-space-xs);border-radius:var(--roxy-radius-full);background:var(--_aspect);vertical-align:middle}:where(.synastry-wheel) .wheel-line{fill:none;stroke:var(--roxy-border)}:where(.synastry-wheel) .p1{--_person: var(--roxy-accent-ink)}:where(.synastry-wheel) .p2{--_person: var(--roxy-fg)}:where(.synastry-wheel) .sign{fill:var(--roxy-secondary);font-size:calc(var(--roxy-text-base) * 0.875)}:where(.synastry-wheel) text.p1,:where(.synastry-wheel) text.p2{fill:var(--_person);font-size:calc(var(--roxy-text-base) * 1.125);font-weight:var(--roxy-weight-bold)}:where(.synastry-wheel) .person-tag,:where(.synastry-wheel) .planet-deg{font-size:calc(var(--roxy-text-base) * 0.625)}:where(.synastry-wheel) .planet-deg{fill:var(--roxy-muted)}:where(.synastry-wheel) .planet-deg .retro{fill:var(--roxy-danger-fg)}:where(.synastry-wheel) .leader{stroke:var(--_person);stroke-width:0.5;opacity:0.7}@container (max-width: 480px){:where(.synastry-wheel) .sign,:where(.synastry-wheel) text.p1,:where(.synastry-wheel) text.p2{font-size:calc(var(--roxy-text-base) * 1.75)}:where(.synastry-wheel) .person-tag,:where(.synastry-wheel) .planet-deg{font-size:calc(var(--roxy-text-base) * 0.9375)}}:where(.synastry-wheel) .asc-tick{stroke:var(--roxy-accent-ink);stroke-width:1.5}:where(.synastry-wheel) .asc-label{fill:var(--roxy-accent-ink);font-size:calc(var(--roxy-text-base) * 0.5625);font-weight:var(--roxy-weight-bold)}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
@font-face{font-family:"Fraunces";font-style:normal;font-weight:400 600;font-display:swap;src:url(./fraunces/fraunces-latin.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:"Fraunces";font-style:normal;font-weight:400 600;font-display:swap;src:url(./fraunces/fraunces-latin-ext.woff2) format("woff2");unicode-range:U+0100-02BA,U+02BD-02C5,U+02C7-02CC,U+02CE-02D7,U+02DD-02FF,U+0304,U+0308,U+0329,U+1D00-1DBF,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:"Jost";font-style:normal;font-weight:400 600;font-display:swap;src:url(./jost/jost-latin.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:"Jost";font-style:normal;font-weight:400 600;font-display:swap;src:url(./jost/jost-latin-ext.woff2) format("woff2");unicode-range:U+0100-02BA,U+02BD-02C5,U+02C7-02CC,U+02CE-02D7,U+02DD-02FF,U+0304,U+0308,U+0329,U+1D00-1DBF,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:"Jost";font-style:normal;font-weight:400 600;font-display:swap;src:url(./jost/jost-cyrillic.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}
|
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
Copyright 2024 The Geist Project Authors (https://github.com/vercel/geist-font) Geist-Italic[wght].ttf: Copyright 2024 The Geist Project Authors (https://github.com/vercel/geist-font)
|
|
2
|
+
|
|
3
|
+
This Font Software is licensed under the SIL Open Font License, Version 1.1.
|
|
4
|
+
This license is copied below, and is also available with a FAQ at:
|
|
5
|
+
http://scripts.sil.org/OFL
|
|
6
|
+
|
|
7
|
+
|
|
8
|
+
-----------------------------------------------------------
|
|
9
|
+
SIL OPEN FONT LICENSE Version 1.1 - 26 February 2007
|
|
10
|
+
-----------------------------------------------------------
|
|
11
|
+
|
|
12
|
+
PREAMBLE
|
|
13
|
+
The goals of the Open Font License (OFL) are to stimulate worldwide
|
|
14
|
+
development of collaborative font projects, to support the font creation
|
|
15
|
+
efforts of academic and linguistic communities, and to provide a free and
|
|
16
|
+
open framework in which fonts may be shared and improved in partnership
|
|
17
|
+
with others.
|
|
18
|
+
|
|
19
|
+
The OFL allows the licensed fonts to be used, studied, modified and
|
|
20
|
+
redistributed freely as long as they are not sold by themselves. The
|
|
21
|
+
fonts, including any derivative works, can be bundled, embedded,
|
|
22
|
+
redistributed and/or sold with any software provided that any reserved
|
|
23
|
+
names are not used by derivative works. The fonts and derivatives,
|
|
24
|
+
however, cannot be released under any other type of license. The
|
|
25
|
+
requirement for fonts to remain under this license does not apply
|
|
26
|
+
to any document created using the fonts or their derivatives.
|
|
27
|
+
|
|
28
|
+
DEFINITIONS
|
|
29
|
+
"Font Software" refers to the set of files released by the Copyright
|
|
30
|
+
Holder(s) under this license and clearly marked as such. This may
|
|
31
|
+
include source files, build scripts and documentation.
|
|
32
|
+
|
|
33
|
+
"Reserved Font Name" refers to any names specified as such after the
|
|
34
|
+
copyright statement(s).
|
|
35
|
+
|
|
36
|
+
"Original Version" refers to the collection of Font Software components as
|
|
37
|
+
distributed by the Copyright Holder(s).
|
|
38
|
+
|
|
39
|
+
"Modified Version" refers to any derivative made by adding to, deleting,
|
|
40
|
+
or substituting -- in part or in whole -- any of the components of the
|
|
41
|
+
Original Version, by changing formats or by porting the Font Software to a
|
|
42
|
+
new environment.
|
|
43
|
+
|
|
44
|
+
"Author" refers to any designer, engineer, programmer, technical
|
|
45
|
+
writer or other person who contributed to the Font Software.
|
|
46
|
+
|
|
47
|
+
PERMISSION & CONDITIONS
|
|
48
|
+
Permission is hereby granted, free of charge, to any person obtaining
|
|
49
|
+
a copy of the Font Software, to use, study, copy, merge, embed, modify,
|
|
50
|
+
redistribute, and sell modified and unmodified copies of the Font
|
|
51
|
+
Software, subject to the following conditions:
|
|
52
|
+
|
|
53
|
+
1) Neither the Font Software nor any of its individual components,
|
|
54
|
+
in Original or Modified Versions, may be sold by itself.
|
|
55
|
+
|
|
56
|
+
2) Original or Modified Versions of the Font Software may be bundled,
|
|
57
|
+
redistributed and/or sold with any software, provided that each copy
|
|
58
|
+
contains the above copyright notice and this license. These can be
|
|
59
|
+
included either as stand-alone text files, human-readable headers or
|
|
60
|
+
in the appropriate machine-readable metadata fields within text or
|
|
61
|
+
binary files as long as those fields can be easily viewed by the user.
|
|
62
|
+
|
|
63
|
+
3) No Modified Version of the Font Software may use the Reserved Font
|
|
64
|
+
Name(s) unless explicit written permission is granted by the corresponding
|
|
65
|
+
Copyright Holder. This restriction only applies to the primary font name as
|
|
66
|
+
presented to the users.
|
|
67
|
+
|
|
68
|
+
4) The name(s) of the Copyright Holder(s) or the Author(s) of the Font
|
|
69
|
+
Software shall not be used to promote, endorse or advertise any
|
|
70
|
+
Modified Version, except to acknowledge the contribution(s) of the
|
|
71
|
+
Copyright Holder(s) and the Author(s) or with their explicit written
|
|
72
|
+
permission.
|
|
73
|
+
|
|
74
|
+
5) The Font Software, modified or unmodified, in part or in whole,
|
|
75
|
+
must be distributed entirely under this license, and must not be
|
|
76
|
+
distributed under any other license. The requirement for fonts to
|
|
77
|
+
remain under this license does not apply to any document created
|
|
78
|
+
using the Font Software.
|
|
79
|
+
|
|
80
|
+
TERMINATION
|
|
81
|
+
This license becomes null and void if any of the above conditions are
|
|
82
|
+
not met.
|
|
83
|
+
|
|
84
|
+
DISCLAIMER
|
|
85
|
+
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
|
|
86
|
+
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
|
|
87
|
+
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
|
|
88
|
+
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
|
|
89
|
+
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
|
|
90
|
+
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
|
|
91
|
+
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
|
|
92
|
+
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
|
|
93
|
+
OTHER DEALINGS IN THE FONT SOFTWARE.
|
|
Binary file
|
|
Binary file
|
|
Binary file
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
@font-face{font-family:"Geist";font-style:normal;font-weight:400 600;font-display:swap;src:url(./geist/geist-latin.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:"Geist";font-style:normal;font-weight:400 600;font-display:swap;src:url(./geist/geist-latin-ext.woff2) format("woff2");unicode-range:U+0100-02BA,U+02BD-02C5,U+02C7-02CC,U+02CE-02D7,U+02DD-02FF,U+0304,U+0308,U+0329,U+1D00-1DBF,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:"Geist";font-style:normal;font-weight:400 600;font-display:swap;src:url(./geist/geist-cyrillic.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}
|
|
@@ -0,0 +1 @@
|
|
|
1
|
+
@font-face{font-family:"Jost";font-style:normal;font-weight:400 600;font-display:swap;src:url(./jost/jost-latin.woff2) format("woff2");unicode-range:U+0000-00FF,U+0131,U+0152-0153,U+02BB-02BC,U+02C6,U+02DA,U+02DC,U+0304,U+0308,U+0329,U+2000-206F,U+20AC,U+2122,U+2191,U+2193,U+2212,U+2215,U+FEFF,U+FFFD}@font-face{font-family:"Jost";font-style:normal;font-weight:400 600;font-display:swap;src:url(./jost/jost-latin-ext.woff2) format("woff2");unicode-range:U+0100-02BA,U+02BD-02C5,U+02C7-02CC,U+02CE-02D7,U+02DD-02FF,U+0304,U+0308,U+0329,U+1D00-1DBF,U+1E00-1E9F,U+1EF2-1EFF,U+2020,U+20A0-20AB,U+20AD-20C0,U+2113,U+2C60-2C7F,U+A720-A7FF}@font-face{font-family:"Jost";font-style:normal;font-weight:400 600;font-display:swap;src:url(./jost/jost-cyrillic.woff2) format("woff2");unicode-range:U+0301,U+0400-045F,U+0490-0491,U+04B0-04B1,U+2116}
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
/** One self-hosted `@font-face` source: a family plus the subset file that carries it. */
|
|
2
|
+
export interface SelfHostedFontFace {
|
|
3
|
+
family: 'Fraunces' | 'Jost' | 'Geist';
|
|
4
|
+
/** Path under `dist/styles/fonts/`, mirrored verbatim on jsDelivr. */
|
|
5
|
+
file: string;
|
|
6
|
+
/** Matches the Google Fonts subset split this replaces, so a page still pays only for the script it renders. */
|
|
7
|
+
unicodeRange: string;
|
|
8
|
+
}
|
|
9
|
+
export type FontKey = 'fraunces-jost' | 'jost' | 'geist' | 'system';
|
|
10
|
+
/** One choosable font pair: the stack for body text and the stack for headings. */
|
|
11
|
+
export interface RoxyFont {
|
|
12
|
+
name: string;
|
|
13
|
+
sans: string;
|
|
14
|
+
display: string;
|
|
15
|
+
}
|
|
16
|
+
/** The font pairs a widget, a report and a plugin may choose, one definition each, published as `fonts[]` in `components-catalog.json`. */
|
|
17
|
+
export declare const ROXY_FONTS: Record<FontKey, RoxyFont>;
|
|
18
|
+
/** The self-hosted families a font pair names in its two stacks; a system pair names none. */
|
|
19
|
+
export declare function fontFamilies(key: FontKey): SelfHostedFontFace['family'][];
|
|
20
|
+
/** The subset files a font pair loads, published beside the pair's stylesheet. */
|
|
21
|
+
export declare function fontFaces(key: FontKey): SelfHostedFontFace[];
|
|
22
|
+
/** `@font-face` rules for subset files served under `base`, the folder that holds each family's directory, one per subset so a page downloads only the script it renders. */
|
|
23
|
+
export declare function fontFaceCss(faces: SelfHostedFontFace[], base: string): string;
|
|
@@ -0,0 +1,3 @@
|
|
|
1
|
+
/** Every theme preset key, kept apart from the palette data so a validator ships none of it; `ROXY_PALETTES` is keyed by exactly these. */
|
|
2
|
+
export declare const PALETTE_NAMES: readonly ['practitioner', 'eucalyptus', 'kiln', 'moonlit', 'celeste'];
|
|
3
|
+
export type PaletteName = (typeof PALETTE_NAMES)[number];
|