@roxyapi/ui 0.42.0 → 0.43.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 (143) hide show
  1. package/components-catalog.json +151 -151
  2. package/dist/cdn/components/endpoint-form.js +3 -3
  3. package/dist/cdn/components/endpoint-form.js.map +3 -3
  4. package/dist/cdn/components/guna-milan.js +1 -1
  5. package/dist/cdn/components/guna-milan.js.map +2 -2
  6. package/dist/cdn/components/kp-finance-card.js +4 -4
  7. package/dist/cdn/components/kp-finance-card.js.map +3 -3
  8. package/dist/cdn/locales/de.js +1 -1
  9. package/dist/cdn/locales/de.js.map +2 -2
  10. package/dist/cdn/locales/es.js +1 -1
  11. package/dist/cdn/locales/es.js.map +2 -2
  12. package/dist/cdn/locales/fr.js +1 -1
  13. package/dist/cdn/locales/fr.js.map +2 -2
  14. package/dist/cdn/locales/hi.js +1 -1
  15. package/dist/cdn/locales/hi.js.map +2 -2
  16. package/dist/cdn/locales/pt.js +1 -1
  17. package/dist/cdn/locales/pt.js.map +2 -2
  18. package/dist/cdn/locales/ru.js +1 -1
  19. package/dist/cdn/locales/ru.js.map +2 -2
  20. package/dist/cdn/locales/tr.js +1 -1
  21. package/dist/cdn/locales/tr.js.map +2 -2
  22. package/dist/cdn/roxy-ui.js +22 -22
  23. package/dist/cdn/roxy-ui.js.map +3 -3
  24. package/dist/components/endpoint-form.d.ts +1 -1
  25. package/dist/components/endpoint-form.d.ts.map +1 -1
  26. package/dist/components/endpoint-form.js +1 -1
  27. package/dist/components/endpoint-form.js.map +3 -3
  28. package/dist/components/guna-milan.js +1 -1
  29. package/dist/components/guna-milan.js.map +2 -2
  30. package/dist/components/kp-finance-card.d.ts +6 -1
  31. package/dist/components/kp-finance-card.d.ts.map +1 -1
  32. package/dist/components/kp-finance-card.js +1 -1
  33. package/dist/components/kp-finance-card.js.map +3 -3
  34. package/dist/i18n/chrome-strings.d.ts +1 -1
  35. package/dist/i18n/chrome-strings.d.ts.map +1 -1
  36. package/dist/index.cjs +22 -22
  37. package/dist/index.cjs.map +3 -3
  38. package/dist/index.js +24 -24
  39. package/dist/index.js.map +3 -3
  40. package/dist/locales/de.d.ts.map +1 -1
  41. package/dist/locales/de.js +1 -1
  42. package/dist/locales/de.js.map +2 -2
  43. package/dist/locales/es.d.ts.map +1 -1
  44. package/dist/locales/es.js +1 -1
  45. package/dist/locales/es.js.map +2 -2
  46. package/dist/locales/fr.d.ts.map +1 -1
  47. package/dist/locales/fr.js +1 -1
  48. package/dist/locales/fr.js.map +2 -2
  49. package/dist/locales/hi.d.ts.map +1 -1
  50. package/dist/locales/hi.js +1 -1
  51. package/dist/locales/hi.js.map +2 -2
  52. package/dist/locales/pt.d.ts.map +1 -1
  53. package/dist/locales/pt.js +1 -1
  54. package/dist/locales/pt.js.map +2 -2
  55. package/dist/locales/ru.d.ts.map +1 -1
  56. package/dist/locales/ru.js +1 -1
  57. package/dist/locales/ru.js.map +2 -2
  58. package/dist/locales/tr.d.ts.map +1 -1
  59. package/dist/locales/tr.js +1 -1
  60. package/dist/locales/tr.js.map +2 -2
  61. package/dist/schemas/get--vedic-astrology-kp-ayanamsa.json +1 -1
  62. package/dist/schemas/post--astrology-arabic-lots.json +1 -1
  63. package/dist/schemas/post--astrology-aspect-patterns.json +1 -1
  64. package/dist/schemas/post--astrology-asteroids.json +1 -1
  65. package/dist/schemas/post--astrology-astrocartography.json +1 -1
  66. package/dist/schemas/post--astrology-compatibility-score.json +1 -1
  67. package/dist/schemas/post--astrology-composite-chart.json +1 -1
  68. package/dist/schemas/post--astrology-fixed-stars.json +1 -1
  69. package/dist/schemas/post--astrology-lilith.json +1 -1
  70. package/dist/schemas/post--astrology-local-space.json +1 -1
  71. package/dist/schemas/post--astrology-natal-chart.json +1 -1
  72. package/dist/schemas/post--astrology-profections.json +1 -1
  73. package/dist/schemas/post--astrology-progressions.json +1 -1
  74. package/dist/schemas/post--astrology-relocation-chart.json +1 -1
  75. package/dist/schemas/post--astrology-solar-arc.json +1 -1
  76. package/dist/schemas/post--astrology-synastry.json +1 -1
  77. package/dist/schemas/post--astrology-transit-aspects.json +1 -1
  78. package/dist/schemas/post--chinese-astrology-bazi-annual-forecast.json +1 -1
  79. package/dist/schemas/post--chinese-astrology-bazi-chart.json +1 -1
  80. package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
  81. package/dist/schemas/post--chinese-astrology-bazi-day-master.json +1 -1
  82. package/dist/schemas/post--chinese-astrology-bazi-luck-pillars.json +1 -1
  83. package/dist/schemas/post--forecast-digest.json +1 -1
  84. package/dist/schemas/post--forecast-significant-dates.json +1 -1
  85. package/dist/schemas/post--forecast-solar-return.json +1 -1
  86. package/dist/schemas/post--forecast-timeline.json +1 -1
  87. package/dist/schemas/post--forecast-transits.json +1 -1
  88. package/dist/schemas/post--human-design-bodygraph.json +1 -1
  89. package/dist/schemas/post--human-design-centers.json +1 -1
  90. package/dist/schemas/post--human-design-channels.json +1 -1
  91. package/dist/schemas/post--human-design-connection.json +1 -1
  92. package/dist/schemas/post--human-design-gates.json +1 -1
  93. package/dist/schemas/post--human-design-profile.json +1 -1
  94. package/dist/schemas/post--human-design-transit.json +1 -1
  95. package/dist/schemas/post--human-design-type.json +1 -1
  96. package/dist/schemas/post--human-design-variables.json +1 -1
  97. package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
  98. package/dist/schemas/post--numerology-compatibility.json +1 -1
  99. package/dist/schemas/post--vastu-timing-griha-pravesh.json +1 -1
  100. package/dist/schemas/post--vedic-astrology-arudha.json +1 -1
  101. package/dist/schemas/post--vedic-astrology-ashtakavarga.json +1 -1
  102. package/dist/schemas/post--vedic-astrology-bhav-chalit.json +1 -1
  103. package/dist/schemas/post--vedic-astrology-bhava-bala.json +1 -1
  104. package/dist/schemas/post--vedic-astrology-birth-chart.json +1 -1
  105. package/dist/schemas/post--vedic-astrology-chara-karakas.json +1 -1
  106. package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
  107. package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
  108. package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
  109. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
  110. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
  111. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
  112. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
  113. package/dist/schemas/post--vedic-astrology-divisional-chart.json +1 -1
  114. package/dist/schemas/post--vedic-astrology-dosha-kalsarpa.json +1 -1
  115. package/dist/schemas/post--vedic-astrology-dosha-manglik.json +1 -1
  116. package/dist/schemas/post--vedic-astrology-dosha-sadhesati.json +1 -1
  117. package/dist/schemas/post--vedic-astrology-navamsa.json +1 -1
  118. package/dist/schemas/post--vedic-astrology-planetary-positions.json +1 -1
  119. package/dist/schemas/post--vedic-astrology-shadbala.json +1 -1
  120. package/dist/schemas/post--vedic-astrology-upagraha.json +1 -1
  121. package/dist/schemas/post--vedic-astrology-yoga-detect.json +1 -1
  122. package/dist/styles/themes/practitioner.css +5 -5
  123. package/dist/types/types.gen.d.ts +88 -88
  124. package/dist/types/types.gen.d.ts.map +1 -1
  125. package/dist/version.d.ts +1 -1
  126. package/package.json +1 -1
  127. package/src/components/endpoint-form.ts +21 -9
  128. package/src/components/guna-milan.ts +1 -1
  129. package/src/components/kp-finance-card.ts +16 -9
  130. package/src/i18n/chrome-strings.ts +4 -0
  131. package/src/locales/de.ts +1 -0
  132. package/src/locales/es.ts +3 -1
  133. package/src/locales/field-labels/de.ts +1 -1
  134. package/src/locales/field-labels/fr.ts +1 -1
  135. package/src/locales/field-labels/pt.ts +1 -1
  136. package/src/locales/fr.ts +3 -1
  137. package/src/locales/hi.ts +3 -1
  138. package/src/locales/pt.ts +3 -1
  139. package/src/locales/ru.ts +3 -1
  140. package/src/locales/tr.ts +1 -0
  141. package/src/styles/themes/practitioner.css +5 -5
  142. package/src/types/types.gen.ts +88 -88
  143. package/src/version.ts +1 -1
