@roxyapi/ui 1.1.1 → 1.1.3

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 (195) hide show
  1. package/AGENTS.md +5 -5
  2. package/README.md +3 -3
  3. package/THEMING.md +3 -3
  4. package/components-catalog.json +258 -158
  5. package/dist/cdn/components/almanac-day.js +3 -205
  6. package/dist/cdn/components/angel-number-card.js +3 -205
  7. package/dist/cdn/components/angel-number-lookup.js +3 -205
  8. package/dist/cdn/components/arudha-padas.js +3 -205
  9. package/dist/cdn/components/ashtakavarga-grid.js +3 -205
  10. package/dist/cdn/components/aspects-table.js +3 -205
  11. package/dist/cdn/components/astrocartography-map.js +3 -205
  12. package/dist/cdn/components/bazi-chart.js +3 -205
  13. package/dist/cdn/components/bhav-chalit-table.js +2 -204
  14. package/dist/cdn/components/bhava-bala-table.js +3 -205
  15. package/dist/cdn/components/biorhythm-chart.js +3 -205
  16. package/dist/cdn/components/bodygraph.js +7 -209
  17. package/dist/cdn/components/chara-karakas.js +3 -205
  18. package/dist/cdn/components/choghadiya-grid.js +3 -205
  19. package/dist/cdn/components/compatibility-card.js +2 -204
  20. package/dist/cdn/components/compound-number.js +3 -205
  21. package/dist/cdn/components/crystal-card.js +3 -205
  22. package/dist/cdn/components/crystal-grid.js +3 -205
  23. package/dist/cdn/components/dasha-timeline.js +3 -205
  24. package/dist/cdn/components/data.js +3 -205
  25. package/dist/cdn/components/divisional-chart.js +13 -215
  26. package/dist/cdn/components/dosha-card.js +3 -205
  27. package/dist/cdn/components/dosha-constitution.js +3 -205
  28. package/dist/cdn/components/dream-card.js +3 -205
  29. package/dist/cdn/components/dream-search.js +3 -205
  30. package/dist/cdn/components/endpoint-form.js +3 -205
  31. package/dist/cdn/components/ephemeris-table.js +2 -204
  32. package/dist/cdn/components/fixed-stars.js +2 -204
  33. package/dist/cdn/components/flying-star-chart.js +2 -204
  34. package/dist/cdn/components/forecast-digest.js +3 -205
  35. package/dist/cdn/components/forecast-timeline.js +3 -205
  36. package/dist/cdn/components/gematria.js +3 -205
  37. package/dist/cdn/components/gochara-table.js +3 -205
  38. package/dist/cdn/components/guna-milan.js +3 -205
  39. package/dist/cdn/components/hd-connection.js +5 -207
  40. package/dist/cdn/components/hd-penta.js +5 -207
  41. package/dist/cdn/components/hd-type-card.js +3 -205
  42. package/dist/cdn/components/hd-variables.js +3 -205
  43. package/dist/cdn/components/heliacal-table.js +3 -205
  44. package/dist/cdn/components/hexagram.js +3 -205
  45. package/dist/cdn/components/hora-table.js +3 -205
  46. package/dist/cdn/components/horoscope-card.js +3 -205
  47. package/dist/cdn/components/kp-chart.js +3 -205
  48. package/dist/cdn/components/kp-finance-card.js +3 -205
  49. package/dist/cdn/components/kp-planets-table.js +3 -205
  50. package/dist/cdn/components/kp-ruling-planets.js +3 -205
  51. package/dist/cdn/components/kua-card.js +3 -205
  52. package/dist/cdn/components/local-space-compass.js +8 -210
  53. package/dist/cdn/components/location-search.js +3 -205
  54. package/dist/cdn/components/luck-pillars.js +3 -205
  55. package/dist/cdn/components/mayan-day-sign.js +3 -205
  56. package/dist/cdn/components/moon-phase.js +3 -205
  57. package/dist/cdn/components/nakshatra-card.js +3 -205
  58. package/dist/cdn/components/natal-chart.js +6 -208
  59. package/dist/cdn/components/numerology-card.js +3 -205
  60. package/dist/cdn/components/panchang-table.js +3 -205
  61. package/dist/cdn/components/positions-table.js +3 -205
  62. package/dist/cdn/components/profection-card.js +3 -205
  63. package/dist/cdn/components/reference-card.js +3 -205
  64. package/dist/cdn/components/relocation-wheel.js +6 -208
  65. package/dist/cdn/components/shadbala-table.js +3 -205
  66. package/dist/cdn/components/synastry-chart.js +7 -209
  67. package/dist/cdn/components/tarot-card.js +3 -205
  68. package/dist/cdn/components/tarot-catalog.js +3 -205
  69. package/dist/cdn/components/tarot-spread.js +3 -205
  70. package/dist/cdn/components/transit-wheel.js +8 -210
  71. package/dist/cdn/components/transits-table.js +3 -205
  72. package/dist/cdn/components/upagraha-table.js +2 -204
  73. package/dist/cdn/components/vastu-mandala.js +4 -206
  74. package/dist/cdn/components/vedic-aspects.js +2 -204
  75. package/dist/cdn/components/vedic-daily.js +3 -205
  76. package/dist/cdn/components/vedic-kundli.js +10 -212
  77. package/dist/cdn/components/vedic-planets-table.js +3 -205
  78. package/dist/cdn/components/western-planets-table.js +2 -204
  79. package/dist/cdn/components/yoga-list.js +3 -205
  80. package/dist/cdn/components/zodiac-card.js +2 -204
  81. package/dist/cdn/locales/de.js +1 -1
  82. package/dist/cdn/roxy-ui.js +49 -251
  83. package/dist/components/almanac-day.js +1 -203
  84. package/dist/components/angel-number-card.js +1 -203
  85. package/dist/components/angel-number-lookup.js +1 -203
  86. package/dist/components/arudha-padas.js +1 -203
  87. package/dist/components/ashtakavarga-grid.js +1 -203
  88. package/dist/components/aspects-table.js +1 -203
  89. package/dist/components/astrocartography-map.js +6 -208
  90. package/dist/components/bazi-chart.js +1 -203
  91. package/dist/components/bhav-chalit-table.js +1 -203
  92. package/dist/components/bhava-bala-table.js +1 -203
  93. package/dist/components/biorhythm-chart.js +1 -203
  94. package/dist/components/bodygraph.js +3 -205
  95. package/dist/components/chara-karakas.js +1 -203
  96. package/dist/components/choghadiya-grid.js +1 -203
  97. package/dist/components/compatibility-card.js +1 -203
  98. package/dist/components/compound-number.js +1 -203
  99. package/dist/components/crystal-card.js +1 -203
  100. package/dist/components/crystal-grid.js +1 -203
  101. package/dist/components/dasha-timeline.js +1 -203
  102. package/dist/components/data.js +1 -203
  103. package/dist/components/divisional-chart.js +45 -247
  104. package/dist/components/dosha-card.js +1 -203
  105. package/dist/components/dosha-constitution.js +1 -203
  106. package/dist/components/dream-card.js +1 -203
  107. package/dist/components/dream-search.js +1 -203
  108. package/dist/components/endpoint-form.js +1 -203
  109. package/dist/components/ephemeris-table.js +1 -203
  110. package/dist/components/fixed-stars.js +1 -203
  111. package/dist/components/flying-star-chart.js +1 -203
  112. package/dist/components/forecast-digest.js +1 -203
  113. package/dist/components/forecast-timeline.js +1 -203
  114. package/dist/components/gematria.js +1 -203
  115. package/dist/components/gochara-table.js +1 -203
  116. package/dist/components/guna-milan.js +1 -203
  117. package/dist/components/hd-connection.js +3 -205
  118. package/dist/components/hd-penta.js +5 -207
  119. package/dist/components/hd-type-card.js +1 -203
  120. package/dist/components/hd-variables.js +1 -203
  121. package/dist/components/heliacal-table.js +1 -203
  122. package/dist/components/hexagram.d.ts +1 -1
  123. package/dist/components/hexagram.js +1 -203
  124. package/dist/components/hora-table.js +1 -203
  125. package/dist/components/horoscope-card.js +1 -203
  126. package/dist/components/kp-chart.js +1 -203
  127. package/dist/components/kp-finance-card.js +1 -203
  128. package/dist/components/kp-planets-table.js +1 -203
  129. package/dist/components/kp-ruling-planets.js +1 -203
  130. package/dist/components/kua-card.js +1 -203
  131. package/dist/components/local-space-compass.js +4 -206
  132. package/dist/components/location-search.js +1 -203
  133. package/dist/components/luck-pillars.js +1 -203
  134. package/dist/components/mayan-day-sign.js +1 -203
  135. package/dist/components/moon-phase.js +1 -203
  136. package/dist/components/nakshatra-card.js +1 -203
  137. package/dist/components/natal-chart.d.ts +1 -1
  138. package/dist/components/natal-chart.js +5 -207
  139. package/dist/components/numerology-card.js +1 -203
  140. package/dist/components/panchang-table.js +1 -203
  141. package/dist/components/positions-table.js +1 -203
  142. package/dist/components/profection-card.js +1 -203
  143. package/dist/components/reference-card.js +1 -203
  144. package/dist/components/relocation-wheel.js +3 -205
  145. package/dist/components/shadbala-table.js +1 -203
  146. package/dist/components/synastry-chart.js +6 -208
  147. package/dist/components/tarot-card.js +1 -203
  148. package/dist/components/tarot-catalog.js +1 -203
  149. package/dist/components/tarot-spread.js +1 -203
  150. package/dist/components/transit-wheel.js +8 -210
  151. package/dist/components/transits-table.js +1 -203
  152. package/dist/components/upagraha-table.js +1 -203
  153. package/dist/components/vastu-mandala.js +6 -208
  154. package/dist/components/vedic-aspects.js +1 -203
  155. package/dist/components/vedic-daily.js +1 -203
  156. package/dist/components/vedic-kundli.js +15 -217
  157. package/dist/components/vedic-planets-table.js +1 -203
  158. package/dist/components/western-planets-table.js +1 -203
  159. package/dist/components/yoga-list.js +1 -203
  160. package/dist/components/zodiac-card.js +1 -203
  161. package/dist/forms.json +1 -1
  162. package/dist/index.cjs +49 -251
  163. package/dist/index.js +50 -252
  164. package/dist/locales/de.js +1 -1
  165. package/dist/schemas/post--astrology-lilith.json +1 -1
  166. package/dist/schemas/post--astrology-progressions.json +1 -1
  167. package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
  168. package/dist/schemas/post--numerology-chart.json +1 -1
  169. package/dist/schemas/post--vedic-astrology-daily.json +1 -1
  170. package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
  171. package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
  172. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
  173. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
  174. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
  175. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
  176. package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
  177. package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
  178. package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
  179. package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
  180. package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
  181. package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
  182. package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
  183. package/dist/schemas/post--vedic-astrology-transit.json +1 -1
  184. package/dist/styles/palettes.d.ts +4 -0
  185. package/dist/styles/themes/celeste.css +1 -115
  186. package/dist/styles/themes/eucalyptus.css +1 -121
  187. package/dist/styles/themes/kiln.css +1 -121
  188. package/dist/styles/themes/moonlit.css +1 -121
  189. package/dist/styles/themes/practitioner.css +1 -170
  190. package/dist/styles/tokens-css.d.ts +1 -1
  191. package/dist/styles/tokens.css +1 -202
  192. package/dist/types/types.gen.d.ts +48 -36
  193. package/dist/utils/string.d.ts +2 -0
  194. package/dist/version.d.ts +1 -1
  195. package/package.json +1 -1
