@roxyapi/ui 1.1.2 → 1.2.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +21 -1
- package/README.md +43 -1
- package/THEMING.md +32 -13
- package/components-catalog.json +1 -11247
- package/dist/cdn/components/almanac-day.js +3 -4
- package/dist/cdn/components/angel-number-card.js +3 -4
- package/dist/cdn/components/angel-number-lookup.js +3 -4
- package/dist/cdn/components/arudha-padas.js +3 -4
- package/dist/cdn/components/ashtakavarga-grid.js +3 -4
- package/dist/cdn/components/aspects-table.js +3 -4
- package/dist/cdn/components/astrocartography-map.js +9 -10
- package/dist/cdn/components/bazi-chart.js +3 -4
- package/dist/cdn/components/bhav-chalit-table.js +3 -4
- package/dist/cdn/components/bhava-bala-table.js +3 -4
- package/dist/cdn/components/biorhythm-chart.js +3 -4
- package/dist/cdn/components/bodygraph.js +14 -13
- package/dist/cdn/components/chara-karakas.js +3 -4
- package/dist/cdn/components/choghadiya-grid.js +3 -4
- package/dist/cdn/components/compatibility-card.js +3 -4
- package/dist/cdn/components/compound-number.js +3 -4
- package/dist/cdn/components/crystal-card.js +3 -4
- package/dist/cdn/components/crystal-grid.js +3 -4
- package/dist/cdn/components/dasha-timeline.js +3 -4
- package/dist/cdn/components/data.js +3 -4
- package/dist/cdn/components/divisional-chart.js +50 -49
- package/dist/cdn/components/dosha-card.js +3 -4
- package/dist/cdn/components/dosha-constitution.js +3 -4
- package/dist/cdn/components/dream-card.js +3 -4
- package/dist/cdn/components/dream-search.js +3 -4
- package/dist/cdn/components/endpoint-form.js +3 -4
- package/dist/cdn/components/ephemeris-table.js +3 -4
- package/dist/cdn/components/fixed-stars.js +3 -4
- package/dist/cdn/components/flying-star-chart.js +3 -4
- package/dist/cdn/components/forecast-digest.js +3 -4
- package/dist/cdn/components/forecast-timeline.js +3 -4
- package/dist/cdn/components/gematria.js +3 -4
- package/dist/cdn/components/gochara-table.js +3 -4
- package/dist/cdn/components/guna-milan.js +3 -4
- package/dist/cdn/components/hd-connection.js +13 -12
- package/dist/cdn/components/hd-penta.js +16 -17
- package/dist/cdn/components/hd-type-card.js +3 -4
- package/dist/cdn/components/hd-variables.js +3 -4
- package/dist/cdn/components/heliacal-table.js +3 -4
- package/dist/cdn/components/hexagram.js +3 -4
- package/dist/cdn/components/hora-table.js +3 -4
- package/dist/cdn/components/horoscope-card.js +3 -4
- package/dist/cdn/components/kp-chart.js +3 -4
- package/dist/cdn/components/kp-finance-card.js +3 -4
- package/dist/cdn/components/kp-planets-table.js +3 -4
- package/dist/cdn/components/kp-ruling-planets.js +3 -4
- package/dist/cdn/components/kua-card.js +3 -4
- package/dist/cdn/components/local-space-compass.js +6 -7
- package/dist/cdn/components/location-search.js +3 -4
- package/dist/cdn/components/luck-pillars.js +3 -4
- package/dist/cdn/components/mayan-day-sign.js +3 -4
- package/dist/cdn/components/moon-phase.js +3 -4
- package/dist/cdn/components/nakshatra-card.js +3 -4
- package/dist/cdn/components/natal-chart.js +24 -14
- package/dist/cdn/components/numerology-card.js +3 -4
- package/dist/cdn/components/panchang-table.js +3 -4
- package/dist/cdn/components/positions-table.js +3 -4
- package/dist/cdn/components/profection-card.js +3 -4
- package/dist/cdn/components/reference-card.js +3 -4
- package/dist/cdn/components/relocation-wheel.js +24 -14
- package/dist/cdn/components/shadbala-table.js +3 -4
- package/dist/cdn/components/synastry-chart.js +21 -12
- package/dist/cdn/components/tarot-card.js +3 -4
- package/dist/cdn/components/tarot-catalog.js +3 -4
- package/dist/cdn/components/tarot-spread.js +3 -4
- package/dist/cdn/components/transit-wheel.js +10 -11
- package/dist/cdn/components/transits-table.js +3 -4
- package/dist/cdn/components/upagraha-table.js +3 -4
- package/dist/cdn/components/vastu-mandala.js +10 -11
- package/dist/cdn/components/vedic-aspects.js +3 -4
- package/dist/cdn/components/vedic-daily.js +3 -4
- package/dist/cdn/components/vedic-kundli.js +62 -61
- package/dist/cdn/components/vedic-planets-table.js +3 -4
- package/dist/cdn/components/western-planets-table.js +3 -4
- package/dist/cdn/components/yoga-list.js +3 -4
- package/dist/cdn/components/zodiac-card.js +3 -4
- package/dist/cdn/locales/de.js +1 -1
- package/dist/cdn/locales/es.js +1 -1
- package/dist/cdn/locales/fr.js +1 -1
- package/dist/cdn/locales/hi.js +1 -1
- package/dist/cdn/locales/pt.js +1 -1
- package/dist/cdn/locales/ru.js +1 -1
- package/dist/cdn/locales/tr.js +1 -1
- package/dist/cdn/roxy-ui.js +113 -96
- package/dist/cdn/widgets.js +1 -1
- package/dist/charts.cjs +111 -0
- package/dist/charts.d.ts +8 -0
- package/dist/charts.js +111 -0
- package/dist/components/almanac-day.js +1 -1
- package/dist/components/angel-number-card.js +1 -1
- package/dist/components/angel-number-lookup.js +1 -1
- package/dist/components/arudha-padas.js +1 -1
- package/dist/components/ashtakavarga-grid.js +1 -1
- package/dist/components/aspects-table.js +1 -1
- package/dist/components/astrocartography-map.js +5 -5
- package/dist/components/bazi-chart.js +1 -1
- package/dist/components/bhav-chalit-table.js +1 -1
- package/dist/components/bhava-bala-table.js +1 -1
- package/dist/components/biorhythm-chart.js +1 -1
- package/dist/components/bodygraph.d.ts +0 -4
- package/dist/components/bodygraph.js +10 -10
- package/dist/components/chara-karakas.js +1 -1
- package/dist/components/choghadiya-grid.js +1 -1
- package/dist/components/compatibility-card.js +1 -1
- package/dist/components/compound-number.js +1 -1
- package/dist/components/crystal-card.js +1 -1
- package/dist/components/crystal-grid.js +1 -1
- package/dist/components/dasha-timeline.js +1 -1
- package/dist/components/data.js +1 -1
- package/dist/components/divisional-chart.js +60 -60
- package/dist/components/dosha-card.js +1 -1
- package/dist/components/dosha-constitution.js +1 -1
- package/dist/components/dream-card.js +1 -1
- package/dist/components/dream-search.js +1 -1
- package/dist/components/endpoint-form.d.ts +3 -1
- package/dist/components/endpoint-form.js +1 -1
- package/dist/components/ephemeris-table.js +1 -1
- package/dist/components/fixed-stars.js +1 -1
- package/dist/components/flying-star-chart.js +1 -1
- package/dist/components/forecast-digest.js +1 -1
- package/dist/components/forecast-timeline.js +1 -1
- package/dist/components/gematria.js +1 -1
- package/dist/components/gochara-table.js +1 -1
- package/dist/components/guna-milan.js +1 -1
- package/dist/components/hd-connection.js +10 -10
- package/dist/components/hd-penta.js +16 -16
- package/dist/components/hd-type-card.js +1 -1
- package/dist/components/hd-variables.js +1 -1
- package/dist/components/heliacal-table.js +1 -1
- package/dist/components/hexagram.js +1 -1
- package/dist/components/hora-table.js +1 -1
- package/dist/components/horoscope-card.js +1 -1
- package/dist/components/kp-chart.js +1 -1
- package/dist/components/kp-finance-card.js +1 -1
- package/dist/components/kp-planets-table.js +1 -1
- package/dist/components/kp-ruling-planets.js +1 -1
- package/dist/components/kua-card.js +1 -1
- package/dist/components/local-space-compass.js +5 -5
- package/dist/components/location-search.d.ts +1 -0
- package/dist/components/location-search.js +1 -1
- package/dist/components/luck-pillars.js +1 -1
- package/dist/components/mayan-day-sign.js +1 -1
- package/dist/components/moon-phase.js +1 -1
- package/dist/components/nakshatra-card.js +1 -1
- package/dist/components/natal-chart.d.ts +3 -82
- package/dist/components/natal-chart.js +20 -11
- package/dist/components/numerology-card.js +1 -1
- package/dist/components/panchang-table.js +1 -1
- package/dist/components/positions-table.js +1 -1
- package/dist/components/profection-card.js +1 -1
- package/dist/components/reference-card.js +1 -1
- package/dist/components/relocation-wheel.js +20 -11
- package/dist/components/shadbala-table.js +1 -1
- package/dist/components/synastry-chart.d.ts +2 -34
- package/dist/components/synastry-chart.js +17 -9
- package/dist/components/tarot-card.js +1 -1
- package/dist/components/tarot-catalog.js +1 -1
- package/dist/components/tarot-spread.js +1 -1
- package/dist/components/transit-wheel.js +7 -7
- package/dist/components/transits-table.js +1 -1
- package/dist/components/upagraha-table.js +1 -1
- package/dist/components/vastu-mandala.js +9 -9
- package/dist/components/vedic-aspects.js +1 -1
- package/dist/components/vedic-daily.js +1 -1
- package/dist/components/vedic-kundli.js +54 -54
- package/dist/components/vedic-planets-table.js +1 -1
- package/dist/components/western-planets-table.js +1 -1
- package/dist/components/yoga-list.js +1 -1
- package/dist/components/zodiac-card.js +1 -1
- package/dist/forms/labels/de.json +1 -1
- package/dist/forms/labels/en.json +1 -1
- package/dist/forms/labels/es.json +1 -1
- package/dist/forms/labels/fr.json +1 -1
- package/dist/forms/labels/hi.json +1 -1
- package/dist/forms/labels/pt.json +1 -1
- package/dist/forms/labels/ru.json +1 -1
- package/dist/forms/labels/tr.json +1 -1
- package/dist/forms.json +1 -1
- package/dist/generated/field-labels-en.d.ts +1 -1
- package/dist/i18n/chrome-strings.d.ts +1 -1
- package/dist/i18n/lang.d.ts +3 -1
- package/dist/i18n/localized-element.d.ts +4 -0
- package/dist/i18n/registry.d.ts +7 -0
- package/dist/index.cjs +111 -94
- package/dist/index.js +110 -93
- package/dist/locales/de.js +1 -1
- package/dist/locales/es.js +1 -1
- package/dist/locales/field-labels/de.d.ts +1 -1
- package/dist/locales/field-labels/es.d.ts +1 -1
- package/dist/locales/field-labels/fr.d.ts +1 -1
- package/dist/locales/field-labels/hi.d.ts +1 -1
- package/dist/locales/field-labels/pt.d.ts +1 -1
- package/dist/locales/field-labels/ru.d.ts +1 -1
- package/dist/locales/field-labels/tr.d.ts +1 -1
- package/dist/locales/fr.js +1 -1
- package/dist/locales/hi.js +1 -1
- package/dist/locales/pt.js +1 -1
- package/dist/locales/ru.js +1 -1
- package/dist/locales/tr.js +1 -1
- package/dist/manifest.d.ts +3 -5
- package/dist/manifest.json +1 -89
- package/dist/schemas/get--angel-numbers-lookup.json +1 -1
- package/dist/schemas/get--angel-numbers-numbers-number.json +1 -1
- package/dist/schemas/get--angel-numbers-numbers.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-daily.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-monthly.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-weekly.json +1 -1
- package/dist/schemas/get--astrology-horoscope-sign-yearly.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-calendar-year-month.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-current.json +1 -1
- package/dist/schemas/get--astrology-moon-phase-upcoming.json +1 -1
- package/dist/schemas/get--astrology-planet-meanings-id.json +1 -1
- package/dist/schemas/get--astrology-planet-meanings.json +1 -1
- package/dist/schemas/get--astrology-signs-id.json +1 -1
- package/dist/schemas/get--astrology-signs.json +1 -1
- package/dist/schemas/get--ayurveda-daily.json +1 -1
- package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
- package/dist/schemas/get--ayurveda-doshas.json +1 -1
- package/dist/schemas/get--ayurveda-qualities.json +1 -1
- package/dist/schemas/get--ayurveda-tastes.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-day-date.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-monthly.json +1 -1
- package/dist/schemas/get--chinese-astrology-calendar-solar-terms-year.json +1 -1
- package/dist/schemas/get--chinese-astrology-elements.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-animals.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-compatibility-sign1-sign2.json +1 -1
- package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
- package/dist/schemas/get--crystals-birthstone-month.json +1 -1
- package/dist/schemas/get--crystals-chakra-chakra.json +1 -1
- package/dist/schemas/get--crystals-colors.json +1 -1
- package/dist/schemas/get--crystals-element-element.json +1 -1
- package/dist/schemas/get--crystals-id.json +1 -1
- package/dist/schemas/get--crystals-pairings-id.json +1 -1
- package/dist/schemas/get--crystals-planets.json +1 -1
- package/dist/schemas/get--crystals-random.json +1 -1
- package/dist/schemas/get--crystals-search.json +1 -1
- package/dist/schemas/get--crystals-zodiac-sign.json +1 -1
- package/dist/schemas/get--crystals.json +1 -1
- package/dist/schemas/get--dreams-symbols-id.json +1 -1
- package/dist/schemas/get--dreams-symbols-letters.json +1 -1
- package/dist/schemas/get--dreams-symbols-random.json +1 -1
- package/dist/schemas/get--dreams-symbols.json +1 -1
- package/dist/schemas/get--feng-shui-afflictions-year.json +1 -1
- package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
- package/dist/schemas/get--feng-shui-bagua.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-annual-year.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-monthly.json +1 -1
- package/dist/schemas/get--feng-shui-flying-stars-stars.json +1 -1
- package/dist/schemas/get--feng-shui-kua-number.json +1 -1
- package/dist/schemas/get--feng-shui-periods.json +1 -1
- package/dist/schemas/get--human-design-centers-id.json +1 -1
- package/dist/schemas/get--human-design-gates-number.json +1 -1
- package/dist/schemas/get--iching-cast.json +1 -1
- package/dist/schemas/get--iching-hexagrams-lookup.json +1 -1
- package/dist/schemas/get--iching-hexagrams-number.json +1 -1
- package/dist/schemas/get--iching-hexagrams-random.json +1 -1
- package/dist/schemas/get--iching-hexagrams.json +1 -1
- package/dist/schemas/get--iching-trigrams-id.json +1 -1
- package/dist/schemas/get--iching-trigrams.json +1 -1
- package/dist/schemas/get--kabbalah-ciphers.json +1 -1
- package/dist/schemas/get--kabbalah-daily.json +1 -1
- package/dist/schemas/get--kabbalah-letters-id.json +1 -1
- package/dist/schemas/get--kabbalah-letters.json +1 -1
- package/dist/schemas/get--kabbalah-names-number.json +1 -1
- package/dist/schemas/get--kabbalah-names.json +1 -1
- package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
- package/dist/schemas/get--kabbalah-tree.json +1 -1
- package/dist/schemas/get--languages-field-labels.json +1 -1
- package/dist/schemas/get--languages.json +1 -1
- package/dist/schemas/get--location-countries-iso2.json +1 -1
- package/dist/schemas/get--location-countries.json +1 -1
- package/dist/schemas/get--location-search.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-daily.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas-number.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-calendar-monthly.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-daily.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas-number.json +1 -1
- package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas.json +1 -1
- package/dist/schemas/get--numerology-compound-number-number.json +1 -1
- package/dist/schemas/get--numerology-meanings-number.json +1 -1
- package/dist/schemas/get--tarot-cards-id.json +1 -1
- package/dist/schemas/get--tarot-cards.json +1 -1
- package/dist/schemas/get--usage.json +1 -1
- package/dist/schemas/get--vastu-devatas-id.json +1 -1
- package/dist/schemas/get--vastu-devatas.json +1 -1
- package/dist/schemas/get--vastu-directions-id.json +1 -1
- package/dist/schemas/get--vastu-directions.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-avasthas.json +1 -1
- package/dist/schemas/get--vedic-astrology-kp-ayanamsa.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-nakshatras.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-rashis.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
- package/dist/schemas/get--vedic-astrology-yoga.json +1 -1
- package/dist/schemas/post--angel-numbers-daily.json +1 -1
- package/dist/schemas/post--astrology-arabic-lots.json +1 -1
- package/dist/schemas/post--astrology-aspect-patterns.json +1 -1
- package/dist/schemas/post--astrology-aspects-monthly.json +1 -1
- package/dist/schemas/post--astrology-aspects.json +1 -1
- package/dist/schemas/post--astrology-asteroids.json +1 -1
- package/dist/schemas/post--astrology-astrocartography.json +1 -1
- package/dist/schemas/post--astrology-compatibility-score.json +1 -1
- package/dist/schemas/post--astrology-composite-chart.json +1 -1
- package/dist/schemas/post--astrology-ecliptic-crossings.json +1 -1
- package/dist/schemas/post--astrology-fixed-stars.json +1 -1
- package/dist/schemas/post--astrology-houses.json +1 -1
- package/dist/schemas/post--astrology-lilith.json +1 -1
- package/dist/schemas/post--astrology-local-space.json +1 -1
- package/dist/schemas/post--astrology-lunar-return.json +1 -1
- package/dist/schemas/post--astrology-natal-chart.json +1 -1
- package/dist/schemas/post--astrology-parallels-monthly.json +1 -1
- package/dist/schemas/post--astrology-planetary-returns.json +1 -1
- package/dist/schemas/post--astrology-planets-monthly.json +1 -1
- package/dist/schemas/post--astrology-planets.json +1 -1
- package/dist/schemas/post--astrology-profections.json +1 -1
- package/dist/schemas/post--astrology-progressions.json +1 -1
- package/dist/schemas/post--astrology-relocation-chart.json +1 -1
- package/dist/schemas/post--astrology-solar-arc.json +1 -1
- package/dist/schemas/post--astrology-solar-return.json +1 -1
- package/dist/schemas/post--astrology-synastry.json +1 -1
- package/dist/schemas/post--astrology-transit-aspects.json +1 -1
- package/dist/schemas/post--astrology-transits-monthly.json +1 -1
- package/dist/schemas/post--astrology-transits.json +1 -1
- package/dist/schemas/post--ayurveda-constitution.json +1 -1
- package/dist/schemas/post--ayurveda-dinacharya.json +1 -1
- package/dist/schemas/post--ayurveda-ritucharya.json +1 -1
- package/dist/schemas/post--biorhythm-compatibility.json +1 -1
- package/dist/schemas/post--biorhythm-critical-days.json +1 -1
- package/dist/schemas/post--biorhythm-daily.json +1 -1
- package/dist/schemas/post--biorhythm-forecast.json +1 -1
- package/dist/schemas/post--biorhythm-phases.json +1 -1
- package/dist/schemas/post--biorhythm-reading.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-annual-forecast.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-chart.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-day-master.json +1 -1
- package/dist/schemas/post--chinese-astrology-bazi-luck-pillars.json +1 -1
- package/dist/schemas/post--chinese-astrology-calendar-auspicious-days.json +1 -1
- package/dist/schemas/post--chinese-astrology-calendar-lunar-date.json +1 -1
- package/dist/schemas/post--chinese-astrology-zodiac-sign.json +1 -1
- package/dist/schemas/post--crystals-daily.json +1 -1
- package/dist/schemas/post--dreams-daily.json +1 -1
- package/dist/schemas/post--feng-shui-eight-mansions.json +1 -1
- package/dist/schemas/post--feng-shui-flying-stars-natal.json +1 -1
- package/dist/schemas/post--feng-shui-kua.json +1 -1
- package/dist/schemas/post--forecast-digest.json +1 -1
- package/dist/schemas/post--forecast-significant-dates.json +1 -1
- package/dist/schemas/post--forecast-solar-return.json +1 -1
- package/dist/schemas/post--forecast-timeline.json +1 -1
- package/dist/schemas/post--forecast-transits.json +1 -1
- package/dist/schemas/post--human-design-bodygraph.json +1 -1
- package/dist/schemas/post--human-design-centers.json +1 -1
- package/dist/schemas/post--human-design-channels.json +1 -1
- package/dist/schemas/post--human-design-connection.json +1 -1
- package/dist/schemas/post--human-design-gates.json +1 -1
- package/dist/schemas/post--human-design-penta.json +1 -1
- package/dist/schemas/post--human-design-profile.json +1 -1
- package/dist/schemas/post--human-design-transit.json +1 -1
- package/dist/schemas/post--human-design-type.json +1 -1
- package/dist/schemas/post--human-design-variables.json +1 -1
- package/dist/schemas/post--iching-daily-cast.json +1 -1
- package/dist/schemas/post--iching-daily.json +1 -1
- package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
- package/dist/schemas/post--kabbalah-compatibility.json +1 -1
- package/dist/schemas/post--kabbalah-gematria.json +1 -1
- package/dist/schemas/post--kabbalah-name-profile.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-aztec-tonalpohualli.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-chart.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-long-count-convert.json +1 -1
- package/dist/schemas/post--mesoamerican-astrology-mayan-tzolkin.json +1 -1
- package/dist/schemas/post--numerology-birth-day.json +1 -1
- package/dist/schemas/post--numerology-bridge.json +1 -1
- package/dist/schemas/post--numerology-business-name.json +1 -1
- package/dist/schemas/post--numerology-chaldean.json +1 -1
- package/dist/schemas/post--numerology-chart.json +1 -1
- package/dist/schemas/post--numerology-compatibility.json +1 -1
- package/dist/schemas/post--numerology-daily.json +1 -1
- package/dist/schemas/post--numerology-dual.json +1 -1
- package/dist/schemas/post--numerology-expression.json +1 -1
- package/dist/schemas/post--numerology-karmic-debt.json +1 -1
- package/dist/schemas/post--numerology-karmic-lessons.json +1 -1
- package/dist/schemas/post--numerology-life-path.json +1 -1
- package/dist/schemas/post--numerology-maturity.json +1 -1
- package/dist/schemas/post--numerology-personal-day.json +1 -1
- package/dist/schemas/post--numerology-personal-month.json +1 -1
- package/dist/schemas/post--numerology-personal-year.json +1 -1
- package/dist/schemas/post--numerology-personality.json +1 -1
- package/dist/schemas/post--numerology-soul-urge.json +1 -1
- package/dist/schemas/post--tarot-daily.json +1 -1
- package/dist/schemas/post--tarot-draw.json +1 -1
- package/dist/schemas/post--tarot-spreads-career.json +1 -1
- package/dist/schemas/post--tarot-spreads-celtic-cross.json +1 -1
- package/dist/schemas/post--tarot-spreads-custom.json +1 -1
- package/dist/schemas/post--tarot-spreads-love.json +1 -1
- package/dist/schemas/post--tarot-spreads-three-card.json +1 -1
- package/dist/schemas/post--tarot-yes-no.json +1 -1
- package/dist/schemas/post--vastu-ayadi.json +1 -1
- package/dist/schemas/post--vastu-entrance.json +1 -1
- package/dist/schemas/post--vastu-mandala.json +1 -1
- package/dist/schemas/post--vastu-plot.json +1 -1
- package/dist/schemas/post--vastu-rooms.json +1 -1
- package/dist/schemas/post--vastu-timing-griha-pravesh.json +1 -1
- package/dist/schemas/post--vedic-astrology-arudha.json +1 -1
- package/dist/schemas/post--vedic-astrology-ashtakavarga.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects-lunar.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-aspects.json +1 -1
- package/dist/schemas/post--vedic-astrology-bhav-chalit.json +1 -1
- package/dist/schemas/post--vedic-astrology-bhava-bala.json +1 -1
- package/dist/schemas/post--vedic-astrology-birth-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-chara-karakas.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
- package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
- package/dist/schemas/post--vedic-astrology-daily.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
- package/dist/schemas/post--vedic-astrology-divisional-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-kalsarpa.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-manglik.json +1 -1
- package/dist/schemas/post--vedic-astrology-dosha-sadhesati.json +1 -1
- package/dist/schemas/post--vedic-astrology-ecliptic-crossings.json +1 -1
- package/dist/schemas/post--vedic-astrology-heliacal.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-rasi-changes.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
- package/dist/schemas/post--vedic-astrology-kp-sublord-changes.json +1 -1
- package/dist/schemas/post--vedic-astrology-navamsa.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-basic.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-choghadiya.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-detailed.json +1 -1
- package/dist/schemas/post--vedic-astrology-panchang-hora.json +1 -1
- package/dist/schemas/post--vedic-astrology-parallels-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-parallels.json +1 -1
- package/dist/schemas/post--vedic-astrology-planetary-positions-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-planetary-positions.json +1 -1
- package/dist/schemas/post--vedic-astrology-shadbala.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit-monthly.json +1 -1
- package/dist/schemas/post--vedic-astrology-transit.json +1 -1
- package/dist/schemas/post--vedic-astrology-upagraha.json +1 -1
- package/dist/schemas/post--vedic-astrology-yoga-detect.json +1 -1
- package/dist/styles/charts/bodygraph.css +1 -0
- package/dist/styles/charts/kundli.css +1 -0
- package/dist/styles/charts/natal-wheel.css +1 -0
- package/dist/styles/charts/synastry-wheel.css +1 -0
- package/dist/styles/fonts/fraunces-jost.css +1 -0
- package/dist/styles/fonts/geist/OFL.txt +93 -0
- package/dist/styles/fonts/geist/geist-cyrillic.woff2 +0 -0
- package/dist/styles/fonts/geist/geist-latin-ext.woff2 +0 -0
- package/dist/styles/fonts/geist/geist-latin.woff2 +0 -0
- package/dist/styles/fonts/geist.css +1 -0
- package/dist/styles/fonts/jost.css +1 -0
- package/dist/styles/fonts.d.ts +23 -0
- package/dist/styles/palette-names.d.ts +3 -0
- package/dist/styles/palettes.d.ts +6 -19
- package/dist/styles/themes/celeste.css +1 -1
- package/dist/styles/themes/eucalyptus.css +1 -1
- package/dist/styles/themes/kiln.css +1 -1
- package/dist/styles/themes/moonlit.css +1 -1
- package/dist/styles/themes/practitioner.css +1 -1
- package/dist/styles/tokens-css.d.ts +1 -1
- package/dist/styles/tokens.css +1 -1
- package/dist/tool-component.cjs +1 -1
- package/dist/tool-component.js +1 -1
- package/dist/utils/angel-sections.d.ts +1 -1
- package/dist/utils/aspect-line.d.ts +1 -10
- package/dist/utils/aspect-styles.d.ts +4 -0
- package/dist/utils/base-element.d.ts +15 -2
- package/dist/utils/bodygraph-render.d.ts +18 -2
- package/dist/utils/bodygraph-styles.d.ts +1 -6
- package/dist/utils/brand.d.ts +22 -0
- package/dist/utils/chart-styles.d.ts +9 -0
- package/dist/utils/chart-viewport.d.ts +1 -1
- package/dist/utils/degree.d.ts +7 -0
- package/dist/utils/dist-base.d.ts +2 -0
- package/dist/utils/fetch-controller.d.ts +9 -2
- package/dist/utils/field-schema.d.ts +10 -4
- package/dist/utils/frame.d.ts +1 -1
- package/dist/utils/hd-reading.d.ts +1 -14
- package/dist/utils/interp-accordion.d.ts +1 -1
- package/dist/utils/kundli-chrome.d.ts +22 -0
- package/dist/utils/kundli-render.d.ts +17 -28
- package/dist/utils/natal-wheel.d.ts +32 -0
- package/dist/utils/reference-table.d.ts +7 -0
- package/dist/utils/stacked-table.d.ts +1 -1
- package/dist/utils/svg-string.d.ts +20 -0
- package/dist/utils/synastry-wheel.d.ts +15 -0
- package/dist/version.d.ts +1 -1
- package/package.json +10 -2
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate the Human Design profile and line keynotes","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00: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. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. 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. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate the Human Design profile and line keynotes","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00: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. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. 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. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. 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":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Generate Human Design transit overlay","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"birthData.timezone","name":"timezone","group":"birthData","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":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"birthData.nodeType","name":"nodeType","group":"birthData","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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.","example":"2026-05-23","label":"Transit date","moment":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS UTC. Optional. Defaults to the current UTC time when omitted. Precision matters: the Moon moves through a gate in roughly half a day.","example":"12:00:00","label":"Transit time","moment":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate Human Design transit overlay","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"birthData.timezone","name":"timezone","group":"birthData","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":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"birthData.nodeType","name":"nodeType","group":"birthData","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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.","example":"2026-05-23","label":"Transit date","moment":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS UTC. Optional. Defaults to the current UTC time when omitted. Precision matters: the Moon moves through a gate in roughly half a day.","example":"12:00:00","label":"Transit time","moment":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Human Design type, authority and profile","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00: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. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. 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. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Human Design type, authority and profile","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00: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. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. 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. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. 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":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Human Design Variables","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00: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. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. 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. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Human Design Variables","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00: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. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. 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. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"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 activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. 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":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Cast daily reading with changing lines","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram 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":"Cast daily reading with changing lines","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram 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":"Daily hexagram","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram 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":"Daily hexagram","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same hexagram every time. Pass any unique identifier (userId, email hash, session token) to give each user their own hexagram for the day. Without a seed every caller receives the same shared hexagram 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":"Generate a birth profile","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD, proleptic Gregorian. Dates before the 1582 reform are read on the same proleptic reckoning rather than switched to the Julian calendar.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":false,"description":"Birth time in HH:MM:SS local to the timezone field. Defaults to noon when omitted, which is stated because the name read from the hour changes every twenty minutes and a defaulted time cannot be precise.","example":"14:30:00","fold":true},{"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","city":true},{"key":"angelDating","name":"angelDating","kind":"tiles","required":false,"description":"How the name of the day is found. Use solar-longitude for the exact five degree arc the Sun stood in at the birth moment, or lenain-blocks for the fixed civil calendar of five day periods. The Sun does not move at a constant rate, so the two drift apart by up to about three days by early August and were never reconciled.","enum":["solar-longitude","lenain-blocks"],"default":"solar-longitude","example":"solar-longitude","fold":true},{"key":"yearStart","name":"yearStart","kind":"tiles","required":false,"description":"Which date the civil wheel of five day periods opens on. Both are conventions rather than facts: the equinox itself moves inside a window that covers both days, and it fell on 20 March in 2026. march-21 is the pinned published wheel and march-20 is that wheel shifted one day. Ignored when angelDating is solar-longitude.","enum":["march-21","march-20"],"default":"march-21","example":"march-21","fold":true},{"key":"leapDayPolicy","name":"leapDayPolicy","kind":"tiles","required":false,"description":"Where 29 February falls. The civil wheel was built for a 365 day year and has no slot for it, so published tables differ: extend-previous reads the day as part of the period ending 28 February, next-angel reads it as the opening of the period starting 1 March. Ignored when angelDating is solar-longitude.","enum":["extend-previous","next-angel"],"default":"extend-previous","example":"extend-previous","fold":true},{"key":"afterSunset","name":"afterSunset","kind":"toggle","required":false,"description":"Set true when the moment falls after nightfall, which advances the Hebrew date by one day because the Hebrew day begins in the evening. It is a caller assertion rather than a computation, since sunset depends on a place and this conversion takes none.","default":false,"example":false,"fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to count the next Hebrew birthday from, in YYYY-MM-DD format. Send the local date of the user for an exact answer: on the birthday itself the answer is that day. Defaults to today (UTC).","example":"2026-10-28","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate a birth profile","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD, proleptic Gregorian. Dates before the 1582 reform are read on the same proleptic reckoning rather than switched to the Julian calendar.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":false,"description":"Birth time in HH:MM:SS local to the timezone field. Defaults to noon when omitted, which is stated because the name read from the hour changes every twenty minutes and a defaulted time cannot be precise.","example":"14:30:00","fold":true},{"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","city":true},{"key":"angelDating","name":"angelDating","kind":"tiles","required":false,"description":"How the name of the day is found. Use solar-longitude for the exact five degree arc the Sun stood in at the birth moment, or lenain-blocks for the fixed civil calendar of five day periods. The Sun does not move at a constant rate, so the two drift apart by up to about three days by early August and were never reconciled.","enum":["solar-longitude","lenain-blocks"],"default":"solar-longitude","example":"solar-longitude","fold":true},{"key":"yearStart","name":"yearStart","kind":"tiles","required":false,"description":"Which date the civil wheel of five day periods opens on. Both are conventions rather than facts: the equinox itself moves inside a window that covers both days, and it fell on 20 March in 2026. march-21 is the pinned published wheel and march-20 is that wheel shifted one day. Ignored when angelDating is solar-longitude.","enum":["march-21","march-20"],"default":"march-21","example":"march-21","fold":true},{"key":"leapDayPolicy","name":"leapDayPolicy","kind":"tiles","required":false,"description":"Where 29 February falls. The civil wheel was built for a 365 day year and has no slot for it, so published tables differ: extend-previous reads the day as part of the period ending 28 February, next-angel reads it as the opening of the period starting 1 March. Ignored when angelDating is solar-longitude.","enum":["extend-previous","next-angel"],"default":"extend-previous","example":"extend-previous","fold":true},{"key":"afterSunset","name":"afterSunset","kind":"toggle","required":false,"description":"Set true when the moment falls after nightfall, which advances the Hebrew date by one day because the Hebrew day begins in the evening. It is a caller assertion rather than a computation, since sunset depends on a place and this conversion takes none.","default":false,"example":false,"fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to count the next Hebrew birthday from, in YYYY-MM-DD format. Send the local date of the user for an exact answer: on the birthday itself the answer is that day. Defaults to today (UTC).","example":"2026-10-28","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Compare two names","fields":[{"key":"firstName","name":"firstName","kind":"text","required":true,"description":"First name in Latin script. Send firstNameHebrew instead to control the spelling.","example":"Sarah"},{"key":"firstNameHebrew","name":"firstNameHebrew","kind":"text","required":false,"description":"First name already in Hebrew, which skips the transliteration step.","example":"שרה","fold":true},{"key":"secondName","name":"secondName","kind":"text","required":true,"description":"Second name in Latin script. Send secondNameHebrew instead to control the spelling.","example":"David"},{"key":"secondNameHebrew","name":"secondNameHebrew","kind":"text","required":false,"description":"Second name already in Hebrew, which skips the transliteration step.","example":"דוד","fold":true},{"key":"transliteration","name":"transliteration","kind":"tiles","required":false,"description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"default":"letter-map-mathers","example":"letter-map-mathers","fold":true},{"key":"misparGadol","name":"misparGadol","kind":"tiles","required":false,"description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"default":"finals-500-900","example":"finals-500-900","fold":true}],"hasLang":true,"requiredAnyOf":[["firstName","secondName"],["firstName","secondNameHebrew"],["firstNameHebrew","secondName"],["firstNameHebrew","secondNameHebrew"]],"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Compare two names","fields":[{"key":"firstName","name":"firstName","kind":"text","required":true,"description":"First name in Latin script. Send firstNameHebrew instead to control the spelling.","example":"Sarah"},{"key":"firstNameHebrew","name":"firstNameHebrew","kind":"text","required":false,"description":"First name already in Hebrew, which skips the transliteration step.","example":"שרה","fold":true},{"key":"secondName","name":"secondName","kind":"text","required":true,"description":"Second name in Latin script. Send secondNameHebrew instead to control the spelling.","example":"David"},{"key":"secondNameHebrew","name":"secondNameHebrew","kind":"text","required":false,"description":"Second name already in Hebrew, which skips the transliteration step.","example":"דוד","fold":true},{"key":"transliteration","name":"transliteration","kind":"tiles","required":false,"description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"default":"letter-map-mathers","example":"letter-map-mathers","fold":true},{"key":"misparGadol","name":"misparGadol","kind":"tiles","required":false,"description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"default":"finals-500-900","example":"finals-500-900","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["firstName","secondName"],["firstName","secondNameHebrew"],["firstNameHebrew","secondName"],["firstNameHebrew","secondNameHebrew"]],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate gematria","fields":[{"key":"text","name":"text","kind":"text","required":true,"description":"Latin text to write in Hebrew and then score, up to 200 characters. Non Latin scripts are folded to Latin first, so a Cyrillic or Devanagari name works. Send textHebrew instead to control the Hebrew spelling yourself.","example":"Sarah"},{"key":"textHebrew","name":"textHebrew","kind":"text","required":false,"description":"Hebrew text to score, up to 200 characters. Anything outside the Hebrew script is rejected. Vowel points, cantillation marks, maqaf and paseq are removed before scoring, so a pointed and an unpointed spelling of one word give the same number.","example":"שלום","fold":true},{"key":"transliteration","name":"transliteration","kind":"tiles","required":false,"description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"default":"letter-map-mathers","example":"letter-map-mathers","fold":true},{"key":"ciphers","name":"ciphers","kind":"array","required":false,"description":"Which ciphers to return, by identifier. Omit for every computed cipher. Valid values are mispar-hechrachi, mispar-gadol, otiyot-be-milui, mispar-katan, mispar-kidmi, mispar-prati, mispar-ha-merubah-ha-klali, mispar-meshulash, mispar-musafi, kolel.","example":["mispar-hechrachi","mispar-gadol"],"fold":true},{"key":"misparGadol","name":"misparGadol","kind":"tiles","required":false,"description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"default":"finals-500-900","example":"finals-500-900","fold":true},{"key":"atbashOutput","name":"atbashOutput","kind":"tiles","required":false,"description":"What AtBash and Albam return: the substituted Hebrew string, its standard value, or both. The biblical witness for AtBash is a substituted WORD rather than a number, which is why the string is available on its own.","enum":["both","string","value"],"default":"both","example":"both","fold":true},{"key":"includeMatches","name":"includeMatches","kind":"toggle","required":false,"description":"Whether to return the curated equal value entries for the chosen spelling. Set false to skip the lookup when only the numbers are wanted.","default":true,"example":true,"fold":true},{"key":"latinCiphers","name":"latinCiphers","kind":"toggle","required":false,"description":"Whether to also score the Latin text with the three Latin alphabet ciphers. They are Renaissance Christian and modern in lineage rather than rabbinic, and the response labels each one. Ignored when textHebrew was sent.","default":false,"example":false,"fold":true}],"hasLang":true,"requiredAnyOf":[["text"],["textHebrew"]],"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate gematria","fields":[{"key":"text","name":"text","kind":"text","required":true,"description":"Latin text to write in Hebrew and then score, up to 200 characters. Non Latin scripts are folded to Latin first, so a Cyrillic or Devanagari name works. Send textHebrew instead to control the Hebrew spelling yourself.","example":"Sarah"},{"key":"textHebrew","name":"textHebrew","kind":"text","required":false,"description":"Hebrew text to score, up to 200 characters. Anything outside the Hebrew script is rejected. Vowel points, cantillation marks, maqaf and paseq are removed before scoring, so a pointed and an unpointed spelling of one word give the same number.","example":"שלום","fold":true},{"key":"transliteration","name":"transliteration","kind":"tiles","required":false,"description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"default":"letter-map-mathers","example":"letter-map-mathers","fold":true},{"key":"ciphers","name":"ciphers","kind":"array","required":false,"description":"Which ciphers to return, by identifier. Omit for every computed cipher. Valid values are mispar-hechrachi, mispar-gadol, otiyot-be-milui, mispar-katan, mispar-kidmi, mispar-prati, mispar-ha-merubah-ha-klali, mispar-meshulash, mispar-musafi, kolel.","example":["mispar-hechrachi","mispar-gadol"],"fold":true},{"key":"misparGadol","name":"misparGadol","kind":"tiles","required":false,"description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"default":"finals-500-900","example":"finals-500-900","fold":true},{"key":"atbashOutput","name":"atbashOutput","kind":"tiles","required":false,"description":"What AtBash and Albam return: the substituted Hebrew string, its standard value, or both. The biblical witness for AtBash is a substituted WORD rather than a number, which is why the string is available on its own.","enum":["both","string","value"],"default":"both","example":"both","fold":true},{"key":"includeMatches","name":"includeMatches","kind":"toggle","required":false,"description":"Whether to return the curated equal value entries for the chosen spelling. Set false to skip the lookup when only the numbers are wanted.","default":true,"example":true,"fold":true},{"key":"latinCiphers","name":"latinCiphers","kind":"toggle","required":false,"description":"Whether to also score the Latin text with the three Latin alphabet ciphers. They are Renaissance Christian and modern in lineage rather than rabbinic, and the response labels each one. Ignored when textHebrew was sent.","default":false,"example":false,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["text"],["textHebrew"]],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Generate a name profile","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The name in Latin script, to be written in Hebrew and then scored. Non Latin scripts are folded to Latin first. Send nameHebrew instead to control the spelling yourself.","example":"Sarah"},{"key":"nameHebrew","name":"nameHebrew","kind":"text","required":false,"description":"The name already in Hebrew, which skips the transliteration step entirely and scores exactly the spelling you sent.","example":"שרה","fold":true},{"key":"transliteration","name":"transliteration","kind":"tiles","required":false,"description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"default":"letter-map-mathers","example":"letter-map-mathers","fold":true},{"key":"misparGadol","name":"misparGadol","kind":"tiles","required":false,"description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"default":"finals-500-900","example":"finals-500-900","fold":true}],"hasLang":true,"requiredAnyOf":[["name"],["nameHebrew"]],"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate a name profile","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The name in Latin script, to be written in Hebrew and then scored. Non Latin scripts are folded to Latin first. Send nameHebrew instead to control the spelling yourself.","example":"Sarah"},{"key":"nameHebrew","name":"nameHebrew","kind":"text","required":false,"description":"The name already in Hebrew, which skips the transliteration step entirely and scores exactly the spelling you sent.","example":"שרה","fold":true},{"key":"transliteration","name":"transliteration","kind":"tiles","required":false,"description":"How a Latin name is written in Hebrew before it is scored. Two members. letter-map-mathers is the 1887 Hermetic letter map, with e read as its author practised it: a point inside a word and alef at the start of one. It writes no c, f, w or x, so a name carrying one of them outside a two letter group returns 400 naming the letter. letter-map-modern follows the modern Israeli transcription rules for the sound each Latin letter carries in English and French spelling, covers every Latin letter, drops the geresh and does not double vav or yod, so send textHebrew for the ktiv male form. Every form states the readings it used in rule. Phonetic Ashkenazi and Sephardi schemes are not offered because no two references agree on a rule for that direction.","enum":["letter-map-mathers","letter-map-modern"],"default":"letter-map-mathers","example":"letter-map-mathers","fold":true},{"key":"misparGadol","name":"misparGadol","kind":"tiles","required":false,"description":"Which method the name mispar gadol means, because the sources use it for two. Use finals-500-900 to score the five word final letters as 500 to 900, or milui to score each letter as the value of its own spelled out name.","enum":["finals-500-900","milui"],"default":"finals-500-900","example":"finals-500-900","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["name"],["nameHebrew"]],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Aztec day sign for a date","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Aztec day sign for a date","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Generate a Mayan chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true},{"key":"yearBearerSystem","name":"yearBearerSystem","kind":"tiles","required":false,"description":"Which Haab day is read as the start of the year when naming its Year Bearer. Only four of the twenty day signs can ever carry a year, and which four depends entirely on this choice, so the three schools never agree. \"classic\" reads the seating of Pop and is the default, because it is the set highland daykeepers still use; its four bearers are Ikʼ, Manikʼ, Ebʼ and Kabʼan. \"campeche\" reads 1 Pop and gives Akʼbʼal, Lamat, Bʼen and Etzʼnabʼ. \"colonial-yucatec\" reads 2 Pop and gives Kʼan, Muluk, Ix and Kawak. The three sets share no member, so a bearer alone tells you which school produced it.","enum":["classic","campeche","colonial-yucatec"],"default":"classic","example":"classic","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate a Mayan chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true},{"key":"yearBearerSystem","name":"yearBearerSystem","kind":"tiles","required":false,"description":"Which Haab day is read as the start of the year when naming its Year Bearer. Only four of the twenty day signs can ever carry a year, and which four depends entirely on this choice, so the three schools never agree. \"classic\" reads the seating of Pop and is the default, because it is the set highland daykeepers still use; its four bearers are Ikʼ, Manikʼ, Ebʼ and Kabʼan. \"campeche\" reads 1 Pop and gives Akʼbʼal, Lamat, Bʼen and Etzʼnabʼ. \"colonial-yucatec\" reads 2 Pop and gives Kʼan, Muluk, Ix and Kawak. The three sets share no member, so a bearer alone tells you which school produced it.","enum":["classic","campeche","colonial-yucatec"],"default":"classic","example":"classic","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Mayan nawal compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true},{"key":"directionScheme","name":"directionScheme","kind":"tiles","required":false,"description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"default":"madrid-codex","example":"madrid-codex","fold":true}],"hasLang":true,"groups":[{"key":"personA","label":"Person A"},{"key":"personB","label":"Person B"},{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Mayan nawal compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true},{"key":"directionScheme","name":"directionScheme","kind":"tiles","required":false,"description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"default":"madrid-codex","example":"madrid-codex","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"personA","label":"Person A"},{"key":"personB","label":"Person B"},{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Convert a Maya Long Count","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Proleptic Gregorian date to convert INTO a Long Count. Supply this or longCount, never both and never neither.","example":"2012-12-21"},{"key":"longCount","name":"longCount","kind":"text","required":false,"description":"Dotted Long Count to convert INTO a date, written baktun.katun.tun.winal.kin. Each position is bounded by its own base, and the winal counts to 17 rather than to 19 because eighteen winal make a tun, so 9.12.11.18.0 is rejected as a date that does not exist. Supply this or date, never both and never neither.","example":"13.0.0.0.0","fold":true},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true}],"hasLang":true,"requiredAnyOf":[["date"],["longCount"]],"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Convert a Maya Long Count","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Proleptic Gregorian date to convert INTO a Long Count. Supply this or longCount, never both and never neither.","example":"2012-12-21"},{"key":"longCount","name":"longCount","kind":"text","required":false,"description":"Dotted Long Count to convert INTO a date, written baktun.katun.tun.winal.kin. Each position is bounded by its own base, and the winal counts to 17 rather than to 19 because eighteen winal make a tun, so 9.12.11.18.0 is rejected as a date that does not exist. Supply this or date, never both and never neither.","example":"13.0.0.0.0","fold":true},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["date"],["longCount"]],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Mayan day sign for a date","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Mayan day sign for a date","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","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 Birth Day number","fields":[{"key":"day","name":"day","kind":"number","required":true,"description":"Day of birth (1-31)","min":1,"max":31,"example":23}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Birth Day number","fields":[{"key":"day","name":"day","kind":"number","required":true,"description":"Day of birth (1-31)","min":1,"max":31,"example":23}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Bridge Numbers","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name as it appears on the birth certificate, first, middle and last names separated by spaces. Used to calculate the Expression, Soul Urge and Personality numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"},{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year between 100 and 2100. Used to calculate the Life Path number via Pythagorean reduction.","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1 to 12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1 to 31)","min":1,"max":31,"example":15}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Bridge Numbers","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name as it appears on the birth certificate, first, middle and last names separated by spaces. Used to calculate the Expression, Soul Urge and Personality numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"},{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year between 100 and 2100. Used to calculate the Life Path number via Pythagorean reduction.","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1 to 12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1 to 31)","min":1,"max":31,"example":15}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate business name numerology","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The business or brand name to evaluate. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"Ford"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate business name numerology","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The business or brand name to evaluate. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"Ford"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Chaldean numerology","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The name to analyze. Chaldean tradition uses the name a person is most known by, not necessarily the full legal birth name. It needs at least one vowel (A, E, I, O, U) and one consonant, since the Soul Urge is read from the vowels and the Personality from the consonants; Y counts as a consonant. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"Helen"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Chaldean numerology","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The name to analyze. Chaldean tradition uses the name a person is most known by, not necessarily the full legal birth name. It needs at least one vowel (A, E, I, O, U) and one consonant, since the Soul Urge is read from the vowels and the Personality from the consonants; Y counts as a consonant. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"Helen"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Generate numerology chart","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name as it appears on the birth certificate. Used for every letter-based number in the chart: Expression, Soul Urge, Personality, Karmic Lessons, Hidden Passion, Subconscious Self and the special letters. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"},{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":15},{"key":"currentYear","name":"currentYear","kind":"number","required":false,"description":"Calendar year for the Personal Year. When omitted it is the year of targetDate, or of the current UTC date when targetDate is omitted too. It moves the Personal Year only: the nested personalMonth and maturityStatus.currentAge read targetDate.","min":100,"max":2100,"example":2025,"fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to read the chart on, in YYYY-MM-DD format, in the years 100 to 2100, on or after the birth date. Send the local date of the user for an exact answer: it sets maturityStatus.currentAge and isActive, the Personal Month, and the Personal Year when currentYear is absent. Defaults to today (UTC).","example":"2026-10-28","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Generate numerology chart","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name as it appears on the birth certificate. Used for every letter-based number in the chart: Expression, Soul Urge, Personality, Karmic Lessons, Hidden Passion, Subconscious Self and the special letters. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"},{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":15},{"key":"currentYear","name":"currentYear","kind":"number","required":false,"description":"Calendar year for the Personal Year. When omitted it is the year of targetDate, or of the current UTC date when targetDate is omitted too. It moves the Personal Year only: the nested personalMonth and maturityStatus.currentAge read targetDate.","min":100,"max":2100,"example":2025,"fold":true},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Date to read the chart on, in YYYY-MM-DD format, in the years 100 to 2100, on or after the birth date. Send the local date of the user for an exact answer: it sets maturityStatus.currentAge and isActive, the Personal Month, and the Personal Year when currentYear is absent. Defaults to today (UTC).","example":"2026-10-28","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 numerology compatibility","fields":[{"key":"person1.fullName","name":"fullName","group":"person1","kind":"text","required":true,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"John William Smith"},{"key":"person1.year","name":"year","group":"person1","kind":"number","required":true,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1990},{"key":"person1.month","name":"month","group":"person1","kind":"number","required":true,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":7},{"key":"person1.day","name":"day","group":"person1","kind":"number","required":true,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":15},{"key":"person1.lifePath","name":"lifePath","group":"person1","kind":"number","required":false,"description":"Person 1 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":5},{"key":"person1.expression","name":"expression","group":"person1","kind":"number","required":false,"description":"Person 1 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":7},{"key":"person1.soulUrge","name":"soulUrge","group":"person1","kind":"number","required":false,"description":"Person 1 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":6},{"key":"person2.fullName","name":"fullName","group":"person2","kind":"text","required":true,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"Jane Marie Doe"},{"key":"person2.year","name":"year","group":"person2","kind":"number","required":true,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1992},{"key":"person2.month","name":"month","group":"person2","kind":"number","required":true,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":3},{"key":"person2.day","name":"day","group":"person2","kind":"number","required":true,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":22},{"key":"person2.lifePath","name":"lifePath","group":"person2","kind":"number","required":false,"description":"Person 2 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":3},{"key":"person2.expression","name":"expression","group":"person2","kind":"number","required":false,"description":"Person 2 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":9},{"key":"person2.soulUrge","name":"soulUrge","group":"person2","kind":"number","required":false,"description":"Person 2 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":2}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate numerology compatibility","fields":[{"key":"person1.fullName","name":"fullName","group":"person1","kind":"text","required":true,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"John William Smith"},{"key":"person1.year","name":"year","group":"person1","kind":"number","required":true,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1990},{"key":"person1.month","name":"month","group":"person1","kind":"number","required":true,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":7},{"key":"person1.day","name":"day","group":"person1","kind":"number","required":true,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":15},{"key":"person1.lifePath","name":"lifePath","group":"person1","kind":"number","required":false,"description":"Person 1 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":5},{"key":"person1.expression","name":"expression","group":"person1","kind":"number","required":false,"description":"Person 1 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":7},{"key":"person1.soulUrge","name":"soulUrge","group":"person1","kind":"number","required":false,"description":"Person 1 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":6},{"key":"person2.fullName","name":"fullName","group":"person2","kind":"text","required":true,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"Jane Marie Doe"},{"key":"person2.year","name":"year","group":"person2","kind":"number","required":true,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1992},{"key":"person2.month","name":"month","group":"person2","kind":"number","required":true,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":3},{"key":"person2.day","name":"day","group":"person2","kind":"number","required":true,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":22},{"key":"person2.lifePath","name":"lifePath","group":"person2","kind":"number","required":false,"description":"Person 2 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":3},{"key":"person2.expression","name":"expression","group":"person2","kind":"number","required":false,"description":"Person 2 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":9},{"key":"person2.soulUrge","name":"soulUrge","group":"person2","kind":"number","required":false,"description":"Person 2 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":2}],"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":"Get daily numerology number","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same number every time. Pass any unique identifier (userId, email hash, session token) to give each user their own number for the day. Without a seed every caller receives the same shared number 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 numerology number","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same number every time. Pass any unique identifier (userId, email hash, session token) to give each user their own number for the day. Without a seed every caller receives the same shared number 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":"Calculate dual numerology","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The name to analyze in both systems. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"David"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate dual numerology","fields":[{"key":"name","name":"name","kind":"text","required":true,"description":"The name to analyze in both systems. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"David"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Expression number","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name (first, middle, last). A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Expression number","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name (first, middle, last). A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Detect Karmic Debt numbers","fields":[{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year (checks Life Path)","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (checks Life Path)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (checks Birth Day on its own, and Life Path with year and month)","min":1,"max":31,"example":15},{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name (checks Expression, Soul Urge, Personality). A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"requiredAnyOf":[["fullName","year","month","day"],["day"],["fullName"]],"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Detect Karmic Debt numbers","fields":[{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year (checks Life Path)","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (checks Life Path)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (checks Birth Day on its own, and Life Path with year and month)","min":1,"max":31,"example":15},{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name (checks Expression, Soul Urge, Personality). A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["fullName","year","month","day"],["day"],["fullName"]],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Analyze Karmic Lessons","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name to analyze for missing numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Analyze Karmic Lessons","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name to analyze for missing numbers. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Life Path number","fields":[{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":15}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Life Path number","fields":[{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year between 100 and 2100. Supports historical figures like Einstein (1879) and Shakespeare (1564).","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":15}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Maturity number","fields":[{"key":"lifePath","name":"lifePath","kind":"number","required":false,"description":"Your Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":5,"fold":true},{"key":"expression","name":"expression","kind":"number","required":false,"description":"Your Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":7,"fold":true},{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name to calculate the Expression number automatically. Use instead of passing expression directly. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"},{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":15}],"hasLang":true,"requiredAnyOf":[["fullName","year","month","day"],["lifePath","expression"],["lifePath","fullName"],["expression","year","month","day"]],"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Maturity number","fields":[{"key":"lifePath","name":"lifePath","kind":"number","required":false,"description":"Your Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":5,"fold":true},{"key":"expression","name":"expression","kind":"number","required":false,"description":"Your Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":7,"fold":true},{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name to calculate the Expression number automatically. Use instead of passing expression directly. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"},{"key":"year","name":"year","kind":"number","required":true,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1990},{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":15}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["fullName","year","month","day"],["lifePath","expression"],["lifePath","fullName"],["expression","year","month","day"]],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Personal Day","fields":[{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":18},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Target date in YYYY-MM-DD format, in the years 100 to 2100. Defaults to today (UTC).","example":"2026-04-04","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Personal Day","fields":[{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":18},{"key":"targetDate","name":"targetDate","kind":"date","required":false,"description":"Target date in YYYY-MM-DD format, in the years 100 to 2100. Defaults to today (UTC).","example":"2026-04-04","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 Personal Month","fields":[{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":18},{"key":"year","name":"year","kind":"number","required":false,"description":"Target year. Defaults to the current UTC year.","min":100,"max":2100,"example":2026,"fold":true},{"key":"targetMonth","name":"targetMonth","kind":"number","required":false,"description":"Target calendar month to forecast (1 to 12). Defaults to the current UTC month.","min":1,"max":12,"example":4,"fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Personal Month","fields":[{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":18},{"key":"year","name":"year","kind":"number","required":false,"description":"Target year. Defaults to the current UTC year.","min":100,"max":2100,"example":2026,"fold":true},{"key":"targetMonth","name":"targetMonth","kind":"number","required":false,"description":"Target calendar month to forecast (1 to 12). Defaults to the current UTC month.","min":1,"max":12,"example":4,"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 Personal Year","fields":[{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":15},{"key":"year","name":"year","kind":"number","required":false,"description":"Year to forecast. Defaults to the current UTC year; the Personal Year turns over on 1 January.","min":100,"max":2100,"example":2025,"fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Personal Year","fields":[{"key":"month","name":"month","kind":"number","required":true,"description":"Birth month (1-12)","min":1,"max":12,"example":7},{"key":"day","name":"day","kind":"number","required":true,"description":"Birth day (1-31)","min":1,"max":31,"example":15},{"key":"year","name":"year","kind":"number","required":false,"description":"Year to forecast. Defaults to the current UTC year; the Personal Year turns over on 1 January.","min":100,"max":2100,"example":2025,"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 Personality number","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name. Its consonants give the Personality number, so a name with none is refused. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Personality number","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name. Its consonants give the Personality number, so a name with none is refused. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Calculate Soul Urge number","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name. Its vowels A, E, I, O and U give the Soul Urge, so a name with none is refused. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Calculate Soul Urge number","fields":[{"key":"fullName","name":"fullName","kind":"text","required":true,"description":"Full birth name. Its vowels A, E, I, O and U give the Soul Urge, so a name with none is refused. A name in any script is converted to Latin letters before it is counted, Cyrillic and Greek as the passport spelling and accents folded to the base letter, and the calculation lists the letters counted. For a script that does not write its vowels, send the Latin spelling the person uses.","example":"John William Smith"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Daily tarot card","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same card every time. Pass any unique identifier (userId, email hash, session token) to give each user their own card for the day. Without a seed every caller receives the same shared card 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":"Daily tarot card","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same card every time. Pass any unique identifier (userId, email hash, session token) to give each user their own card for the day. Without a seed every caller receives the same shared card 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":"Draw tarot cards","fields":[{"key":"count","name":"count","kind":"number","required":true,"description":"Number of cards to draw (1-78). Common values: 1 for daily card, 3 for past-present-future, 5 for relationship spread, 10 for Celtic Cross. Drawing 78 returns the entire shuffled deck.","min":1,"max":78,"example":3},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed = same cards in same order. Use format like \"userId-date\" for daily consistency, or \"readingId\" for shareable readings. Omit for true randomness.","example":"user123-2025-12-27","role":"seed"},{"key":"allowReversals","name":"allowReversals","kind":"toggle","required":false,"description":"Whether cards can appear reversed (upside down). Reversed cards have different meanings. Set false for upright-only readings. Default: true (50% chance of reversal per card).","default":true,"example":true,"fold":true},{"key":"allowDuplicates","name":"allowDuplicates","kind":"toggle","required":false,"description":"Whether same card can be drawn multiple times. Set false for traditional deck behavior (each card drawn only once). Set true for statistical analysis or oracle-style readings. Default: false.","default":false,"example":false,"fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Draw tarot cards","fields":[{"key":"count","name":"count","kind":"number","required":true,"description":"Number of cards to draw (1-78). Common values: 1 for daily card, 3 for past-present-future, 5 for relationship spread, 10 for Celtic Cross. Drawing 78 returns the entire shuffled deck.","min":1,"max":78,"example":3},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed = same cards in same order. Use format like \"userId-date\" for daily consistency, or \"readingId\" for shareable readings. Omit for true randomness.","example":"user123-2025-12-27","role":"seed"},{"key":"allowReversals","name":"allowReversals","kind":"toggle","required":false,"description":"Whether cards can appear reversed (upside down). Reversed cards have different meanings. Set false for upright-only readings. Default: true (50% chance of reversal per card).","default":true,"example":true,"fold":true},{"key":"allowDuplicates","name":"allowDuplicates","kind":"toggle","required":false,"description":"Whether same card can be drawn multiple times. Set false for traditional deck behavior (each card drawn only once). Set true for statistical analysis or oracle-style readings. Default: false.","default":false,"example":false,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Career spread, 7 cards","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the career spread. It is echoed back on the reading and gives the seven career positions their context. Omit for general work and vocation guidance.","example":"What do I need to know about my career path?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. The same seed always draws the same seven cards into the same career positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Career spread, 7 cards","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the career spread. It is echoed back on the reading and gives the seven career positions their context. Omit for general work and vocation guidance.","example":"What do I need to know about my career path?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. The same seed always draws the same seven cards into the same career positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Celtic Cross spread, 10 cards","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the Celtic Cross. It is echoed back on the reading and gives the ten positions their context. Omit for a general reading of the situation.","example":"What should I know about this situation?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. The same seed always draws the same ten cards into the same Celtic Cross positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Celtic Cross spread, 10 cards","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the Celtic Cross. It is echoed back on the reading and gives the ten positions their context. Omit for a general reading of the situation.","example":"What should I know about this situation?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. The same seed always draws the same ten cards into the same Celtic Cross positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Custom spread builder","fields":[{"key":"spreadName","name":"spreadName","kind":"text","required":false,"description":"Optional name for your custom tarot spread layout. Used as the spread identifier in the response.","example":"My Custom Spread","fold":true},{"key":"positions.0.name","name":"name","group":"positions.0","kind":"text","required":true,"description":"Name for this position in the spread (e.g. Core Issue, Hidden Factor, Best Action). Defines what aspect of the reading this card represents.","example":"Core Issue"},{"key":"positions.0.interpretation","name":"interpretation","group":"positions.0","kind":"text","required":true,"description":"Description of what this position reveals in the reading. Guides the tarot interpretation for the card drawn in this slot.","example":"What is really going on"},{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the custom tarot reading. Provides context for position-specific interpretations.","example":"How do I move forward with this project?","fold":true},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed with the same positions produces identical card draws for consistent divination.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"repeats":[{"key":"positions","min":1,"max":10}],"groups":[{},{"key":"positions.0","label":"Spread positions 1"}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Custom spread builder","fields":[{"key":"spreadName","name":"spreadName","kind":"text","required":false,"description":"Optional name for your custom tarot spread layout. Used as the spread identifier in the response.","example":"My Custom Spread","fold":true},{"key":"positions.0.name","name":"name","group":"positions.0","kind":"text","required":true,"description":"Name for this position in the spread (e.g. Core Issue, Hidden Factor, Best Action). Defines what aspect of the reading this card represents.","example":"Core Issue"},{"key":"positions.0.interpretation","name":"interpretation","group":"positions.0","kind":"text","required":true,"description":"Description of what this position reveals in the reading. Guides the tarot interpretation for the card drawn in this slot.","example":"What is really going on"},{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the custom tarot reading. Provides context for position-specific interpretations.","example":"How do I move forward with this project?","fold":true},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed with the same positions produces identical card draws for consistent divination.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"repeats":[{"key":"positions","min":1,"max":10}],"groups":[{},{"key":"positions.0","label":"Spread positions 1"}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Love spread, 5 cards","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the love spread. It is echoed back on the reading and gives the five relationship positions their context. Omit for general relationship guidance.","example":"What do I need to know about my relationship?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. The same seed always draws the same five cards into the same love positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Love spread, 5 cards","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the love spread. It is echoed back on the reading and gives the five relationship positions their context. Omit for general relationship guidance.","example":"What do I need to know about my relationship?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. The same seed always draws the same five cards into the same love positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Three card spread, past present future","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional specific question to focus the reading. Examples: \"What should I know about my relationship?\", \"How can I improve my finances?\", \"What is blocking my creative growth?\" Leave empty for general guidance.","example":"What do I need to know about my career?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed = same 3 cards in same positions. Useful for sharing readings, testing, or ensuring users get consistent results. Omit for random draws.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Three card spread, past present future","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Optional specific question to focus the reading. Examples: \"What should I know about my relationship?\", \"How can I improve my finances?\", \"What is blocking my creative growth?\" Leave empty for general guidance.","example":"What do I need to know about my career?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed = same 3 cards in same positions. Useful for sharing readings, testing, or ensuring users get consistent results. Omit for random draws.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"title":"Yes or no answer","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Your specific yes/no question. Be clear and focused. Good: \"Should I move to a new city?\" Bad: \"What should I do about my life?\" The more specific the question, the more useful the tarot guidance.","example":"Should I accept the job offer?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed + same question = same answer. Useful for testing, sharing readings, or ensuring consistency. Omit for random draws each time.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
|
|
1
|
+
{"title":"Yes or no answer","fields":[{"key":"question","name":"question","kind":"text","required":false,"description":"Your specific yes/no question. Be clear and focused. Good: \"Should I move to a new city?\" Bad: \"What should I do about my life?\" The more specific the question, the more useful the tarot guidance.","example":"Should I accept the job offer?"},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed + same question = same answer. Useful for testing, sharing readings, or ensuring consistency. Omit for random draws each time.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
|