@@ -1 +1 @@
1
- {"title":"Get KP-Newcomb ayanamsa","fields":[{"key":"date","name":"date","inQuery":true,"kind":"date","required":false,"description":"Date for ayanamsa calculation in YYYY-MM-DD format. Defaults to today if not provided. Ayanamsa changes by ~0.01 degrees per month due to the precession of Earth.","example":"2025-12-26"},{"key":"time","name":"time","inQuery":true,"kind":"time","required":false,"description":"Time of day in 24-hour HH:MM:SS format, interpreted in the timezone below. Omit for midnight UTC. The ayanamsa moves about 0.14 arcseconds across a day, so supplying the time matters only when reconciling a chart against reference software to the arcsecond.","example":"09:00:00"},{"key":"timezone","name":"timezone","inQuery":true,"kind":"text","required":false,"description":"IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\"), decimal hours (e.g. 5.5 for IST, -5 for EST), or a fixed UTC offset (e.g. \"+05:30\"). IANA resolved to the DST-correct offset for the given date. Applies to the time field above. Defaults to 0 (UTC).","example":"Asia/Kolkata"}],"hasLang":false}
1
+ {"title":"Get KP-Newcomb ayanamsa","fields":[{"key":"date","name":"date","inQuery":true,"kind":"date","required":false,"description":"Date for ayanamsa calculation in YYYY-MM-DD format. Defaults to today if not provided. Ayanamsa changes by ~0.01 degrees per month due to the precession of Earth.","example":"2025-12-26"},{"key":"time","name":"time","inQuery":true,"kind":"time","required":false,"description":"Time of day in 24-hour HH:MM:SS format, interpreted in the timezone below. Omit for midnight UTC. The ayanamsa moves about 0.14 arcseconds across a day, so supplying the time matters only when reconciling a chart against reference software to the arcsecond.","example":"09:00:00"},{"key":"timezone","name":"timezone","inQuery":true,"kind":"text","required":false,"description":"IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\"), decimal hours (e.g. 5.5 for IST, -5 for EST), or a fixed UTC offset (e.g. \"+05:30\"). IANA resolved to the offset in force at the given date and the time field above. Defaults to 0 (UTC).","example":"Asia/Kolkata"}],"hasLang":false}
@@ -1 +1 @@
1
- {"title":"Arabic lots calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to place the Sun, which determines the chart sect (day when the Sun is above the horizon, night when below) and therefore which lot formula applies. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Arabic lots calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to place the Sun, which determines the chart sect (day when the Sun is above the horizon, night when below) and therefore which lot formula applies. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Detect aspect patterns","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"strictOrbs","name":"strictOrbs","inQuery":true,"kind":"text","required":false,"description":"Use tighter orbs, so only closely formed patterns are reported. Truthy values (true, 1, yes, on; case-insensitive) narrow trine to 5 degrees, square to 5, sextile to 4, quincunx to 2. Defaults to false, the standard pattern-detection orbs.","example":"false"},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Comma-separated list of optional bodies to include beyond the classical 10 planets. Valid tokens (case-insensitive): chiron, northNode (also accepts north_node, north-node, northnode). Empty by default.","example":""}],"hasLang":true}
1
+ {"title":"Detect aspect patterns","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"strictOrbs","name":"strictOrbs","inQuery":true,"kind":"text","required":false,"description":"Use tighter orbs, so only closely formed patterns are reported. Truthy values (true, 1, yes, on; case-insensitive) narrow trine to 5 degrees, square to 5, sextile to 4, quincunx to 2. Defaults to false, the standard pattern-detection orbs.","example":"false"},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Comma-separated list of optional bodies to include beyond the classical 10 planets. Valid tokens (case-insensitive): chiron, northNode (also accepts north_node, north-node, northnode). Empty by default.","example":""}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Asteroid goddesses calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to assign each asteroid to a natal house. Placidus (default), Whole Sign, Equal, or Koch. Above the polar circle, quadrant systems fall back to Whole Sign and the echoed houseSystem reports the system actually used.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Asteroid goddesses calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to assign each asteroid to a natal house. Placidus (default), Whole Sign, Equal, or Koch. Above the polar circle, quadrant systems fall back to Whole Sign and the echoed houseSystem reports the system actually used.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Astrocartography map","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Optional comma separated list of extra bodies to plot beyond the ten classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Unknown values are ignored. Defaults to none.","example":"chiron"}],"hasLang":true}
1
+ {"title":"Astrocartography map","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Optional comma separated list of extra bodies to plot beyond the ten classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Unknown values are ignored. Defaults to none.","example":"chiron"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true}
1
+ {"title":"Compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Composite Chart","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the composite chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Composite Chart","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for the composite chart. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Fixed stars and star conjunctions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"orb","name":"orb","inQuery":true,"kind":"number","required":false,"description":"Conjunction orb in degrees, the maximum separation for a star to count as conjunct a chart point. Defaults to 1, maximum 3. Widen it to surface looser contacts or tighten it for only the closest hits.","min":0,"max":3,"default":1,"example":1}],"hasLang":true}
1
+ {"title":"Fixed stars and star conjunctions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"orb","name":"orb","inQuery":true,"kind":"number","required":false,"description":"Conjunction orb in degrees, the maximum separation for a star to count as conjunct a chart point. Defaults to 1, maximum 3. Widen it to surface looser contacts or tighten it for only the closest hits.","min":0,"max":3,"default":1,"example":1}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Black Moon Lilith calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to place each Lilith variant in a house. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Black Moon Lilith calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to place each Lilith variant in a house. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Local space astrology map","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Combined with time and timezone it fixes the birth instant whose planetary positions are projected onto the local horizon.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is essential: the local horizon rotates a full circle each day, so the azimuth (compass direction) of every body depends on the exact birth time.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). This is the origin point of every local space line and the observer latitude used to turn each body into an azimuth and altitude.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Sets the local horizon orientation and the starting point from which the directional lines radiate.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the DST-correct offset for the birth date.","min":-14,"max":14,"example":-5},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Optional comma-separated extra bodies to add beyond the 10 classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Omit to return the 10 classical planets only.","example":"chiron,lilith"}],"hasLang":true}
1
+ {"title":"Local space astrology map","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Combined with time and timezone it fixes the birth instant whose planetary positions are projected onto the local horizon.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is essential: the local horizon rotates a full circle each day, so the azimuth (compass direction) of every body depends on the exact birth time.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). This is the origin point of every local space line and the observer latitude used to turn each body into an azimuth and altitude.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Sets the local horizon orientation and the starting point from which the directional lines radiate.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Decimal hours from UTC (e.g. -5 for EST, 5.5 for IST, 9 for JST) OR IANA name (e.g. \"America/New_York\"). IANA resolved to the offset in force at the birth date and time.","min":-14,"max":14,"example":-5},{"key":"include","name":"include","inQuery":true,"kind":"text","required":false,"description":"Optional comma-separated extra bodies to add beyond the 10 classical planets. Allowed values: north-node, chiron, lilith. north-node is the mean lunar node. Omit to return the 10 classical planets only.","example":"chiron,lilith"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Generate natal chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the chart into 12 houses. Placidus (default) is most popular in Western astrology and time-sensitive. Whole Sign assigns one sign per house (simpler, ancient). Equal houses divide chart into 30° segments from Ascendant. Koch emphasizes houses in high latitudes.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Generate natal chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the chart into 12 houses. Placidus (default) is most popular in Western astrology and time-sensitive. Whole Sign assigns one sign per house (simpler, ancient). Equal houses divide chart into 30° segments from Ascendant. Koch emphasizes houses in high latitudes.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Annual profections calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.","example":"2025-08-04"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Annual profections calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.","example":"2025-08-04"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Secondary progressions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.","example":"2025-07-15"}],"hasLang":true}
1
+ {"title":"Secondary progressions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birth moment.","example":"2025-07-15"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Generate relocation chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.","example":"1961-08-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.","example":"19:24:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Birth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\"). Resolved to the DST-correct offset for the birth date. This is the birthplace timezone, not the new location timezone.","min":-14,"max":14,"example":-10},{"key":"birthLatitude","name":"latitude","group":"birth","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","min":-90,"max":90,"example":21.3069},{"key":"birthLongitude","name":"longitude","group":"birth","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","min":-180,"max":180,"example":-157.8583},{"key":"relocationLatitude","name":"latitude","group":"relocation","kind":"number","required":true,"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","min":-90,"max":90,"example":40.7167},{"key":"relocationLongitude","name":"longitude","group":"relocation","kind":"number","required":true,"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","min":-180,"max":180,"example":-74.006},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Generate relocation chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.","example":"1961-08-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.","example":"19:24:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Birth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. \"America/New_York\"). Resolved to the offset in force at the birth date and time. This is the birthplace timezone, not the new location timezone.","min":-14,"max":14,"example":-10},{"key":"birthLatitude","name":"latitude","group":"birth","kind":"number","required":true,"description":"Birthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.","min":-90,"max":90,"example":21.3069},{"key":"birthLongitude","name":"longitude","group":"birth","kind":"number","required":true,"description":"Birthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.","min":-180,"max":180,"example":-157.8583},{"key":"relocationLatitude","name":"latitude","group":"relocation","kind":"number","required":true,"description":"New location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.","min":-90,"max":90,"example":40.7167},{"key":"relocationLongitude","name":"longitude","group":"relocation","kind":"number","required":true,"description":"New location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.","min":-180,"max":180,"example":-74.006},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Solar arc directions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to direct the chart to, in YYYY-MM-DD format. Every natal point is advanced by the solar arc accumulated from birth to this date, about one degree for each year of life.","example":"2025-07-15"}],"hasLang":true}
1
+ {"title":"Solar arc directions calculator","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"targetDate","name":"targetDate","kind":"date","required":true,"description":"Date to direct the chart to, in YYYY-MM-DD format. Every natal point is advanced by the solar arc accumulated from birth to this date, about one degree for each year of life.","example":"2025-07-15"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Calculate synastry","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person1.name","name":"name","group":"person1","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.name","name":"name","group":"person2","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Calculate synastry","fields":[{"key":"person1.date","name":"date","group":"person1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person1.time","name":"time","group":"person1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person1.latitude","name":"latitude","group":"person1","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person1.longitude","name":"longitude","group":"person1","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person1.timezone","name":"timezone","group":"person1","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person1.nodeType","name":"nodeType","group":"person1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person1.name","name":"name","group":"person1","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"person2.date","name":"date","group":"person2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"person2.time","name":"time","group":"person2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"person2.latitude","name":"latitude","group":"person2","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"person2.longitude","name":"longitude","group":"person2","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"person2.timezone","name":"timezone","group":"person2","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"person2.nodeType","name":"nodeType","group":"person2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"person2.name","name":"name","group":"person2","kind":"text","required":false,"description":"Optional display name for this person. Included in the response for easy identification.","example":"Alex"},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Transit Aspects","fields":[{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"natalChart.nodeType","name":"nodeType","group":"natalChart","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"transitDate","name":"transitDate","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.","example":"2026-02-03"},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format. Defaults to 12:00:00 (noon) if omitted.","example":"12:00:00"},{"key":"planets","name":"planets","kind":"array","required":false,"description":"Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).","example":["Jupiter","Saturn","Pluto"]},{"key":"aspectTypes","name":"aspectTypes","kind":"array","required":false,"description":"Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.","example":["CONJUNCTION","OPPOSITION","TRINE","SQUARE"]},{"key":"minStrength","name":"minStrength","kind":"number","required":false,"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","min":0,"max":100,"example":50},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
1
+ {"title":"Transit Aspects","fields":[{"key":"natalChart.date","name":"date","group":"natalChart","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.","example":"1990-07-15"},{"key":"natalChart.time","name":"time","group":"natalChart","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.","example":"14:30:00"},{"key":"natalChart.latitude","name":"latitude","group":"natalChart","kind":"number","required":true,"description":"Birth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.","min":-90,"max":90,"example":40.7128},{"key":"natalChart.longitude","name":"longitude","group":"natalChart","kind":"number","required":true,"description":"Birth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.","min":-180,"max":180,"example":-74.006},{"key":"natalChart.timezone","name":"timezone","group":"natalChart","kind":"number","required":true,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the offset in force at the given date and time, so you can pass `cities[0].timezone` from /location/search directly.","min":-14,"max":14,"example":-5},{"key":"natalChart.nodeType","name":"nodeType","group":"natalChart","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node. True is the osculating node and the default, because it is what most Western chart software reports; mean is the smoothed node preferred by several evolutionary schools, so pass \"mean\" to match one. Nothing else in the chart changes, and the two agree on the sign except when the node sits within about 1.8 degrees of a cusp. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"transitDate","name":"transitDate","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.","example":"2026-02-03"},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format. Defaults to 12:00:00 (noon) if omitted.","example":"12:00:00"},{"key":"planets","name":"planets","kind":"array","required":false,"description":"Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).","example":["Jupiter","Saturn","Pluto"]},{"key":"aspectTypes","name":"aspectTypes","kind":"array","required":false,"description":"Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.","example":["CONJUNCTION","OPPOSITION","TRINE","SQUARE"]},{"key":"minStrength","name":"minStrength","kind":"number","required":false,"description":"Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.","min":0,"max":100,"example":50},{"key":"houseSystem","name":"houseSystem","kind":"tiles","required":false,"description":"House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (default) is time sensitive and the most widely used in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30 degree segments from the Ascendant. Koch emphasizes higher latitudes. Quadrant systems fall back to Whole Sign above the polar circle.","enum":["placidus","whole-sign","equal","koch"],"default":"placidus","example":"placidus"}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Calculate BaZi annual forecast","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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":"year","name":"year","kind":"number","required":true,"description":"Gregorian year to read against the natal chart. The annual pillar for that year is resolved under the same year boundary the request selected, so a li-chun reading and a lunar-new-year reading of the same calendar year can differ.","min":1900,"max":2100,"example":2026}],"hasLang":true}
1
+ {"title":"Calculate BaZi annual forecast","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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":"year","name":"year","kind":"number","required":true,"description":"Gregorian year to read against the natal chart. The annual pillar for that year is resolved under the same year boundary the request selected, so a li-chun reading and a lunar-new-year reading of the same calendar year can differ.","min":1900,"max":2100,"example":2026}],"hasLang":true}
@@ -1 +1 @@
1
- {"title":"Generate BaZi chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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}
1
+ {"title":"Generate BaZi chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Sets the year, month and day pillars. The year pillar turns at Beginning of Spring rather than on 1 January, and the month pillar turns at each of the twelve minor solar terms rather than at a calendar month boundary.","example":"1990-06-15"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Sets the hour pillar, which is one of the four and carries the whole picture of later life and offspring. Each Earthly Branch covers two hours, so a birth within a few minutes of an odd hour can land in either. All four pillars are read in the local clock of the birth, and the day boundary is applied in that same clock; only the lunisolar calendar date itself is a world constant, fixed at UTC plus 8 so one instant has one Chinese date everywhere.","example":"14:30:00"},{"key":"timezone","name":"timezone","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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}
@@ -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 DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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 HOUR branch is read from. \"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 DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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 HOUR branch is read from. \"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}
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"},{"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},{"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},{"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 HOUR branch is read from. \"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"},{"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},{"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},{"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 HOUR branch is read from. \"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}
@@ -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 DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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}
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"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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}
@@ -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 DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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":"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},{"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":1900,"max":2100,"example":2026},{"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}],"hasLang":true}
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"},{"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},{"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},{"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"},{"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"},{"key":"hourClock","name":"hourClock","kind":"tiles","required":false,"description":"Which clock the HOUR branch is read from. \"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":"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},{"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":1900,"max":2100,"example":2026},{"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}],"hasLang":true}