@roxyapi/ui 0.51.0 → 0.51.1

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 (73) hide show
  1. package/components-catalog.json +153 -153
  2. package/dist/cdn/components/endpoint-form.js +4 -4
  3. package/dist/cdn/components/endpoint-form.js.map +3 -3
  4. package/dist/cdn/roxy-ui.js +74 -74
  5. package/dist/cdn/roxy-ui.js.map +3 -3
  6. package/dist/components/endpoint-form.d.ts +3 -9
  7. package/dist/components/endpoint-form.d.ts.map +1 -1
  8. package/dist/components/endpoint-form.js +1 -1
  9. package/dist/components/endpoint-form.js.map +3 -3
  10. package/dist/forms/labels/de.json +1 -1
  11. package/dist/forms/labels/en.json +1 -1
  12. package/dist/forms/labels/es.json +1 -1
  13. package/dist/forms/labels/fr.json +1 -1
  14. package/dist/forms/labels/hi.json +1 -1
  15. package/dist/forms/labels/pt.json +1 -1
  16. package/dist/forms/labels/ru.json +1 -1
  17. package/dist/forms/labels/tr.json +1 -1
  18. package/dist/forms.json +1 -1
  19. package/dist/index.cjs +57 -57
  20. package/dist/index.cjs.map +3 -3
  21. package/dist/index.js +59 -59
  22. package/dist/index.js.map +3 -3
  23. package/dist/schemas/get--ayurveda-doshas-id.json +1 -1
  24. package/dist/schemas/get--chinese-astrology-zodiac-animals-id.json +1 -1
  25. package/dist/schemas/get--chinese-astrology-zodiac-id-daily.json +1 -1
  26. package/dist/schemas/get--feng-shui-bagua-id.json +1 -1
  27. package/dist/schemas/get--human-design-centers-id.json +1 -1
  28. package/dist/schemas/get--kabbalah-letters-id.json +1 -1
  29. package/dist/schemas/get--kabbalah-sephirot-id.json +1 -1
  30. package/dist/schemas/get--mesoamerican-astrology-aztec-day-signs-id.json +1 -1
  31. package/dist/schemas/get--mesoamerican-astrology-mayan-day-signs-id.json +1 -1
  32. package/dist/schemas/get--mesoamerican-astrology-mayan-haab-months-id.json +1 -1
  33. package/dist/schemas/get--vastu-devatas-id.json +1 -1
  34. package/dist/schemas/get--vastu-directions-id.json +1 -1
  35. package/dist/schemas/get--vedic-astrology-avasthas-id.json +1 -1
  36. package/dist/schemas/get--vedic-astrology-nakshatras-id.json +1 -1
  37. package/dist/schemas/get--vedic-astrology-rashis-id.json +1 -1
  38. package/dist/schemas/get--vedic-astrology-yoga-id.json +1 -1
  39. package/dist/schemas/post--astrology-compatibility-score.json +1 -1
  40. package/dist/schemas/post--astrology-composite-chart.json +1 -1
  41. package/dist/schemas/post--astrology-relocation-chart.json +1 -1
  42. package/dist/schemas/post--astrology-synastry.json +1 -1
  43. package/dist/schemas/post--astrology-transit-aspects.json +1 -1
  44. package/dist/schemas/post--astrology-transits.json +1 -1
  45. package/dist/schemas/post--biorhythm-compatibility.json +1 -1
  46. package/dist/schemas/post--chinese-astrology-bazi-compatibility.json +1 -1
  47. package/dist/schemas/post--forecast-digest.json +1 -1
  48. package/dist/schemas/post--forecast-significant-dates.json +1 -1
  49. package/dist/schemas/post--forecast-timeline.json +1 -1
  50. package/dist/schemas/post--forecast-transits.json +1 -1
  51. package/dist/schemas/post--human-design-connection.json +1 -1
  52. package/dist/schemas/post--human-design-penta.json +1 -1
  53. package/dist/schemas/post--human-design-transit.json +1 -1
  54. package/dist/schemas/post--mesoamerican-astrology-mayan-compatibility.json +1 -1
  55. package/dist/schemas/post--numerology-compatibility.json +1 -1
  56. package/dist/schemas/post--tarot-spreads-custom.json +1 -1
  57. package/dist/schemas/post--vastu-entrance.json +1 -1
  58. package/dist/schemas/post--vastu-mandala.json +1 -1
  59. package/dist/schemas/post--vastu-plot.json +1 -1
  60. package/dist/schemas/post--vastu-rooms.json +1 -1
  61. package/dist/schemas/post--vedic-astrology-compatibility-dashakoot.json +1 -1
  62. package/dist/schemas/post--vedic-astrology-compatibility-papasamyam.json +1 -1
  63. package/dist/schemas/post--vedic-astrology-compatibility.json +1 -1
  64. package/dist/schemas/post--vedic-astrology-kp-daily-finance.json +1 -1
  65. package/dist/styles/themes/practitioner.css +5 -5
  66. package/dist/utils/field-schema.d.ts +18 -0
  67. package/dist/utils/field-schema.d.ts.map +1 -1
  68. package/dist/version.d.ts +1 -1
  69. package/package.json +1 -1
  70. package/src/components/endpoint-form.ts +19 -25
  71. package/src/styles/themes/practitioner.css +5 -5
  72. package/src/utils/field-schema.ts +61 -20
  73. package/src/version.ts +1 -1