@@ -1 +1 @@
1
- {"title":"Get all 9 Mahadasha periods (120-year cycle)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get all 9 Mahadasha periods (120-year cycle)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get all Prana dashas for a Mahadasha, Antardasha, Pratyantardasha and Sookshma","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn"},{"key":"antardasha","name":"antardasha","inQuery":false,"kind":"tiles","required":true,"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus"},{"key":"pratyantardasha","name":"pratyantardasha","inQuery":false,"kind":"tiles","required":true,"description":"Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Rahu"},{"key":"sookshma","name":"sookshma","inQuery":false,"kind":"tiles","required":true,"description":"Sookshma dasha planet name inside that Pratyantardasha, case-insensitive. Every full period contains all 9 lords, so a repeat such as saturn/saturn/saturn/saturn is valid.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Jupiter"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get all Prana dashas for a Mahadasha, Antardasha, Pratyantardasha and Sookshma","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn"},{"key":"antardasha","name":"antardasha","inQuery":false,"kind":"tiles","required":true,"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus"},{"key":"pratyantardasha","name":"pratyantardasha","inQuery":false,"kind":"tiles","required":true,"description":"Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Rahu"},{"key":"sookshma","name":"sookshma","inQuery":false,"kind":"tiles","required":true,"description":"Sookshma dasha planet name inside that Pratyantardasha, case-insensitive. Every full period contains all 9 lords, so a repeat such as saturn/saturn/saturn/saturn is valid.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Jupiter"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get all Sookshma dashas for a Mahadasha, Antardasha and Pratyantardasha","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn"},{"key":"antardasha","name":"antardasha","inQuery":false,"kind":"tiles","required":true,"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus"},{"key":"pratyantardasha","name":"pratyantardasha","inQuery":false,"kind":"tiles","required":true,"description":"Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Rahu"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get all Sookshma dashas for a Mahadasha, Antardasha and Pratyantardasha","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive. Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn"},{"key":"antardasha","name":"antardasha","inQuery":false,"kind":"tiles","required":true,"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus"},{"key":"pratyantardasha","name":"pratyantardasha","inQuery":false,"kind":"tiles","required":true,"description":"Pratyantardasha (antara) planet name inside that Antardasha, case-insensitive.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Rahu"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get all Pratyantardashas (antara periods) for a Mahadasha and Antardasha","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive (e.g. saturn, Saturn, SATURN all work). Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn"},{"key":"antardasha","name":"antardasha","inQuery":false,"kind":"tiles","required":true,"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive. Every Mahadasha contains all 9 lords, so a repeat such as saturn/saturn is valid.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get all Pratyantardashas (antara periods) for a Mahadasha and Antardasha","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive (e.g. saturn, Saturn, SATURN all work). Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Saturn"},{"key":"antardasha","name":"antardasha","inQuery":false,"kind":"tiles","required":true,"description":"Antardasha (bhukti) planet name inside that Mahadasha, case-insensitive. Every Mahadasha contains all 9 lords, so a repeat such as saturn/saturn is valid.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Venus"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get all Antardashas (sub-periods) for a specific Mahadasha","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive (e.g., jupiter, Jupiter, JUPITER all work). Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Jupiter"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get all Antardashas (sub-periods) for a specific Mahadasha","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. \"lahiri\" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. \"kp-old\" uses the Krishnamurti original table from KP Reader-1. \"raman\" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"lahiri","example":"lahiri","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"significators","name":"significators","kind":"toggle","required":false,"description":"Set true to attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","default":false,"example":false,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu, used ONLY when \"significators\" is true. Dasha dates themselves come from the Moon and never move with this field. \"mean\" uses the smooth mean node (traditional default). \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean over a 173-day cycle and can therefore change which house or star a node falls in. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"mahadasha","name":"mahadasha","inQuery":false,"kind":"tiles","required":true,"description":"Mahadasha planet name, case-insensitive (e.g., jupiter, Jupiter, JUPITER all work). Valid: Ketu, Venus, Sun, Moon, Mars, Rahu, Jupiter, Saturn, Mercury.","enum":["Ketu","Venus","Sun","Moon","Mars","Rahu","Jupiter","Saturn","Mercury"],"example":"Jupiter"},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Generate complete KP birth chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. CRITICAL for accurate Lagna and house calculations.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Generate complete KP birth chart","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. CRITICAL for accurate Lagna and house calculations.","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get KP Placidus house cusps with sub-lords","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get KP Placidus house cusps with sub-lords","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Daily finance score from four KP sub lord layers","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date, YYYY-MM-DD. Fixes the Placidus cusps, the four tier significators and the Vimshottari balance every layer reads.","example":"1990-06-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time, HH:MM:SS, 24 hour, local to the birth place. The cusp sub lords move about one sub every four minutes of clock time, so this is the input the whole reading is most sensitive to.","example":"07:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees. Sets the Placidus cusps; also the place the ruling planets and the Moon windows are read at.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees, east positive.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name (Asia/Kolkata) or decimal hours from UTC. Applies to the birth time, to the reading date and time, and to every local timestamp in the response. IANA names resolve to the offset in force on the date being read.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, YYYY-MM-DD in the request timezone. Defaults to today (UTC). The Moon windows cover this date from midnight to midnight.","example":"2026-09-14","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Reading moment on that date, HH:MM:SS local. The ruling planets and the running sookshma lord are read at this instant. Defaults to 12:00:00; pass a market open or any hour for an intraday read.","example":"12:00:00","fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"gainHouses","name":"gainHouses","kind":"array","required":false,"description":"Houses whose significators count as gain, 1 to 12. Defaults to the convention, 2 and 11. Override it to run your own school: the two lists may not share a house.","default":[2,11],"example":[2,11],"fold":true},{"key":"lossHouses","name":"lossHouses","kind":"array","required":false,"description":"Houses whose significators count as loss, 1 to 12. Defaults to the convention, 6 and 8 and 12. Override it to run your own school: the two lists may not share a house.","default":[6,8,12],"example":[6,8,12],"fold":true},{"key":"weights.cusps","name":"cusps","group":"weights","kind":"number","required":false,"description":"Percent of the final score the cusps layer carries.","min":0,"max":100,"example":30,"fold":true},{"key":"weights.dasha","name":"dasha","group":"weights","kind":"number","required":false,"description":"Percent of the final score the dasha layer carries.","min":0,"max":100,"example":40,"fold":true},{"key":"weights.rulingPlanets","name":"rulingPlanets","group":"weights","kind":"number","required":false,"description":"Percent of the final score the rulingPlanets layer carries.","min":0,"max":100,"example":15,"fold":true},{"key":"weights.moonWindows","name":"moonWindows","group":"weights","kind":"number","required":false,"description":"Percent of the final score the moonWindows layer carries.","min":0,"max":100,"example":15,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}},{"key":"weights","label":"Weights","fold":true}],"opensOnLoad":false}
1
+ {"title":"Daily finance score from four KP sub lord layers","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date, YYYY-MM-DD. Fixes the Placidus cusps, the four tier significators and the Vimshottari balance every layer reads.","example":"1990-06-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time, HH:MM:SS, 24 hour, local to the birth place. The cusp sub lords move about one sub every four minutes of clock time, so this is the input the whole reading is most sensitive to.","example":"07:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees. Sets the Placidus cusps; also the place the ruling planets and the Moon windows are read at. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees, east positive.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name (Asia/Kolkata) or decimal hours from UTC. Applies to the birth time, to the reading date and time, and to every local timestamp in the response. An IANA name is resolved twice, each to the offset in force at its own moment: at the birth date and time for the natal chart, and on the date being read for the reading. A decimal is applied to both as sent.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, YYYY-MM-DD in the request timezone. Defaults to today (UTC). The Moon windows cover this date from midnight to midnight.","example":"2026-09-14","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Reading moment on that date, HH:MM:SS local. The ruling planets and the running sookshma lord are read at this instant. Defaults to 12:00:00; pass a market open or any hour for an intraday read.","example":"12:00:00","fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"gainHouses","name":"gainHouses","kind":"array","required":false,"description":"Houses whose significators count as gain, 1 to 12. Defaults to the convention, 2 and 11. Override it to run your own school: the two lists may not share a house.","default":[2,11],"example":[2,11],"fold":true},{"key":"lossHouses","name":"lossHouses","kind":"array","required":false,"description":"Houses whose significators count as loss, 1 to 12. Defaults to the convention, 6 and 8 and 12. Override it to run your own school: the two lists may not share a house.","default":[6,8,12],"example":[6,8,12],"fold":true},{"key":"weights.cusps","name":"cusps","group":"weights","kind":"number","required":false,"description":"Percent of the final score the cusps layer carries.","min":0,"max":100,"example":30,"fold":true},{"key":"weights.dasha","name":"dasha","group":"weights","kind":"number","required":false,"description":"Percent of the final score the dasha layer carries.","min":0,"max":100,"example":40,"fold":true},{"key":"weights.rulingPlanets","name":"rulingPlanets","group":"weights","kind":"number","required":false,"description":"Percent of the final score the rulingPlanets layer carries.","min":0,"max":100,"example":15,"fold":true},{"key":"weights.moonWindows","name":"moonWindows","group":"weights","kind":"number","required":false,"description":"Percent of the final score the moonWindows layer carries.","min":0,"max":100,"example":15,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}},{"key":"weights","label":"Weights","fold":true}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Cast a KP horary (Prashna) chart from a number 1-249","fields":[{"key":"horaryNumber","name":"horaryNumber","kind":"number","required":true,"description":"Horary number from 1 to 249, given by the querent while focused on their question. It maps to one of the 249 KP sub divisions of the zodiac, and that division sets the Ascendant of the chart. The querent should give the first number that comes to mind and use it once for that question; the astrologer never chooses it. Numbers outside 1 to 249 are rejected rather than wrapped, because a wrapped number would silently answer a different question.","min":1,"max":249,"example":108},{"key":"date","name":"date","kind":"date","required":true,"description":"Date the question was taken up for judgment, YYYY-MM-DD. Not a birth date: a horary chart needs no birth details at all, which is the point of the method.","example":"2026-03-08"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time the question was taken up for judgment, 24-hour HH:MM:SS. In KP practice this is the moment the astrologer receives and understands the question, not the moment the querent first thought of it. It sets every planetary position and all twelve cusps except the Ascendant.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude where the question is judged, decimal degrees. The house cusps are Placidus and therefore latitude dependent, so this is the place of judgment, not the querent birthplace.","min":-90,"max":90,"example":19.076,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude where the question is judged, decimal degrees.","min":-180,"max":180,"example":72.8777,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\") OR decimal hours from UTC. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Cast a KP horary (Prashna) chart from a number 1-249","fields":[{"key":"horaryNumber","name":"horaryNumber","kind":"number","required":true,"description":"Horary number from 1 to 249, given by the querent while focused on their question. It maps to one of the 249 KP sub divisions of the zodiac, and that division sets the Ascendant of the chart. The querent should give the first number that comes to mind and use it once for that question; the astrologer never chooses it. Numbers outside 1 to 249 are rejected rather than wrapped, because a wrapped number would silently answer a different question.","min":1,"max":249,"example":108},{"key":"date","name":"date","kind":"date","required":true,"description":"Date the question was taken up for judgment, YYYY-MM-DD. Not a birth date: a horary chart needs no birth details at all, which is the point of the method.","example":"2026-03-08"},{"key":"time","name":"time","kind":"time","required":true,"description":"Time the question was taken up for judgment, 24-hour HH:MM:SS. In KP practice this is the moment the astrologer receives and understands the question, not the moment the querent first thought of it. It sets every planetary position and all twelve cusps except the Ascendant.","example":"14:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Latitude where the question is judged, decimal degrees. The house cusps are Placidus and therefore latitude dependent, so this is the place of judgment, not the querent birthplace. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":19.076,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Longitude where the question is judged, decimal degrees.","min":-180,"max":180,"example":72.8777,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\") OR decimal hours from UTC. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get KP planetary positions with sub-lords","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get KP planetary positions with sub-lords","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format","example":"1990-07-04"},{"key":"time","name":"time","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format","example":"10:12:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Accepted at any latitude, polar included: planet longitudes are geocentric and the star and sub lords are divisions of longitude, so no house cusp is involved.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST) for Vedic astrology.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula (most common for KP). \"kp-old\" uses the Krishnamurti original table. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. \"custom\" allows providing your own value via ayanamsaValue. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman","custom"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"ayanamsaValue","name":"ayanamsaValue","kind":"number","required":false,"description":"Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.","example":24,"fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get KP ruling planets with significators at intervals","fields":[{"key":"startDatetime","name":"startDatetime","kind":"datetime","required":true,"description":"Start of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T00:00:00Z"},{"key":"endDatetime","name":"endDatetime","kind":"datetime","required":true,"description":"End of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T01:00:00Z"},{"key":"intervalMinutes","name":"intervalMinutes","kind":"number","required":true,"description":"Interval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.","min":1,"max":1440,"example":5},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","min":-180,"max":180,"example":78.486671,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get KP ruling planets with significators at intervals","fields":[{"key":"startDatetime","name":"startDatetime","kind":"datetime","required":true,"description":"Start of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T00:00:00Z"},{"key":"endDatetime","name":"endDatetime","kind":"datetime","required":true,"description":"End of the interval range in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-02-03T01:00:00Z"},{"key":"intervalMinutes","name":"intervalMinutes","kind":"number","required":true,"description":"Interval between calculations in minutes (1-1440). Use 1-5 for birth time rectification.","min":1,"max":1440,"example":5},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. The latitude must lie below 66.56 degrees north or south, inside the polar circles: KP cusps are Placidus, which has no solution beyond them, so a polar latitude returns 400.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","min":-180,"max":180,"example":78.486671,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved once, at the start of the window, and that offset applies to every time in the response. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Output times are also converted to this timezone. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get KP ruling planets with optional significators","fields":[{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T10:30:00Z","fold":true},{"key":"birthDate","name":"birthDate","kind":"date","required":false,"description":"Birth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.","example":"1990-07-04","fold":true},{"key":"birthTime","name":"birthTime","kind":"time","required":false,"description":"Birth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.","example":"10:12:00","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get KP ruling planets with optional significators","fields":[{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Any latitude for the ruling planets alone; with birthDate and birthTime the significators read Placidus cusps, so the latitude must lie below 66.56 degrees north or south and a polar latitude returns 400.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. An IANA name is resolved to the DST-correct offset of each moment separately: at datetime for the ruling planets, and at birthDate and birthTime for the significators. A decimal is applied to both as sent. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) for ruling planets. Defaults to current time. Interpreted as local time when a non-zero timezone is provided (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2025-01-15T10:30:00Z","fold":true},{"key":"birthDate","name":"birthDate","kind":"date","required":false,"description":"Birth date (YYYY-MM-DD) to calculate significators. If provided with birthTime, response includes which houses each ruling planet signifies.","example":"1990-07-04","fold":true},{"key":"birthTime","name":"birthTime","kind":"time","required":false,"description":"Birth time (HH:MM:SS) for significator calculation. Required if birthDate is provided.","example":"10:12:00","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"focus","name":"focus","inQuery":true,"kind":"tiles","required":false,"description":"Which signification vocabulary the houseThemes map returns. \"general\" gives the classical bhava significations (self, wealth, siblings, home, and so on). \"finance\" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use \"finance\" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to \"general\".","enum":["general","finance"],"default":"general","example":"general","fold":true}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Transit Analysis","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.","example":"1990-07-04"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.","example":"10:12:00"},{"key":"transitDate","name":"transitDate","kind":"date","required":true,"description":"Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.","example":"2026-02-03"},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.","example":"12:00:00","fold":true},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations.","min":-180,"max":180,"example":78.486671,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Transit Analysis","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Used to calculate the natal chart against which transits are analyzed.","example":"1990-07-04"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). Critical for accurate natal Lagna and Placidus house cusps which determine transit house placements.","example":"10:12:00"},{"key":"transitDate","name":"transitDate","kind":"date","required":true,"description":"Transit date to analyze in YYYY-MM-DD format. Planetary positions on this date are overlaid on the natal chart.","example":"2026-02-03"},{"key":"transitTime","name":"transitTime","kind":"time","required":false,"description":"Transit time in HH:MM:SS format (24-hour). Affects fast-moving planets like Moon. Defaults to noon.","example":"12:00:00","fold":true},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees. Determines Placidus house cusps for natal chart house assignments.","min":-90,"max":90,"example":17.385044,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Affects local sidereal time for Lagna and house calculations.","min":-180,"max":180,"example":78.486671,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: an IANA name (e.g. \"America/New_York\", \"Europe/London\", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to the offset in force at the given date and time. The birth moment and the transit moment are each resolved at their own date and time. Defaults to 5.5 (IST).","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"coordinateSystem","name":"coordinateSystem","kind":"tiles","required":false,"description":"Coordinate system for longitude output. \"sidereal\" (Nirayana) uses Lahiri ayanamsa, the standard for Vedic astrology. \"tropical\" (Sayana) uses raw ecliptic longitude matching Western astrology. Defaults to \"sidereal\".","enum":["sidereal","tropical"],"default":"sidereal","example":"sidereal","fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -63,3 +63,7 @@ export declare const SHARED_THEME: ThemeChrome & {
63
63
  /** The chrome one preset ships: the shared set with its own overrides on top. */
64
64
  export declare function themeChrome(name: PaletteName): ThemeChrome;
65
65
  export declare const ROXY_PALETTES: Record<PaletteName, Palette>;
66
+ /** Every colour one preset sets in one mode, its own tokens plus the shared `danger`; the one source for the theme stylesheets and the published catalog. */
67
+ export declare function paletteColors(name: PaletteName, mode: 'light' | 'dark'): PaletteTokens & {
68
+ danger: string;
69
+ };
@@ -1,115 +1 @@
1
- /*
2
- * Celeste theme preset for Roxy UI. GENERATED by scripts/sync-themes.ts
3
- * from src/styles/palettes.ts. Do not edit; change the palette data and
4
- * rerun the codegen.
5
- *
6
- * It only reassigns --roxy-* tokens, so it composes with the core token
7
- * contract instead of replacing it: link it AFTER the base tokens (or the
8
- * CDN bundle that injects them) and every component on the page adopts the
9
- * look. Light and dark blocks mirror the trigger structure of tokens.css
10
- * exactly (OS preference, [data-theme] / .dark opt-in, and the explicit-
11
- * light opt-out), all at :where() zero specificity and inside the
12
- * roxy.theme cascade layer, so a per-page override still wins and the
13
- * preset still outranks the token defaults whichever file loads first.
14
- *
15
- * Fonts are the system stack, so the preset loads no font file.
16
- *
17
- * To use the whole preset with one line instead of copying tokens, link
18
- * the file:
19
- *
20
- * <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/@roxyapi/ui@latest/dist/styles/themes/celeste.css">
21
- */
22
-
23
- @layer roxy.tokens, roxy.theme;
24
-
25
- @layer roxy.theme {
26
- /* Light defaults. Fonts, radius, and shadow do not vary by theme, so they are
27
- * set once here and inherited by the dark blocks unchanged. */
28
- :where(:root, :host) {
29
- --roxy-font-sans:
30
- system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto,
31
- "Helvetica Neue", Arial, sans-serif;
32
- --roxy-font-display:
33
- system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto,
34
- "Helvetica Neue", Arial, sans-serif;
35
-
36
- --roxy-radius-sm: 0.125rem;
37
- --roxy-radius-md: 0.25rem;
38
- --roxy-radius-lg: 0.375rem;
39
-
40
- --roxy-shadow-sm: none;
41
- --roxy-shadow-md: none;
42
- --roxy-shadow-lg: none;
43
-
44
- --roxy-accent: #017272;
45
- --roxy-accent-ink: color-mix(in oklab, var(--roxy-accent) 70%, black);
46
- --roxy-ring: var(--roxy-accent);
47
- /* Secondary ink (form labels, generic-renderer text, chart strokes): tuned per palette between fg and muted, so it stays stronger than help text. */
48
- --roxy-secondary: #282f35;
49
- --roxy-danger: #b23a38;
50
-
51
- --roxy-bg: #fcfcfc;
52
- --roxy-surface: #fcfcfc;
53
- --roxy-fg: #030303;
54
- --roxy-muted: #474e55;
55
- --roxy-border: #d4d8dd;
56
- }
57
-
58
- /* Dark theme via system preference. Mirrors tokens.css: only the theme-varying
59
- * tokens are reassigned; accent-ink follows the accent (already legible on the
60
- * dark surface) rather than mixing toward black. */
61
- @media (prefers-color-scheme: dark) {
62
- :where(:root, :host) {
63
- --roxy-accent: #00bcbc;
64
- --roxy-accent-ink: var(--roxy-accent);
65
- --roxy-secondary: #c9ced4;
66
- --roxy-danger: #e4736b;
67
-
68
- --roxy-bg: #050a0f;
69
- --roxy-surface: #10171e;
70
- --roxy-fg: #f5f5f5;
71
- --roxy-muted: #a0a5ab;
72
- --roxy-border: #282f35;
73
- }
74
- }
75
-
76
- /* Light opt-out: beats the OS-dark block when the host explicitly chooses light. */
77
- :where(
78
- :root[data-theme="light"],
79
- [data-theme="light"],
80
- :root.light,
81
- .light,
82
- :host([data-theme="light"])
83
- ) {
84
- --roxy-accent: #017272;
85
- --roxy-accent-ink: color-mix(in oklab, var(--roxy-accent) 70%, black);
86
- --roxy-secondary: #282f35;
87
- --roxy-danger: #b23a38;
88
-
89
- --roxy-bg: #fcfcfc;
90
- --roxy-surface: #fcfcfc;
91
- --roxy-fg: #030303;
92
- --roxy-muted: #474e55;
93
- --roxy-border: #d4d8dd;
94
- }
95
-
96
- /* Dark theme via explicit opt-in ([data-theme=dark] or .dark on any ancestor). */
97
- :where(
98
- :root[data-theme="dark"],
99
- [data-theme="dark"],
100
- :root.dark,
101
- .dark,
102
- :host([data-theme="dark"])
103
- ) {
104
- --roxy-accent: #00bcbc;
105
- --roxy-accent-ink: var(--roxy-accent);
106
- --roxy-secondary: #c9ced4;
107
- --roxy-danger: #e4736b;
108
-
109
- --roxy-bg: #050a0f;
110
- --roxy-surface: #10171e;
111
- --roxy-fg: #f5f5f5;
112
- --roxy-muted: #a0a5ab;
113
- --roxy-border: #282f35;
114
- }
115
- }
1
+ @layer roxy.tokens,roxy.theme;@layer roxy.theme{:where(:root,:host){--roxy-font-sans: system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;--roxy-font-display: system-ui, -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif;--roxy-radius-sm: 0.125rem;--roxy-radius-md: 0.25rem;--roxy-radius-lg: 0.375rem;--roxy-shadow-sm: none;--roxy-shadow-md: none;--roxy-shadow-lg: none;--roxy-accent: #017272;--roxy-accent-ink: color-mix(in oklab, var(--roxy-accent) 70%, black);--roxy-ring: var(--roxy-accent);--roxy-secondary: #282f35;--roxy-danger: #b23a38;--roxy-bg: #fcfcfc;--roxy-surface: #fcfcfc;--roxy-fg: #030303;--roxy-muted: #474e55;--roxy-border: #d4d8dd}@media(prefers-color-scheme:dark){:where(:root,:host){--roxy-accent: #00bcbc;--roxy-accent-ink: var(--roxy-accent);--roxy-secondary: #c9ced4;--roxy-danger: #e4736b;--roxy-bg: #050a0f;--roxy-surface: #10171e;--roxy-fg: #f5f5f5;--roxy-muted: #a0a5ab;--roxy-border: #282f35}}:where(:root[data-theme=light],[data-theme=light],:root.light,.light,:host([data-theme="light"])){--roxy-accent: #017272;--roxy-accent-ink: color-mix(in oklab, var(--roxy-accent) 70%, black);--roxy-secondary: #282f35;--roxy-danger: #b23a38;--roxy-bg: #fcfcfc;--roxy-surface: #fcfcfc;--roxy-fg: #030303;--roxy-muted: #474e55;--roxy-border: #d4d8dd}:where(:root[data-theme=dark],[data-theme=dark],:root.dark,.dark,:host([data-theme="dark"])){--roxy-accent: #00bcbc;--roxy-accent-ink: var(--roxy-accent);--roxy-secondary: #c9ced4;--roxy-danger: #e4736b;--roxy-bg: #050a0f;--roxy-surface: #10171e;--roxy-fg: #f5f5f5;--roxy-muted: #a0a5ab;--roxy-border: #282f35}}