@roxyapi/ui 1.1.3 → 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.
Files changed (514) hide show
  1. package/AGENTS.md +21 -1
  2. package/README.md +43 -1
  3. package/THEMING.md +32 -13
  4. package/components-catalog.json +1 -11247
  5. package/dist/cdn/components/almanac-day.js +3 -4
  6. package/dist/cdn/components/angel-number-card.js +3 -4
  7. package/dist/cdn/components/angel-number-lookup.js +3 -4
  8. package/dist/cdn/components/arudha-padas.js +3 -4
  9. package/dist/cdn/components/ashtakavarga-grid.js +3 -4
  10. package/dist/cdn/components/aspects-table.js +3 -4
  11. package/dist/cdn/components/astrocartography-map.js +9 -10
  12. package/dist/cdn/components/bazi-chart.js +3 -4
  13. package/dist/cdn/components/bhav-chalit-table.js +3 -4
  14. package/dist/cdn/components/bhava-bala-table.js +3 -4
  15. package/dist/cdn/components/biorhythm-chart.js +3 -4
  16. package/dist/cdn/components/bodygraph.js +14 -13
  17. package/dist/cdn/components/chara-karakas.js +3 -4
  18. package/dist/cdn/components/choghadiya-grid.js +3 -4
  19. package/dist/cdn/components/compatibility-card.js +3 -4
  20. package/dist/cdn/components/compound-number.js +3 -4
  21. package/dist/cdn/components/crystal-card.js +3 -4
  22. package/dist/cdn/components/crystal-grid.js +3 -4
  23. package/dist/cdn/components/dasha-timeline.js +3 -4
  24. package/dist/cdn/components/data.js +3 -4
  25. package/dist/cdn/components/divisional-chart.js +50 -49
  26. package/dist/cdn/components/dosha-card.js +3 -4
  27. package/dist/cdn/components/dosha-constitution.js +3 -4
  28. package/dist/cdn/components/dream-card.js +3 -4
  29. package/dist/cdn/components/dream-search.js +3 -4
  30. package/dist/cdn/components/endpoint-form.js +3 -4
  31. package/dist/cdn/components/ephemeris-table.js +3 -4
  32. package/dist/cdn/components/fixed-stars.js +3 -4
  33. package/dist/cdn/components/flying-star-chart.js +3 -4
  34. package/dist/cdn/components/forecast-digest.js +3 -4
  35. package/dist/cdn/components/forecast-timeline.js +3 -4
  36. package/dist/cdn/components/gematria.js +3 -4
  37. package/dist/cdn/components/gochara-table.js +3 -4
  38. package/dist/cdn/components/guna-milan.js +3 -4
  39. package/dist/cdn/components/hd-connection.js +13 -12
  40. package/dist/cdn/components/hd-penta.js +16 -17
  41. package/dist/cdn/components/hd-type-card.js +3 -4
  42. package/dist/cdn/components/hd-variables.js +3 -4
  43. package/dist/cdn/components/heliacal-table.js +3 -4
  44. package/dist/cdn/components/hexagram.js +3 -4
  45. package/dist/cdn/components/hora-table.js +3 -4
  46. package/dist/cdn/components/horoscope-card.js +3 -4
  47. package/dist/cdn/components/kp-chart.js +3 -4
  48. package/dist/cdn/components/kp-finance-card.js +3 -4
  49. package/dist/cdn/components/kp-planets-table.js +3 -4
  50. package/dist/cdn/components/kp-ruling-planets.js +3 -4
  51. package/dist/cdn/components/kua-card.js +3 -4
  52. package/dist/cdn/components/local-space-compass.js +6 -7
  53. package/dist/cdn/components/location-search.js +3 -4
  54. package/dist/cdn/components/luck-pillars.js +3 -4
  55. package/dist/cdn/components/mayan-day-sign.js +3 -4
  56. package/dist/cdn/components/moon-phase.js +3 -4
  57. package/dist/cdn/components/nakshatra-card.js +3 -4
  58. package/dist/cdn/components/natal-chart.js +24 -14
  59. package/dist/cdn/components/numerology-card.js +3 -4
  60. package/dist/cdn/components/panchang-table.js +3 -4
  61. package/dist/cdn/components/positions-table.js +3 -4
  62. package/dist/cdn/components/profection-card.js +3 -4
  63. package/dist/cdn/components/reference-card.js +3 -4
  64. package/dist/cdn/components/relocation-wheel.js +24 -14
  65. package/dist/cdn/components/shadbala-table.js +3 -4
  66. package/dist/cdn/components/synastry-chart.js +21 -12
  67. package/dist/cdn/components/tarot-card.js +3 -4
  68. package/dist/cdn/components/tarot-catalog.js +3 -4
  69. package/dist/cdn/components/tarot-spread.js +3 -4
  70. package/dist/cdn/components/transit-wheel.js +10 -11
  71. package/dist/cdn/components/transits-table.js +3 -4
  72. package/dist/cdn/components/upagraha-table.js +3 -4
  73. package/dist/cdn/components/vastu-mandala.js +10 -11
  74. package/dist/cdn/components/vedic-aspects.js +3 -4
  75. package/dist/cdn/components/vedic-daily.js +3 -4
  76. package/dist/cdn/components/vedic-kundli.js +62 -61
  77. package/dist/cdn/components/vedic-planets-table.js +3 -4
  78. package/dist/cdn/components/western-planets-table.js +3 -4
  79. package/dist/cdn/components/yoga-list.js +3 -4
  80. package/dist/cdn/components/zodiac-card.js +3 -4
  81. package/dist/cdn/locales/de.js +1 -1
  82. package/dist/cdn/locales/es.js +1 -1
  83. package/dist/cdn/locales/fr.js +1 -1
  84. package/dist/cdn/locales/hi.js +1 -1
  85. package/dist/cdn/locales/pt.js +1 -1
  86. package/dist/cdn/locales/ru.js +1 -1
  87. package/dist/cdn/locales/tr.js +1 -1
  88. package/dist/cdn/roxy-ui.js +113 -96
  89. package/dist/cdn/widgets.js +1 -1
  90. package/dist/charts.cjs +111 -0
  91. package/dist/charts.d.ts +8 -0
  92. package/dist/charts.js +111 -0
  93. package/dist/components/almanac-day.js +1 -1
  94. package/dist/components/angel-number-card.js +1 -1
  95. package/dist/components/angel-number-lookup.js +1 -1
  96. package/dist/components/arudha-padas.js +1 -1
  97. package/dist/components/ashtakavarga-grid.js +1 -1
  98. package/dist/components/aspects-table.js +1 -1
  99. package/dist/components/astrocartography-map.js +5 -5
  100. package/dist/components/bazi-chart.js +1 -1
  101. package/dist/components/bhav-chalit-table.js +1 -1
  102. package/dist/components/bhava-bala-table.js +1 -1
  103. package/dist/components/biorhythm-chart.js +1 -1
  104. package/dist/components/bodygraph.d.ts +0 -4
  105. package/dist/components/bodygraph.js +10 -10
  106. package/dist/components/chara-karakas.js +1 -1
  107. package/dist/components/choghadiya-grid.js +1 -1
  108. package/dist/components/compatibility-card.js +1 -1
  109. package/dist/components/compound-number.js +1 -1
  110. package/dist/components/crystal-card.js +1 -1
  111. package/dist/components/crystal-grid.js +1 -1
  112. package/dist/components/dasha-timeline.js +1 -1
  113. package/dist/components/data.js +1 -1
  114. package/dist/components/divisional-chart.js +60 -60
  115. package/dist/components/dosha-card.js +1 -1
  116. package/dist/components/dosha-constitution.js +1 -1
  117. package/dist/components/dream-card.js +1 -1
  118. package/dist/components/dream-search.js +1 -1
  119. package/dist/components/endpoint-form.d.ts +3 -1
  120. package/dist/components/endpoint-form.js +1 -1
  121. package/dist/components/ephemeris-table.js +1 -1
  122. package/dist/components/fixed-stars.js +1 -1
  123. package/dist/components/flying-star-chart.js +1 -1
  124. package/dist/components/forecast-digest.js +1 -1
  125. package/dist/components/forecast-timeline.js +1 -1
  126. package/dist/components/gematria.js +1 -1
  127. package/dist/components/gochara-table.js +1 -1
  128. package/dist/components/guna-milan.js +1 -1
  129. package/dist/components/hd-connection.js +10 -10
  130. package/dist/components/hd-penta.js +16 -16
  131. package/dist/components/hd-type-card.js +1 -1
  132. package/dist/components/hd-variables.js +1 -1
  133. package/dist/components/heliacal-table.js +1 -1
  134. package/dist/components/hexagram.js +1 -1
  135. package/dist/components/hora-table.js +1 -1
  136. package/dist/components/horoscope-card.js +1 -1
  137. package/dist/components/kp-chart.js +1 -1
  138. package/dist/components/kp-finance-card.js +1 -1
  139. package/dist/components/kp-planets-table.js +1 -1
  140. package/dist/components/kp-ruling-planets.js +1 -1
  141. package/dist/components/kua-card.js +1 -1
  142. package/dist/components/local-space-compass.js +5 -5
  143. package/dist/components/location-search.d.ts +1 -0
  144. package/dist/components/location-search.js +1 -1
  145. package/dist/components/luck-pillars.js +1 -1
  146. package/dist/components/mayan-day-sign.js +1 -1
  147. package/dist/components/moon-phase.js +1 -1
  148. package/dist/components/nakshatra-card.js +1 -1
  149. package/dist/components/natal-chart.d.ts +3 -82
  150. package/dist/components/natal-chart.js +20 -11
  151. package/dist/components/numerology-card.js +1 -1
  152. package/dist/components/panchang-table.js +1 -1
  153. package/dist/components/positions-table.js +1 -1
  154. package/dist/components/profection-card.js +1 -1
  155. package/dist/components/reference-card.js +1 -1
  156. package/dist/components/relocation-wheel.js +20 -11
  157. package/dist/components/shadbala-table.js +1 -1
  158. package/dist/components/synastry-chart.d.ts +2 -34
  159. package/dist/components/synastry-chart.js +17 -9
  160. package/dist/components/tarot-card.js +1 -1
  161. package/dist/components/tarot-catalog.js +1 -1
  162. package/dist/components/tarot-spread.js +1 -1
  163. package/dist/components/transit-wheel.js +7 -7
  164. package/dist/components/transits-table.js +1 -1
  165. package/dist/components/upagraha-table.js +1 -1
  166. package/dist/components/vastu-mandala.js +9 -9
  167. package/dist/components/vedic-aspects.js +1 -1
  168. package/dist/components/vedic-daily.js +1 -1
  169. package/dist/components/vedic-kundli.js +54 -54
  170. package/dist/components/vedic-planets-table.js +1 -1
  171. package/dist/components/western-planets-table.js +1 -1
  172. package/dist/components/yoga-list.js +1 -1
  173. package/dist/components/zodiac-card.js +1 -1
  174. package/dist/forms/labels/de.json +1 -1
  175. package/dist/forms/labels/en.json +1 -1
  176. package/dist/forms/labels/es.json +1 -1
  177. package/dist/forms/labels/fr.json +1 -1
  178. package/dist/forms/labels/hi.json +1 -1
  179. package/dist/forms/labels/pt.json +1 -1
  180. package/dist/forms/labels/ru.json +1 -1
  181. package/dist/forms/labels/tr.json +1 -1
  182. package/dist/forms.json +1 -1
  183. package/dist/generated/field-labels-en.d.ts +1 -1
  184. package/dist/i18n/chrome-strings.d.ts +1 -1
  185. package/dist/i18n/lang.d.ts +3 -1
  186. package/dist/i18n/localized-element.d.ts +4 -0
  187. package/dist/i18n/registry.d.ts +7 -0
  188. package/dist/index.cjs +111 -94
  189. package/dist/index.js +110 -93
  190. package/dist/locales/de.js +1 -1
  191. package/dist/locales/es.js +1 -1
  192. package/dist/locales/field-labels/de.d.ts +1 -1
  193. package/dist/locales/field-labels/es.d.ts +1 -1
  194. package/dist/locales/field-labels/fr.d.ts +1 -1
  195. package/dist/locales/field-labels/hi.d.ts +1 -1
  196. package/dist/locales/field-labels/pt.d.ts +1 -1
  197. package/dist/locales/field-labels/ru.d.ts +1 -1
  198. package/dist/locales/field-labels/tr.d.ts +1 -1
  199. package/dist/locales/fr.js +1 -1
  200. package/dist/locales/hi.js +1 -1
  201. package/dist/locales/pt.js +1 -1
  202. package/dist/locales/ru.js +1 -1
  203. package/dist/locales/tr.js +1 -1
  204. package/dist/manifest.d.ts +3 -5
  205. package/dist/manifest.json +1 -89
  206. package/dist/schemas/get--angel-numbers-lookup.json +1 -1
  207. package/dist/schemas/get--angel-numbers-numbers-number.json +1 -1
  208. package/dist/schemas/get--angel-numbers-numbers.json +1 -1
  209. package/dist/schemas/get--astrology-horoscope-sign-daily.json +1 -1
  210. package/dist/schemas/get--astrology-horoscope-sign-monthly.json +1 -1
  211. package/dist/schemas/get--astrology-horoscope-sign-weekly.json +1 -1
  212. package/dist/schemas/get--astrology-horoscope-sign-yearly.json +1 -1
  213. package/dist/schemas/get--astrology-moon-phase-calendar-year-month.json +1 -1
  214. package/dist/schemas/get--astrology-moon-phase-current.json +1 -1
  215. package/dist/schemas/get--astrology-moon-phase-upcoming.json +1 -1
  216. package/dist/schemas/get--astrology-planet-meanings-id.json +1 -1
  217. package/dist/schemas/get--astrology-planet-meanings.json +1 -1
  218. package/dist/schemas/get--astrology-signs-id.json +1 -1
  219. package/dist/schemas/get--astrology-signs.json +1 -1
  220. package/dist/schemas/get--ayurveda-daily.json +1 -1
  221. package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
  222. package/dist/schemas/get--ayurveda-doshas.json +1 -1
  223. package/dist/schemas/get--ayurveda-qualities.json +1 -1
  224. package/dist/schemas/get--ayurveda-tastes.json +1 -1
  225. package/dist/schemas/get--chinese-astrology-calendar-day-date.json +1 -1
  226. package/dist/schemas/get--chinese-astrology-calendar-monthly.json +1 -1
  227. package/dist/schemas/get--chinese-astrology-calendar-solar-terms-year.json +1 -1
  228. package/dist/schemas/get--chinese-astrology-elements.json +1 -1
  229. package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
  230. package/dist/schemas/get--chinese-astrology-zodiac-animals.json +1 -1
  231. package/dist/schemas/get--chinese-astrology-zodiac-compatibility-sign1-sign2.json +1 -1
  232. package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
  233. package/dist/schemas/get--crystals-birthstone-month.json +1 -1
  234. package/dist/schemas/get--crystals-chakra-chakra.json +1 -1
  235. package/dist/schemas/get--crystals-colors.json +1 -1
  236. package/dist/schemas/get--crystals-element-element.json +1 -1
  237. package/dist/schemas/get--crystals-id.json +1 -1
  238. package/dist/schemas/get--crystals-pairings-id.json +1 -1
  239. package/dist/schemas/get--crystals-planets.json +1 -1
  240. package/dist/schemas/get--crystals-random.json +1 -1
  241. package/dist/schemas/get--crystals-search.json +1 -1
  242. package/dist/schemas/get--crystals-zodiac-sign.json +1 -1
  243. package/dist/schemas/get--crystals.json +1 -1
  244. package/dist/schemas/get--dreams-symbols-id.json +1 -1
  245. package/dist/schemas/get--dreams-symbols-letters.json +1 -1
  246. package/dist/schemas/get--dreams-symbols-random.json +1 -1
  247. package/dist/schemas/get--dreams-symbols.json +1 -1
  248. package/dist/schemas/get--feng-shui-afflictions-year.json +1 -1
  249. package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
  250. package/dist/schemas/get--feng-shui-bagua.json +1 -1
  251. package/dist/schemas/get--feng-shui-flying-stars-annual-year.json +1 -1
  252. package/dist/schemas/get--feng-shui-flying-stars-monthly.json +1 -1
  253. package/dist/schemas/get--feng-shui-flying-stars-stars.json +1 -1
  254. package/dist/schemas/get--feng-shui-kua-number.json +1 -1
  255. package/dist/schemas/get--feng-shui-periods.json +1 -1
  256. package/dist/schemas/get--human-design-centers-id.json +1 -1
  257. package/dist/schemas/get--human-design-gates-number.json +1 -1
  258. package/dist/schemas/get--iching-cast.json +1 -1
  259. package/dist/schemas/get--iching-hexagrams-lookup.json +1 -1
  260. package/dist/schemas/get--iching-hexagrams-number.json +1 -1
  261. package/dist/schemas/get--iching-hexagrams-random.json +1 -1
  262. package/dist/schemas/get--iching-hexagrams.json +1 -1
  263. package/dist/schemas/get--iching-trigrams-id.json +1 -1
  264. package/dist/schemas/get--iching-trigrams.json +1 -1
  265. package/dist/schemas/get--kabbalah-ciphers.json +1 -1
  266. package/dist/schemas/get--kabbalah-daily.json +1 -1
  267. package/dist/schemas/get--kabbalah-letters-id.json +1 -1
  268. package/dist/schemas/get--kabbalah-letters.json +1 -1
  269. package/dist/schemas/get--kabbalah-names-number.json +1 -1
  270. package/dist/schemas/get--kabbalah-names.json +1 -1
  271. package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
  272. package/dist/schemas/get--kabbalah-tree.json +1 -1
  273. package/dist/schemas/get--languages-field-labels.json +1 -1
  274. package/dist/schemas/get--languages.json +1 -1
  275. package/dist/schemas/get--location-countries-iso2.json +1 -1
  276. package/dist/schemas/get--location-countries.json +1 -1
  277. package/dist/schemas/get--location-search.json +1 -1
  278. package/dist/schemas/get--mesoamerican-astrology-aztec-daily.json +1 -1
  279. package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
  280. package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs.json +1 -1
  281. package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas-number.json +1 -1
  282. package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas.json +1 -1
  283. package/dist/schemas/get--mesoamerican-astrology-mayan-calendar-monthly.json +1 -1
  284. package/dist/schemas/get--mesoamerican-astrology-mayan-daily.json +1 -1
  285. package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
  286. package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs.json +1 -1
  287. package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
  288. package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months.json +1 -1
  289. package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas-number.json +1 -1
  290. package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas.json +1 -1
  291. package/dist/schemas/get--numerology-compound-number-number.json +1 -1
  292. package/dist/schemas/get--numerology-meanings-number.json +1 -1
  293. package/dist/schemas/get--tarot-cards-id.json +1 -1
  294. package/dist/schemas/get--tarot-cards.json +1 -1
  295. package/dist/schemas/get--usage.json +1 -1
  296. package/dist/schemas/get--vastu-devatas-id.json +1 -1
  297. package/dist/schemas/get--vastu-devatas.json +1 -1
  298. package/dist/schemas/get--vastu-directions-id.json +1 -1
  299. package/dist/schemas/get--vastu-directions.json +1 -1
  300. package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
  301. package/dist/schemas/get--vedic-astrology-avasthas.json +1 -1
  302. package/dist/schemas/get--vedic-astrology-kp-ayanamsa.json +1 -1
  303. package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
  304. package/dist/schemas/get--vedic-astrology-nakshatras.json +1 -1
  305. package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
  306. package/dist/schemas/get--vedic-astrology-rashis.json +1 -1
  307. package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
  308. package/dist/schemas/get--vedic-astrology-yoga.json +1 -1
  309. package/dist/schemas/post--angel-numbers-daily.json +1 -1
  310. package/dist/schemas/post--astrology-arabic-lots.json +1 -1
  311. package/dist/schemas/post--astrology-aspect-patterns.json +1 -1
  312. package/dist/schemas/post--astrology-aspects-monthly.json +1 -1
  313. package/dist/schemas/post--astrology-aspects.json +1 -1
  314. package/dist/schemas/post--astrology-asteroids.json +1 -1
  315. package/dist/schemas/post--astrology-astrocartography.json +1 -1
  316. package/dist/schemas/post--astrology-compatibility-score.json +1 -1
  317. package/dist/schemas/post--astrology-composite-chart.json +1 -1
  318. package/dist/schemas/post--astrology-ecliptic-crossings.json +1 -1
  319. package/dist/schemas/post--astrology-fixed-stars.json +1 -1
  320. package/dist/schemas/post--astrology-houses.json +1 -1
  321. package/dist/schemas/post--astrology-lilith.json +1 -1
  322. package/dist/schemas/post--astrology-local-space.json +1 -1
  323. package/dist/schemas/post--astrology-lunar-return.json +1 -1
  324. package/dist/schemas/post--astrology-natal-chart.json +1 -1
  325. package/dist/schemas/post--astrology-parallels-monthly.json +1 -1
  326. package/dist/schemas/post--astrology-planetary-returns.json +1 -1
  327. package/dist/schemas/post--astrology-planets-monthly.json +1 -1
  328. package/dist/schemas/post--astrology-planets.json +1 -1
  329. package/dist/schemas/post--astrology-profections.json +1 -1
  330. package/dist/schemas/post--astrology-progressions.json +1 -1
  331. package/dist/schemas/post--astrology-relocation-chart.json +1 -1
  332. package/dist/schemas/post--astrology-solar-arc.json +1 -1
  333. package/dist/schemas/post--astrology-solar-return.json +1 -1
  334. package/dist/schemas/post--astrology-synastry.json +1 -1
  335. package/dist/schemas/post--astrology-transit-aspects.json +1 -1
  336. package/dist/schemas/post--astrology-transits-monthly.json +1 -1
  337. package/dist/schemas/post--astrology-transits.json +1 -1
  338. package/dist/schemas/post--ayurveda-constitution.json +1 -1
  339. package/dist/schemas/post--ayurveda-dinacharya.json +1 -1
  340. package/dist/schemas/post--ayurveda-ritucharya.json +1 -1
  341. package/dist/schemas/post--biorhythm-compatibility.json +1 -1
  342. package/dist/schemas/post--biorhythm-critical-days.json +1 -1
  343. package/dist/schemas/post--biorhythm-daily.json +1 -1
  344. package/dist/schemas/post--biorhythm-forecast.json +1 -1
  345. package/dist/schemas/post--biorhythm-phases.json +1 -1
  346. package/dist/schemas/post--biorhythm-reading.json +1 -1
  347. package/dist/schemas/post--chinese-astrology-bazi-annual-forecast.json +1 -1
  348. package/dist/schemas/post--chinese-astrology-bazi-chart.json +1 -1
  349. package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
  350. package/dist/schemas/post--chinese-astrology-bazi-day-master.json +1 -1
  351. package/dist/schemas/post--chinese-astrology-bazi-luck-pillars.json +1 -1
  352. package/dist/schemas/post--chinese-astrology-calendar-auspicious-days.json +1 -1
  353. package/dist/schemas/post--chinese-astrology-calendar-lunar-date.json +1 -1
  354. package/dist/schemas/post--chinese-astrology-zodiac-sign.json +1 -1
  355. package/dist/schemas/post--crystals-daily.json +1 -1
  356. package/dist/schemas/post--dreams-daily.json +1 -1
  357. package/dist/schemas/post--feng-shui-eight-mansions.json +1 -1
  358. package/dist/schemas/post--feng-shui-flying-stars-natal.json +1 -1
  359. package/dist/schemas/post--feng-shui-kua.json +1 -1
  360. package/dist/schemas/post--forecast-digest.json +1 -1
  361. package/dist/schemas/post--forecast-significant-dates.json +1 -1
  362. package/dist/schemas/post--forecast-solar-return.json +1 -1
  363. package/dist/schemas/post--forecast-timeline.json +1 -1
  364. package/dist/schemas/post--forecast-transits.json +1 -1
  365. package/dist/schemas/post--human-design-bodygraph.json +1 -1
  366. package/dist/schemas/post--human-design-centers.json +1 -1
  367. package/dist/schemas/post--human-design-channels.json +1 -1
  368. package/dist/schemas/post--human-design-connection.json +1 -1
  369. package/dist/schemas/post--human-design-gates.json +1 -1
  370. package/dist/schemas/post--human-design-penta.json +1 -1
  371. package/dist/schemas/post--human-design-profile.json +1 -1
  372. package/dist/schemas/post--human-design-transit.json +1 -1
  373. package/dist/schemas/post--human-design-type.json +1 -1
  374. package/dist/schemas/post--human-design-variables.json +1 -1
  375. package/dist/schemas/post--iching-daily-cast.json +1 -1
  376. package/dist/schemas/post--iching-daily.json +1 -1
  377. package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
  378. package/dist/schemas/post--kabbalah-compatibility.json +1 -1
  379. package/dist/schemas/post--kabbalah-gematria.json +1 -1
  380. package/dist/schemas/post--kabbalah-name-profile.json +1 -1
  381. package/dist/schemas/post--mesoamerican-astrology-aztec-tonalpohualli.json +1 -1
  382. package/dist/schemas/post--mesoamerican-astrology-mayan-chart.json +1 -1
  383. package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
  384. package/dist/schemas/post--mesoamerican-astrology-mayan-long-count-convert.json +1 -1
  385. package/dist/schemas/post--mesoamerican-astrology-mayan-tzolkin.json +1 -1
  386. package/dist/schemas/post--numerology-birth-day.json +1 -1
  387. package/dist/schemas/post--numerology-bridge.json +1 -1
  388. package/dist/schemas/post--numerology-business-name.json +1 -1
  389. package/dist/schemas/post--numerology-chaldean.json +1 -1
  390. package/dist/schemas/post--numerology-chart.json +1 -1
  391. package/dist/schemas/post--numerology-compatibility.json +1 -1
  392. package/dist/schemas/post--numerology-daily.json +1 -1
  393. package/dist/schemas/post--numerology-dual.json +1 -1
  394. package/dist/schemas/post--numerology-expression.json +1 -1
  395. package/dist/schemas/post--numerology-karmic-debt.json +1 -1
  396. package/dist/schemas/post--numerology-karmic-lessons.json +1 -1
  397. package/dist/schemas/post--numerology-life-path.json +1 -1
  398. package/dist/schemas/post--numerology-maturity.json +1 -1
  399. package/dist/schemas/post--numerology-personal-day.json +1 -1
  400. package/dist/schemas/post--numerology-personal-month.json +1 -1
  401. package/dist/schemas/post--numerology-personal-year.json +1 -1
  402. package/dist/schemas/post--numerology-personality.json +1 -1
  403. package/dist/schemas/post--numerology-soul-urge.json +1 -1
  404. package/dist/schemas/post--tarot-daily.json +1 -1
  405. package/dist/schemas/post--tarot-draw.json +1 -1
  406. package/dist/schemas/post--tarot-spreads-career.json +1 -1
  407. package/dist/schemas/post--tarot-spreads-celtic-cross.json +1 -1
  408. package/dist/schemas/post--tarot-spreads-custom.json +1 -1
  409. package/dist/schemas/post--tarot-spreads-love.json +1 -1
  410. package/dist/schemas/post--tarot-spreads-three-card.json +1 -1
  411. package/dist/schemas/post--tarot-yes-no.json +1 -1
  412. package/dist/schemas/post--vastu-ayadi.json +1 -1
  413. package/dist/schemas/post--vastu-entrance.json +1 -1
  414. package/dist/schemas/post--vastu-mandala.json +1 -1
  415. package/dist/schemas/post--vastu-plot.json +1 -1
  416. package/dist/schemas/post--vastu-rooms.json +1 -1
  417. package/dist/schemas/post--vastu-timing-griha-pravesh.json +1 -1
  418. package/dist/schemas/post--vedic-astrology-arudha.json +1 -1
  419. package/dist/schemas/post--vedic-astrology-ashtakavarga.json +1 -1
  420. package/dist/schemas/post--vedic-astrology-aspects-lunar.json +1 -1
  421. package/dist/schemas/post--vedic-astrology-aspects-monthly.json +1 -1
  422. package/dist/schemas/post--vedic-astrology-aspects.json +1 -1
  423. package/dist/schemas/post--vedic-astrology-bhav-chalit.json +1 -1
  424. package/dist/schemas/post--vedic-astrology-bhava-bala.json +1 -1
  425. package/dist/schemas/post--vedic-astrology-birth-chart.json +1 -1
  426. package/dist/schemas/post--vedic-astrology-chara-karakas.json +1 -1
  427. package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
  428. package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
  429. package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
  430. package/dist/schemas/post--vedic-astrology-daily.json +1 -1
  431. package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
  432. package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
  433. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
  434. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
  435. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
  436. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
  437. package/dist/schemas/post--vedic-astrology-divisional-chart.json +1 -1
  438. package/dist/schemas/post--vedic-astrology-dosha-kalsarpa.json +1 -1
  439. package/dist/schemas/post--vedic-astrology-dosha-manglik.json +1 -1
  440. package/dist/schemas/post--vedic-astrology-dosha-sadhesati.json +1 -1
  441. package/dist/schemas/post--vedic-astrology-ecliptic-crossings.json +1 -1
  442. package/dist/schemas/post--vedic-astrology-heliacal.json +1 -1
  443. package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
  444. package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
  445. package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
  446. package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
  447. package/dist/schemas/post--vedic-astrology-kp-planets-interval.json +1 -1
  448. package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
  449. package/dist/schemas/post--vedic-astrology-kp-rasi-changes.json +1 -1
  450. package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
  451. package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
  452. package/dist/schemas/post--vedic-astrology-kp-sublord-changes.json +1 -1
  453. package/dist/schemas/post--vedic-astrology-navamsa.json +1 -1
  454. package/dist/schemas/post--vedic-astrology-panchang-basic.json +1 -1
  455. package/dist/schemas/post--vedic-astrology-panchang-choghadiya.json +1 -1
  456. package/dist/schemas/post--vedic-astrology-panchang-detailed.json +1 -1
  457. package/dist/schemas/post--vedic-astrology-panchang-hora.json +1 -1
  458. package/dist/schemas/post--vedic-astrology-parallels-monthly.json +1 -1
  459. package/dist/schemas/post--vedic-astrology-parallels.json +1 -1
  460. package/dist/schemas/post--vedic-astrology-planetary-positions-monthly.json +1 -1
  461. package/dist/schemas/post--vedic-astrology-planetary-positions.json +1 -1
  462. package/dist/schemas/post--vedic-astrology-shadbala.json +1 -1
  463. package/dist/schemas/post--vedic-astrology-transit-monthly.json +1 -1
  464. package/dist/schemas/post--vedic-astrology-transit.json +1 -1
  465. package/dist/schemas/post--vedic-astrology-upagraha.json +1 -1
  466. package/dist/schemas/post--vedic-astrology-yoga-detect.json +1 -1
  467. package/dist/styles/charts/bodygraph.css +1 -0
  468. package/dist/styles/charts/kundli.css +1 -0
  469. package/dist/styles/charts/natal-wheel.css +1 -0
  470. package/dist/styles/charts/synastry-wheel.css +1 -0
  471. package/dist/styles/fonts/fraunces-jost.css +1 -0
  472. package/dist/styles/fonts/geist/OFL.txt +93 -0
  473. package/dist/styles/fonts/geist/geist-cyrillic.woff2 +0 -0
  474. package/dist/styles/fonts/geist/geist-latin-ext.woff2 +0 -0
  475. package/dist/styles/fonts/geist/geist-latin.woff2 +0 -0
  476. package/dist/styles/fonts/geist.css +1 -0
  477. package/dist/styles/fonts/jost.css +1 -0
  478. package/dist/styles/fonts.d.ts +23 -0
  479. package/dist/styles/palette-names.d.ts +3 -0
  480. package/dist/styles/palettes.d.ts +6 -19
  481. package/dist/styles/themes/celeste.css +1 -1
  482. package/dist/styles/themes/eucalyptus.css +1 -1
  483. package/dist/styles/themes/kiln.css +1 -1
  484. package/dist/styles/themes/moonlit.css +1 -1
  485. package/dist/styles/themes/practitioner.css +1 -1
  486. package/dist/styles/tokens-css.d.ts +1 -1
  487. package/dist/styles/tokens.css +1 -1
  488. package/dist/tool-component.cjs +1 -1
  489. package/dist/tool-component.js +1 -1
  490. package/dist/utils/angel-sections.d.ts +1 -1
  491. package/dist/utils/aspect-line.d.ts +1 -10
  492. package/dist/utils/aspect-styles.d.ts +4 -0
  493. package/dist/utils/base-element.d.ts +15 -2
  494. package/dist/utils/bodygraph-render.d.ts +18 -2
  495. package/dist/utils/bodygraph-styles.d.ts +1 -6
  496. package/dist/utils/brand.d.ts +22 -0
  497. package/dist/utils/chart-styles.d.ts +9 -0
  498. package/dist/utils/chart-viewport.d.ts +1 -1
  499. package/dist/utils/degree.d.ts +7 -0
  500. package/dist/utils/dist-base.d.ts +2 -0
  501. package/dist/utils/fetch-controller.d.ts +9 -2
  502. package/dist/utils/field-schema.d.ts +10 -4
  503. package/dist/utils/frame.d.ts +1 -1
  504. package/dist/utils/hd-reading.d.ts +1 -14
  505. package/dist/utils/interp-accordion.d.ts +1 -1
  506. package/dist/utils/kundli-chrome.d.ts +22 -0
  507. package/dist/utils/kundli-render.d.ts +17 -28
  508. package/dist/utils/natal-wheel.d.ts +32 -0
  509. package/dist/utils/reference-table.d.ts +7 -0
  510. package/dist/utils/stacked-table.d.ts +1 -1
  511. package/dist/utils/svg-string.d.ts +20 -0
  512. package/dist/utils/synastry-wheel.d.ts +15 -0
  513. package/dist/version.d.ts +1 -1
  514. package/package.json +10 -2
