@roxyapi/ui 1.1.2 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +21 -1
- package/README.md +43 -1
- package/THEMING.md +32 -13
- package/components-catalog.json +1 -11247
- package/dist/cdn/components/almanac-day.js +3 -4
- package/dist/cdn/components/angel-number-card.js +3 -4
- package/dist/cdn/components/angel-number-lookup.js +3 -4
- package/dist/cdn/components/arudha-padas.js +3 -4
- package/dist/cdn/components/ashtakavarga-grid.js +3 -4
- package/dist/cdn/components/aspects-table.js +3 -4
- package/dist/cdn/components/astrocartography-map.js +9 -10
- package/dist/cdn/components/bazi-chart.js +3 -4
- package/dist/cdn/components/bhav-chalit-table.js +3 -4
- package/dist/cdn/components/bhava-bala-table.js +3 -4
- package/dist/cdn/components/biorhythm-chart.js +3 -4
- package/dist/cdn/components/bodygraph.js +14 -13
- package/dist/cdn/components/chara-karakas.js +3 -4
- package/dist/cdn/components/choghadiya-grid.js +3 -4
- package/dist/cdn/components/compatibility-card.js +3 -4
- package/dist/cdn/components/compound-number.js +3 -4
- package/dist/cdn/components/crystal-card.js +3 -4
- package/dist/cdn/components/crystal-grid.js +3 -4
- package/dist/cdn/components/dasha-timeline.js +3 -4
- package/dist/cdn/components/data.js +3 -4
- package/dist/cdn/components/divisional-chart.js +50 -49
- package/dist/cdn/components/dosha-card.js +3 -4
- package/dist/cdn/components/dosha-constitution.js +3 -4
- package/dist/cdn/components/dream-card.js +3 -4
- package/dist/cdn/components/dream-search.js +3 -4
- package/dist/cdn/components/endpoint-form.js +3 -4
- package/dist/cdn/components/ephemeris-table.js +3 -4
- package/dist/cdn/components/fixed-stars.js +3 -4
- package/dist/cdn/components/flying-star-chart.js +3 -4
- package/dist/cdn/components/forecast-digest.js +3 -4
- package/dist/cdn/components/forecast-timeline.js +3 -4
- package/dist/cdn/components/gematria.js +3 -4
- package/dist/cdn/components/gochara-table.js +3 -4
- package/dist/cdn/components/guna-milan.js +3 -4
- package/dist/cdn/components/hd-connection.js +13 -12
- package/dist/cdn/components/hd-penta.js +16 -17
- package/dist/cdn/components/hd-type-card.js +3 -4
- package/dist/cdn/components/hd-variables.js +3 -4
- package/dist/cdn/components/heliacal-table.js +3 -4
- package/dist/cdn/components/hexagram.js +3 -4
- package/dist/cdn/components/hora-table.js +3 -4
- package/dist/cdn/components/horoscope-card.js +3 -4
- package/dist/cdn/components/kp-chart.js +3 -4
- package/dist/cdn/components/kp-finance-card.js +3 -4
- package/dist/cdn/components/kp-planets-table.js +3 -4
- package/dist/cdn/components/kp-ruling-planets.js +3 -4
- package/dist/cdn/components/kua-card.js +3 -4
- package/dist/cdn/components/local-space-compass.js +6 -7
- package/dist/cdn/components/location-search.js +3 -4
- package/dist/cdn/components/luck-pillars.js +3 -4
- package/dist/cdn/components/mayan-day-sign.js +3 -4
- package/dist/cdn/components/moon-phase.js +3 -4
- package/dist/cdn/components/nakshatra-card.js +3 -4
- package/dist/cdn/components/natal-chart.js +24 -14
- package/dist/cdn/components/numerology-card.js +3 -4
- package/dist/cdn/components/panchang-table.js +3 -4
- package/dist/cdn/components/positions-table.js +3 -4
- package/dist/cdn/components/profection-card.js +3 -4
- package/dist/cdn/components/reference-card.js +3 -4
- package/dist/cdn/components/relocation-wheel.js +24 -14
- package/dist/cdn/components/shadbala-table.js +3 -4
- package/dist/cdn/components/synastry-chart.js +21 -12
- package/dist/cdn/components/tarot-card.js +3 -4
- package/dist/cdn/components/tarot-catalog.js +3 -4
- package/dist/cdn/components/tarot-spread.js +3 -4
- package/dist/cdn/components/transit-wheel.js +10 -11
- package/dist/cdn/components/transits-table.js +3 -4
- package/dist/cdn/components/upagraha-table.js +3 -4
- package/dist/cdn/components/vastu-mandala.js +10 -11
- package/dist/cdn/components/vedic-aspects.js +3 -4
- package/dist/cdn/components/vedic-daily.js +3 -4
- package/dist/cdn/components/vedic-kundli.js +62 -61
- package/dist/cdn/components/vedic-planets-table.js +3 -4
- package/dist/cdn/components/western-planets-table.js +3 -4
- package/dist/cdn/components/yoga-list.js +3 -4
- package/dist/cdn/components/zodiac-card.js +3 -4
- package/dist/cdn/locales/de.js +1 -1
- package/dist/cdn/locales/es.js +1 -1
- package/dist/cdn/locales/fr.js +1 -1
- package/dist/cdn/locales/hi.js +1 -1
- package/dist/cdn/locales/pt.js +1 -1
- package/dist/cdn/locales/ru.js +1 -1
- package/dist/cdn/locales/tr.js +1 -1
- package/dist/cdn/roxy-ui.js +113 -96
- package/dist/cdn/widgets.js +1 -1
- package/dist/charts.cjs +111 -0
- package/dist/charts.d.ts +8 -0
- package/dist/charts.js +111 -0
- package/dist/components/almanac-day.js +1 -1
- package/dist/components/angel-number-card.js +1 -1
- package/dist/components/angel-number-lookup.js +1 -1
- package/dist/components/arudha-padas.js +1 -1
- package/dist/components/ashtakavarga-grid.js +1 -1
- package/dist/components/aspects-table.js +1 -1
- package/dist/components/astrocartography-map.js +5 -5
- package/dist/components/bazi-chart.js +1 -1
- package/dist/components/bhav-chalit-table.js +1 -1
- package/dist/components/bhava-bala-table.js +1 -1
- package/dist/components/biorhythm-chart.js +1 -1
- package/dist/components/bodygraph.d.ts +0 -4
- package/dist/components/bodygraph.js +10 -10
- package/dist/components/chara-karakas.js +1 -1
- package/dist/components/choghadiya-grid.js +1 -1
- package/dist/components/compatibility-card.js +1 -1
- package/dist/components/compound-number.js +1 -1
- package/dist/components/crystal-card.js +1 -1
- package/dist/components/crystal-grid.js +1 -1
- package/dist/components/dasha-timeline.js +1 -1
- package/dist/components/data.js +1 -1
- package/dist/components/divisional-chart.js +60 -60
- package/dist/components/dosha-card.js +1 -1
- package/dist/components/dosha-constitution.js +1 -1
- package/dist/components/dream-card.js +1 -1
- package/dist/components/dream-search.js +1 -1
- package/dist/components/endpoint-form.d.ts +3 -1
- package/dist/components/endpoint-form.js +1 -1
- package/dist/components/ephemeris-table.js +1 -1
- package/dist/components/fixed-stars.js +1 -1
- package/dist/components/flying-star-chart.js +1 -1
- package/dist/components/forecast-digest.js +1 -1
- package/dist/components/forecast-timeline.js +1 -1
- package/dist/components/gematria.js +1 -1
- package/dist/components/gochara-table.js +1 -1
- package/dist/components/guna-milan.js +1 -1
- package/dist/components/hd-connection.js +10 -10
- package/dist/components/hd-penta.js +16 -16
- package/dist/components/hd-type-card.js +1 -1
- package/dist/components/hd-variables.js +1 -1
- package/dist/components/heliacal-table.js +1 -1
- package/dist/components/hexagram.js +1 -1
- package/dist/components/hora-table.js +1 -1
- package/dist/components/horoscope-card.js +1 -1
- package/dist/components/kp-chart.js +1 -1
- package/dist/components/kp-finance-card.js +1 -1
- package/dist/components/kp-planets-table.js +1 -1
- package/dist/components/kp-ruling-planets.js +1 -1
- package/dist/components/kua-card.js +1 -1
- package/dist/components/local-space-compass.js +5 -5
- package/dist/components/location-search.d.ts +1 -0
- package/dist/components/location-search.js +1 -1
- package/dist/components/luck-pillars.js +1 -1
- package/dist/components/mayan-day-sign.js +1 -1
- package/dist/components/moon-phase.js +1 -1
- package/dist/components/nakshatra-card.js +1 -1
- package/dist/components/natal-chart.d.ts +3 -82
- package/dist/components/natal-chart.js +20 -11
- package/dist/components/numerology-card.js +1 -1
- package/dist/components/panchang-table.js +1 -1
- package/dist/components/positions-table.js +1 -1
- package/dist/components/profection-card.js +1 -1
- package/dist/components/reference-card.js +1 -1
- package/dist/components/relocation-wheel.js +20 -11
- package/dist/components/shadbala-table.js +1 -1
- package/dist/components/synastry-chart.d.ts +2 -34
- package/dist/components/synastry-chart.js +17 -9
- package/dist/components/tarot-card.js +1 -1
- package/dist/components/tarot-catalog.js +1 -1
- package/dist/components/tarot-spread.js +1 -1
- package/dist/components/transit-wheel.js +7 -7
- package/dist/components/transits-table.js +1 -1
- package/dist/components/upagraha-table.js +1 -1
- package/dist/components/vastu-mandala.js +9 -9
- package/dist/components/vedic-aspects.js +1 -1
- package/dist/components/vedic-daily.js +1 -1
- package/dist/components/vedic-kundli.js +54 -54
- package/dist/components/vedic-planets-table.js +1 -1
- package/dist/components/western-planets-table.js +1 -1
- package/dist/components/yoga-list.js +1 -1
- package/dist/components/zodiac-card.js +1 -1
- package/dist/forms/labels/de.json +1 -1
- package/dist/forms/labels/en.json +1 -1
- package/dist/forms/labels/es.json +1 -1
- package/dist/forms/labels/fr.json +1 -1
- package/dist/forms/labels/hi.json +1 -1
- package/dist/forms/labels/pt.json +1 -1
- package/dist/forms/labels/ru.json +1 -1
- package/dist/forms/labels/tr.json +1 -1
- package/dist/forms.json +1 -1
- package/dist/generated/field-labels-en.d.ts +1 -1
- package/dist/i18n/chrome-strings.d.ts +1 -1
- package/dist/i18n/lang.d.ts +3 -1
- package/dist/i18n/localized-element.d.ts +4 -0
- package/dist/i18n/registry.d.ts +7 -0
- package/dist/index.cjs +111 -94
- package/dist/index.js +110 -93
- package/dist/locales/de.js +1 -1
- package/dist/locales/es.js +1 -1
- package/dist/locales/field-labels/de.d.ts +1 -1
- package/dist/locales/field-labels/es.d.ts +1 -1
- package/dist/locales/field-labels/fr.d.ts +1 -1
- package/dist/locales/field-labels/hi.d.ts +1 -1
- package/dist/locales/field-labels/pt.d.ts +1 -1
- package/dist/locales/field-labels/ru.d.ts +1 -1
- package/dist/locales/field-labels/tr.d.ts +1 -1
- package/dist/locales/fr.js +1 -1
- package/dist/locales/hi.js +1 -1
- package/dist/locales/pt.js +1 -1
- package/dist/locales/ru.js +1 -1
- package/dist/locales/tr.js +1 -1
- package/dist/manifest.d.ts +3 -5
- package/dist/manifest.json +1 -89
- package/dist/schemas/get--angel-numbers-lookup.json +1 -1
- package/dist/schemas/get--angel-numbers-numbers-number.json +1 -1
- package/dist/schemas/get--angel-numbers-numbers.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-daily.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-monthly.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-weekly.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-yearly.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-calendar-year-month.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-current.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-upcoming.json +1 -1
- package/dist/schemas/get--astrology-planet-meanings-id.json +1 -1
- package/dist/schemas/get--astrology-planet-meanings.json +1 -1
- package/dist/schemas/get--astrology-signs-id.json +1 -1
- package/dist/schemas/get--astrology-signs.json +1 -1
- package/dist/schemas/get--ayurveda-daily.json +1 -1
- package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
- package/dist/schemas/get--ayurveda-doshas.json +1 -1
- package/dist/schemas/get--ayurveda-qualities.json +1 -1
- package/dist/schemas/get--ayurveda-tastes.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-day-date.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-monthly.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-solar-terms-year.json +1 -1
- package/dist/schemas/get--chinese-astrology-elements.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-compatibility-sign1-sign2.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
- package/dist/schemas/get--crystals-birthstone-month.json +1 -1
- package/dist/schemas/get--crystals-chakra-chakra.json +1 -1
- package/dist/schemas/get--crystals-colors.json +1 -1
- package/dist/schemas/get--crystals-element-element.json +1 -1
- package/dist/schemas/get--crystals-id.json +1 -1
- package/dist/schemas/get--crystals-pairings-id.json +1 -1
- package/dist/schemas/get--crystals-planets.json +1 -1
- package/dist/schemas/get--crystals-random.json +1 -1
- package/dist/schemas/get--crystals-search.json +1 -1
- package/dist/schemas/get--crystals-zodiac-sign.json +1 -1
- package/dist/schemas/get--crystals.json +1 -1
- package/dist/schemas/get--dreams-symbols-id.json +1 -1
- package/dist/schemas/get--dreams-symbols-letters.json +1 -1
- package/dist/schemas/get--dreams-symbols-random.json +1 -1
- package/dist/schemas/get--dreams-symbols.json +1 -1
- package/dist/schemas/get--feng-shui-afflictions-year.json +1 -1
- package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
- package/dist/schemas/get--feng-shui-bagua.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-annual-year.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-monthly.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-stars.json +1 -1
- package/dist/schemas/get--feng-shui-kua-number.json +1 -1
- package/dist/schemas/get--feng-shui-periods.json +1 -1
- package/dist/schemas/get--human-design-centers-id.json +1 -1
- package/dist/schemas/get--human-design-gates-number.json +1 -1
- package/dist/schemas/get--iching-cast.json +1 -1
- package/dist/schemas/get--iching-hexagrams-lookup.json +1 -1
- package/dist/schemas/get--iching-hexagrams-number.json +1 -1
- package/dist/schemas/get--iching-hexagrams-random.json +1 -1
- package/dist/schemas/get--iching-hexagrams.json +1 -1
- package/dist/schemas/get--iching-trigrams-id.json +1 -1
- package/dist/schemas/get--iching-trigrams.json +1 -1
- package/dist/schemas/get--kabbalah-ciphers.json +1 -1
- package/dist/schemas/get--kabbalah-daily.json +1 -1
- package/dist/schemas/get--kabbalah-letters-id.json +1 -1
- package/dist/schemas/get--kabbalah-letters.json +1 -1
- package/dist/schemas/get--kabbalah-names-number.json +1 -1
- package/dist/schemas/get--kabbalah-names.json +1 -1
- package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
- package/dist/schemas/get--kabbalah-tree.json +1 -1
- package/dist/schemas/get--languages-field-labels.json +1 -1
- package/dist/schemas/get--languages.json +1 -1
- package/dist/schemas/get--location-countries-iso2.json +1 -1
- package/dist/schemas/get--location-countries.json +1 -1
- package/dist/schemas/get--location-search.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-daily.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas-number.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-calendar-monthly.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-daily.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas-number.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas.json +1 -1
- package/dist/schemas/get--numerology-compound-number-number.json +1 -1
- package/dist/schemas/get--numerology-meanings-number.json +1 -1
- package/dist/schemas/get--tarot-cards-id.json +1 -1
- package/dist/schemas/get--tarot-cards.json +1 -1
- package/dist/schemas/get--usage.json +1 -1
- package/dist/schemas/get--vastu-devatas-id.json +1 -1
- package/dist/schemas/get--vastu-devatas.json +1 -1
- package/dist/schemas/get--vastu-directions-id.json +1 -1
- package/dist/schemas/get--vastu-directions.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas.json +1 -1
- package/dist/schemas/get--vedic-astrology-kp-ayanamsa.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga.json +1 -1
- package/dist/schemas/post--angel-numbers-daily.json +1 -1
- package/dist/schemas/post--astrology-arabic-lots.json +1 -1
- package/dist/schemas/post--astrology-aspect-patterns.json +1 -1
- package/dist/schemas/post--astrology-aspects-monthly.json +1 -1
- package/dist/schemas/post--astrology-aspects.json +1 -1
- package/dist/schemas/post--astrology-asteroids.json +1 -1
- package/dist/schemas/post--astrology-astrocartography.json +1 -1
- package/dist/schemas/post--astrology-compatibility-score.json +1 -1
- package/dist/schemas/post--astrology-composite-chart.json +1 -1
- package/dist/schemas/post--astrology-ecliptic-crossings.json +1 -1
- package/dist/schemas/post--astrology-fixed-stars.json +1 -1
- package/dist/schemas/post--astrology-houses.json +1 -1
- package/dist/schemas/post--astrology-lilith.json +1 -1
- package/dist/schemas/post--astrology-local-space.json +1 -1
- package/dist/schemas/post--astrology-lunar-return.json +1 -1
- package/dist/schemas/post--astrology-natal-chart.json +1 -1
- package/dist/schemas/post--astrology-parallels-monthly.json +1 -1
- package/dist/schemas/post--astrology-planetary-returns.json +1 -1
- package/dist/schemas/post--astrology-planets-monthly.json +1 -1
- package/dist/schemas/post--astrology-planets.json +1 -1
- package/dist/schemas/post--astrology-profections.json +1 -1
- package/dist/schemas/post--astrology-progressions.json +1 -1
- package/dist/schemas/post--astrology-relocation-chart.json +1 -1
- package/dist/schemas/post--astrology-solar-arc.json +1 -1
- package/dist/schemas/post--astrology-solar-return.json +1 -1
- package/dist/schemas/post--astrology-synastry.json +1 -1
- package/dist/schemas/post--astrology-transit-aspects.json +1 -1
- package/dist/schemas/post--astrology-transits-monthly.json +1 -1
- package/dist/schemas/post--astrology-transits.json +1 -1
- package/dist/schemas/post--ayurveda-constitution.json +1 -1
- package/dist/schemas/post--ayurveda-dinacharya.json +1 -1
- package/dist/schemas/post--ayurveda-ritucharya.json +1 -1
- package/dist/schemas/post--biorhythm-compatibility.json +1 -1
- package/dist/schemas/post--biorhythm-critical-days.json +1 -1
- package/dist/schemas/post--biorhythm-daily.json +1 -1
- package/dist/schemas/post--biorhythm-forecast.json +1 -1
- package/dist/schemas/post--biorhythm-phases.json +1 -1
- package/dist/schemas/post--biorhythm-reading.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-annual-forecast.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-chart.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-day-master.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-luck-pillars.json +1 -1
- package/dist/schemas/post--chinese-astrology-calendar-auspicious-days.json +1 -1
- package/dist/schemas/post--chinese-astrology-calendar-lunar-date.json +1 -1
- package/dist/schemas/post--chinese-astrology-zodiac-sign.json +1 -1
- package/dist/schemas/post--crystals-daily.json +1 -1
- package/dist/schemas/post--dreams-daily.json +1 -1
- package/dist/schemas/post--feng-shui-eight-mansions.json +1 -1
- package/dist/schemas/post--feng-shui-flying-stars-natal.json +1 -1
- package/dist/schemas/post--feng-shui-kua.json +1 -1
- package/dist/schemas/post--forecast-digest.json +1 -1
- package/dist/schemas/post--forecast-significant-dates.json +1 -1
- package/dist/schemas/post--forecast-solar-return.json +1 -1
- package/dist/schemas/post--forecast-timeline.json +1 -1
- package/dist/schemas/post--forecast-transits.json +1 -1
- package/dist/schemas/post--human-design-bodygraph.json +1 -1
- package/dist/schemas/post--human-design-centers.json +1 -1
- package/dist/schemas/post--human-design-channels.json +1 -1
- package/dist/schemas/post--human-design-connection.json +1 -1
- package/dist/schemas/post--human-design-gates.json +1 -1
- package/dist/schemas/post--human-design-penta.json +1 -1
- package/dist/schemas/post--human-design-profile.json +1 -1
- package/dist/schemas/post--human-design-transit.json +1 -1
- package/dist/schemas/post--human-design-type.json +1 -1
- package/dist/schemas/post--human-design-variables.json +1 -1
- package/dist/schemas/post--iching-daily-cast.json +1 -1
- package/dist/schemas/post--iching-daily.json +1 -1
- package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
- package/dist/schemas/post--kabbalah-compatibility.json +1 -1
- package/dist/schemas/post--kabbalah-gematria.json +1 -1
- package/dist/schemas/post--kabbalah-name-profile.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-aztec-tonalpohualli.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-chart.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-long-count-convert.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-tzolkin.json +1 -1
- package/dist/schemas/post--numerology-birth-day.json +1 -1
- package/dist/schemas/post--numerology-bridge.json +1 -1
- package/dist/schemas/post--numerology-business-name.json +1 -1
- package/dist/schemas/post--numerology-chaldean.json +1 -1
- package/dist/schemas/post--numerology-chart.json +1 -1
- package/dist/schemas/post--numerology-compatibility.json +1 -1
- package/dist/schemas/post--numerology-daily.json +1 -1
- package/dist/schemas/post--numerology-dual.json +1 -1
- package/dist/schemas/post--numerology-expression.json +1 -1
- package/dist/schemas/post--numerology-karmic-debt.json +1 -1
- package/dist/schemas/post--numerology-karmic-lessons.json +1 -1
- package/dist/schemas/post--numerology-life-path.json +1 -1
- package/dist/schemas/post--numerology-maturity.json +1 -1
- package/dist/schemas/post--numerology-personal-day.json +1 -1
- package/dist/schemas/post--numerology-personal-month.json +1 -1
- package/dist/schemas/post--numerology-personal-year.json +1 -1
- package/dist/schemas/post--numerology-personality.json +1 -1
- package/dist/schemas/post--numerology-soul-urge.json +1 -1
- package/dist/schemas/post--tarot-daily.json +1 -1
- package/dist/schemas/post--tarot-draw.json +1 -1
- package/dist/schemas/post--tarot-spreads-career.json +1 -1
- package/dist/schemas/post--tarot-spreads-celtic-cross.json +1 -1
- package/dist/schemas/post--tarot-spreads-custom.json +1 -1
- package/dist/schemas/post--tarot-spreads-love.json +1 -1
- package/dist/schemas/post--tarot-spreads-three-card.json +1 -1
- package/dist/schemas/post--tarot-yes-no.json +1 -1
- package/dist/schemas/post--vastu-ayadi.json +1 -1
- package/dist/schemas/post--vastu-entrance.json +1 -1
- package/dist/schemas/post--vastu-mandala.json +1 -1
- package/dist/schemas/post--vastu-plot.json +1 -1
- package/dist/schemas/post--vastu-rooms.json +1 -1
- package/dist/schemas/post--vastu-timing-griha-pravesh.json +1 -1
- package/dist/schemas/post--vedic-astrology-arudha.json +1 -1
- package/dist/schemas/post--vedic-astrology-ashtakavarga.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects-lunar.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects.json +1 -1
- package/dist/schemas/post--vedic-astrology-bhav-chalit.json +1 -1
- package/dist/schemas/post--vedic-astrology-bhava-bala.json +1 -1
- package/dist/schemas/post--vedic-astrology-birth-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-chara-karakas.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
- package/dist/schemas/post--vedic-astrology-daily.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-divisional-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-kalsarpa.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-manglik.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-sadhesati.json +1 -1
- package/dist/schemas/post--vedic-astrology-ecliptic-crossings.json +1 -1
- package/dist/schemas/post--vedic-astrology-heliacal.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-rasi-changes.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-sublord-changes.json +1 -1
- package/dist/schemas/post--vedic-astrology-navamsa.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-basic.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-choghadiya.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-detailed.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-hora.json +1 -1
- package/dist/schemas/post--vedic-astrology-parallels-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-parallels.json +1 -1
- package/dist/schemas/post--vedic-astrology-planetary-positions-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-planetary-positions.json +1 -1
- package/dist/schemas/post--vedic-astrology-shadbala.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit.json +1 -1
- package/dist/schemas/post--vedic-astrology-upagraha.json +1 -1
- package/dist/schemas/post--vedic-astrology-yoga-detect.json +1 -1
- package/dist/styles/charts/bodygraph.css +1 -0
- package/dist/styles/charts/kundli.css +1 -0
- package/dist/styles/charts/natal-wheel.css +1 -0
- package/dist/styles/charts/synastry-wheel.css +1 -0
- package/dist/styles/fonts/fraunces-jost.css +1 -0
- package/dist/styles/fonts/geist/OFL.txt +93 -0
- package/dist/styles/fonts/geist/geist-cyrillic.woff2 +0 -0
- package/dist/styles/fonts/geist/geist-latin-ext.woff2 +0 -0
- package/dist/styles/fonts/geist/geist-latin.woff2 +0 -0
- package/dist/styles/fonts/geist.css +1 -0
- package/dist/styles/fonts/jost.css +1 -0
- package/dist/styles/fonts.d.ts +23 -0
- package/dist/styles/palette-names.d.ts +3 -0
- package/dist/styles/palettes.d.ts +6 -19
- package/dist/styles/themes/celeste.css +1 -1
- package/dist/styles/themes/eucalyptus.css +1 -1
- package/dist/styles/themes/kiln.css +1 -1
- package/dist/styles/themes/moonlit.css +1 -1
- package/dist/styles/themes/practitioner.css +1 -1
- package/dist/styles/tokens-css.d.ts +1 -1
- package/dist/styles/tokens.css +1 -1
- package/dist/tool-component.cjs +1 -1
- package/dist/tool-component.js +1 -1
- package/dist/utils/angel-sections.d.ts +1 -1
- package/dist/utils/aspect-line.d.ts +1 -10
- package/dist/utils/aspect-styles.d.ts +4 -0
- package/dist/utils/base-element.d.ts +15 -2
- package/dist/utils/bodygraph-render.d.ts +18 -2
- package/dist/utils/bodygraph-styles.d.ts +1 -6
- package/dist/utils/brand.d.ts +22 -0
- package/dist/utils/chart-styles.d.ts +9 -0
- package/dist/utils/chart-viewport.d.ts +1 -1
- package/dist/utils/degree.d.ts +7 -0
- package/dist/utils/dist-base.d.ts +2 -0
- package/dist/utils/fetch-controller.d.ts +9 -2
- package/dist/utils/field-schema.d.ts +10 -4
- package/dist/utils/frame.d.ts +1 -1
- package/dist/utils/hd-reading.d.ts +1 -14
- package/dist/utils/interp-accordion.d.ts +1 -1
- package/dist/utils/kundli-chrome.d.ts +22 -0
- package/dist/utils/kundli-render.d.ts +17 -28
- package/dist/utils/natal-wheel.d.ts +32 -0
- package/dist/utils/reference-table.d.ts +7 -0
- package/dist/utils/stacked-table.d.ts +1 -1
- package/dist/utils/svg-string.d.ts +20 -0
- package/dist/utils/synastry-wheel.d.ts +15 -0
- package/dist/version.d.ts +1 -1
- package/package.json +10 -2
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Local space astrology map","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Combined with time and timezone it fixes the birth instant whose planetary positions are projected onto the local horizon.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is essential: the local horizon rotates a full circle each day, so the azimuth (compass direction) of every body depends on the exact birth time.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). This is the origin point of every local space line and the observer latitude used to turn each body into an azimuth and altitude.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Sets the local horizon orientation and the starting point from which the directional lines radiate.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the offset in force at the birth date and time.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Optional comma-separated extra bodies to add beyond the 10 classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Omit to return the 10 classical planets only.","example":"chiron,lilith","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Local space astrology map","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Combined with time and timezone it fixes the birth instant whose planetary positions are projected onto the local horizon.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is essential: the local horizon rotates a full circle each day, so the azimuth (compass direction) of every body depends on the exact birth time.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). This is the origin point of every local space line and the observer latitude used to turn each body into an azimuth and altitude.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Sets the local horizon orientation and the starting point from which the directional lines radiate.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the offset in force at the birth date and time.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Optional comma-separated extra bodies to add beyond the 10 classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Omit to return the 10 classical planets only.","example":"chiron,lilith","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":"Lunar Return Chart","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Original birth date in YYYY-MM-DD format. Used to determine natal Moon longitude for the lunar return calculation.","example":"1990-07-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal Moon position for monthly return timing.","example":"14:30:00"},{"key":"returnDate","name":"returnDate","kind":"date","required":true,"description":"Approximate date near the desired lunar return (YYYY-MM-DD). The Moon returns to its natal position every ~27.3 days, so provide a date within a few days of the expected return.","example":"2026-02-12"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the lunar return location in decimal degrees (-90 to 90). Affects the Ascendant and house cusps of the return chart.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the lunar return location in decimal degrees (-180 to 180). Determines local sidereal time for house calculations.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the lunar return chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Lunar Return Chart","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Original birth date in YYYY-MM-DD format. Used to determine natal Moon longitude for the lunar return calculation.","example":"1990-07-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal Moon position for monthly return timing.","example":"14:30:00"},{"key":"returnDate","name":"returnDate","kind":"date","required":true,"description":"Approximate date near the desired lunar return (YYYY-MM-DD). The Moon returns to its natal position every ~27.3 days, so provide a date within a few days of the expected return.","example":"2026-02-12"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the lunar return location in decimal degrees (-90 to 90). Affects the Ascendant and house cusps of the return chart.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the lunar return location in decimal degrees (-180 to 180). Determines local sidereal time for house calculations.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the lunar return chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","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":"Generate natal chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the chart into 12 houses. Placidus (default) is most popular in Western astrology and time-sensitive. Whole Sign assigns one sign per house (simpler, ancient). Equal houses divide chart into 30° segments from Ascendant. Koch emphasizes houses in high latitudes.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate natal chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the chart into 12 houses. Placidus (default) is most popular in Western astrology and time-sensitive. Whole Sign assigns one sign per house (simpler, ancient). Equal houses divide chart into 30° segments from Ascendant. Koch emphasizes houses in high latitudes.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","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 Parallels","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for the declination calendar (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":3},{"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. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":"America/New_York","city":true,"viewerZone":true,"fold":true},{"key":"orb","name":"orb","kind":"number","required":false,"description":"How far from exact still counts, in degrees. The traditional orb for a declination contact is tighter than for a zodiacal aspect because declination changes slowly. Defaults to 1.5.","min":0.1,"max":3,"default":1.5,"example":1.5,"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Monthly Parallels","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for the declination calendar (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":3},{"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. Event dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":"America/New_York","city":true,"viewerZone":true,"fold":true},{"key":"orb","name":"orb","kind":"number","required":false,"description":"How far from exact still counts, in degrees. The traditional orb for a declination contact is tighter than for a zodiacal aspect because declination changes slowly. Defaults to 1.5.","min":0.1,"max":3,"default":1.5,"example":1.5,"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"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":"Planetary Return Chart","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Original birth date in YYYY-MM-DD format. Used to determine the natal longitude of the selected planet.","example":"1990-07-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal planet position for return timing.","example":"14:30:00"},{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet for the return calculation. Supports Mercury (~88 days), Venus (~225 days), Mars (~687 days), Jupiter (~12 years), and Saturn (~29 years). Saturn return is a major life milestone in Western astrology.","enum":["Mercury","Venus","Mars","Jupiter","Saturn"],"example":"Jupiter"},{"key":"approximateDate","name":"approximateDate","kind":"date","required":true,"description":"Approximate date near the expected planetary return (YYYY-MM-DD). The return nearest this date is returned, so a date off by months still lands on a genuine return; during a retrograde loop the planet crosses its natal degree up to three times and the crossing nearest the date is the one returned.","example":"2026-08-15"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the return location in decimal degrees (-90 to 90). Affects house cusps and Ascendant of the return chart.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the return location in decimal degrees (-180 to 180).","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the return chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Planetary Return Chart","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Original birth date in YYYY-MM-DD format. Used to determine the natal longitude of the selected planet.","example":"1990-07-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal planet position for return timing.","example":"14:30:00"},{"key":"planet","name":"planet","kind":"tiles","required":true,"description":"Planet for the return calculation. Supports Mercury (~88 days), Venus (~225 days), Mars (~687 days), Jupiter (~12 years), and Saturn (~29 years). Saturn return is a major life milestone in Western astrology.","enum":["Mercury","Venus","Mars","Jupiter","Saturn"],"example":"Jupiter"},{"key":"approximateDate","name":"approximateDate","kind":"date","required":true,"description":"Approximate date near the expected planetary return (YYYY-MM-DD). The return nearest this date is returned, so a date off by months still lands on a genuine return; during a retrograde loop the planet crosses its natal degree up to three times and the crossing nearest the date is the one returned.","example":"2026-08-15"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the return location in decimal degrees (-90 to 90). Affects house cusps and Ascendant of the return chart.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the return location in decimal degrees (-180 to 180).","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the return chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","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 Ephemeris","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for the 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 the ephemeris. Defaults to the current month (UTC).","min":1,"max":12,"example":8}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Monthly Ephemeris","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for the 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 the ephemeris. Defaults to the current month (UTC).","min":1,"max":12,"example":8}],"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":"Target date for planetary positions in YYYY-MM-DD format. Use current date for transit positions, or any historical/future date for research. Planets move daily, so this date determines their zodiac positions.","example":"2025-12-18"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in 24-hour HH:MM:SS format for precise calculations. Moon moves ~13° per day, so time matters for accurate lunar position. Use 12:00:00 (noon) as default if exact time not needed.","example":"12:00:00"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees (-90 to 90). While planetary longitudes are geocentric (same worldwide), this is needed for house calculations if extending functionality. For basic ephemeris, use 0 as default.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees (-180 to 180). Used for precise local time conversion. For basic planetary positions, this has minimal impact but ensures accuracy.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST, 5.75 for NPT) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the chart date.","min":-14,"max":14,"example":"America/New_York","role":"location"}],"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":"Target date for planetary positions in YYYY-MM-DD format. Use current date for transit positions, or any historical/future date for research. Planets move daily, so this date determines their zodiac positions.","example":"2025-12-18"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time in 24-hour HH:MM:SS format for precise calculations. Moon moves ~13° per day, so time matters for accurate lunar position. Use 12:00:00 (noon) as default if exact time not needed.","example":"12:00:00"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees (-90 to 90). While planetary longitudes are geocentric (same worldwide), this is needed for house calculations if extending functionality. For basic ephemeris, use 0 as default.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees (-180 to 180). Used for precise local time conversion. For basic planetary positions, this has minimal impact but ensures accuracy.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST, 5.75 for NPT) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the chart date.","min":-14,"max":14,"example":"America/New_York","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":"Annual profections calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.","example":"2025-08-04"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Annual profections calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.","example":"2025-08-04"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","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":"Secondary progressions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.","example":"2025-07-15"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system of the natal chart that every progressed body is placed in. Pass the system the natal chart was drawn in so the house numbers match it. Placidus (default) is the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Secondary progressions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.","example":"2025-07-15"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system of the natal chart that every progressed body is placed in. Pass the system the natal chart was drawn in so the house numbers match it. Placidus (default) is the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","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":"Generate relocation chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.","example":"1961-08-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.","example":"19:24:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Birth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\"). Resolved to the offset in force at the birth date and time. This is the birthplace timezone, not the new location timezone.","min":-14,"max":14,"example":-10,"role":"location"},{"key":"birthLatitude","name":"latitude","group":"birth","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","min":-90,"max":90,"example":21.3069,"label":"Birth latitude","role":"location"},{"key":"birthLongitude","name":"longitude","group":"birth","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","min":-180,"max":180,"example":-157.8583,"label":"Birth longitude","role":"location"},{"key":"relocationLatitude","name":"latitude","group":"relocation","kind":"number","required":true,"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","min":-90,"max":90,"example":40.7167,"label":"Relocation latitude","role":"location"},{"key":"relocationLongitude","name":"longitude","group":"relocation","kind":"number","required":true,"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","min":-180,"max":180,"example":-74.006,"label":"Relocation longitude","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{},{"key":"birth","label":"Birth","location":{"fields":["birthLatitude","birthLongitude","timezone"],"required":true}},{"key":"relocation","label":"Relocation","location":{"fields":["relocationLatitude","relocationLongitude"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate relocation chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.","example":"1961-08-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.","example":"19:24:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Birth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\"). Resolved to the offset in force at the birth date and time. This is the birthplace timezone, not the new location timezone.","min":-14,"max":14,"example":-10,"role":"location"},{"key":"birthLatitude","name":"latitude","group":"birth","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","min":-90,"max":90,"example":21.3069,"label":"Birth latitude","role":"location"},{"key":"birthLongitude","name":"longitude","group":"birth","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","min":-180,"max":180,"example":-157.8583,"label":"Birth longitude","role":"location"},{"key":"relocationLatitude","name":"latitude","group":"relocation","kind":"number","required":true,"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","min":-90,"max":90,"example":40.7167,"label":"Relocation latitude","role":"location"},{"key":"relocationLongitude","name":"longitude","group":"relocation","kind":"number","required":true,"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","min":-180,"max":180,"example":-74.006,"label":"Relocation longitude","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{},{"key":"birth","label":"Birth","location":{"fields":["birthLatitude","birthLongitude","timezone"],"required":true}},{"key":"relocation","label":"Relocation","location":{"fields":["relocationLatitude","relocationLongitude"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Solar arc directions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to direct the chart to, in YYYY-MM-DD format. Every natal point is advanced by the solar arc accumulated from birth to this date, about one degree for each year of life.","example":"2025-07-15"}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Solar arc directions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to direct the chart to, in YYYY-MM-DD format. Every natal point is advanced by the solar arc accumulated from birth to this date, about one degree for each year of life.","example":"2025-07-15"}],"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":"Solar Return Chart","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Original birth date in YYYY-MM-DD format. Used to determine natal Sun longitude for the solar return calculation.","example":"1990-07-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal Sun position for annual return timing.","example":"14:30:00"},{"key":"returnYear","name":"returnYear","kind":"number","required":true,"description":"Year for which to cast the solar return chart. The chart is erected for the exact moment the transiting Sun conjuncts the natal Sun longitude in this year.","example":2026},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the solar return location in decimal degrees (-90 to 90). Use current residence or travel location at time of birthday. Solar return charts are location-sensitive.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the solar return location in decimal degrees (-180 to 180). Affects house cusps and Ascendant of the return chart.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the solar return chart. Placidus (default) is most common in Western astrology. Whole Sign, Equal, and Koch also supported.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Solar Return Chart","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Original birth date in YYYY-MM-DD format. Used to determine natal Sun longitude for the solar return calculation.","example":"1990-07-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Original birth time in 24-hour HH:MM:SS format. Determines exact natal Sun position for annual return timing.","example":"14:30:00"},{"key":"returnYear","name":"returnYear","kind":"number","required":true,"description":"Year for which to cast the solar return chart. The chart is erected for the exact moment the transiting Sun conjuncts the natal Sun longitude in this year.","example":2026},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the solar return location in decimal degrees (-90 to 90). Use current residence or travel location at time of birthday. Solar return charts are location-sensitive.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the solar return location in decimal degrees (-180 to 180). Affects house cusps and Ascendant of the return chart.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the solar return chart. Placidus (default) is most common in Western astrology. Whole Sign, Equal, and Koch also supported.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate synastry","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person1.name","name":"name","group":"person1","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.name","name":"name","group":"person2","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate synastry","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person1.nodeType","name":"nodeType","group":"person1","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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person1.name","name":"name","group":"person1","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"person2.nodeType","name":"nodeType","group":"person2","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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.name","name":"name","group":"person2","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Transit Aspects","fields":[{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"natalChart.nodeType","name":"nodeType","group":"natalChart","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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"transitDate","name":"transitDate","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.","example":"2026-02-03","moment":true},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format, read on the clock of the natal chart timezone at the transit date (an IANA zone takes the offset in force on that date, daylight saving included). Defaults to 12:00:00 (noon) if omitted.","example":"12:00:00","moment":true},{"key":"planets","name":"planets","kind":"array","required":false,"description":"Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).","example":["Jupiter","Saturn","Pluto"],"fold":true},{"key":"aspectTypes","name":"aspectTypes","kind":"array","required":false,"description":"Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.","example":["CONJUNCTION","OPPOSITION","TRINE","SQUARE"],"fold":true},{"key":"minStrength","name":"minStrength","kind":"number","required":false,"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","min":0,"max":100,"example":50,"fold":true},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Transit Aspects","fields":[{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":true,"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.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"natalChart.nodeType","name":"nodeType","group":"natalChart","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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"transitDate","name":"transitDate","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.","example":"2026-02-03","moment":true},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format, read on the clock of the natal chart timezone at the transit date (an IANA zone takes the offset in force on that date, daylight saving included). Defaults to 12:00:00 (noon) if omitted.","example":"12:00:00","moment":true},{"key":"planets","name":"planets","kind":"array","required":false,"description":"Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).","example":["Jupiter","Saturn","Pluto"],"fold":true},{"key":"aspectTypes","name":"aspectTypes","kind":"array","required":false,"description":"Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.","example":["CONJUNCTION","OPPOSITION","TRINE","SQUARE"],"fold":true},{"key":"minStrength","name":"minStrength","kind":"number","required":false,"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","min":0,"max":100,"example":50,"fold":true},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Monthly Transits","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for the monthly transit table (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":3},{"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. Ingress dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":"America/New_York","city":true,"viewerZone":true,"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Monthly Transits","fields":[{"key":"year","name":"year","kind":"number","required":false,"description":"Year for the monthly transit table (1551 to 2649). Defaults to the current year (UTC).","min":1551,"max":2649,"example":2026},{"key":"month","name":"month","kind":"number","required":false,"description":"Month number (1-12). Defaults to the current month (UTC).","min":1,"max":12,"example":3},{"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. Ingress dates and times are reported in this zone, which is what makes a published calendar read correctly for its audience. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":"America/New_York","city":true,"viewerZone":true,"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"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":"Calculate planetary transits","fields":[{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format (defaults to current date)","example":"2025-12-19","label":"Transit date","moment":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (defaults to current time)","example":"12:00:00","label":"Transit time","moment":true},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Transit timezone: decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the transit date. When `date` or `time` is omitted, the current moment is read in this zone, so `transitDate` and `transitTime` come back as its local clock. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":0,"city":true,"viewerZone":true,"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":false,"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":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","required":false,"description":"Time in 24-hour format. Seconds are optional and default to 00 (14:30 becomes 14:30:00); a single-digit hour is zero-padded. Out-of-range values are rejected.","example":"14:30:00"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":false,"description":"Natal birth latitude in decimal degrees, positive north. Sets the local sidereal time behind the natal Ascendant and house cusps that the transits are measured against.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":false,"description":"Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":false,"description":"Natal timezone: decimal hours OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the natal date.","min":-14,"max":14,"example":"America/New_York","role":"location"}],"hasLang":true,"groups":[{},{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":false}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate planetary transits","fields":[{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format (defaults to current date)","example":"2025-12-19","label":"Transit date","moment":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (defaults to current time)","example":"12:00:00","label":"Transit time","moment":true},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Transit timezone: decimal hours from UTC OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the transit date. When `date` or `time` is omitted, the current moment is read in this zone, so `transitDate` and `transitTime` come back as its local clock. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":0,"city":true,"viewerZone":true,"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 North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true},{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":false,"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":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","required":false,"description":"Time in 24-hour format. Seconds are optional and default to 00 (14:30 becomes 14:30:00); a single-digit hour is zero-padded. Out-of-range values are rejected.","example":"14:30:00"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":false,"description":"Natal birth latitude in decimal degrees, positive north. Sets the local sidereal time behind the natal Ascendant and house cusps that the transits are measured against.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":false,"description":"Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":false,"description":"Natal timezone: decimal hours OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the natal date.","min":-14,"max":14,"example":"America/New_York","role":"location"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{},{"key":"natalChart","label":"Natal Chart","location":{"fields":["natalChart.latitude","natalChart.longitude","natalChart.timezone"],"required":false}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Ayurvedic constitution from a birth chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. It sets the sidereal positions the whole reading is built from, so an approximate date gives an approximate constitution.","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. The rising sign turns roughly every two hours and carries the heaviest weight of the three factors, so time is the input a reading is most sensitive to.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees. It sets the local sidereal time behind the rising sign, and it feeds the strength of each graha through the sunrise at that place.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees. It sets the local sidereal time behind the rising sign, together with the latitude.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name such as \"Asia/Kolkata\", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the birth date, so a summer-time birth is placed correctly. 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 the chart is cast in. \"lahiri\" is the traditional Vedic standard used by most software and is the default. \"raman\" sits about 1.45 degrees below it. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue. The frame rotates the whole zodiac, so a graha within 1.45 degrees of a boundary can change rashi when you switch, which moves both sign factors of the reading.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom sidereal frame value in degrees. Required when ayanamsa is \"custom\" and ignored otherwise. Use it to reconcile exactly against a specific reference program.","example":24,"fold":true},{"key":"signDoshaScheme","name":"signDoshaScheme","kind":"tiles","required":false,"description":"Which classical sign table the rising sign and the Moon sign are read through. \"satyacharya\" is the twelve-sign extract appended to Brihat Jataka 18.20, carried in two independent public-domain translations that agree on all twelve rows, and is the default. \"bphs\" is the Brihat Parasara Hora Sastra rule by elemental triplicity. The two agree exactly on three signs of twelve, overlap in part on seven, and share no humour at all on Scorpio or Sagittarius, so the choice can change the reading outright and is echoed in the response.","enum":["satyacharya","bphs"],"default":"satyacharya","example":"satyacharya","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Ayurvedic constitution from a birth chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. It sets the sidereal positions the whole reading is built from, so an approximate date gives an approximate constitution.","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. The rising sign turns roughly every two hours and carries the heaviest weight of the three factors, so time is the input a reading is most sensitive to.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees. It sets the local sidereal time behind the rising sign, and it feeds the strength of each graha through the sunrise at that place.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees. It sets the local sidereal time behind the rising sign, together with the latitude.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name such as \"Asia/Kolkata\", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the birth date, so a summer-time birth is placed correctly. 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 the chart is cast in. \"lahiri\" is the traditional Vedic standard used by most software and is the default. \"raman\" sits about 1.45 degrees below it. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue. The frame rotates the whole zodiac, so a graha within 1.45 degrees of a boundary can change rashi when you switch, which moves both sign factors of the reading.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom sidereal frame value in degrees. Required when ayanamsa is \"custom\" and ignored otherwise. Use it to reconcile exactly against a specific reference program.","example":24,"fold":true},{"key":"signDoshaScheme","name":"signDoshaScheme","kind":"tiles","required":false,"description":"Which classical sign table the rising sign and the Moon sign are read through. \"satyacharya\" is the twelve-sign extract appended to Brihat Jataka 18.20, carried in two independent public-domain translations that agree on all twelve rows, and is the default. \"bphs\" is the Brihat Parasara Hora Sastra rule by elemental triplicity. The two agree exactly on three signs of twelve, overlap in part on seven, and share no humour at all on Scorpio or Sagittarius, so the choice can change the reading outright and is echoed in the response.","enum":["satyacharya","bphs"],"default":"satyacharya","example":"satyacharya","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":"Dinacharya daily routine","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"The local calendar date, in YYYY-MM-DD format. Sunrise and sunset are computed for this date at the given place, and the whole routine follows from them, so the answer changes through the year at any latitude away from the equator.","example":"2026-06-21"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude in decimal degrees. It sets how long the day and the night actually are, which is the whole difference between this and a printed timetable: at 51 north in June the day runs about sixteen and a half hours and its thirds are five and a half hours each.","min":-90,"max":90,"example":51.5074,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude in decimal degrees. It sets the clock time of sunrise at this place.","min":-180,"max":180,"example":-0.1278,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name such as \"Europe/London\", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the requested date, and on the clock-hour grid at the local hour each block opens, so on a daylight-saving change every block keeps its printed hour and one that falls in the skipped hour moves forward past it. It decides which local day is meant and, on the clock-hour grid, where the blocks fall. Defaults to 0.","min":-14,"max":14,"default":0,"example":"Europe/London","role":"location"},{"key":"doshaClock","name":"doshaClock","kind":"tiles","required":false,"description":"How the six dosha periods are cut. \"sunrise-anchored\" divides the actual day and the actual night at this place into thirds, which is the division the frame chapter states, and is the default. \"clock-hours\" is the modern grid of six four-hour blocks from six in the morning; no classical text assigns clock hours, and the grid is only exact at an equinox near the equator. Both sets are returned whichever is chosen, so a caller can show one and reconcile against the other.","enum":["sunrise-anchored","clock-hours"],"default":"sunrise-anchored","example":"sunrise-anchored","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Dinacharya daily routine","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"The local calendar date, in YYYY-MM-DD format. Sunrise and sunset are computed for this date at the given place, and the whole routine follows from them, so the answer changes through the year at any latitude away from the equator.","example":"2026-06-21"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude in decimal degrees. It sets how long the day and the night actually are, which is the whole difference between this and a printed timetable: at 51 north in June the day runs about sixteen and a half hours and its thirds are five and a half hours each.","min":-90,"max":90,"example":51.5074,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude in decimal degrees. It sets the clock time of sunrise at this place.","min":-180,"max":180,"example":-0.1278,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name such as \"Europe/London\", or as decimal hours from UTC such as 5.5. An IANA name is resolved to the offset in force on the requested date, and on the clock-hour grid at the local hour each block opens, so on a daylight-saving change every block keeps its printed hour and one that falls in the skipped hour moves forward past it. It decides which local day is meant and, on the clock-hour grid, where the blocks fall. Defaults to 0.","min":-14,"max":14,"default":0,"example":"Europe/London","role":"location"},{"key":"doshaClock","name":"doshaClock","kind":"tiles","required":false,"description":"How the six dosha periods are cut. \"sunrise-anchored\" divides the actual day and the actual night at this place into thirds, which is the division the frame chapter states, and is the default. \"clock-hours\" is the modern grid of six four-hour blocks from six in the morning; no classical text assigns clock hours, and the grid is only exact at an equinox near the equator. Both sets are returned whichever is chosen, so a caller can show one and reconcile against the other.","enum":["sunrise-anchored","clock-hours"],"default":"sunrise-anchored","example":"sunrise-anchored","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":"Ayurveda seasonal regimen","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"The date to resolve, in YYYY-MM-DD format. The season is read at midday UTC on this date, because a season boundary is an instant and a calendar day has to be reduced to one; on a day that carries a boundary, the half the midday falls in is the answer. Within about two months of either end of the supported span, a date whose season opens or closes outside that span answers 400.","example":"2026-03-01"},{"key":"ritucharyaScheme","name":"ritucharyaScheme","kind":"tiles","required":false,"description":"Which six-season division the year is cut into. \"sutrasthana-6\" is the standard set of sisira, vasanta, grisma, varsa, sarad and hemanta, and is the default. \"vimana-8\" is the alternate division in which three seasons of extreme character alternate with three of moderate character and pravrt, the season of the first rains, replaces sisira. The alternate is not a relabelling: five of the six boundaries move, and because its verse gives no solar-month boundaries the month allocation is a RoxyAPI convention, stated in the response.","enum":["sutrasthana-6","vimana-8"],"default":"sutrasthana-6","example":"sutrasthana-6","fold":true},{"key":"rituZodiac","name":"rituZodiac","kind":"tiles","required":false,"description":"Which zodiac the solar-month boundaries are measured in. \"sayana\" is the tropical reading, which is what published almanacs use for seasons and is the default. \"nirayana\" is the sidereal reading in the Lahiri frame, which runs about 24 days later. The gap is the size of the ayanamsa, so near a boundary the two answer with different seasons for the same date, which is why the value is echoed in every response.","enum":["sayana","nirayana"],"default":"sayana","example":"sayana","fold":true},{"key":"hemisphere","name":"hemisphere","kind":"tiles","required":false,"description":"Which half of the world the season names are stated for. Defaults to \"northern\", which is the half the primary text describes. It is NEVER inferred from a latitude: a silent flip would change the answer without the caller asking, and no classical text handles the southern case at all. Passing \"southern\" rotates the six season names by three places, following a modern almanac rather than a verse, and the response says so and states what was not rotated with them.","enum":["northern","southern"],"default":"northern","example":"northern","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Ayurveda seasonal regimen","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"The date to resolve, in YYYY-MM-DD format. The season is read at midday UTC on this date, because a season boundary is an instant and a calendar day has to be reduced to one; on a day that carries a boundary, the half the midday falls in is the answer. Within about two months of either end of the supported span, a date whose season opens or closes outside that span answers 400.","example":"2026-03-01"},{"key":"ritucharyaScheme","name":"ritucharyaScheme","kind":"tiles","required":false,"description":"Which six-season division the year is cut into. \"sutrasthana-6\" is the standard set of sisira, vasanta, grisma, varsa, sarad and hemanta, and is the default. \"vimana-8\" is the alternate division in which three seasons of extreme character alternate with three of moderate character and pravrt, the season of the first rains, replaces sisira. The alternate is not a relabelling: five of the six boundaries move, and because its verse gives no solar-month boundaries the month allocation is a RoxyAPI convention, stated in the response.","enum":["sutrasthana-6","vimana-8"],"default":"sutrasthana-6","example":"sutrasthana-6","fold":true},{"key":"rituZodiac","name":"rituZodiac","kind":"tiles","required":false,"description":"Which zodiac the solar-month boundaries are measured in. \"sayana\" is the tropical reading, which is what published almanacs use for seasons and is the default. \"nirayana\" is the sidereal reading in the Lahiri frame, which runs about 24 days later. The gap is the size of the ayanamsa, so near a boundary the two answer with different seasons for the same date, which is why the value is echoed in every response.","enum":["sayana","nirayana"],"default":"sayana","example":"sayana","fold":true},{"key":"hemisphere","name":"hemisphere","kind":"tiles","required":false,"description":"Which half of the world the season names are stated for. Defaults to \"northern\", which is the half the primary text describes. It is NEVER inferred from a latitude: a silent flip would change the answer without the caller asking, and no classical text handles the southern case at all. Passing \"southern\" rotates the six season names by three places, following a modern almanac rather than a verse, and the response says so and states what was not rotated with them.","enum":["northern","southern"],"default":"northern","example":"northern","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate compatibility","fields":[{"key":"person1.birthDate","name":"birthDate","group":"person1","kind":"date","required":true,"description":"Birth date of person 1 in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"person2.birthDate","name":"birthDate","group":"person2","kind":"date","required":true,"description":"Birth date of person 2 in YYYY-MM-DD format.","example":"1992-03-22"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to evaluate compatibility on in YYYY-MM-DD format. Defaults to today (UTC). Compatibility varies by day since biorhythm cycles are continuous.","example":"2026-04-10","moment":true}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate compatibility","fields":[{"key":"person1.birthDate","name":"birthDate","group":"person1","kind":"date","required":true,"description":"Birth date of person 1 in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"person2.birthDate","name":"birthDate","group":"person2","kind":"date","required":true,"description":"Birth date of person 2 in YYYY-MM-DD format.","example":"1992-03-22"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to evaluate compatibility on in YYYY-MM-DD format. Defaults to today (UTC). Compatibility varies by day since biorhythm cycles are continuous.","example":"2026-04-10","moment":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Find critical days","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"Start date of the search range in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"End date of the search range in YYYY-MM-DD format. Defaults to startDate + 90 days. Maximum range: 180 days.","example":"2026-06-30","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Find critical days","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"Start date of the search range in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"End date of the search range in YYYY-MM-DD format. Defaults to startDate + 90 days. Maximum range: 180 days.","example":"2026-06-30","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 daily biorhythm","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same reading every time. Pass any unique identifier (userId, email hash, session token) to give each user their own reading for the day. Without a seed every caller receives the same shared reading of the day.","example":"user123","role":"seed"},{"key":"date","name":"date","kind":"date","required":false,"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get daily biorhythm","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same reading every time. Pass any unique identifier (userId, email hash, session token) to give each user their own reading for the day. Without a seed every caller receives the same shared reading of the day.","example":"user123","role":"seed"},{"key":"date","name":"date","kind":"date","required":false,"description":"Date for the reading in YYYY-MM-DD format. Defaults to today (UTC). Useful for viewing past daily readings or pre-generating future ones.","example":"2026-03-06"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get biorhythm forecast","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"Start date of the forecast range in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"End date of the forecast range in YYYY-MM-DD format. Defaults to startDate + 30 days. Maximum range: 90 days.","example":"2026-04-30","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get biorhythm forecast","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"Start date of the forecast range in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-01","fold":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"End date of the forecast range in YYYY-MM-DD format. Defaults to startDate + 30 days. Maximum range: 90 days.","example":"2026-04-30","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 phase info","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to get phase information for in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-10","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get phase info","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format.","example":"1990-07-15"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to get phase information for in YYYY-MM-DD format. Defaults to today (UTC).","example":"2026-04-10","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Get biorhythm reading","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format. This is the anchor for all biorhythm cycle calculations.","example":"1990-07-15"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to calculate the reading for in YYYY-MM-DD format. Defaults to today (UTC) if omitted.","example":"2026-04-10","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Get biorhythm reading","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date of the person in YYYY-MM-DD format. This is the anchor for all biorhythm cycle calculations.","example":"1990-07-15"},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to calculate the reading for in YYYY-MM-DD format. Defaults to today (UTC) if omitted.","example":"2026-04-10","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate BaZi annual forecast","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true},{"key":"year","name":"year","kind":"number","required":true,"description":"Gregorian year to read against the natal chart. The annual pillar for that year is resolved under the same year boundary the request selected, so a li-chun reading and a lunar-new-year reading of the same calendar year can differ.","min":1551,"max":2649,"example":2026}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate BaZi annual forecast","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true},{"key":"year","name":"year","kind":"number","required":true,"description":"Gregorian year to read against the natal chart. The annual pillar for that year is resolved under the same year boundary the request selected, so a li-chun reading and a lunar-new-year reading of the same calendar year can differ.","min":1551,"max":2649,"example":2026}],"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":"Generate BaZi chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate BaZi chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","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}
|