@roxyapi/ui 1.1.3 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (531) hide show
  1. package/AGENTS.md +39 -1
  2. package/README.md +82 -1
  3. package/THEMING.md +34 -13
  4. package/components-catalog.json +1 -11247
  5. package/dist/cdn/components/almanac-day.js +3 -4
  6. package/dist/cdn/components/angel-number-card.js +3 -4
  7. package/dist/cdn/components/angel-number-lookup.js +3 -4
  8. package/dist/cdn/components/arudha-padas.js +3 -4
  9. package/dist/cdn/components/ashtakavarga-grid.js +3 -4
  10. package/dist/cdn/components/aspects-table.js +3 -4
  11. package/dist/cdn/components/astrocartography-map.js +9 -10
  12. package/dist/cdn/components/bazi-chart.js +3 -4
  13. package/dist/cdn/components/bhav-chalit-table.js +3 -4
  14. package/dist/cdn/components/bhava-bala-table.js +3 -4
  15. package/dist/cdn/components/biorhythm-chart.js +3 -4
  16. package/dist/cdn/components/bodygraph.js +14 -13
  17. package/dist/cdn/components/chara-karakas.js +3 -4
  18. package/dist/cdn/components/choghadiya-grid.js +3 -4
  19. package/dist/cdn/components/compatibility-card.js +3 -4
  20. package/dist/cdn/components/compound-number.js +3 -4
  21. package/dist/cdn/components/crystal-card.js +3 -4
  22. package/dist/cdn/components/crystal-grid.js +3 -4
  23. package/dist/cdn/components/dasha-timeline.js +3 -4
  24. package/dist/cdn/components/data.js +3 -4
  25. package/dist/cdn/components/divisional-chart.js +50 -49
  26. package/dist/cdn/components/dosha-card.js +3 -4
  27. package/dist/cdn/components/dosha-constitution.js +3 -4
  28. package/dist/cdn/components/dream-card.js +3 -4
  29. package/dist/cdn/components/dream-search.js +3 -4
  30. package/dist/cdn/components/endpoint-form.js +3 -4
  31. package/dist/cdn/components/ephemeris-table.js +3 -4
  32. package/dist/cdn/components/fixed-stars.js +3 -4
  33. package/dist/cdn/components/flying-star-chart.js +3 -4
  34. package/dist/cdn/components/forecast-digest.js +3 -4
  35. package/dist/cdn/components/forecast-timeline.js +3 -4
  36. package/dist/cdn/components/gematria.js +3 -4
  37. package/dist/cdn/components/gochara-table.js +3 -4
  38. package/dist/cdn/components/guna-milan.js +3 -4
  39. package/dist/cdn/components/hd-connection.js +13 -12
  40. package/dist/cdn/components/hd-penta.js +18 -19
  41. package/dist/cdn/components/hd-type-card.js +3 -4
  42. package/dist/cdn/components/hd-variables.js +3 -4
  43. package/dist/cdn/components/heliacal-table.js +3 -4
  44. package/dist/cdn/components/hexagram.js +3 -4
  45. package/dist/cdn/components/hora-table.js +3 -4
  46. package/dist/cdn/components/horoscope-card.js +3 -4
  47. package/dist/cdn/components/kp-chart.js +3 -4
  48. package/dist/cdn/components/kp-finance-card.js +3 -4
  49. package/dist/cdn/components/kp-planets-table.js +3 -4
  50. package/dist/cdn/components/kp-ruling-planets.js +3 -4
  51. package/dist/cdn/components/kua-card.js +3 -4
  52. package/dist/cdn/components/local-space-compass.js +6 -7
  53. package/dist/cdn/components/location-search.js +3 -4
  54. package/dist/cdn/components/luck-pillars.js +3 -4
  55. package/dist/cdn/components/mayan-day-sign.js +3 -4
  56. package/dist/cdn/components/moon-phase.js +3 -4
  57. package/dist/cdn/components/nakshatra-card.js +3 -4
  58. package/dist/cdn/components/natal-chart.js +24 -14
  59. package/dist/cdn/components/numerology-card.js +3 -4
  60. package/dist/cdn/components/panchang-table.js +3 -4
  61. package/dist/cdn/components/positions-table.js +3 -4
  62. package/dist/cdn/components/profection-card.js +3 -4
  63. package/dist/cdn/components/reference-card.js +3 -4
  64. package/dist/cdn/components/relocation-wheel.js +24 -14
  65. package/dist/cdn/components/report.js +50 -0
  66. package/dist/cdn/components/shadbala-table.js +3 -4
  67. package/dist/cdn/components/synastry-chart.js +21 -12
  68. package/dist/cdn/components/tarot-card.js +3 -4
  69. package/dist/cdn/components/tarot-catalog.js +3 -4
  70. package/dist/cdn/components/tarot-spread.js +3 -4
  71. package/dist/cdn/components/transit-wheel.js +10 -11
  72. package/dist/cdn/components/transits-table.js +3 -4
  73. package/dist/cdn/components/upagraha-table.js +3 -4
  74. package/dist/cdn/components/vastu-mandala.js +9 -10
  75. package/dist/cdn/components/vedic-aspects.js +3 -4
  76. package/dist/cdn/components/vedic-daily.js +3 -4
  77. package/dist/cdn/components/vedic-kundli.js +49 -48
  78. package/dist/cdn/components/vedic-planets-table.js +3 -4
  79. package/dist/cdn/components/western-planets-table.js +3 -4
  80. package/dist/cdn/components/yoga-list.js +3 -4
  81. package/dist/cdn/components/zodiac-card.js +3 -4
  82. package/dist/cdn/locales/de.js +1 -1
  83. package/dist/cdn/locales/es.js +1 -1
  84. package/dist/cdn/locales/fr.js +1 -1
  85. package/dist/cdn/locales/hi.js +1 -1
  86. package/dist/cdn/locales/pt.js +1 -1
  87. package/dist/cdn/locales/ru.js +1 -1
  88. package/dist/cdn/locales/tr.js +1 -1
  89. package/dist/cdn/roxy-ui.js +113 -96
  90. package/dist/cdn/widgets.js +1 -1
  91. package/dist/charts.cjs +111 -0
  92. package/dist/charts.d.ts +8 -0
  93. package/dist/charts.js +111 -0
  94. package/dist/components/almanac-day.js +1 -1
  95. package/dist/components/angel-number-card.js +1 -1
  96. package/dist/components/angel-number-lookup.js +1 -1
  97. package/dist/components/arudha-padas.js +1 -1
  98. package/dist/components/ashtakavarga-grid.js +1 -1
  99. package/dist/components/aspects-table.js +1 -1
  100. package/dist/components/astrocartography-map.js +5 -5
  101. package/dist/components/bazi-chart.js +1 -1
  102. package/dist/components/bhav-chalit-table.js +1 -1
  103. package/dist/components/bhava-bala-table.js +1 -1
  104. package/dist/components/biorhythm-chart.js +1 -1
  105. package/dist/components/bodygraph.d.ts +0 -4
  106. package/dist/components/bodygraph.js +10 -10
  107. package/dist/components/chara-karakas.js +1 -1
  108. package/dist/components/choghadiya-grid.js +1 -1
  109. package/dist/components/compatibility-card.js +1 -1
  110. package/dist/components/compound-number.js +1 -1
  111. package/dist/components/crystal-card.js +1 -1
  112. package/dist/components/crystal-grid.js +1 -1
  113. package/dist/components/dasha-timeline.js +1 -1
  114. package/dist/components/data.js +1 -1
  115. package/dist/components/divisional-chart.js +60 -60
  116. package/dist/components/dosha-card.js +1 -1
  117. package/dist/components/dosha-constitution.js +1 -1
  118. package/dist/components/dream-card.js +1 -1
  119. package/dist/components/dream-search.js +1 -1
  120. package/dist/components/endpoint-form.d.ts +3 -1
  121. package/dist/components/endpoint-form.js +1 -1
  122. package/dist/components/ephemeris-table.js +1 -1
  123. package/dist/components/fixed-stars.js +1 -1
  124. package/dist/components/flying-star-chart.js +1 -1
  125. package/dist/components/forecast-digest.js +1 -1
  126. package/dist/components/forecast-timeline.js +1 -1
  127. package/dist/components/gematria.js +1 -1
  128. package/dist/components/gochara-table.js +1 -1
  129. package/dist/components/guna-milan.js +1 -1
  130. package/dist/components/hd-connection.js +10 -10
  131. package/dist/components/hd-penta.js +16 -16
  132. package/dist/components/hd-type-card.js +1 -1
  133. package/dist/components/hd-variables.js +1 -1
  134. package/dist/components/heliacal-table.js +1 -1
  135. package/dist/components/hexagram.js +1 -1
  136. package/dist/components/hora-table.js +1 -1
  137. package/dist/components/horoscope-card.js +1 -1
  138. package/dist/components/kp-chart.js +1 -1
  139. package/dist/components/kp-finance-card.js +1 -1
  140. package/dist/components/kp-planets-table.js +1 -1
  141. package/dist/components/kp-ruling-planets.js +1 -1
  142. package/dist/components/kua-card.js +1 -1
  143. package/dist/components/local-space-compass.js +5 -5
  144. package/dist/components/location-search.d.ts +1 -0
  145. package/dist/components/location-search.js +1 -1
  146. package/dist/components/luck-pillars.js +1 -1
  147. package/dist/components/mayan-day-sign.js +1 -1
  148. package/dist/components/moon-phase.js +1 -1
  149. package/dist/components/nakshatra-card.js +1 -1
  150. package/dist/components/natal-chart.d.ts +3 -82
  151. package/dist/components/natal-chart.js +20 -11
  152. package/dist/components/numerology-card.js +1 -1
  153. package/dist/components/panchang-table.js +1 -1
  154. package/dist/components/positions-table.js +1 -1
  155. package/dist/components/profection-card.js +1 -1
  156. package/dist/components/reference-card.js +1 -1
  157. package/dist/components/relocation-wheel.js +20 -11
  158. package/dist/components/report.d.ts +61 -0
  159. package/dist/components/report.js +1 -0
  160. package/dist/components/shadbala-table.js +1 -1
  161. package/dist/components/synastry-chart.d.ts +2 -34
  162. package/dist/components/synastry-chart.js +17 -9
  163. package/dist/components/tarot-card.js +1 -1
  164. package/dist/components/tarot-catalog.js +1 -1
  165. package/dist/components/tarot-spread.js +1 -1
  166. package/dist/components/transit-wheel.js +7 -7
  167. package/dist/components/transits-table.js +1 -1
  168. package/dist/components/upagraha-table.js +1 -1
  169. package/dist/components/vastu-mandala.js +9 -9
  170. package/dist/components/vedic-aspects.js +1 -1
  171. package/dist/components/vedic-daily.js +1 -1
  172. package/dist/components/vedic-kundli.js +54 -54
  173. package/dist/components/vedic-planets-table.js +1 -1
  174. package/dist/components/western-planets-table.js +1 -1
  175. package/dist/components/yoga-list.js +1 -1
  176. package/dist/components/zodiac-card.js +1 -1
  177. package/dist/forms/labels/de.json +1 -1
  178. package/dist/forms/labels/en.json +1 -1
  179. package/dist/forms/labels/es.json +1 -1
  180. package/dist/forms/labels/fr.json +1 -1
  181. package/dist/forms/labels/hi.json +1 -1
  182. package/dist/forms/labels/pt.json +1 -1
  183. package/dist/forms/labels/ru.json +1 -1
  184. package/dist/forms/labels/tr.json +1 -1
  185. package/dist/forms.json +1 -1
  186. package/dist/generated/endpoint-defaults.d.ts +1 -0
  187. package/dist/generated/field-labels-en.d.ts +1 -1
  188. package/dist/i18n/chrome-strings.d.ts +1 -1
  189. package/dist/i18n/lang.d.ts +3 -1
  190. package/dist/i18n/localized-element.d.ts +4 -0
  191. package/dist/i18n/registry.d.ts +7 -0
  192. package/dist/index.cjs +111 -94
  193. package/dist/index.d.ts +1 -0
  194. package/dist/index.js +111 -94
  195. package/dist/locales/de.js +1 -1
  196. package/dist/locales/es.js +1 -1
  197. package/dist/locales/field-labels/de.d.ts +1 -1
  198. package/dist/locales/field-labels/es.d.ts +1 -1
  199. package/dist/locales/field-labels/fr.d.ts +1 -1
  200. package/dist/locales/field-labels/hi.d.ts +1 -1
  201. package/dist/locales/field-labels/pt.d.ts +1 -1
  202. package/dist/locales/field-labels/ru.d.ts +1 -1
  203. package/dist/locales/field-labels/tr.d.ts +1 -1
  204. package/dist/locales/fr.js +1 -1
  205. package/dist/locales/hi.js +1 -1
  206. package/dist/locales/pt.js +1 -1
  207. package/dist/locales/ru.js +1 -1
  208. package/dist/locales/tr.js +1 -1
  209. package/dist/manifest.d.ts +3 -5
  210. package/dist/manifest.json +1 -89
  211. package/dist/schemas/get--angel-numbers-lookup.json +1 -1
  212. package/dist/schemas/get--angel-numbers-numbers-number.json +1 -1
  213. package/dist/schemas/get--angel-numbers-numbers.json +1 -1
  214. package/dist/schemas/get--astrology-horoscope-sign-daily.json +1 -1
  215. package/dist/schemas/get--astrology-horoscope-sign-monthly.json +1 -1
  216. package/dist/schemas/get--astrology-horoscope-sign-weekly.json +1 -1
  217. package/dist/schemas/get--astrology-horoscope-sign-yearly.json +1 -1
  218. package/dist/schemas/get--astrology-moon-phase-calendar-year-month.json +1 -1
  219. package/dist/schemas/get--astrology-moon-phase-current.json +1 -1
  220. package/dist/schemas/get--astrology-moon-phase-upcoming.json +1 -1
  221. package/dist/schemas/get--astrology-planet-meanings-id.json +1 -1
  222. package/dist/schemas/get--astrology-planet-meanings.json +1 -1
  223. package/dist/schemas/get--astrology-signs-id.json +1 -1
  224. package/dist/schemas/get--astrology-signs.json +1 -1
  225. package/dist/schemas/get--ayurveda-daily.json +1 -1
  226. package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
  227. package/dist/schemas/get--ayurveda-doshas.json +1 -1
  228. package/dist/schemas/get--ayurveda-qualities.json +1 -1
  229. package/dist/schemas/get--ayurveda-tastes.json +1 -1
  230. package/dist/schemas/get--chinese-astrology-calendar-day-date.json +1 -1
  231. package/dist/schemas/get--chinese-astrology-calendar-monthly.json +1 -1
  232. package/dist/schemas/get--chinese-astrology-calendar-solar-terms-year.json +1 -1
  233. package/dist/schemas/get--chinese-astrology-elements.json +1 -1
  234. package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
  235. package/dist/schemas/get--chinese-astrology-zodiac-animals.json +1 -1
  236. package/dist/schemas/get--chinese-astrology-zodiac-compatibility-sign1-sign2.json +1 -1
  237. package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
  238. package/dist/schemas/get--crystals-birthstone-month.json +1 -1
  239. package/dist/schemas/get--crystals-chakra-chakra.json +1 -1
  240. package/dist/schemas/get--crystals-colors.json +1 -1
  241. package/dist/schemas/get--crystals-element-element.json +1 -1
  242. package/dist/schemas/get--crystals-id.json +1 -1
  243. package/dist/schemas/get--crystals-pairings-id.json +1 -1
  244. package/dist/schemas/get--crystals-planets.json +1 -1
  245. package/dist/schemas/get--crystals-random.json +1 -1
  246. package/dist/schemas/get--crystals-search.json +1 -1
  247. package/dist/schemas/get--crystals-zodiac-sign.json +1 -1
  248. package/dist/schemas/get--crystals.json +1 -1
  249. package/dist/schemas/get--dreams-symbols-id.json +1 -1
  250. package/dist/schemas/get--dreams-symbols-letters.json +1 -1
  251. package/dist/schemas/get--dreams-symbols-random.json +1 -1
  252. package/dist/schemas/get--dreams-symbols.json +1 -1
  253. package/dist/schemas/get--feng-shui-afflictions-year.json +1 -1
  254. package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
  255. package/dist/schemas/get--feng-shui-bagua.json +1 -1
  256. package/dist/schemas/get--feng-shui-flying-stars-annual-year.json +1 -1
  257. package/dist/schemas/get--feng-shui-flying-stars-monthly.json +1 -1
  258. package/dist/schemas/get--feng-shui-flying-stars-stars.json +1 -1
  259. package/dist/schemas/get--feng-shui-kua-number.json +1 -1
  260. package/dist/schemas/get--feng-shui-periods.json +1 -1
  261. package/dist/schemas/get--human-design-centers-id.json +1 -1
  262. package/dist/schemas/get--human-design-gates-number.json +1 -1
  263. package/dist/schemas/get--iching-cast.json +1 -1
  264. package/dist/schemas/get--iching-hexagrams-lookup.json +1 -1
  265. package/dist/schemas/get--iching-hexagrams-number.json +1 -1
  266. package/dist/schemas/get--iching-hexagrams-random.json +1 -1
  267. package/dist/schemas/get--iching-hexagrams.json +1 -1
  268. package/dist/schemas/get--iching-trigrams-id.json +1 -1
  269. package/dist/schemas/get--iching-trigrams.json +1 -1
  270. package/dist/schemas/get--kabbalah-ciphers.json +1 -1
  271. package/dist/schemas/get--kabbalah-daily.json +1 -1
  272. package/dist/schemas/get--kabbalah-letters-id.json +1 -1
  273. package/dist/schemas/get--kabbalah-letters.json +1 -1
  274. package/dist/schemas/get--kabbalah-names-number.json +1 -1
  275. package/dist/schemas/get--kabbalah-names.json +1 -1
  276. package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
  277. package/dist/schemas/get--kabbalah-tree.json +1 -1
  278. package/dist/schemas/get--languages-field-labels.json +1 -1
  279. package/dist/schemas/get--languages.json +1 -1
  280. package/dist/schemas/get--location-countries-iso2.json +1 -1
  281. package/dist/schemas/get--location-countries.json +1 -1
  282. package/dist/schemas/get--location-search.json +1 -1
  283. package/dist/schemas/get--mesoamerican-astrology-aztec-daily.json +1 -1
  284. package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
  285. package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs.json +1 -1
  286. package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas-number.json +1 -1
  287. package/dist/schemas/get--mesoamerican-astrology-aztec-trecenas.json +1 -1
  288. package/dist/schemas/get--mesoamerican-astrology-mayan-calendar-monthly.json +1 -1
  289. package/dist/schemas/get--mesoamerican-astrology-mayan-daily.json +1 -1
  290. package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
  291. package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs.json +1 -1
  292. package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
  293. package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months.json +1 -1
  294. package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas-number.json +1 -1
  295. package/dist/schemas/get--mesoamerican-astrology-mayan-trecenas.json +1 -1
  296. package/dist/schemas/get--numerology-compound-number-number.json +1 -1
  297. package/dist/schemas/get--numerology-meanings-number.json +1 -1
  298. package/dist/schemas/get--tarot-cards-id.json +1 -1
  299. package/dist/schemas/get--tarot-cards.json +1 -1
  300. package/dist/schemas/get--usage.json +1 -1
  301. package/dist/schemas/get--vastu-devatas-id.json +1 -1
  302. package/dist/schemas/get--vastu-devatas.json +1 -1
  303. package/dist/schemas/get--vastu-directions-id.json +1 -1
  304. package/dist/schemas/get--vastu-directions.json +1 -1
  305. package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
  306. package/dist/schemas/get--vedic-astrology-avasthas.json +1 -1
  307. package/dist/schemas/get--vedic-astrology-kp-ayanamsa.json +1 -1
  308. package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
  309. package/dist/schemas/get--vedic-astrology-nakshatras.json +1 -1
  310. package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
  311. package/dist/schemas/get--vedic-astrology-rashis.json +1 -1
  312. package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
  313. package/dist/schemas/get--vedic-astrology-yoga.json +1 -1
  314. package/dist/schemas/post--angel-numbers-daily.json +1 -1
  315. package/dist/schemas/post--astrology-arabic-lots.json +1 -1
  316. package/dist/schemas/post--astrology-aspect-patterns.json +1 -1
  317. package/dist/schemas/post--astrology-aspects-monthly.json +1 -1
  318. package/dist/schemas/post--astrology-aspects.json +1 -1
  319. package/dist/schemas/post--astrology-asteroids.json +1 -1
  320. package/dist/schemas/post--astrology-astrocartography.json +1 -1
  321. package/dist/schemas/post--astrology-compatibility-score.json +1 -1
  322. package/dist/schemas/post--astrology-composite-chart.json +1 -1
  323. package/dist/schemas/post--astrology-ecliptic-crossings.json +1 -1
  324. package/dist/schemas/post--astrology-fixed-stars.json +1 -1
  325. package/dist/schemas/post--astrology-houses.json +1 -1
  326. package/dist/schemas/post--astrology-lilith.json +1 -1
  327. package/dist/schemas/post--astrology-local-space.json +1 -1
  328. package/dist/schemas/post--astrology-lunar-return.json +1 -1
  329. package/dist/schemas/post--astrology-natal-chart.json +1 -1
  330. package/dist/schemas/post--astrology-parallels-monthly.json +1 -1
  331. package/dist/schemas/post--astrology-planetary-returns.json +1 -1
  332. package/dist/schemas/post--astrology-planets-monthly.json +1 -1
  333. package/dist/schemas/post--astrology-planets.json +1 -1
  334. package/dist/schemas/post--astrology-profections.json +1 -1
  335. package/dist/schemas/post--astrology-progressions.json +1 -1
  336. package/dist/schemas/post--astrology-relocation-chart.json +1 -1
  337. package/dist/schemas/post--astrology-solar-arc.json +1 -1
  338. package/dist/schemas/post--astrology-solar-return.json +1 -1
  339. package/dist/schemas/post--astrology-synastry.json +1 -1
  340. package/dist/schemas/post--astrology-transit-aspects.json +1 -1
  341. package/dist/schemas/post--astrology-transits-monthly.json +1 -1
  342. package/dist/schemas/post--astrology-transits.json +1 -1
  343. package/dist/schemas/post--ayurveda-constitution.json +1 -1
  344. package/dist/schemas/post--ayurveda-dinacharya.json +1 -1
  345. package/dist/schemas/post--ayurveda-ritucharya.json +1 -1
  346. package/dist/schemas/post--biorhythm-compatibility.json +1 -1
  347. package/dist/schemas/post--biorhythm-critical-days.json +1 -1
  348. package/dist/schemas/post--biorhythm-daily.json +1 -1
  349. package/dist/schemas/post--biorhythm-forecast.json +1 -1
  350. package/dist/schemas/post--biorhythm-phases.json +1 -1
  351. package/dist/schemas/post--biorhythm-reading.json +1 -1
  352. package/dist/schemas/post--chinese-astrology-bazi-annual-forecast.json +1 -1
  353. package/dist/schemas/post--chinese-astrology-bazi-chart.json +1 -1
  354. package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
  355. package/dist/schemas/post--chinese-astrology-bazi-day-master.json +1 -1
  356. package/dist/schemas/post--chinese-astrology-bazi-luck-pillars.json +1 -1
  357. package/dist/schemas/post--chinese-astrology-calendar-auspicious-days.json +1 -1
  358. package/dist/schemas/post--chinese-astrology-calendar-lunar-date.json +1 -1
  359. package/dist/schemas/post--chinese-astrology-zodiac-sign.json +1 -1
  360. package/dist/schemas/post--crystals-daily.json +1 -1
  361. package/dist/schemas/post--dreams-daily.json +1 -1
  362. package/dist/schemas/post--feng-shui-eight-mansions.json +1 -1
  363. package/dist/schemas/post--feng-shui-flying-stars-natal.json +1 -1
  364. package/dist/schemas/post--feng-shui-kua.json +1 -1
  365. package/dist/schemas/post--forecast-digest.json +1 -1
  366. package/dist/schemas/post--forecast-significant-dates.json +1 -1
  367. package/dist/schemas/post--forecast-solar-return.json +1 -1
  368. package/dist/schemas/post--forecast-timeline.json +1 -1
  369. package/dist/schemas/post--forecast-transits.json +1 -1
  370. package/dist/schemas/post--human-design-bodygraph.json +1 -1
  371. package/dist/schemas/post--human-design-centers.json +1 -1
  372. package/dist/schemas/post--human-design-channels.json +1 -1
  373. package/dist/schemas/post--human-design-connection.json +1 -1
  374. package/dist/schemas/post--human-design-gates.json +1 -1
  375. package/dist/schemas/post--human-design-penta.json +1 -1
  376. package/dist/schemas/post--human-design-profile.json +1 -1
  377. package/dist/schemas/post--human-design-transit.json +1 -1
  378. package/dist/schemas/post--human-design-type.json +1 -1
  379. package/dist/schemas/post--human-design-variables.json +1 -1
  380. package/dist/schemas/post--iching-daily-cast.json +1 -1
  381. package/dist/schemas/post--iching-daily.json +1 -1
  382. package/dist/schemas/post--kabbalah-birth-profile.json +1 -1
  383. package/dist/schemas/post--kabbalah-compatibility.json +1 -1
  384. package/dist/schemas/post--kabbalah-gematria.json +1 -1
  385. package/dist/schemas/post--kabbalah-name-profile.json +1 -1
  386. package/dist/schemas/post--mesoamerican-astrology-aztec-tonalpohualli.json +1 -1
  387. package/dist/schemas/post--mesoamerican-astrology-mayan-chart.json +1 -1
  388. package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
  389. package/dist/schemas/post--mesoamerican-astrology-mayan-long-count-convert.json +1 -1
  390. package/dist/schemas/post--mesoamerican-astrology-mayan-tzolkin.json +1 -1
  391. package/dist/schemas/post--numerology-birth-day.json +1 -1
  392. package/dist/schemas/post--numerology-bridge.json +1 -1
  393. package/dist/schemas/post--numerology-business-name.json +1 -1
  394. package/dist/schemas/post--numerology-chaldean.json +1 -1
  395. package/dist/schemas/post--numerology-chart.json +1 -1
  396. package/dist/schemas/post--numerology-compatibility.json +1 -1
  397. package/dist/schemas/post--numerology-daily.json +1 -1
  398. package/dist/schemas/post--numerology-dual.json +1 -1
  399. package/dist/schemas/post--numerology-expression.json +1 -1
  400. package/dist/schemas/post--numerology-karmic-debt.json +1 -1
  401. package/dist/schemas/post--numerology-karmic-lessons.json +1 -1
  402. package/dist/schemas/post--numerology-life-path.json +1 -1
  403. package/dist/schemas/post--numerology-maturity.json +1 -1
  404. package/dist/schemas/post--numerology-personal-day.json +1 -1
  405. package/dist/schemas/post--numerology-personal-month.json +1 -1
  406. package/dist/schemas/post--numerology-personal-year.json +1 -1
  407. package/dist/schemas/post--numerology-personality.json +1 -1
  408. package/dist/schemas/post--numerology-soul-urge.json +1 -1
  409. package/dist/schemas/post--reports-bazi.json +1 -0
  410. package/dist/schemas/post--reports-human-design.json +1 -0
  411. package/dist/schemas/post--reports-kundli.json +1 -0
  412. package/dist/schemas/post--reports-matchmaking.json +1 -0
  413. package/dist/schemas/post--reports-natal.json +1 -0
  414. package/dist/schemas/post--reports-numerology.json +1 -0
  415. package/dist/schemas/post--reports-synastry.json +1 -0
  416. package/dist/schemas/post--reports-tarot.json +1 -0
  417. package/dist/schemas/post--reports-yearly-forecast.json +1 -0
  418. package/dist/schemas/post--tarot-daily.json +1 -1
  419. package/dist/schemas/post--tarot-draw.json +1 -1
  420. package/dist/schemas/post--tarot-spreads-career.json +1 -1
  421. package/dist/schemas/post--tarot-spreads-celtic-cross.json +1 -1
  422. package/dist/schemas/post--tarot-spreads-custom.json +1 -1
  423. package/dist/schemas/post--tarot-spreads-love.json +1 -1
  424. package/dist/schemas/post--tarot-spreads-three-card.json +1 -1
  425. package/dist/schemas/post--tarot-yes-no.json +1 -1
  426. package/dist/schemas/post--vastu-ayadi.json +1 -1
  427. package/dist/schemas/post--vastu-entrance.json +1 -1
  428. package/dist/schemas/post--vastu-mandala.json +1 -1
  429. package/dist/schemas/post--vastu-plot.json +1 -1
  430. package/dist/schemas/post--vastu-rooms.json +1 -1
  431. package/dist/schemas/post--vastu-timing-griha-pravesh.json +1 -1
  432. package/dist/schemas/post--vedic-astrology-arudha.json +1 -1
  433. package/dist/schemas/post--vedic-astrology-ashtakavarga.json +1 -1
  434. package/dist/schemas/post--vedic-astrology-aspects-lunar.json +1 -1
  435. package/dist/schemas/post--vedic-astrology-aspects-monthly.json +1 -1
  436. package/dist/schemas/post--vedic-astrology-aspects.json +1 -1
  437. package/dist/schemas/post--vedic-astrology-bhav-chalit.json +1 -1
  438. package/dist/schemas/post--vedic-astrology-bhava-bala.json +1 -1
  439. package/dist/schemas/post--vedic-astrology-birth-chart.json +1 -1
  440. package/dist/schemas/post--vedic-astrology-chara-karakas.json +1 -1
  441. package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
  442. package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
  443. package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
  444. package/dist/schemas/post--vedic-astrology-daily.json +1 -1
  445. package/dist/schemas/post--vedic-astrology-dasha-current.json +1 -1
  446. package/dist/schemas/post--vedic-astrology-dasha-major.json +1 -1
  447. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha-sookshma.json +1 -1
  448. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha-pratyantardasha.json +1 -1
  449. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha-antardasha.json +1 -1
  450. package/dist/schemas/post--vedic-astrology-dasha-sub-mahadasha.json +1 -1
  451. package/dist/schemas/post--vedic-astrology-divisional-chart.json +1 -1
  452. package/dist/schemas/post--vedic-astrology-dosha-kalsarpa.json +1 -1
  453. package/dist/schemas/post--vedic-astrology-dosha-manglik.json +1 -1
  454. package/dist/schemas/post--vedic-astrology-dosha-sadhesati.json +1 -1
  455. package/dist/schemas/post--vedic-astrology-ecliptic-crossings.json +1 -1
  456. package/dist/schemas/post--vedic-astrology-heliacal.json +1 -1
  457. package/dist/schemas/post--vedic-astrology-kp-chart.json +1 -1
  458. package/dist/schemas/post--vedic-astrology-kp-cusps.json +1 -1
  459. package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
  460. package/dist/schemas/post--vedic-astrology-kp-horary.json +1 -1
  461. package/dist/schemas/post--vedic-astrology-kp-planets-interval.json +1 -1
  462. package/dist/schemas/post--vedic-astrology-kp-planets.json +1 -1
  463. package/dist/schemas/post--vedic-astrology-kp-rasi-changes.json +1 -1
  464. package/dist/schemas/post--vedic-astrology-kp-ruling-planets-interval.json +1 -1
  465. package/dist/schemas/post--vedic-astrology-kp-ruling-planets.json +1 -1
  466. package/dist/schemas/post--vedic-astrology-kp-sublord-changes.json +1 -1
  467. package/dist/schemas/post--vedic-astrology-navamsa.json +1 -1
  468. package/dist/schemas/post--vedic-astrology-panchang-basic.json +1 -1
  469. package/dist/schemas/post--vedic-astrology-panchang-choghadiya.json +1 -1
  470. package/dist/schemas/post--vedic-astrology-panchang-detailed.json +1 -1
  471. package/dist/schemas/post--vedic-astrology-panchang-hora.json +1 -1
  472. package/dist/schemas/post--vedic-astrology-parallels-monthly.json +1 -1
  473. package/dist/schemas/post--vedic-astrology-parallels.json +1 -1
  474. package/dist/schemas/post--vedic-astrology-planetary-positions-monthly.json +1 -1
  475. package/dist/schemas/post--vedic-astrology-planetary-positions.json +1 -1
  476. package/dist/schemas/post--vedic-astrology-shadbala.json +1 -1
  477. package/dist/schemas/post--vedic-astrology-transit-monthly.json +1 -1
  478. package/dist/schemas/post--vedic-astrology-transit.json +1 -1
  479. package/dist/schemas/post--vedic-astrology-upagraha.json +1 -1
  480. package/dist/schemas/post--vedic-astrology-yoga-detect.json +1 -1
  481. package/dist/styles/charts/bodygraph.css +1 -0
  482. package/dist/styles/charts/kundli.css +1 -0
  483. package/dist/styles/charts/natal-wheel.css +1 -0
  484. package/dist/styles/charts/synastry-wheel.css +1 -0
  485. package/dist/styles/fonts/fraunces-jost.css +1 -0
  486. package/dist/styles/fonts/geist/OFL.txt +93 -0
  487. package/dist/styles/fonts/geist/geist-cyrillic.woff2 +0 -0
  488. package/dist/styles/fonts/geist/geist-latin-ext.woff2 +0 -0
  489. package/dist/styles/fonts/geist/geist-latin.woff2 +0 -0
  490. package/dist/styles/fonts/geist.css +1 -0
  491. package/dist/styles/fonts/jost.css +1 -0
  492. package/dist/styles/fonts.d.ts +23 -0
  493. package/dist/styles/palette-names.d.ts +3 -0
  494. package/dist/styles/palettes.d.ts +6 -19
  495. package/dist/styles/themes/celeste.css +1 -1
  496. package/dist/styles/themes/eucalyptus.css +1 -1
  497. package/dist/styles/themes/kiln.css +1 -1
  498. package/dist/styles/themes/moonlit.css +1 -1
  499. package/dist/styles/themes/practitioner.css +1 -1
  500. package/dist/styles/tokens-css.d.ts +1 -1
  501. package/dist/styles/tokens.css +1 -1
  502. package/dist/tool-component.cjs +1 -1
  503. package/dist/tool-component.js +1 -1
  504. package/dist/types/index.d.ts +1 -1
  505. package/dist/types/types.gen.d.ts +17614 -15166
  506. package/dist/utils/angel-sections.d.ts +1 -1
  507. package/dist/utils/aspect-line.d.ts +1 -10
  508. package/dist/utils/aspect-styles.d.ts +4 -0
  509. package/dist/utils/base-element.d.ts +15 -2
  510. package/dist/utils/bodygraph-render.d.ts +18 -2
  511. package/dist/utils/bodygraph-styles.d.ts +1 -6
  512. package/dist/utils/brand.d.ts +25 -0
  513. package/dist/utils/chart-styles.d.ts +9 -0
  514. package/dist/utils/chart-viewport.d.ts +1 -1
  515. package/dist/utils/degree.d.ts +7 -0
  516. package/dist/utils/dist-base.d.ts +2 -0
  517. package/dist/utils/fetch-controller.d.ts +9 -2
  518. package/dist/utils/field-schema.d.ts +10 -4
  519. package/dist/utils/frame.d.ts +1 -1
  520. package/dist/utils/hd-reading.d.ts +1 -14
  521. package/dist/utils/interp-accordion.d.ts +1 -1
  522. package/dist/utils/kundli-chrome.d.ts +22 -0
  523. package/dist/utils/kundli-render.d.ts +17 -28
  524. package/dist/utils/natal-wheel.d.ts +32 -0
  525. package/dist/utils/object-url.d.ts +17 -0
  526. package/dist/utils/reference-table.d.ts +7 -0
  527. package/dist/utils/stacked-table.d.ts +1 -1
  528. package/dist/utils/svg-string.d.ts +20 -0
  529. package/dist/utils/synastry-wheel.d.ts +15 -0
  530. package/dist/version.d.ts +1 -1
  531. package/package.json +10 -2