@@ -1 +1 @@
1
- {"title":"Calculate BaZi compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"personA.time","name":"time","group":"personA","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"personA.timezone","name":"timezone","group":"personA","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":"personA.latitude","name":"latitude","group":"personA","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personA.longitude","name":"longitude","group":"personA","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personA.dayBoundary","name":"dayBoundary","group":"personA","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi"},{"key":"personA.yearBoundary","name":"yearBoundary","group":"personA","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun"},{"key":"personA.hourClock","name":"hourClock","group":"personA","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"personB.time","name":"time","group":"personB","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"personB.timezone","name":"timezone","group":"personB","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":"personB.latitude","name":"latitude","group":"personB","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personB.longitude","name":"longitude","group":"personB","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personB.dayBoundary","name":"dayBoundary","group":"personB","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi"},{"key":"personB.yearBoundary","name":"yearBoundary","group":"personB","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun"},{"key":"personB.hourClock","name":"hourClock","group":"personB","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock"}],"hasLang":true,"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate BaZi compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"personA.time","name":"time","group":"personA","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"personA.timezone","name":"timezone","group":"personA","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":"personA.latitude","name":"latitude","group":"personA","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personA.longitude","name":"longitude","group":"personA","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personA.dayBoundary","name":"dayBoundary","group":"personA","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi"},{"key":"personA.yearBoundary","name":"yearBoundary","group":"personA","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun"},{"key":"personA.hourClock","name":"hourClock","group":"personA","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"personB.time","name":"time","group":"personB","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"personB.timezone","name":"timezone","group":"personB","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":"personB.latitude","name":"latitude","group":"personB","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personB.longitude","name":"longitude","group":"personB","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"personB.dayBoundary","name":"dayBoundary","group":"personB","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi"},{"key":"personB.yearBoundary","name":"yearBoundary","group":"personB","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun"},{"key":"personB.hourClock","name":"hourClock","group":"personB","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate Day Master strength","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate Day Master strength","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate luck pillars","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true},{"key":"gender","name":"gender","kind":"tiles","required":true,"description":"Subject sex, used only to pick the luck-pillar direction: a male born in a yang-stem year and a female born in a yin-stem year run forward through the sexagenary cycle, and the other two combinations run backward. It affects nothing else in the response.","enum":["male","female"],"example":"male"},{"key":"count","name":"count","kind":"number","required":false,"description":"How many ten-year luck pillars to return, 1 to 12. Eight covers eighty years from the start age, which reaches past a normal lifetime for most start ages.","min":1,"max":12,"default":8,"example":8,"fold":true},{"key":"annualFromYear","name":"annualFromYear","kind":"number","required":false,"description":"First Gregorian year of the annual pillar overlay. Omit it to leave annualPillars out of the response entirely. The annual pillar is the year the chart is currently walking through, read against the ten-year luck pillar underneath it.","min":1551,"max":2649,"example":2026,"fold":true},{"key":"annualYears","name":"annualYears","kind":"number","required":false,"description":"How many consecutive years the annual overlay covers, 1 to 20. Ignored unless annualFromYear is present.","min":1,"max":20,"default":10,"example":10,"fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate luck pillars","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"latitude","name":"latitude","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Accepted for consistency with the other birth-data endpoints and does not affect any part of a BaZi chart. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Positive is East, negative is West. Required when hourClock is \"local-mean\" or \"solar\", which shift the hour branch to the sun over the birth place; omitting it in either case returns 400. Ignored when hourClock is \"clock\".","min":-180,"max":180,"example":116.4,"role":"location"},{"key":"dayBoundary","name":"dayBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary DAY, which only matters for a birth between 23:00 and 23:59. \"midnight\" is the classical position of the Ming compendium San Ming Tong Hui: the day turns at 00:00 and 23:00 to 23:59 is the late zi hour of the day that is ending, so the hour stem is taken from that day. \"early-zi\" turns the whole day at 23:00, the practice in Hong Kong, Taiwan and much of South East Asia. \"split-zi\" is the compromise most software implements and the default here: the day still turns at 00:00, but the hour stem is taken from the next day. The three give three different answers for a late-evening birth and identical answers for every other birth.","enum":["split-zi","midnight","early-zi"],"default":"split-zi","example":"split-zi","fold":true},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the sexagenary YEAR. \"li-chun\" is Beginning of Spring, around 4 February, and is the classical rule every BaZi text uses, so it is the default on this endpoint. \"lunar-new-year\" is the folk rule people mean when they say which animal they are, and it falls between late January and late February. The two disagree for any birth in the weeks between them: 14 February 2026 is a Wood Snake year under lunar-new-year and a Fire Horse year under li-chun.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the day boundary and the hour branch are read from, so a correction that carries a birth across midnight moves the day pillar with the hour. \"clock\" is civil time exactly as a birth certificate records it, which is what most calculators use and the default here. \"local-mean\" shifts to the mean sun over the birth longitude, a correction of up to 59 minutes at the edge of a wide time zone. \"solar\" adds the equation of time on top of that, up to a further 16 minutes. Both non-civil options need \"longitude\" in the request and return 400 without it.","enum":["clock","local-mean","solar"],"default":"clock","example":"clock","fold":true},{"key":"gender","name":"gender","kind":"tiles","required":true,"description":"Subject sex, used only to pick the luck-pillar direction: a male born in a yang-stem year and a female born in a yin-stem year run forward through the sexagenary cycle, and the other two combinations run backward. It affects nothing else in the response.","enum":["male","female"],"example":"male"},{"key":"count","name":"count","kind":"number","required":false,"description":"How many ten-year luck pillars to return, 1 to 12. Eight covers eighty years from the start age, which reaches past a normal lifetime for most start ages.","min":1,"max":12,"default":8,"example":8,"fold":true},{"key":"annualFromYear","name":"annualFromYear","kind":"number","required":false,"description":"First Gregorian year of the annual pillar overlay. Omit it to leave annualPillars out of the response entirely. The annual pillar is the year the chart is currently walking through, read against the ten-year luck pillar underneath it.","min":1551,"max":2649,"example":2026,"fold":true},{"key":"annualYears","name":"annualYears","kind":"number","required":false,"description":"How many consecutive years the annual overlay covers, 1 to 20. Ignored unless annualFromYear is present.","min":1,"max":20,"default":10,"example":10,"fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Find auspicious days","fields":[{"key":"activity","name":"activity","kind":"tiles","required":true,"description":"Activity to choose a date for. One of wedding, travel, moving-house, opening-business, signing-contracts, construction, groundbreaking, burial, medical-treatment, praying. Matching folds case and punctuation, so moving-house and MOVING_HOUSE both resolve.","enum":["wedding","travel","moving-house","opening-business","signing-contracts","construction","groundbreaking","burial","medical-treatment","praying"],"example":"wedding"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First date of the range to search, inclusive.","example":"2026-03-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last date of the range to search, inclusive. The range may not exceed 93 days.","example":"2026-04-30"},{"key":"avoidAnimal","name":"avoidAnimal","kind":"tiles","required":false,"description":"Zodiac animal to protect. Days that clash with this animal are dropped from the results, which is how a date is chosen around the people attending rather than in the abstract. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"rat","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Find auspicious days","fields":[{"key":"activity","name":"activity","kind":"tiles","required":true,"description":"Activity to choose a date for. One of wedding, travel, moving-house, opening-business, signing-contracts, construction, groundbreaking, burial, medical-treatment, praying. Matching folds case and punctuation, so moving-house and MOVING_HOUSE both resolve.","enum":["wedding","travel","moving-house","opening-business","signing-contracts","construction","groundbreaking","burial","medical-treatment","praying"],"example":"wedding"},{"key":"startDate","name":"startDate","kind":"date","required":true,"description":"First date of the range to search, inclusive.","example":"2026-03-01"},{"key":"endDate","name":"endDate","kind":"date","required":true,"description":"Last date of the range to search, inclusive. The range may not exceed 93 days.","example":"2026-04-30"},{"key":"avoidAnimal","name":"avoidAnimal","kind":"tiles","required":false,"description":"Zodiac animal to protect. Days that clash with this animal are dropped from the results, which is how a date is chosen around the people attending rather than in the abstract. One of rat, ox, tiger, rabbit, dragon, snake, horse, goat, monkey, rooster, dog, pig.","enum":["rat","ox","tiger","rabbit","dragon","snake","horse","goat","monkey","rooster","dog","pig"],"example":"rat","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Convert lunar and Gregorian dates","fields":[{"key":"date","name":"date","kind":"date","required":false,"description":"Gregorian date to convert to the lunisolar calendar. Send this OR the lunar fields, never both. Converts from the first day of lunar year 1551 to the last day of lunar year 2648, a little inside the supported date span, because numbering a lunar month needs the winter solstice on each side of it and placing a leap month needs the year before; a date outside that answers 400 date_out_of_range.","example":"1990-06-15"},{"key":"lunarYear","name":"lunarYear","kind":"number","required":false,"description":"Lunisolar year to convert back to a Gregorian date. Requires lunarMonth and lunarDay.","min":1900,"max":2100,"example":1990},{"key":"lunarMonth","name":"lunarMonth","kind":"number","required":false,"description":"Lunar month, 1 to 12. Requires lunarYear and lunarDay.","min":1,"max":12,"example":5},{"key":"lunarDay","name":"lunarDay","kind":"number","required":false,"description":"Day of the lunar month, 1 to 30. Requires lunarYear and lunarMonth.","min":1,"max":30,"example":23},{"key":"isLeapMonth","name":"isLeapMonth","kind":"toggle","required":false,"description":"Set true to address the leap repetition of lunarMonth rather than the first pass. Requesting a leap month a year does not have returns 400.","default":false,"example":false,"fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Convert lunar and Gregorian dates","fields":[{"key":"date","name":"date","kind":"date","required":false,"description":"Gregorian date to convert to the lunisolar calendar. Send this OR the lunar fields, never both. Converts from the first day of lunar year 1551 to the last day of lunar year 2648, a little inside the supported date span, because numbering a lunar month needs the winter solstice on each side of it and placing a leap month needs the year before; a date outside that answers 400 date_out_of_range.","example":"1990-06-15"},{"key":"lunarYear","name":"lunarYear","kind":"number","required":false,"description":"Lunisolar year to convert back to a Gregorian date. Requires lunarMonth and lunarDay.","min":1900,"max":2100,"example":1990},{"key":"lunarMonth","name":"lunarMonth","kind":"number","required":false,"description":"Lunar month, 1 to 12. Requires lunarYear and lunarDay.","min":1,"max":12,"example":5},{"key":"lunarDay","name":"lunarDay","kind":"number","required":false,"description":"Day of the lunar month, 1 to 30. Requires lunarYear and lunarMonth.","min":1,"max":30,"example":23},{"key":"isLeapMonth","name":"isLeapMonth","kind":"toggle","required":false,"description":"Set true to address the leap repetition of lunarMonth rather than the first pass. Requesting a leap month a year does not have returns 400.","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":"Find the Chinese zodiac animal for a birth date","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Only the date is needed: the zodiac animal is a property of the year, so no time, timezone or place changes the answer.","example":"1990-06-15"},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the zodiac year. lunar-new-year is the folk rule and the default on this route, because it is the rule people mean when they say what animal they are: the sign turns on Chinese New Year, between late January and late February. li-chun is the classical rule every Four Pillars text uses, turning the year at the solar term Beginning of Spring around 4 February. The two agree for roughly eleven months of every year and disagree for the weeks between them, so a 14 February 2026 birth is a Snake under lunar-new-year and a Horse under li-chun. The BaZi routes default to li-chun instead, because a chart and a folk sign are answering different questions.","enum":["lunar-new-year","li-chun"],"default":"lunar-new-year","example":"lunar-new-year","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Find the Chinese zodiac animal for a birth date","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Only the date is needed: the zodiac animal is a property of the year, so no time, timezone or place changes the answer.","example":"1990-06-15"},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which instant starts the zodiac year. lunar-new-year is the folk rule and the default on this route, because it is the rule people mean when they say what animal they are: the sign turns on Chinese New Year, between late January and late February. li-chun is the classical rule every Four Pillars text uses, turning the year at the solar term Beginning of Spring around 4 February. The two agree for roughly eleven months of every year and disagree for the weeks between them, so a 14 February 2026 birth is a Snake under lunar-new-year and a Horse under li-chun. The BaZi routes default to li-chun instead, because a chart and a folk sign are answering different questions.","enum":["lunar-new-year","li-chun"],"default":"lunar-new-year","example":"lunar-new-year","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Daily crystal","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same crystal every time. Pass any unique identifier (userId, email hash, session token) to give each user their own crystal for the day. Without a seed every caller receives the same shared crystal 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 crystal","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same crystal every time. Pass any unique identifier (userId, email hash, session token) to give each user their own crystal for the day. Without a seed every caller receives the same shared crystal 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 dream symbol","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same symbol every time. Pass any unique identifier (userId, email hash, session token) to give each user their own symbol for the day. Without a seed every caller receives the same shared symbol 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":false,"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Daily dream symbol","fields":[{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible readings. Same seed + same date = same symbol every time. Pass any unique identifier (userId, email hash, session token) to give each user their own symbol for the day. Without a seed every caller receives the same shared symbol 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":false,"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Generate Eight Mansions map","fields":[{"key":"kua","name":"kua","kind":"number","required":false,"description":"Kua number to build the map for, if you already have one. Send this OR date and gender, not neither. A Kua of 5 is read as the Kua 2 chart, since 5 has no direction of its own.","min":1,"max":9,"example":6,"fold":true},{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format, used to derive the Kua when no kua is sent. Requires gender alongside it. A date is read at the start of its day, so a birth date landing exactly on the year boundary is placed in the outgoing year.","example":"1985-07-15"},{"key":"gender","name":"gender","kind":"tiles","required":true,"description":"Selects the Kua formula variant. Required when the Kua is being derived from a birth date.","enum":["male","female"],"example":"male"},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which boundary starts the Chinese year when the Kua is derived from a birth date. Defaults to li-chun, the classical position. Ignored when a kua is sent directly, and echoed back either way.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Optional compass sector the main door faces, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. When sent, the response names the star sitting on that sector so a caller can judge an entrance without scanning the whole map.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast","fold":true}],"hasLang":true,"requiredAnyOf":[["date","gender"],["kua"]],"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Generate Eight Mansions map","fields":[{"key":"kua","name":"kua","kind":"number","required":false,"description":"Kua number to build the map for, if you already have one. Send this OR date and gender, not neither. A Kua of 5 is read as the Kua 2 chart, since 5 has no direction of its own.","min":1,"max":9,"example":6,"fold":true},{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format, used to derive the Kua when no kua is sent. Requires gender alongside it. A date is read at the start of its day, so a birth date landing exactly on the year boundary is placed in the outgoing year.","example":"1985-07-15"},{"key":"gender","name":"gender","kind":"tiles","required":true,"description":"Selects the Kua formula variant. Required when the Kua is being derived from a birth date.","enum":["male","female"],"example":"male"},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which boundary starts the Chinese year when the Kua is derived from a birth date. Defaults to li-chun, the classical position. Ignored when a kua is sent directly, and echoed back either way.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Optional compass sector the main door faces, one of North, Northeast, East, Southeast, South, Southwest, West, Northwest. When sent, the response names the star sitting on that sector so a caller can judge an entrance without scanning the whole map.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["date","gender"],["kua"]],"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Generate flying star natal chart","fields":[{"key":"period","name":"period","kind":"number","required":false,"description":"Construction period of the building, 1 to 9. This is the twenty year cycle the building was completed in, or last renovated heavily enough to reset, and it is fixed for the life of the building. Periods change at Li Chun in early February, so a building finished in January 2024 is a Period 8 building. Defaults to the period in force now.","min":1,"max":9,"example":9,"fold":true},{"key":"facing","name":"facing","kind":"select","required":false,"description":"The mountain the front of the building faces, by id or by compass label such as S2. Send this or facingDegrees, not neither. The facing side is the open, active, public side, which is not always the side with the front door.","enum":["ren","zi","gui","chou","gen","yin","jia","mao","yi","chen","xun","si","bing","wu","ding","wei","kun","shen","geng","you","xin","xu","qian","hai","N1","N2","N3","NE1","NE2","NE3","E1","E2","E3","SE1","SE2","SE3","S1","S2","S3","SW1","SW2","SW3","W1","W2","W3","NW1","NW2","NW3"],"example":"wu","fold":true},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":true,"description":"The compass bearing the front of the building faces, 0 to 360 degrees, measured looking out from inside. Resolved to one of the 24 mountains. Send this or facing, not neither.","min":0,"max":360,"example":180}],"hasLang":true,"requiredAnyOf":[["facingDegrees"],["facing"]],"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Generate flying star natal chart","fields":[{"key":"period","name":"period","kind":"number","required":false,"description":"Construction period of the building, 1 to 9. This is the twenty year cycle the building was completed in, or last renovated heavily enough to reset, and it is fixed for the life of the building. Periods change at Li Chun in early February, so a building finished in January 2024 is a Period 8 building. Defaults to the period in force now.","min":1,"max":9,"example":9,"fold":true},{"key":"facing","name":"facing","kind":"select","required":false,"description":"The mountain the front of the building faces, by id or by compass label such as S2. Send this or facingDegrees, not neither. The facing side is the open, active, public side, which is not always the side with the front door.","enum":["ren","zi","gui","chou","gen","yin","jia","mao","yi","chen","xun","si","bing","wu","ding","wei","kun","shen","geng","you","xin","xu","qian","hai","N1","N2","N3","NE1","NE2","NE3","E1","E2","E3","SE1","SE2","SE3","S1","S2","S3","SW1","SW2","SW3","W1","W2","W3","NW1","NW2","NW3"],"example":"wu","fold":true},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":true,"description":"The compass bearing the front of the building faces, 0 to 360 degrees, measured looking out from inside. Resolved to one of the 24 mountains. Send this or facing, not neither.","min":0,"max":360,"example":180}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"requiredAnyOf":[["facingDegrees"],["facing"]],"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate Kua number","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Only the Chinese YEAR this date falls in enters the formula, so no birth time, latitude or longitude is needed. A January or early February birthday is the case that matters: it usually belongs to the PREVIOUS Chinese year and produces a different Kua. A date is read at the start of its day, and the boundary falls part-way through its own day, so a birth date landing exactly on the boundary day is placed in the outgoing year.","example":"1985-07-15"},{"key":"gender","name":"gender","kind":"tiles","required":true,"description":"Selects the Kua formula variant. The two formulas are different arithmetic on the same year, and they also differ in where a raw result of 5 is reassigned.","enum":["male","female"],"example":"male"},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which boundary starts the Chinese year. Defaults to li-chun, the astronomical start of spring in early February, which is the classical position and the one feng shui uses for periods, annual stars and afflictions alike. Send lunar-new-year to match popular zodiac tables, which start the year two to four weeks later. The two disagree for anyone born between the two dates.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true}],"hasLang":true,"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Calculate Kua number","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Only the Chinese YEAR this date falls in enters the formula, so no birth time, latitude or longitude is needed. A January or early February birthday is the case that matters: it usually belongs to the PREVIOUS Chinese year and produces a different Kua. A date is read at the start of its day, and the boundary falls part-way through its own day, so a birth date landing exactly on the boundary day is placed in the outgoing year.","example":"1985-07-15"},{"key":"gender","name":"gender","kind":"tiles","required":true,"description":"Selects the Kua formula variant. The two formulas are different arithmetic on the same year, and they also differ in where a raw result of 5 is reassigned.","enum":["male","female"],"example":"male"},{"key":"yearBoundary","name":"yearBoundary","kind":"tiles","required":false,"description":"Which boundary starts the Chinese year. Defaults to li-chun, the astronomical start of spring in early February, which is the classical position and the one feng shui uses for periods, annual stars and afflictions alike. Send lunar-new-year to match popular zodiac tables, which start the year two to four weeks later. The two disagree for anyone born between the two dates.","enum":["li-chun","lunar-new-year"],"default":"li-chun","example":"li-chun","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Forecast digest","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"Start anchor for every window in YYYY-MM-DD format. The next 24h, 7d, 30d, and 90d windows are measured forward from this date at 00:00:00 UTC. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to include before rolling up the windows. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"top","name":"top","kind":"number","required":false,"description":"Number of highest-significance events to surface per window. Defaults to 3, capped at 20.","min":0,"max":20,"example":3,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
1
+ {"title":"Forecast digest","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"Start anchor for every window in YYYY-MM-DD format. The next 24h, 7d, 30d, and 90d windows are measured forward from this date at 00:00:00 UTC. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to include before rolling up the windows. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"top","name":"top","kind":"number","required":false,"description":"Number of highest-significance events to surface per window. Defaults to 3, capped at 20.","min":0,"max":20,"example":3,"fold":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}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Significant dates","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"Last day of the window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.","example":"2026-08-30","moment":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to consider before filtering by significance. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.","min":0,"max":100,"example":70,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
1
+ {"title":"Significant dates","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"Last day of the window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.","example":"2026-08-30","moment":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to consider before filtering by significance. Defaults to all three.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.","min":0,"max":100,"example":70,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":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}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Solar return chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal Sun longitude the transiting Sun returns to each year.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Pins the exact natal Sun position that defines the solar return moment.","example":"14:30:00"},{"key":"year","name":"year","kind":"number","required":true,"description":"Year to cast the solar return for. The chart is erected for the moment in this year when the transiting Sun returns to the natal Sun longitude, on or within a day of the birthday.","min":1551,"max":2649,"example":2026},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the solar return location in decimal degrees. The solar return is location-sensitive: use the birthplace to anchor the chart to natal geography, or the current city for a relocated solar return.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the solar return location in decimal degrees. Sets the local sidereal time, so it drives the Ascendant, Midheaven, and house cusps of the return chart.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the return chart. placidus is the Western default. whole-sign, equal, and koch are also supported.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Solar return chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal Sun longitude the transiting Sun returns to each year.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Pins the exact natal Sun position that defines the solar return moment.","example":"14:30:00"},{"key":"year","name":"year","kind":"number","required":true,"description":"Year to cast the solar return for. The chart is erected for the moment in this year when the transiting Sun returns to the natal Sun longitude, on or within a day of the birthday.","min":1551,"max":2649,"example":2026},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude of the solar return location in decimal degrees. The solar return is location-sensitive: use the birthplace to anchor the chart to natal geography, or the current city for a relocated solar return.","min":-90,"max":90,"example":40.7128,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude of the solar return location in decimal degrees. Sets the local sidereal time, so it drives the Ascendant, Midheaven, and house cusps of the return chart.","min":-180,"max":180,"example":-74.006,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the return chart. placidus is the Western default. whole-sign, equal, and koch are also supported.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus","fold":true}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Cross-domain forecast timeline","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"Last day of the forecast window in YYYY-MM-DD format. Defaults to startDate plus 30 days. The window is clamped to a maximum of 90 days from startDate.","example":"2026-08-30","moment":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to include. Defaults to all three. Pass a subset to scope the timeline to one or two engines.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
1
+ {"title":"Cross-domain forecast timeline","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"Last day of the forecast window in YYYY-MM-DD format. Defaults to startDate plus 30 days. The window is clamped to a maximum of 90 days from startDate.","example":"2026-08-30","moment":true},{"key":"domains","name":"domains","kind":"array","required":false,"description":"Which forecast domains to include. Defaults to all three. Pass a subset to scope the timeline to one or two engines.","example":["western","vedic","biorhythm"],"fold":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.","min":0,"max":100,"example":0,"fold":true},{"key":"domainWeights.western","name":"western","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.vedic","name":"vedic","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":true},{"key":"domainWeights.biorhythm","name":"biorhythm","group":"domainWeights","kind":"number","required":false,"description":"Multiplier for this domain significance. 1 leaves it unchanged, above 1 promotes the domain, below 1 demotes it.","min":0,"max":100,"example":1.5,"fold":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}},{},{"key":"domainWeights","label":"Domain Weights","fold":true}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Western astrology forecast","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"Last day of the transit window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.","example":"2026-08-30","moment":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.","min":0,"max":100,"example":0,"fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
1
+ {"title":"Western astrology forecast","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Anchors the natal chart and the Vimshottari dasha sequence.","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 for the natal positions the transit aspects are measured against.","example":"13:30: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 timeline. 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 timeline. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"startDate","name":"startDate","kind":"date","required":false,"description":"First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.","example":"2026-06-01","moment":true},{"key":"endDate","name":"endDate","kind":"date","required":false,"description":"Last day of the transit window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.","example":"2026-08-30","moment":true},{"key":"minSignificance","name":"minSignificance","kind":"number","required":false,"description":"Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.","min":0,"max":100,"example":0,"fold":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":"Generate full Human Design bodygraph","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":"Generate full Human Design bodygraph","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 the nine Human Design centers","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 nine Human Design centers","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 the defined Human Design channels","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 defined Human Design channels","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 connection chart","fields":[{"key":"personA.date","name":"date","group":"personA","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":"personA.time","name":"time","group":"personA","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":"personA.timezone","name":"timezone","group":"personA","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":"personA.latitude","name":"latitude","group":"personA","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":"personA.longitude","name":"longitude","group":"personA","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":"personA.nodeType","name":"nodeType","group":"personA","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":"personB.date","name":"date","group":"personB","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":"personB.time","name":"time","group":"personB","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":"personB.timezone","name":"timezone","group":"personB","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":"personB.latitude","name":"latitude","group":"personB","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":"personB.longitude","name":"longitude","group":"personB","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":"personB.nodeType","name":"nodeType","group":"personB","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"}],"hasLang":true,"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate Human Design connection chart","fields":[{"key":"personA.date","name":"date","group":"personA","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":"personA.time","name":"time","group":"personA","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":"personA.timezone","name":"timezone","group":"personA","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":"personA.latitude","name":"latitude","group":"personA","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":"personA.longitude","name":"longitude","group":"personA","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":"personA.nodeType","name":"nodeType","group":"personA","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":"personB.date","name":"date","group":"personB","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":"personB.time","name":"time","group":"personB","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":"personB.timezone","name":"timezone","group":"personB","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":"personB.latitude","name":"latitude","group":"personB","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":"personB.longitude","name":"longitude","group":"personB","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":"personB.nodeType","name":"nodeType","group":"personB","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"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate the 26 Human Design gate activations","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 26 Human Design gate activations","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 Penta","fields":[{"key":"members.0.date","name":"date","group":"members.0","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":"members.0.time","name":"time","group":"members.0","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":"members.0.timezone","name":"timezone","group":"members.0","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":"members.0.latitude","name":"latitude","group":"members.0","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":"members.0.longitude","name":"longitude","group":"members.0","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":"members.0.nodeType","name":"nodeType","group":"members.0","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":"members.1.date","name":"date","group":"members.1","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":"members.1.time","name":"time","group":"members.1","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":"members.1.timezone","name":"timezone","group":"members.1","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":"members.1.latitude","name":"latitude","group":"members.1","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":"members.1.longitude","name":"longitude","group":"members.1","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":"members.1.nodeType","name":"nodeType","group":"members.1","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":"members.2.date","name":"date","group":"members.2","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":"members.2.time","name":"time","group":"members.2","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":"members.2.timezone","name":"timezone","group":"members.2","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":"members.2.latitude","name":"latitude","group":"members.2","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":"members.2.longitude","name":"longitude","group":"members.2","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":"members.2.nodeType","name":"nodeType","group":"members.2","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"}],"hasLang":true,"repeats":[{"key":"members","min":3,"max":5}],"groups":[{"key":"members.0","label":"Group members 1","location":{"fields":["members.0.latitude","members.0.longitude","members.0.timezone"],"required":true}},{"key":"members.1","label":"Group members 2","location":{"fields":["members.1.latitude","members.1.longitude","members.1.timezone"],"required":true}},{"key":"members.2","label":"Group members 3","location":{"fields":["members.2.latitude","members.2.longitude","members.2.timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate Human Design Penta","fields":[{"key":"members.0.date","name":"date","group":"members.0","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":"members.0.time","name":"time","group":"members.0","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":"members.0.timezone","name":"timezone","group":"members.0","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":"members.0.latitude","name":"latitude","group":"members.0","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":"members.0.longitude","name":"longitude","group":"members.0","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":"members.0.nodeType","name":"nodeType","group":"members.0","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":"members.1.date","name":"date","group":"members.1","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":"members.1.time","name":"time","group":"members.1","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":"members.1.timezone","name":"timezone","group":"members.1","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":"members.1.latitude","name":"latitude","group":"members.1","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":"members.1.longitude","name":"longitude","group":"members.1","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":"members.1.nodeType","name":"nodeType","group":"members.1","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":"members.2.date","name":"date","group":"members.2","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":"members.2.time","name":"time","group":"members.2","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":"members.2.timezone","name":"timezone","group":"members.2","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":"members.2.latitude","name":"latitude","group":"members.2","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":"members.2.longitude","name":"longitude","group":"members.2","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":"members.2.nodeType","name":"nodeType","group":"members.2","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"}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"repeats":[{"key":"members","min":3,"max":5}],"groups":[{"key":"members.0","label":"Group members 1","location":{"fields":["members.0.latitude","members.0.longitude","members.0.timezone"],"required":true}},{"key":"members.1","label":"Group members 2","location":{"fields":["members.1.latitude","members.1.longitude","members.1.timezone"],"required":true}},{"key":"members.2","label":"Group members 3","location":{"fields":["members.2.latitude","members.2.longitude","members.2.timezone"],"required":true}}],"opensOnLoad":false}