@@ -1 +1 @@
1
- {"title":"Calculate Human Design connection chart","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"personA.time","name":"time","group":"personA","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"personA.timezone","name":"timezone","group":"personA","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personA.latitude","name":"latitude","group":"personA","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personA.longitude","name":"longitude","group":"personA","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"personA.nodeType","name":"nodeType","group":"personA","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"personB.time","name":"time","group":"personB","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"personB.timezone","name":"timezone","group":"personB","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personB.latitude","name":"latitude","group":"personB","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personB.longitude","name":"longitude","group":"personB","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"personB.nodeType","name":"nodeType","group":"personB","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true,"groups":[{"key":"personA","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate Human Design connection chart","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"personA.time","name":"time","group":"personA","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"personA.timezone","name":"timezone","group":"personA","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personA.latitude","name":"latitude","group":"personA","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personA.longitude","name":"longitude","group":"personA","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"personA.nodeType","name":"nodeType","group":"personA","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"personB.time","name":"time","group":"personB","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"personB.timezone","name":"timezone","group":"personB","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"personB.latitude","name":"latitude","group":"personB","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"personB.longitude","name":"longitude","group":"personB","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"personB.nodeType","name":"nodeType","group":"personB","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true,"groups":[{"key":"personA","label":"Person A","location":{"fields":["personA.latitude","personA.longitude","personA.timezone"],"required":true}},{"key":"personB","label":"Person B","location":{"fields":["personB.latitude","personB.longitude","personB.timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate Human Design Penta","fields":[{"key":"members.0.date","name":"date","group":"members.0","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"members.0.time","name":"time","group":"members.0","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"members.0.timezone","name":"timezone","group":"members.0","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"members.0.latitude","name":"latitude","group":"members.0","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"members.0.longitude","name":"longitude","group":"members.0","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"members.0.nodeType","name":"nodeType","group":"members.0","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"members.1.date","name":"date","group":"members.1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"members.1.time","name":"time","group":"members.1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"members.1.timezone","name":"timezone","group":"members.1","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"members.1.latitude","name":"latitude","group":"members.1","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"members.1.longitude","name":"longitude","group":"members.1","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"members.1.nodeType","name":"nodeType","group":"members.1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"members.2.date","name":"date","group":"members.2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"members.2.time","name":"time","group":"members.2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"members.2.timezone","name":"timezone","group":"members.2","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"members.2.latitude","name":"latitude","group":"members.2","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"members.2.longitude","name":"longitude","group":"members.2","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"members.2.nodeType","name":"nodeType","group":"members.2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true,"repeats":[{"key":"members","min":3,"max":5}],"groups":[{"key":"members.0","location":{"fields":["members.0.latitude","members.0.longitude","members.0.timezone"],"required":true}},{"key":"members.1","location":{"fields":["members.1.latitude","members.1.longitude","members.1.timezone"],"required":true}},{"key":"members.2","location":{"fields":["members.2.latitude","members.2.longitude","members.2.timezone"],"required":true}}],"opensOnLoad":false}
1
+ {"title":"Calculate Human Design Penta","fields":[{"key":"members.0.date","name":"date","group":"members.0","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"members.0.time","name":"time","group":"members.0","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"members.0.timezone","name":"timezone","group":"members.0","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"members.0.latitude","name":"latitude","group":"members.0","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"members.0.longitude","name":"longitude","group":"members.0","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"members.0.nodeType","name":"nodeType","group":"members.0","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"members.1.date","name":"date","group":"members.1","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"members.1.time","name":"time","group":"members.1","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"members.1.timezone","name":"timezone","group":"members.1","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"members.1.latitude","name":"latitude","group":"members.1","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"members.1.longitude","name":"longitude","group":"members.1","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"members.1.nodeType","name":"nodeType","group":"members.1","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"members.2.date","name":"date","group":"members.2","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"members.2.time","name":"time","group":"members.2","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"members.2.timezone","name":"timezone","group":"members.2","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"members.2.latitude","name":"latitude","group":"members.2","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"members.2.longitude","name":"longitude","group":"members.2","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"members.2.nodeType","name":"nodeType","group":"members.2","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"}],"hasLang":true,"repeats":[{"key":"members","min":3,"max":5}],"groups":[{"key":"members.0","label":"Group members 1","location":{"fields":["members.0.latitude","members.0.longitude","members.0.timezone"],"required":true}},{"key":"members.1","label":"Group members 2","location":{"fields":["members.1.latitude","members.1.longitude","members.1.timezone"],"required":true}},{"key":"members.2","label":"Group members 3","location":{"fields":["members.2.latitude","members.2.longitude","members.2.timezone"],"required":true}}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Generate Human Design transit overlay","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"birthData.nodeType","name":"nodeType","group":"birthData","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.","example":"2026-05-23","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS UTC. Optional. Defaults to the current UTC time when omitted. Precision matters: the Moon moves through a gate in roughly half a day.","example":"12:00:00","fold":true}],"hasLang":true,"groups":[{"key":"birthData","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
1
+ {"title":"Generate Human Design transit overlay","fields":[{"key":"birthData.date","name":"date","group":"birthData","kind":"date","required":true,"description":"Birth date in YYYY-MM-DD format. The anchor for both the Personality activations at birth and the Design activations 88 degrees of solar arc earlier.","example":"1990-07-15"},{"key":"birthData.time","name":"time","group":"birthData","kind":"time","required":true,"description":"Birth time in 24-hour HH:MM:SS format. Precision matters: the profile lines and gate boundaries shift with the exact minute of birth.","example":"13:00:00"},{"key":"birthData.timezone","name":"timezone","group":"birthData","kind":"number","required":true,"description":"IANA name (e.g. \"America/New_York\", \"Europe/London\", \"UTC\"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. \"-05:00\", \"+01:00\"). Prefer the IANA name: it is resolved to the offset in force at the birth date and time, historical daylight-saving rules included, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state at that moment. On a transition day a time in the repeated hour is read as its first occurrence and a time in the skipped hour is moved forward past the gap. Invalid timezones return 400 with a validation error.","min":-14,"max":14,"example":"America/New_York","role":"location"},{"key":"birthData.latitude","name":"latitude","group":"birthData","kind":"number","required":false,"description":"Birth latitude in decimal degrees. Optional and does not affect the bodygraph, which depends only on ecliptic longitudes. Defaults to 0.","min":-90,"max":90,"default":0,"example":0,"role":"location"},{"key":"birthData.longitude","name":"longitude","group":"birthData","kind":"number","required":false,"description":"Birth longitude in decimal degrees. Optional and does not affect the bodygraph. Defaults to 0.","min":-180,"max":180,"default":0,"example":0,"role":"location"},{"key":"birthData.nodeType","name":"nodeType","group":"birthData","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the North and South Node activations. True is what professional Human Design software uses (HumanDesign.ai, Total Human Design) and is the value RoxyAPI verifies against, so leave it unset for a standard chart. It matters only when a node sits on a gate boundary, where the choice moves a node gate. Because a gate can be half of a channel, that can change the completed channels and, with them, whether a center reads defined or open, plus the definition, authority, profile or type. A chart where only one center disagrees is the usual shape, since the type and profile often survive unchanged. If another calculator disagrees on any of those, it is almost certainly using the mean node: pass \"mean\" to match it. Defaults to \"true\".","enum":["mean","true"],"default":"true","example":"true"},{"key":"date","name":"date","kind":"date","required":false,"description":"Transit date in YYYY-MM-DD UTC. Optional. Defaults to today in UTC when omitted, giving the just-now transit.","example":"2026-05-23","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Transit time in HH:MM:SS UTC. Optional. Defaults to the current UTC time when omitted. Precision matters: the Moon moves through a gate in roughly half a day.","example":"12:00:00","fold":true}],"hasLang":true,"groups":[{"key":"birthData","label":"Birth Data","location":{"fields":["birthData.latitude","birthData.longitude","birthData.timezone"],"required":true}},{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Mayan nawal compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true},{"key":"directionScheme","name":"directionScheme","kind":"tiles","required":false,"description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"default":"madrid-codex","example":"madrid-codex","fold":true}],"hasLang":true,"groups":[{"key":"personA"},{"key":"personB"},{}],"opensOnLoad":false}
1
+ {"title":"Mayan nawal compatibility","fields":[{"key":"personA.date","name":"date","group":"personA","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"personB.date","name":"date","group":"personB","kind":"date","required":true,"description":"Date in YYYY-MM-DD format, in the PROLEPTIC GREGORIAN calendar, extended backwards unchanged through the 1582 reform. Years 1 to 4000 are accepted. A reference converter that switches to the Julian calendar below the reform will disagree with a date before 15 October 1582 by ten or eleven days; that is a difference of input convention rather than of arithmetic, and passing the Julian equivalent to such a tool reproduces these values exactly. A single-digit month or day is accepted and zero padded.","example":"2012-12-21"},{"key":"correlation","name":"correlation","kind":"tiles","required":false,"description":"Which correlation constant ties the day count to a civil date. This is the single choice that shifts every value in the response, so it is a parameter rather than a hidden default, and the resolved value comes back under conventions. \"gmt-584283\" is the commonly accepted constant and the default, and it is the one the major institutional converter runs on. \"martinez-hernandez-584281\" sits two days earlier, \"astronomical-584285\" two days later, and \"martin-skidmore-584286\" three days later, each shifting the Long Count by exactly its difference in days. Four of the eight published constants are offered: the other four sit tens of thousands of days away and are of historical interest only. The 584281 constant is the Martínez Hernández correlation, after Juan Martínez Hernández.","enum":["gmt-584283","martinez-hernandez-584281","astronomical-584285","martin-skidmore-584286"],"default":"gmt-584283","example":"gmt-584283","fold":true},{"key":"directionScheme","name":"directionScheme","kind":"tiles","required":false,"description":"Which reading of the world direction and colour to serve for a day sign. The two published assignments differ by exactly one quarter turn on all twenty signs, so neither is a rounding of the other and a silent pick would be a school choice. \"madrid-codex\" is the codex reading and the default; \"landa\" is the sixteenth century assignment recorded beside it.","enum":["madrid-codex","landa"],"default":"madrid-codex","example":"madrid-codex","fold":true}],"hasLang":true,"groups":[{"key":"personA","label":"Person A"},{"key":"personB","label":"Person B"},{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate numerology compatibility","fields":[{"key":"person1.fullName","name":"fullName","group":"person1","kind":"text","required":false,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"John William Smith"},{"key":"person1.year","name":"year","group":"person1","kind":"number","required":false,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1990},{"key":"person1.month","name":"month","group":"person1","kind":"number","required":false,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":7},{"key":"person1.day","name":"day","group":"person1","kind":"number","required":false,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":15},{"key":"person1.lifePath","name":"lifePath","group":"person1","kind":"number","required":false,"description":"Person 1 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":5},{"key":"person1.expression","name":"expression","group":"person1","kind":"number","required":false,"description":"Person 1 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":7},{"key":"person1.soulUrge","name":"soulUrge","group":"person1","kind":"number","required":false,"description":"Person 1 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":6},{"key":"person2.fullName","name":"fullName","group":"person2","kind":"text","required":false,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"Jane Marie Doe"},{"key":"person2.year","name":"year","group":"person2","kind":"number","required":false,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1992},{"key":"person2.month","name":"month","group":"person2","kind":"number","required":false,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":3},{"key":"person2.day","name":"day","group":"person2","kind":"number","required":false,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":22},{"key":"person2.lifePath","name":"lifePath","group":"person2","kind":"number","required":false,"description":"Person 2 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":3},{"key":"person2.expression","name":"expression","group":"person2","kind":"number","required":false,"description":"Person 2 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":9},{"key":"person2.soulUrge","name":"soulUrge","group":"person2","kind":"number","required":false,"description":"Person 2 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":2}],"hasLang":true,"groups":[{"key":"person1"},{"key":"person2"}],"opensOnLoad":false}
1
+ {"title":"Calculate numerology compatibility","fields":[{"key":"person1.fullName","name":"fullName","group":"person1","kind":"text","required":false,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"John William Smith"},{"key":"person1.year","name":"year","group":"person1","kind":"number","required":false,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1990},{"key":"person1.month","name":"month","group":"person1","kind":"number","required":false,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":7},{"key":"person1.day","name":"day","group":"person1","kind":"number","required":false,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":15},{"key":"person1.lifePath","name":"lifePath","group":"person1","kind":"number","required":false,"description":"Person 1 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":5},{"key":"person1.expression","name":"expression","group":"person1","kind":"number","required":false,"description":"Person 1 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":7},{"key":"person1.soulUrge","name":"soulUrge","group":"person1","kind":"number","required":false,"description":"Person 1 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":6},{"key":"person2.fullName","name":"fullName","group":"person2","kind":"text","required":false,"description":"Full birth name to calculate Expression and Soul Urge numbers automatically. Use instead of passing expression and soulUrge directly.","example":"Jane Marie Doe"},{"key":"person2.year","name":"year","group":"person2","kind":"number","required":false,"description":"Birth year to calculate Life Path automatically. Use with month and day instead of passing lifePath directly.","min":100,"max":2100,"example":1992},{"key":"person2.month","name":"month","group":"person2","kind":"number","required":false,"description":"Birth month (1-12). Required with year and day for automatic Life Path calculation.","min":1,"max":12,"example":3},{"key":"person2.day","name":"day","group":"person2","kind":"number","required":false,"description":"Birth day (1-31). Required with year and month for automatic Life Path calculation.","min":1,"max":31,"example":22},{"key":"person2.lifePath","name":"lifePath","group":"person2","kind":"number","required":false,"description":"Person 2 Life Path number (1-9, 11, 22, 33). Optional if year, month, day are provided.","min":1,"max":33,"example":3},{"key":"person2.expression","name":"expression","group":"person2","kind":"number","required":false,"description":"Person 2 Expression number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":9},{"key":"person2.soulUrge","name":"soulUrge","group":"person2","kind":"number","required":false,"description":"Person 2 Soul Urge number (1-9, 11, 22, 33). Optional if fullName is provided.","min":1,"max":33,"example":2}],"hasLang":true,"groups":[{"key":"person1","label":"Person 1"},{"key":"person2","label":"Person 2"}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Custom spread builder","fields":[{"key":"spreadName","name":"spreadName","kind":"text","required":false,"description":"Optional name for your custom tarot spread layout. Used as the spread identifier in the response.","example":"My Custom Spread","fold":true},{"key":"positions.0.name","name":"name","group":"positions.0","kind":"text","required":true,"description":"Name for this position in the spread (e.g. Core Issue, Hidden Factor, Best Action). Defines what aspect of the reading this card represents.","example":"Core Issue"},{"key":"positions.0.interpretation","name":"interpretation","group":"positions.0","kind":"text","required":true,"description":"Description of what this position reveals in the reading. Guides the tarot interpretation for the card drawn in this slot.","example":"What is really going on"},{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the custom tarot reading. Provides context for position-specific interpretations.","example":"How do I move forward with this project?","fold":true},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed with the same positions produces identical card draws for consistent divination.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"repeats":[{"key":"positions","min":1,"max":10}],"groups":[{},{"key":"positions.0"}],"opensOnLoad":false}
1
+ {"title":"Custom spread builder","fields":[{"key":"spreadName","name":"spreadName","kind":"text","required":false,"description":"Optional name for your custom tarot spread layout. Used as the spread identifier in the response.","example":"My Custom Spread","fold":true},{"key":"positions.0.name","name":"name","group":"positions.0","kind":"text","required":true,"description":"Name for this position in the spread (e.g. Core Issue, Hidden Factor, Best Action). Defines what aspect of the reading this card represents.","example":"Core Issue"},{"key":"positions.0.interpretation","name":"interpretation","group":"positions.0","kind":"text","required":true,"description":"Description of what this position reveals in the reading. Guides the tarot interpretation for the card drawn in this slot.","example":"What is really going on"},{"key":"question","name":"question","kind":"text","required":false,"description":"Optional querent question to focus the custom tarot reading. Provides context for position-specific interpretations.","example":"How do I move forward with this project?","fold":true},{"key":"seed","name":"seed","kind":"text","required":false,"description":"Optional seed for reproducible results. Same seed with the same positions produces identical card draws for consistent divination.","example":"reading-2f9c1a","role":"seed"}],"hasLang":true,"repeats":[{"key":"positions","min":1,"max":10}],"groups":[{},{"key":"positions.0","label":"Spread positions 1"}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate entrance pada","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15},{"key":"door.x","name":"x","group":"door","kind":"number","required":false,"description":"Distance east of the plot origin, in the same unit as the plot. The x axis runs east.","example":15},{"key":"door.y","name":"y","group":"door","kind":"number","required":false,"description":"Distance north of the plot origin, in the same unit as the plot. The y axis runs north.","example":0},{"key":"doorPosition","name":"doorPosition","kind":"number","required":false,"description":"Where the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facing, the south-west for a west facing and the north-west for a north facing. The side carries 8 padas, so to aim at pada n of 8 send its midpoint, (n - 0.5) / 8: 0.0625 for the first pada, 0.4375 for the fourth, 0.9375 for the eighth. The response names the pada the fraction resolved to in ordinalOnSide. Requires a cardinal facing, since an intercardinal facing names no single side. Send this or door, never both.","min":0,"max":1,"example":0.4},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"groups":[{"key":"plot"},{},{"key":"door"}],"opensOnLoad":false}
1
+ {"title":"Calculate entrance pada","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15},{"key":"door.x","name":"x","group":"door","kind":"number","required":false,"description":"Distance east of the plot origin, in the same unit as the plot. The x axis runs east.","example":15},{"key":"door.y","name":"y","group":"door","kind":"number","required":false,"description":"Distance north of the plot origin, in the same unit as the plot. The y axis runs north.","example":0},{"key":"doorPosition","name":"doorPosition","kind":"number","required":false,"description":"Where the main door sits along the facing side, as a fraction from 0 to 1 measured from the corner the chapter starts that side at: the north-east for an east facing, the south-east for a south facing, the south-west for a west facing and the north-west for a north facing. The side carries 8 padas, so to aim at pada n of 8 send its midpoint, (n - 0.5) / 8: 0.0625 for the first pada, 0.4375 for the fourth, 0.9375 for the eighth. The response names the pada the fraction resolved to in ordinalOnSide. Requires a cardinal facing, since an intercardinal facing names no single side. Send this or door, never both.","min":0,"max":1,"example":0.4},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"groups":[{"key":"plot","label":"Plot"},{},{"key":"door","label":"Door"}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Generate Vastu Purusha Mandala","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"groups":[{"key":"plot"},{}],"opensOnLoad":false}
1
+ {"title":"Generate Vastu Purusha Mandala","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"grid","name":"grid","kind":"tiles","required":false,"description":"Which division of the ground to read: 81-pada is the Paramasayika of Brihat Samhita 53.42, the grid the chapter numbers and names every devata on, and 64-pada is the Manduka of 53.55, for which the chapter gives structure only and no devata names. Defaults to 81-pada.","enum":["81-pada","64-pada"],"default":"81-pada","example":"81-pada","fold":true}],"hasLang":true,"groups":[{"key":"plot","label":"Plot"},{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Analyse a plot","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15},{"key":"slopeLowDirection","name":"slopeLowDirection","kind":"tiles","required":false,"description":"Which quarter of the plot the ground falls toward, that is where the LOW point is. The chapter states its rules in terms of the side that stands HIGHER, so the opposite of this value is what the verses are read against, and both are returned. Omit it if the ground is level.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast"},{"key":"road","name":"road","kind":"tiles","required":false,"description":"Which side a road runs along. The verdict is convention: the chapter states no rule for the side a road is on, only that an obstruction facing the gate brings misery unless it lies beyond twice the height of the house.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"extensions","name":"extensions","kind":"array","required":false,"description":"Quarters where the plot bulges out beyond a rectangle. Every extension verdict is convention: the chapter states no rule for a named corner and the nearest verses speak of a figure with a limb wanting.","example":["Northeast"]},{"key":"cuts","name":"cuts","kind":"array","required":false,"description":"Quarters where a corner is missing from the rectangle. Every cut verdict is convention, for the same reason as the extensions.","example":["Southwest"]},{"key":"water","name":"water","kind":"tiles","required":false,"description":"Which quarter holds standing water, a well, a tank or a sump. This one IS sourced: 53.119 gives a distinct effect for each of the eight directions and calls only the north and the north-east favourable.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast"},{"key":"slopeSchool","name":"slopeSchool","kind":"tiles","required":false,"description":"Which reading of the ground level to lead with. brihat-samhita applies verses 115 to 117 as written, where a higher north-east is a loss, a higher east or north is permitted when level ground is unavoidable and still carries its stated cost, and a higher south or west carries its cost with no allowance. modern applies the widely taught rule that the north-east must be the lowest point, which agrees with verse 115 and contradicts the verse 116 allowance. Both readings are returned whichever you choose, so the disagreement is visible rather than hidden. Defaults to brihat-samhita.","enum":["brihat-samhita","modern"],"default":"brihat-samhita","example":"brihat-samhita","fold":true}],"hasLang":true,"groups":[{"key":"plot"},{}],"opensOnLoad":false}
1
+ {"title":"Analyse a plot","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet"},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15},{"key":"slopeLowDirection","name":"slopeLowDirection","kind":"tiles","required":false,"description":"Which quarter of the plot the ground falls toward, that is where the LOW point is. The chapter states its rules in terms of the side that stands HIGHER, so the opposite of this value is what the verses are read against, and both are returned. Omit it if the ground is level.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast"},{"key":"road","name":"road","kind":"tiles","required":false,"description":"Which side a road runs along. The verdict is convention: the chapter states no rule for the side a road is on, only that an obstruction facing the gate brings misery unless it lies beyond twice the height of the house.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North"},{"key":"extensions","name":"extensions","kind":"array","required":false,"description":"Quarters where the plot bulges out beyond a rectangle. Every extension verdict is convention: the chapter states no rule for a named corner and the nearest verses speak of a figure with a limb wanting.","example":["Northeast"]},{"key":"cuts","name":"cuts","kind":"array","required":false,"description":"Quarters where a corner is missing from the rectangle. Every cut verdict is convention, for the same reason as the extensions.","example":["Southwest"]},{"key":"water","name":"water","kind":"tiles","required":false,"description":"Which quarter holds standing water, a well, a tank or a sump. This one IS sourced: 53.119 gives a distinct effect for each of the eight directions and calls only the north and the north-east favourable.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Northeast"},{"key":"slopeSchool","name":"slopeSchool","kind":"tiles","required":false,"description":"Which reading of the ground level to lead with. brihat-samhita applies verses 115 to 117 as written, where a higher north-east is a loss, a higher east or north is permitted when level ground is unavoidable and still carries its stated cost, and a higher south or west carries its cost with no allowance. modern applies the widely taught rule that the north-east must be the lowest point, which agrees with verse 115 and contradicts the verse 116 allowance. Both readings are returned whichever you choose, so the disagreement is visible rather than hidden. Defaults to brihat-samhita.","enum":["brihat-samhita","modern"],"default":"brihat-samhita","example":"brihat-samhita","fold":true}],"hasLang":true,"groups":[{"key":"plot","label":"Plot"},{}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Check room placement","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30,"fold":true},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40,"fold":true},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet","fold":true},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","fold":true},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"rooms.0.type","name":"type","group":"rooms.0","kind":"tiles","required":true,"description":"What the room is, one of puja, kitchen, master-bedroom, bedroom, living, dining, study, toilet, store, staircase, water-storage, entrance. Case and punctuation are folded, so Master Bedroom and master_bedroom both resolve. Four of the twelve carry a verse and the rest carry convention, and the response says which.","enum":["puja","kitchen","master-bedroom","bedroom","living","dining","study","toilet","store","staircase","water-storage","entrance"],"example":"kitchen"},{"key":"rooms.0.direction","name":"direction","group":"rooms.0","kind":"tiles","required":false,"description":"Which quarter of the plot the room sits in, if you already know it. Send this or polygon, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast"},{"key":"rooms.0.polygon","name":"polygon","group":"rooms.0","kind":"array","required":false,"description":"The room outline in plot coordinates, 3 to 16 vertices. The quarter is read from the area centroid against thirds of the plot, so an L-shaped room lands where its mass is rather than where its corners are. Send this or direction, never both.","example":[{"x":20,"y":2},{"x":28,"y":2},{"x":28,"y":12},{"x":20,"y":12}]}],"hasLang":true,"repeats":[{"key":"rooms","min":1,"max":24}],"groups":[{"key":"plot","fold":true},{},{"key":"rooms.0"}],"opensOnLoad":false}
1
+ {"title":"Check room placement","fields":[{"key":"plot.width","name":"width","group":"plot","kind":"number","required":false,"description":"East-west extent of a rectangular plot, in the unit given. Send this with depth for a rectangle, or send polygon instead.","min":0,"example":30,"fold":true},{"key":"plot.depth","name":"depth","group":"plot","kind":"number","required":false,"description":"North-south extent of a rectangular plot, in the unit given. Send this with width for a rectangle, or send polygon instead.","min":0,"example":40,"fold":true},{"key":"plot.unit","name":"unit","group":"plot","kind":"tiles","required":false,"description":"Unit the plot dimensions are given in. Every distance the response returns is in this same unit. The mandala projection is scale free, so this affects the areas and the marma size and nothing else.","enum":["feet","metres"],"default":"feet","example":"feet","fold":true},{"key":"facing","name":"facing","kind":"tiles","required":false,"description":"Direction the front of the house looks out toward, one of the eight compass sectors. Case and punctuation are folded, so north-east, northeast and NorthEast all resolve. Send this or facingDegrees, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"North","fold":true},{"key":"facingDegrees","name":"facingDegrees","kind":"number","required":false,"description":"Direction the front of the house looks out toward, as a compass bearing in degrees clockwise from true north, measured looking OUT from the building. The same convention the feng shui facing endpoints use, so a bearing works unchanged across the two domains. Send this or facing, never both.","min":0,"max":360,"example":15,"fold":true},{"key":"rooms.0.type","name":"type","group":"rooms.0","kind":"tiles","required":true,"description":"What the room is, one of puja, kitchen, master-bedroom, bedroom, living, dining, study, toilet, store, staircase, water-storage, entrance. Case and punctuation are folded, so Master Bedroom and master_bedroom both resolve. Four of the twelve carry a verse and the rest carry convention, and the response says which.","enum":["puja","kitchen","master-bedroom","bedroom","living","dining","study","toilet","store","staircase","water-storage","entrance"],"example":"kitchen"},{"key":"rooms.0.direction","name":"direction","group":"rooms.0","kind":"tiles","required":false,"description":"Which quarter of the plot the room sits in, if you already know it. Send this or polygon, never both.","enum":["North","Northeast","East","Southeast","South","Southwest","West","Northwest"],"example":"Southeast"},{"key":"rooms.0.polygon","name":"polygon","group":"rooms.0","kind":"array","required":false,"description":"The room outline in plot coordinates, 3 to 16 vertices. The quarter is read from the area centroid against thirds of the plot, so an L-shaped room lands where its mass is rather than where its corners are. Send this or direction, never both.","example":[{"x":20,"y":2},{"x":28,"y":2},{"x":28,"y":12},{"x":20,"y":12}]}],"hasLang":true,"repeats":[{"key":"rooms","min":1,"max":24}],"groups":[{"key":"plot","label":"Plot","fold":true},{},{"key":"rooms.0","label":"Rooms 1"}],"opensOnLoad":false}
@@ -1 +1 @@
1
- {"title":"Calculate ten porutham match","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","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
1
+ {"title":"Calculate ten porutham match","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 +1 @@
1
- {"title":"Compare malefic affliction","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","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","location":{"fields":["person2.latitude","person2.longitude","person2.timezone"],"required":true}},{}],"opensOnLoad":false}
1
+ {"title":"Compare malefic affliction","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 +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","location":{"fields":["person1.latitude","person1.longitude","person1.timezone"],"required":true}},{"key":"person2","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,"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 finance score from four KP sub lord layers","fields":[{"key":"birthDate","name":"birthDate","kind":"date","required":true,"description":"Birth date, YYYY-MM-DD. Fixes the Placidus cusps, the four tier significators and the Vimshottari balance every layer reads.","example":"1990-06-15"},{"key":"birthTime","name":"birthTime","kind":"time","required":true,"description":"Birth time, HH:MM:SS, 24 hour, local to the birth place. The cusp sub lords move about one sub every four minutes of clock time, so this is the input the whole reading is most sensitive to.","example":"07:30:00"},{"key":"latitude","name":"latitude","kind":"number","required":true,"description":"Birth latitude in decimal degrees. Sets the Placidus cusps; also the place the ruling planets and the Moon windows are read at.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees, east positive.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name (Asia/Kolkata) or decimal hours from UTC. Applies to the birth time, to the reading date and time, and to every local timestamp in the response. IANA names resolve to the offset in force on the date being read.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, YYYY-MM-DD in the request timezone. Defaults to today (UTC). The Moon windows cover this date from midnight to midnight.","example":"2026-09-14","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Reading moment on that date, HH:MM:SS local. The ruling planets and the running sookshma lord are read at this instant. Defaults to 12:00:00; pass a market open or any hour for an intraday read.","example":"12:00:00","fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"gainHouses","name":"gainHouses","kind":"array","required":false,"description":"Houses whose significators count as gain, 1 to 12. Defaults to the convention, 2 and 11. Override it to run your own school: the two lists may not share a house.","default":[2,11],"example":[2,11],"fold":true},{"key":"lossHouses","name":"lossHouses","kind":"array","required":false,"description":"Houses whose significators count as loss, 1 to 12. Defaults to the convention, 6 and 8 and 12. Override it to run your own school: the two lists may not share a house.","default":[6,8,12],"example":[6,8,12],"fold":true},{"key":"weights.cusps","name":"cusps","group":"weights","kind":"number","required":false,"description":"Percent of the final score the cusps layer carries.","min":0,"max":100,"example":30,"fold":true},{"key":"weights.dasha","name":"dasha","group":"weights","kind":"number","required":false,"description":"Percent of the final score the dasha layer carries.","min":0,"max":100,"example":40,"fold":true},{"key":"weights.rulingPlanets","name":"rulingPlanets","group":"weights","kind":"number","required":false,"description":"Percent of the final score the rulingPlanets layer carries.","min":0,"max":100,"example":15,"fold":true},{"key":"weights.moonWindows","name":"moonWindows","group":"weights","kind":"number","required":false,"description":"Percent of the final score the moonWindows layer carries.","min":0,"max":100,"example":15,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}},{"key":"weights","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.","min":-90,"max":90,"example":28.6139,"role":"location"},{"key":"longitude","name":"longitude","kind":"number","required":true,"description":"Birth longitude in decimal degrees, east positive.","min":-180,"max":180,"example":77.209,"role":"location"},{"key":"timezone","name":"timezone","kind":"number","required":false,"description":"Timezone as an IANA name (Asia/Kolkata) or decimal hours from UTC. Applies to the birth time, to the reading date and time, and to every local timestamp in the response. IANA names resolve to the offset in force on the date being read.","min":-14,"max":14,"default":5.5,"example":5.5,"role":"location"},{"key":"date","name":"date","kind":"date","required":false,"description":"Civil date to read, YYYY-MM-DD in the request timezone. Defaults to today (UTC). The Moon windows cover this date from midnight to midnight.","example":"2026-09-14","fold":true},{"key":"time","name":"time","kind":"time","required":false,"description":"Reading moment on that date, HH:MM:SS local. The ruling planets and the running sookshma lord are read at this instant. Defaults to 12:00:00; pass a market open or any hour for an intraday read.","example":"12:00:00","fold":true},{"key":"ayanamsa","name":"ayanamsa","kind":"tiles","required":false,"description":"Ayanamsa system for sidereal conversion. \"kp-newcomb\" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. \"kp-old\" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. \"lahiri\" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. \"raman\" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to \"kp-newcomb\".","enum":["kp-newcomb","kp-old","lahiri","raman"],"default":"kp-newcomb","example":"kp-newcomb","fold":true},{"key":"nodeType","name":"nodeType","kind":"tiles","required":false,"description":"Lunar node convention. \"mean\" is the smoothed average node, which always moves retrograde; \"true\" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees either side of the mean on a 173-day cycle, and can briefly turn direct. Neither is more correct and they almost always fall in the same sign. Applies to the Rahu and Ketu positions. Mean is the traditional Vedic default and what printed panchangs use; the choice can move a KP sub-lord in narrow boundary cases, where a span can be as small as 0.5 degrees. Defaults to \"mean\".","enum":["mean","true"],"default":"mean","example":"mean","fold":true},{"key":"gainHouses","name":"gainHouses","kind":"array","required":false,"description":"Houses whose significators count as gain, 1 to 12. Defaults to the convention, 2 and 11. Override it to run your own school: the two lists may not share a house.","default":[2,11],"example":[2,11],"fold":true},{"key":"lossHouses","name":"lossHouses","kind":"array","required":false,"description":"Houses whose significators count as loss, 1 to 12. Defaults to the convention, 6 and 8 and 12. Override it to run your own school: the two lists may not share a house.","default":[6,8,12],"example":[6,8,12],"fold":true},{"key":"weights.cusps","name":"cusps","group":"weights","kind":"number","required":false,"description":"Percent of the final score the cusps layer carries.","min":0,"max":100,"example":30,"fold":true},{"key":"weights.dasha","name":"dasha","group":"weights","kind":"number","required":false,"description":"Percent of the final score the dasha layer carries.","min":0,"max":100,"example":40,"fold":true},{"key":"weights.rulingPlanets","name":"rulingPlanets","group":"weights","kind":"number","required":false,"description":"Percent of the final score the rulingPlanets layer carries.","min":0,"max":100,"example":15,"fold":true},{"key":"weights.moonWindows","name":"moonWindows","group":"weights","kind":"number","required":false,"description":"Percent of the final score the moonWindows layer carries.","min":0,"max":100,"example":15,"fold":true}],"hasLang":false,"groups":[{"location":{"fields":["latitude","longitude","timezone"],"required":true}},{"key":"weights","label":"Weights","fold":true}],"opensOnLoad":false}
@@ -27,7 +27,7 @@
27
27
  font-style: normal;
28
28
  font-weight: 400 600;
29
29
  font-display: swap;
30
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.0/dist/styles/fonts/fraunces/fraunces-latin.woff2")
30
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.1/dist/styles/fonts/fraunces/fraunces-latin.woff2")
31
31
  format("woff2");
32
32
  unicode-range:
33
33
  U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
@@ -38,7 +38,7 @@
38
38
  font-style: normal;
39
39
  font-weight: 400 600;
40
40
  font-display: swap;
41
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.0/dist/styles/fonts/fraunces/fraunces-latin-ext.woff2")
41
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.1/dist/styles/fonts/fraunces/fraunces-latin-ext.woff2")
42
42
  format("woff2");
43
43
  unicode-range:
44
44
  U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
@@ -49,7 +49,7 @@
49
49
  font-style: normal;
50
50
  font-weight: 400 600;
51
51
  font-display: swap;
52
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.0/dist/styles/fonts/jost/jost-latin.woff2")
52
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.1/dist/styles/fonts/jost/jost-latin.woff2")
53
53
  format("woff2");
54
54
  unicode-range:
55
55
  U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD;
@@ -60,7 +60,7 @@
60
60
  font-style: normal;
61
61
  font-weight: 400 600;
62
62
  font-display: swap;
63
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.0/dist/styles/fonts/jost/jost-latin-ext.woff2")
63
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.1/dist/styles/fonts/jost/jost-latin-ext.woff2")
64
64
  format("woff2");
65
65
  unicode-range:
66
66
  U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF;
@@ -71,7 +71,7 @@
71
71
  font-style: normal;
72
72
  font-weight: 400 600;
73
73
  font-display: swap;
74
- src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.0/dist/styles/fonts/jost/jost-cyrillic.woff2")
74
+ src: url("https://cdn.jsdelivr.net/npm/@roxyapi/ui@0.51.1/dist/styles/fonts/jost/jost-cyrillic.woff2")
75
75
  format("woff2");
76
76
  unicode-range: U+0301, U+0400-045F, U+0490-0491, U+04B0-04B1, U+2116;
77
77
  }
@@ -4,6 +4,7 @@
4
4
  * @remarks
5
5
  * The registry is by SHAPE, never by name: {@link classifyInput} inspects `enum` / `type` / `format` only, so a new API parameter gets a working widget with no code change, and the taxonomy gate fails loudly (via a `null` return) the day a genuinely new shape appears. Name-driven render intent (hidden values, city searches and the Advanced fold) is resolved here too, so browser and server renderers consume the same decisions.
6
6
  */
7
+ import { interpolate } from '../i18n/registry.js';
7
8
  /** A JSON `$ref` node, before resolution against `components.schemas`. */
8
9
  export interface OpenApiSchemaRef {
9
10
  $ref?: string;
@@ -42,6 +43,7 @@ export interface OperationSchema {
42
43
  parameters?: Array<{
43
44
  name: string;
44
45
  in: string;
46
+ description?: string;
45
47
  required?: boolean;
46
48
  schema?: OpenApiSchema;
47
49
  }>;
@@ -70,6 +72,8 @@ export interface FieldDef {
70
72
  key: string;
71
73
  /** Schema property name (the label source), e.g. "date". */
72
74
  name: string;
75
+ /** Contextual English label, overriding the generic name label when it loses the field's meaning. */
76
+ label?: string;
73
77
  /** Parent object key for a nested schema (person1/person2); undefined for a flat field. */
74
78
  group?: string;
75
79
  /** True when the spec declares the field as `in: query`, so it belongs in the query string even on a POST. */
@@ -137,6 +141,8 @@ export interface RepeatDef {
137
141
  /** One field group, in field order. An absent key denotes the flat top level. */
138
142
  export interface FormGroup {
139
143
  key?: string;
144
+ /** English legend for a named group; absent for the unlabelled flat top level. */
145
+ label?: string;
140
146
  fold?: true;
141
147
  /** A coordinate pair's city box, with the exact wire keys it fills (including its claimed timezone). */
142
148
  location?: {
@@ -165,6 +171,18 @@ export declare function parseRepeatGroup(group: string): {
165
171
  key: string;
166
172
  index: number;
167
173
  } | null;
174
+ /**
175
+ * A group legend, shared by the browser and published labels. Named objects use the chrome
176
+ * catalogue (whose lookup folds case); repeating records use the array's field label and the
177
+ * catalogued numbered-group template. The defaults produce the same legend in English.
178
+ *
179
+ * Catalogue lookup folds case: `humanize('natalChart')` produces `Natal Chart` and reuses
180
+ * the existing `Natal chart` heading translation. Do not add a capitalized twin, which
181
+ * would overwrite that heading in every locale. A new group with no catalogue entry
182
+ * falls back to its humanized English name, so a missing translation never leaves a key
183
+ * or an empty legend inside translated location labels.
184
+ */
185
+ export declare function deriveGroupLabel(group: string, t?: typeof interpolate, fieldText?: (name: string) => string): string;
168
186
  /** The fields of one record of a repeating property, from the fields of its first record. Every record is the same template, so the form grows a repeat by re-keying record zero. */
169
187
  export declare function repeatFields(fields: readonly FieldDef[], key: string, index: number): FieldDef[];
170
188
  /**
@@ -1 +1 @@
1
- {"version":3,"file":"field-schema.d.ts","sourceRoot":"","sources":["../../src/utils/field-schema.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAMH,0EAA0E;AAC1E,MAAM,WAAW,gBAAgB;IAChC,IAAI,CAAC,EAAE,MAAM,CAAC;CACd;AAED,+DAA+D;AAC/D,MAAM,WAAW,aAAc,SAAQ,gBAAgB;IACtD,gKAAgK;IAChK,IAAI,CAAC,EAAE,MAAM,GAAG,MAAM,EAAE,CAAC;IACzB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,IAAI,CAAC,EAAE,MAAM,EAAE,CAAC;IAChB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,UAAU,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,CAAC;IAC3C,QAAQ,CAAC,EAAE,MAAM,EAAE,CAAC;IACpB,KAAK,CAAC,EAAE,aAAa,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,KAAK,CAAC,EAAE,aAAa,EAAE,CAAC;IACxB,KAAK,CAAC,EAAE,aAAa,EAAE,CAAC;CACxB;AAED,8EAA8E;AAC9E,MAAM,WAAW,eAAe;IAC/B,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,WAAW,CAAC,EAAE;QACb,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE;YAAE,MAAM,CAAC,EAAE,aAAa,GAAG,gBAAgB,CAAA;SAAE,CAAC,CAAC;KACxE,CAAC;IACF,UAAU,CAAC,EAAE,KAAK,CAAC;QAClB,IAAI,EAAE,MAAM,CAAC;QACb,EAAE,EAAE,MAAM,CAAC;QACX,QAAQ,CAAC,EAAE,OAAO,CAAC;QACnB,MAAM,CAAC,EAAE,aAAa,CAAC;KACvB,CAAC,CAAC;CACH;AAED,iEAAiE;AACjE,MAAM,WAAW,UAAU;IAC1B,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,CAAC;IAChD,UAAU,CAAC,EAAE;QAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,CAAA;KAAE,CAAC;CACzD;AAED,0RAA0R;AAC1R,MAAM,WAAW,OAAO;IACvB,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC,CAAC;IACvD,UAAU,CAAC,EAAE;QAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,CAAA;KAAE,CAAC;CACzD;AAED;;GAEG;AACH,MAAM,MAAM,SAAS,GAClB,OAAO,GACP,QAAQ,GACR,QAAQ,GACR,MAAM,GACN,MAAM,GACN,UAAU,GACV,QAAQ,GACR,MAAM,GACN,OAAO,CAAC;AAEX,uFAAuF;AACvF,MAAM,WAAW,QAAQ;IACxB,gGAAgG;IAChG,GAAG,EAAE,MAAM,CAAC;IACZ,4DAA4D;IAC5D,IAAI,EAAE,MAAM,CAAC;IACb,2FAA2F;IAC3F,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,8GAA8G;IAC9G,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,gCAAgC;IAChC,IAAI,EAAE,SAAS,CAAC;IAChB,QAAQ,EAAE,OAAO,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,IAAI,CAAC,EAAE,MAAM,EAAE,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,gEAAgE;IAChE,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,8GAA8G;IAC9G,MAAM,CAAC,EAAE,YAAY,CAAC;IACtB,6FAA6F;IAC7F,IAAI,CAAC,EAAE,MAAM,GAAG,gBAAgB,GAAG,UAAU,CAAC;IAC9C,4FAA4F;IAC5F,IAAI,CAAC,EAAE,IAAI,CAAC;IACZ,wEAAwE;IACxE,IAAI,CAAC,EAAE,IAAI,CAAC;IACZ,uFAAuF;IACvF,YAAY,CAAC,EAAE,cAAc,CAAC;CAC9B;AAED,0GAA0G;AAC1G,MAAM,WAAW,cAAc;IAC9B,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;CACd;AAED;;;;;GAKG;AACH,MAAM,WAAW,YAAY;IAC5B,6CAA6C;IAC7C,IAAI,EAAE,MAAM,CAAC;IACb,sJAAsJ;IACtJ,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,sGAAsG;IACtG,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,yFAAyF;IACzF,IAAI,CAAC,EAAE,IAAI,CAAC;CACZ;AAED,0GAA0G;AAC1G,MAAM,WAAW,WAAW;IAC3B,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;IACd,QAAQ,CAAC,EAAE,OAAO,CAAC;CACnB;AAED;;;;;GAKG;AACH,MAAM,WAAW,SAAS;IACzB,2DAA2D;IAC3D,GAAG,EAAE,MAAM,CAAC;IACZ,GAAG,EAAE,MAAM,CAAC;IACZ,GAAG,EAAE,MAAM,CAAC;CACZ;AAED,iFAAiF;AACjF,MAAM,WAAW,SAAS;IACzB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,IAAI,CAAC,EAAE,IAAI,CAAC;IACZ,wGAAwG;IACxG,QAAQ,CAAC,EAAE;QAAE,MAAM,EAAE,MAAM,EAAE,CAAC;QAAC,QAAQ,EAAE,OAAO,CAAA;KAAE,CAAC;CACnD;AAED,uFAAuF;AACvF,MAAM,WAAW,SAAS;IACzB,oFAAoF;IACpF,KAAK,EAAE,MAAM,CAAC;IACd,0LAA0L;IAC1L,MAAM,EAAE,QAAQ,EAAE,CAAC;IACnB,gJAAgJ;IAChJ,OAAO,EAAE,OAAO,CAAC;IACjB,+FAA+F;IAC/F,MAAM,CAAC,EAAE,SAAS,EAAE,CAAC;IACrB,kEAAkE;IAClE,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,iIAAiI;IACjI,OAAO,CAAC,EAAE,SAAS,EAAE,CAAC;CACtB;AAED,sFAAsF;AACtF,eAAO,MAAM,WAAW,GAAI,KAAK,MAAM,EAAE,OAAO,MAAM,KAAG,MACvC,CAAC;AACnB,wBAAgB,gBAAgB,CAC/B,KAAK,EAAE,MAAM,GACX;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,GAAG,IAAI,CAGvC;AAED,qLAAqL;AACrL,wBAAgB,YAAY,CAC3B,MAAM,EAAE,SAAS,QAAQ,EAAE,EAC3B,GAAG,EAAE,MAAM,EACX,KAAK,EAAE,MAAM,GACX,QAAQ,EAAE,CASZ;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,GAAG,QAAQ,CAExE;AAED,+FAA+F;AAC/F,wBAAgB,OAAO,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,CAE1D;AAED,2IAA2I;AAC3I,eAAO,MAAM,aAAa,gDAAiD,CAAC;AAE5E;;;;;;;;;;GAUG;AACH,eAAO,MAAM,aAAa,oCAAqC,CAAC;AAiChE,qGAAqG;AACrG,wBAAgB,aAAa,CAC5B,MAAM,EAAE,aAAa,GAAG,gBAAgB,GAAG,SAAS,EACpD,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,GAChC,aAAa,GAAG,SAAS,CAO3B;AAgBD;;GAEG;AACH;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,CAAC,EAAE,aAAa,GAAG,MAAM,GAAG,SAAS,CAK/D;AAED,wBAAgB,aAAa,CAAC,MAAM,EAAE,aAAa,GAAG,SAAS,GAAG,IAAI,CAYrE;AAED,6HAA6H;AAC7H,wBAAgB,YAAY,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,CAI/D;AA0BD;;GAEG;AACH,wBAAgB,cAAc,CAC7B,EAAE,EAAE,eAAe,EACnB,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,EACtC,QAAQ,EAAE,MAAM,EAChB,MAAM,GAAE,MAAwC,GAC9C,SAAS,CAyGX;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,gBAAgB,CAC/B,KAAK,EAAE,SAAS,EAChB,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,MAAM,GACd,SAAS,CA0EX;AAED;;GAEG;AACH,wBAAgB,WAAW,CAC1B,OAAO,EAAE,MAAM,GAAG,SAAS,EAC3B,QAAQ,EAAE,MAAM,GACd,MAAM,CAIR;AAED;;;;;GAKG;AACH,wBAAgB,WAAW,CAAC,KAAK,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAIrE;AAED;;;;;;GAMG;AACH,wBAAgB,iBAAiB,CAChC,QAAQ,EAAE,MAAM,EAChB,MAAM,GAAE,SAAS,QAAQ,EAAO,GAC9B,MAAM,CAUR;AAED,wIAAwI;AACxI,wBAAgB,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CAMtE;AAkBD;;;;;;;GAOG;AACH,wBAAgB,WAAW,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,SAAO,GAAG,WAAW,EAAE,CA4BtE;AAED,+EAA+E;AAC/E,wBAAgB,OAAO,CAAC,IAAI,EAAE,OAAO,GAAG,MAAM,GAAG,SAAS,CAGzD;AAED;;;;;GAKG;AACH,wBAAgB,YAAY,CAC3B,IAAI,EAAE,OAAO,EACb,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,EAAE,OAAO,CAAC;IAAC,MAAM,CAAC,EAAE,aAAa,CAAA;CAAE,GACjE,YAAY,GAAG,SAAS,CAQ1B;AAED,gKAAgK;AAChK,wBAAgB,gBAAgB,CAC/B,IAAI,EAAE,OAAO,EACb,IAAI,EAAE,MAAM,GACV,YAAY,GAAG,SAAS,CAa1B"}
1
+ {"version":3,"file":"field-schema.d.ts","sourceRoot":"","sources":["../../src/utils/field-schema.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAIH,OAAO,EAAE,WAAW,EAAE,MAAM,qBAAqB,CAAC;AAIlD,0EAA0E;AAC1E,MAAM,WAAW,gBAAgB;IAChC,IAAI,CAAC,EAAE,MAAM,CAAC;CACd;AAED,+DAA+D;AAC/D,MAAM,WAAW,aAAc,SAAQ,gBAAgB;IACtD,gKAAgK;IAChK,IAAI,CAAC,EAAE,MAAM,GAAG,MAAM,EAAE,CAAC;IACzB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,IAAI,CAAC,EAAE,MAAM,EAAE,CAAC;IAChB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,gBAAgB,CAAC,EAAE,MAAM,CAAC;IAC1B,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,UAAU,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,CAAC;IAC3C,QAAQ,CAAC,EAAE,MAAM,EAAE,CAAC;IACpB,KAAK,CAAC,EAAE,aAAa,CAAC;IACtB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,KAAK,CAAC,EAAE,aAAa,EAAE,CAAC;IACxB,KAAK,CAAC,EAAE,aAAa,EAAE,CAAC;CACxB;AAED,8EAA8E;AAC9E,MAAM,WAAW,eAAe;IAC/B,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,WAAW,CAAC,EAAE;QACb,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE;YAAE,MAAM,CAAC,EAAE,aAAa,GAAG,gBAAgB,CAAA;SAAE,CAAC,CAAC;KACxE,CAAC;IACF,UAAU,CAAC,EAAE,KAAK,CAAC;QAClB,IAAI,EAAE,MAAM,CAAC;QACb,EAAE,EAAE,MAAM,CAAC;QACX,WAAW,CAAC,EAAE,MAAM,CAAC;QACrB,QAAQ,CAAC,EAAE,OAAO,CAAC;QACnB,MAAM,CAAC,EAAE,aAAa,CAAC;KACvB,CAAC,CAAC;CACH;AAED,iEAAiE;AACjE,MAAM,WAAW,UAAU;IAC1B,KAAK,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,CAAC,CAAC;IAChD,UAAU,CAAC,EAAE;QAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,CAAA;KAAE,CAAC;CACzD;AAED,0RAA0R;AAC1R,MAAM,WAAW,OAAO;IACvB,KAAK,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,MAAM,EAAE,eAAe,CAAC,CAAC,CAAC;IACvD,UAAU,CAAC,EAAE;QAAE,OAAO,CAAC,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,CAAA;KAAE,CAAC;CACzD;AAED;;GAEG;AACH,MAAM,MAAM,SAAS,GAClB,OAAO,GACP,QAAQ,GACR,QAAQ,GACR,MAAM,GACN,MAAM,GACN,UAAU,GACV,QAAQ,GACR,MAAM,GACN,OAAO,CAAC;AAEX,uFAAuF;AACvF,MAAM,WAAW,QAAQ;IACxB,gGAAgG;IAChG,GAAG,EAAE,MAAM,CAAC;IACZ,4DAA4D;IAC5D,IAAI,EAAE,MAAM,CAAC;IACb,qGAAqG;IACrG,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,2FAA2F;IAC3F,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,8GAA8G;IAC9G,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,gCAAgC;IAChC,IAAI,EAAE,SAAS,CAAC;IAChB,QAAQ,EAAE,OAAO,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,IAAI,CAAC,EAAE,MAAM,EAAE,CAAC;IAChB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,gEAAgE;IAChE,OAAO,CAAC,EAAE,OAAO,CAAC;IAClB,8GAA8G;IAC9G,MAAM,CAAC,EAAE,YAAY,CAAC;IACtB,6FAA6F;IAC7F,IAAI,CAAC,EAAE,MAAM,GAAG,gBAAgB,GAAG,UAAU,CAAC;IAC9C,4FAA4F;IAC5F,IAAI,CAAC,EAAE,IAAI,CAAC;IACZ,wEAAwE;IACxE,IAAI,CAAC,EAAE,IAAI,CAAC;IACZ,uFAAuF;IACvF,YAAY,CAAC,EAAE,cAAc,CAAC;CAC9B;AAED,0GAA0G;AAC1G,MAAM,WAAW,cAAc;IAC9B,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;CACd;AAED;;;;;GAKG;AACH,MAAM,WAAW,YAAY;IAC5B,6CAA6C;IAC7C,IAAI,EAAE,MAAM,CAAC;IACb,sJAAsJ;IACtJ,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,sGAAsG;IACtG,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,yFAAyF;IACzF,IAAI,CAAC,EAAE,IAAI,CAAC;CACZ;AAED,0GAA0G;AAC1G,MAAM,WAAW,WAAW;IAC3B,KAAK,EAAE,MAAM,CAAC;IACd,KAAK,EAAE,MAAM,CAAC;IACd,QAAQ,CAAC,EAAE,OAAO,CAAC;CACnB;AAED;;;;;GAKG;AACH,MAAM,WAAW,SAAS;IACzB,2DAA2D;IAC3D,GAAG,EAAE,MAAM,CAAC;IACZ,GAAG,EAAE,MAAM,CAAC;IACZ,GAAG,EAAE,MAAM,CAAC;CACZ;AAED,iFAAiF;AACjF,MAAM,WAAW,SAAS;IACzB,GAAG,CAAC,EAAE,MAAM,CAAC;IACb,kFAAkF;IAClF,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,IAAI,CAAC,EAAE,IAAI,CAAC;IACZ,wGAAwG;IACxG,QAAQ,CAAC,EAAE;QAAE,MAAM,EAAE,MAAM,EAAE,CAAC;QAAC,QAAQ,EAAE,OAAO,CAAA;KAAE,CAAC;CACnD;AAED,uFAAuF;AACvF,MAAM,WAAW,SAAS;IACzB,oFAAoF;IACpF,KAAK,EAAE,MAAM,CAAC;IACd,0LAA0L;IAC1L,MAAM,EAAE,QAAQ,EAAE,CAAC;IACnB,gJAAgJ;IAChJ,OAAO,EAAE,OAAO,CAAC;IACjB,+FAA+F;IAC/F,MAAM,CAAC,EAAE,SAAS,EAAE,CAAC;IACrB,kEAAkE;IAClE,WAAW,CAAC,EAAE,OAAO,CAAC;IACtB,iIAAiI;IACjI,OAAO,CAAC,EAAE,SAAS,EAAE,CAAC;CACtB;AAED,sFAAsF;AACtF,eAAO,MAAM,WAAW,GAAI,KAAK,MAAM,EAAE,OAAO,MAAM,KAAG,MACvC,CAAC;AACnB,wBAAgB,gBAAgB,CAC/B,KAAK,EAAE,MAAM,GACX;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,GAAG,IAAI,CAGvC;AAED;;;;;;;;;;GAUG;AACH,wBAAgB,gBAAgB,CAC/B,KAAK,EAAE,MAAM,EACb,CAAC,GAAE,OAAO,WAAyB,EACnC,SAAS,GAAE,CAAC,IAAI,EAAE,MAAM,KAAK,MACW,GACtC,MAAM,CAQR;AAED,qLAAqL;AACrL,wBAAgB,YAAY,CAC3B,MAAM,EAAE,SAAS,QAAQ,EAAE,EAC3B,GAAG,EAAE,MAAM,EACX,KAAK,EAAE,MAAM,GACX,QAAQ,EAAE,CASZ;AAED;;GAEG;AACH,wBAAgB,UAAU,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,GAAG,QAAQ,CAExE;AAED,+FAA+F;AAC/F,wBAAgB,OAAO,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,CAE1D;AAED,2IAA2I;AAC3I,eAAO,MAAM,aAAa,gDAAiD,CAAC;AAE5E;;;;;;;;;;GAUG;AACH,eAAO,MAAM,aAAa,oCAAqC,CAAC;AAiChE,qGAAqG;AACrG,wBAAgB,aAAa,CAC5B,MAAM,EAAE,aAAa,GAAG,gBAAgB,GAAG,SAAS,EACpD,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,GAChC,aAAa,GAAG,SAAS,CAO3B;AAgBD;;GAEG;AACH;;;;;GAKG;AACH,wBAAgB,UAAU,CAAC,CAAC,EAAE,aAAa,GAAG,MAAM,GAAG,SAAS,CAK/D;AAED,wBAAgB,aAAa,CAAC,MAAM,EAAE,aAAa,GAAG,SAAS,GAAG,IAAI,CAYrE;AAED,6HAA6H;AAC7H,wBAAgB,YAAY,CAAC,MAAM,EAAE,SAAS,MAAM,EAAE,GAAG,OAAO,CAI/D;AA0BD;;GAEG;AACH,wBAAgB,cAAc,CAC7B,EAAE,EAAE,eAAe,EACnB,OAAO,EAAE,MAAM,CAAC,MAAM,EAAE,aAAa,CAAC,EACtC,QAAQ,EAAE,MAAM,EAChB,MAAM,GAAE,MAAwC,GAC9C,SAAS,CAiHX;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,gBAAgB,CAC/B,KAAK,EAAE,SAAS,EAChB,MAAM,EAAE,MAAM,EACd,QAAQ,EAAE,MAAM,GACd,SAAS,CA0EX;AAED;;GAEG;AACH,wBAAgB,WAAW,CAC1B,OAAO,EAAE,MAAM,GAAG,SAAS,EAC3B,QAAQ,EAAE,MAAM,GACd,MAAM,CAIR;AAED;;;;;GAKG;AACH,wBAAgB,WAAW,CAAC,KAAK,EAAE,SAAS,EAAE,MAAM,EAAE,MAAM,GAAG,OAAO,CAIrE;AAED;;;;;;GAMG;AACH,wBAAgB,iBAAiB,CAChC,QAAQ,EAAE,MAAM,EAChB,MAAM,GAAE,SAAS,QAAQ,EAAO,GAC9B,MAAM,CAUR;AAED,wIAAwI;AACxI,wBAAgB,aAAa,CAAC,MAAM,EAAE,MAAM,EAAE,QAAQ,EAAE,MAAM,GAAG,MAAM,CAMtE;AAkBD;;;;;;;GAOG;AACH,wBAAgB,WAAW,CAAC,IAAI,EAAE,OAAO,EAAE,KAAK,SAAO,GAAG,WAAW,EAAE,CA4BtE;AAED,+EAA+E;AAC/E,wBAAgB,OAAO,CAAC,IAAI,EAAE,OAAO,GAAG,MAAM,GAAG,SAAS,CAGzD;AAED;;;;;GAKG;AACH,wBAAgB,YAAY,CAC3B,IAAI,EAAE,OAAO,EACb,IAAI,EAAE,MAAM,EACZ,KAAK,EAAE;IAAE,IAAI,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,EAAE,OAAO,CAAC;IAAC,MAAM,CAAC,EAAE,aAAa,CAAA;CAAE,GACjE,YAAY,GAAG,SAAS,CAQ1B;AAED,gKAAgK;AAChK,wBAAgB,gBAAgB,CAC/B,IAAI,EAAE,OAAO,EACb,IAAI,EAAE,MAAM,GACV,YAAY,GAAG,SAAS,CAa1B"}
package/dist/version.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const ROXY_UI_VERSION = "0.51.0";
1
+ export declare const ROXY_UI_VERSION = "0.51.1";
2
2
  //# sourceMappingURL=version.d.ts.map
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@roxyapi/ui",
3
- "version": "0.51.0",
3
+ "version": "0.51.1",
4
4
  "description": "Web components for the RoxyAPI catalog. Drop-in charts, tables, cards, forms for astrology, tarot, numerology, biorhythm, I Ching, crystals, dreams, angel numbers, and more. One key, beautiful in 30 minutes.",
5
5
  "type": "module",
6
6
  "main": "./dist/index.cjs",