@@ -1 +1 @@
1
- {"title":"Calculate compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","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":"person1.time","name":"time","group":"person1","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":"person1.latitude","name":"latitude","group":"person1","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":"person1.longitude","name":"longitude","group":"person1","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":"person1.timezone","name":"timezone","group":"person1","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":"person2.date","name":"date","group":"person2","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":"person2.time","name":"time","group":"person2","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":"person2.latitude","name":"latitude","group":"person2","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":"person2.longitude","name":"longitude","group":"person2","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":"person2.timezone","name":"timezone","group":"person2","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
1
+ {"title":"Calculate compatibility score","fields":[{"key":"person1.date","name":"date","group":"person1","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":"person1.time","name":"time","group":"person1","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":"person1.latitude","name":"latitude","group":"person1","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":"person1.longitude","name":"longitude","group":"person1","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":"person1.timezone","name":"timezone","group":"person1","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":"person2.date","name":"date","group":"person2","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":"person2.time","name":"time","group":"person2","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":"person2.latitude","name":"latitude","group":"person2","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":"person2.longitude","name":"longitude","group":"person2","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":"person2.timezone","name":"timezone","group":"person2","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"key":"person1","label":"Person 1","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","label":"Person 2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Daily Reading","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Fixes the Janma Rashi and Janma Nakshatra every part of this reading is counted from, and the natal Ashtakavarga the bindu gate reads.","example":"1984-11-03"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). The Moon moves about half a degree an hour, so an error here moves the Janma Rashi and Janma Nakshatra and therefore every gochara house count, the tarabala and the chandrabala in this response.","example":"01:35:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Sets the natal house cusps behind the Ashtakavarga scorecard and the KP significators, and the sunrise that opens the panchanga day.","min":-90,"max":90,"example":28.8944,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local sidereal time for the natal cusps and the sunrise the reading is composed at.","min":-180,"max":180,"example":76.5894,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\") OR decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). IANA strings are resolved twice, each to the DST-correct offset of its own moment: at the birth date and time for the birth chart, and on the date being read for the reading day. 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":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, in YYYY-MM-DD format. Defaults to today (UTC). The panchanga day it names runs from sunrise at the birth coordinates to the next sunrise, not from midnight, so a reading for this date covers the night that follows it.","example":"2026-06-21","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu. \"mean\" uses the smooth mean node, which is the traditional Vedic default and what printed panchangs use. \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean and can therefore move a node into a different rashi and change its gochara house. 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":"Daily Reading","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. Fixes the Janma Rashi and Janma Nakshatra every part of this reading is counted from, and the natal Ashtakavarga the bindu gate reads.","example":"1984-11-03"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time in HH:MM:SS format (24-hour). The Moon moves about half a degree an hour, so an error here moves the Janma Rashi and Janma Nakshatra and therefore every gochara house count, the tarabala and the chandrabala in this response.","example":"01:35:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth location latitude in decimal degrees. Sets the natal house cusps behind the Ashtakavarga scorecard and the KP significators, and the sunrise that opens the panchanga day.","min":-90,"max":90,"example":28.8944,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth location longitude in decimal degrees. Affects local sidereal time for the natal cusps and the sunrise the reading is composed at.","min":-180,"max":180,"example":76.5894,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone: IANA name (e.g. \"Asia/Kolkata\", \"America/New_York\") OR decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). IANA strings are resolved twice, each to the DST-correct offset of its own moment: at the birth date and time for the birth chart, and on the date being read for the reading day. 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":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, in YYYY-MM-DD format. Defaults to today (UTC). The panchanga day it names runs from sunrise at the birth coordinates to the next sunrise, not from midnight, so a reading for this date covers the night that follows it.","example":"2026-06-21","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node type for Rahu and Ketu. \"mean\" uses the smooth mean node, which is the traditional Vedic default and what printed panchangs use. \"true\" uses the osculating node, which swings up to 1.5 degrees either side of mean and can therefore move a node into a different rashi and change its gochara house. 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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana","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":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone, an IANA name resolved at this datetime rather than at the birth (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-08-23T13:47:46Z","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 current Mahadasha, Antardasha, Pratyantardasha, Sookshma, Prana","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":"datetime","name":"datetime","kind":"datetime","required":false,"description":"ISO 8601 datetime (YYYY-MM-DDTHH:MM:SS) to read the running periods at, for a reading prepared for a future day, a backtest, or a chart cast for a past moment. Defaults to the current instant. Interpreted as local time in the request timezone, an IANA name resolved at this datetime rather than at the birth (a trailing Z is accepted but ignored); with timezone 0 it is UTC.","example":"2026-08-23T13:47:46Z","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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get divisional chart (Varga)","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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":"division","name":"division","kind":"number","required":true,"description":"Divisional chart number. Each division reveals a specific life area. Supported: 2 (Hora, wealth), 3 (Drekkana, siblings), 4 (Chaturthamsa, property), 7 (Saptamsa, children), 9 (Navamsa, marriage), 10 (Dasamsa, career), 12 (Dwadasamsa, parents), 16 (Shodasamsa, vehicles), 20 (Vimsamsa, spirituality), 24 (Chaturvimsamsa, education), 27 (Bhamsa, strength), 30 (Trimsamsa, misfortunes), 40 (Khavedamsa, merit), 45 (Akshavedamsa, character), 60 (Shashtiamsa, past life karma).","example":10}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get divisional chart (Varga)","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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":"division","name":"division","kind":"number","required":true,"description":"Divisional chart number. Each division reveals a specific life area. Supported: 2 (Hora, wealth), 3 (Drekkana, siblings), 4 (Chaturthamsa, property), 7 (Saptamsa, children), 9 (Navamsa, marriage), 10 (Dasamsa, career), 12 (Dwadasamsa, parents), 16 (Shodasamsa, vehicles), 20 (Vimsamsa, spirituality), 24 (Chaturvimsamsa, education), 27 (Bhamsa, strength), 30 (Trimsamsa, misfortunes), 40 (Khavedamsa, merit), 45 (Akshavedamsa, character), 60 (Shashtiamsa, past life karma).","example":10}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Check Kalsarpa Dosha","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Check Kalsarpa Dosha","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Check Manglik Dosha","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Check Manglik Dosha","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Check Sadhesati","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Check Sadhesati","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":"Sidereal frame (ayanamsa) the chart is cast in. \"lahiri\" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. \"raman\" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. \"kp-newcomb\" and \"kp-old\" are the two Krishnamurti Paddhati frames. \"custom\" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.","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}],"hasLang":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Ecliptic Crossings","fields":[{"key":"year","name":"year","kind":"number","required":true,"description":"Year to scan for ecliptic crossings (1551 to 2649).","min":1551,"max":2649,"example":2026},{"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. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"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":true,"groups":[{}],"opensOnLoad":false}
1
+ {"title":"Ecliptic Crossings","fields":[{"key":"year","name":"year","kind":"number","required":true,"description":"Year to scan for ecliptic crossings (1551 to 2649).","min":1551,"max":2649,"example":2026},{"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. Output times are converted to this timezone. Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"example":5.5,"city":true,"viewerZone":true,"fold":true},{"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":true,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Heliacal rising and setting (udaya and asta)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Local calendar date to judge, in YYYY-MM-DD format. There is deliberately no time field: heliacal visibility is a once-a-day verdict read at that day sunrise or sunset, so a clock time could only pick a different day.","example":"2026-07-25"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees, restricted to -60 to 60. Visibility depends on the observer, unlike the longitude orb every chart API reports, because the angle the ecliptic makes with the horizon decides how long a graha lingers after the Sun. Beyond this band the classical rule stops describing solar glare and starts describing polar horizon geometry, so it is declined rather than answered wrongly.","min":-60,"max":60,"example":19.076,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Sets local sunrise and sunset, which are the instants the verdict is read at. Example: Mumbai 72.8777, Delhi 77.2090, London -0.1278.","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\", \"Europe/London\") OR decimal hours from UTC. Fixes which local day the date refers to, and every datetime in the response is returned in it. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Heliacal rising and setting (udaya and asta)","fields":[{"key":"date","name":"date","kind":"date","required":true,"description":"Local calendar date to judge, in YYYY-MM-DD format. There is deliberately no time field: heliacal visibility is a once-a-day verdict read at that day sunrise or sunset, so a clock time could only pick a different day.","example":"2026-07-25"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees, restricted to -60 to 60. Visibility depends on the observer, unlike the longitude orb every chart API reports, because the angle the ecliptic makes with the horizon decides how long a graha lingers after the Sun. Beyond this band the classical rule stops describing solar glare and starts describing polar horizon geometry, so it is declined rather than answered wrongly.","min":-60,"max":60,"example":19.076,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees. Sets local sunrise and sunset, which are the instants the verdict is read at. Example: Mumbai 72.8777, Delhi 77.2090, London -0.1278.","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\", \"Europe/London\") OR decimal hours from UTC. Fixes which local day the date refers to, and every datetime in the response is returned in it. Defaults to 5.5.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"}],"hasLang":false,"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. 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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"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
+ {"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. 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
+ {"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,"langs":["en","tr","de","es","hi","pt","fr","ru","zh-Hans","zh-Hant"],"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Get KP planets at time intervals","fields":[{"key":"startDatetime","name":"startDatetime","kind":"datetime","required":true,"description":"Start datetime 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":"2025-01-15T00:00:00Z"},{"key":"endDatetime","name":"endDatetime","kind":"datetime","required":true,"description":"End datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Maximum 7 days from start. 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-15T23:59:00Z"},{"key":"intervalMinutes","name":"intervalMinutes","kind":"number","required":true,"description":"Time between calculations in minutes. Range: 15 (quarter-hourly) to 1440 (daily).","min":15,"max":1440,"example":60},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees (for future Lagna calculations)","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees (for future Lagna calculations)","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"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}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Get KP planets at time intervals","fields":[{"key":"startDatetime","name":"startDatetime","kind":"datetime","required":true,"description":"Start datetime 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":"2025-01-15T00:00:00Z"},{"key":"endDatetime","name":"endDatetime","kind":"datetime","required":true,"description":"End datetime in ISO 8601 (YYYY-MM-DDTHH:MM:SS). Maximum 7 days from start. 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-15T23:59:00Z"},{"key":"intervalMinutes","name":"intervalMinutes","kind":"number","required":true,"description":"Time between calculations in minutes. Range: 15 (quarter-hourly) to 1440 (daily).","min":15,"max":1440,"example":60},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Observer latitude in decimal degrees (for future Lagna calculations)","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Observer longitude in decimal degrees (for future Lagna calculations)","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Defaults to 0 (UTC).","min":-14,"max":14,"default":0,"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}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}}],"opensOnLoad":false}