@roxyapi/ui-react 1.6.2 → 1.7.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (84) hide show
  1. package/dist/components/almanac-day.js +1 -1
  2. package/dist/components/angel-number-card.js +1 -1
  3. package/dist/components/angel-number-lookup.js +1 -1
  4. package/dist/components/arudha-padas.js +1 -1
  5. package/dist/components/ashtakavarga-grid.js +1 -1
  6. package/dist/components/aspects-table.js +1 -1
  7. package/dist/components/astrocartography-map.js +1 -1
  8. package/dist/components/bazi-chart.js +1 -1
  9. package/dist/components/bhav-chalit-table.js +1 -1
  10. package/dist/components/bhava-bala-table.js +1 -1
  11. package/dist/components/biorhythm-chart.js +1 -1
  12. package/dist/components/bodygraph.js +1 -1
  13. package/dist/components/chara-karakas.js +1 -1
  14. package/dist/components/choghadiya-grid.js +1 -1
  15. package/dist/components/compatibility-card.js +1 -1
  16. package/dist/components/compound-number.js +1 -1
  17. package/dist/components/crystal-card.js +1 -1
  18. package/dist/components/crystal-grid.js +1 -1
  19. package/dist/components/dasha-timeline.js +1 -1
  20. package/dist/components/data.js +1 -1
  21. package/dist/components/divisional-chart.js +1 -1
  22. package/dist/components/dosha-card.js +1 -1
  23. package/dist/components/dosha-constitution.js +1 -1
  24. package/dist/components/dream-card.js +1 -1
  25. package/dist/components/dream-search.js +1 -1
  26. package/dist/components/endpoint-form.js +1 -1
  27. package/dist/components/ephemeris-table.js +1 -1
  28. package/dist/components/fixed-stars.js +1 -1
  29. package/dist/components/flying-star-chart.js +1 -1
  30. package/dist/components/forecast-digest.js +1 -1
  31. package/dist/components/forecast-timeline.js +1 -1
  32. package/dist/components/gematria.js +1 -1
  33. package/dist/components/gochara-table.js +1 -1
  34. package/dist/components/guna-milan.js +1 -1
  35. package/dist/components/hd-connection.js +1 -1
  36. package/dist/components/hd-penta.js +1 -1
  37. package/dist/components/hd-type-card.js +1 -1
  38. package/dist/components/hd-variables.js +1 -1
  39. package/dist/components/heliacal-table.js +1 -1
  40. package/dist/components/hexagram.js +1 -1
  41. package/dist/components/hora-table.js +1 -1
  42. package/dist/components/horoscope-card.d.ts +5 -0
  43. package/dist/components/horoscope-card.js +1 -1
  44. package/dist/components/kp-chart.js +1 -1
  45. package/dist/components/kp-finance-card.js +1 -1
  46. package/dist/components/kp-planets-table.js +1 -1
  47. package/dist/components/kp-ruling-planets.js +1 -1
  48. package/dist/components/kua-card.js +1 -1
  49. package/dist/components/local-space-compass.js +1 -1
  50. package/dist/components/location-search.js +1 -1
  51. package/dist/components/luck-pillars.js +1 -1
  52. package/dist/components/mayan-day-sign.js +1 -1
  53. package/dist/components/moon-phase.js +1 -1
  54. package/dist/components/nakshatra-card.js +1 -1
  55. package/dist/components/natal-chart.js +1 -1
  56. package/dist/components/numerology-card.js +1 -1
  57. package/dist/components/panchang-table.js +1 -1
  58. package/dist/components/positions-table.js +1 -1
  59. package/dist/components/profection-card.js +1 -1
  60. package/dist/components/reference-card.js +1 -1
  61. package/dist/components/relocation-wheel.js +1 -1
  62. package/dist/components/report.js +1 -1
  63. package/dist/components/shadbala-table.js +1 -1
  64. package/dist/components/synastry-chart.js +1 -1
  65. package/dist/components/tarot-card.js +1 -1
  66. package/dist/components/tarot-catalog.js +1 -1
  67. package/dist/components/tarot-spread.js +1 -1
  68. package/dist/components/transit-wheel.js +1 -1
  69. package/dist/components/transits-table.js +1 -1
  70. package/dist/components/upagraha-table.js +1 -1
  71. package/dist/components/vastu-mandala.js +1 -1
  72. package/dist/components/vedic-aspects.js +1 -1
  73. package/dist/components/vedic-daily.js +1 -1
  74. package/dist/components/vedic-kundli.js +1 -1
  75. package/dist/components/vedic-planets-table.js +1 -1
  76. package/dist/components/western-planets-table.js +1 -1
  77. package/dist/components/yoga-list.js +1 -1
  78. package/dist/components/zodiac-card.js +1 -1
  79. package/dist/index.cjs +1 -1
  80. package/dist/index.js +1 -1
  81. package/dist/load-ui.d.ts +1 -1
  82. package/dist/load-ui.js +1 -1
  83. package/dist/types/types.gen.d.ts +344 -51
  84. package/package.json +1 -1
@@ -15519,7 +15519,7 @@ export type GetDailyHoroscopeData = {
15519
15519
  */
15520
15520
  date?: string;
15521
15521
  /**
15522
- * Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each day. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
15522
+ * The clock the day is read on: it decides which events fall on the date, so a transit the evening before in the timezone of the end user is never called today, and which date is current when date is omitted. Defaults to UTC. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
15523
15523
  */
15524
15524
  timezone?: string;
15525
15525
  };
@@ -15661,33 +15661,37 @@ export type GetDailyHoroscopeResponses = {
15661
15661
  */
15662
15662
  date: string;
15663
15663
  /**
15664
- * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 30 to 60 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
15664
+ * The event of the day that most reaches home, roots and the self, or on a quiet day a standing planet, written as the five topic fields are and opening on the lead of column whenever focus is overview. Typically 80 to 120 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
15665
15665
  */
15666
15666
  overview: string;
15667
15667
  /**
15668
- * Love and relationship forecast, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
15668
+ * Love and relationship forecast, read into the whole-sign houses of this sign. It opens on the event of the day that most reaches romance and partnership, or on a quiet day a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries romance and partnership; the aggregate event house remains the leading body house. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15669
15669
  */
15670
15670
  love: string;
15671
15671
  /**
15672
- * Career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
15672
+ * Career and professional outlook, read into the whole-sign houses of this sign. It opens on the event of the day that most reaches career, work and reputation, or on a quiet day a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries career, work and reputation; the aggregate event house remains the leading body house. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15673
15673
  */
15674
15674
  career: string;
15675
15675
  /**
15676
- * Health, energy, and wellness guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
15676
+ * Health, energy, and wellness guidance, read into the whole-sign houses of this sign. It opens on the event of the day that most reaches health, or on a quiet day a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries health; the aggregate event house remains the leading body house. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15677
15677
  */
15678
15678
  health: string;
15679
15679
  /**
15680
- * Financial outlook and money-related guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 50 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
15680
+ * Financial outlook and money-related guidance, read into the whole-sign houses of this sign. It opens on the event of the day that most reaches finance, or on a quiet day a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries finance; the aggregate event house remains the leading body house. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15681
15681
  */
15682
15682
  finance: string;
15683
15683
  /**
15684
- * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
15684
+ * The single actionable takeaway of the period. It opens on the event of the day that most reaches travel, belief, conversation and daily learning, or on a quiet day a standing planet, naming the bodies, the aspect and the life area, then a situation with a way through it, a conditional with a few options, and a close, in the shape of the five fields beside it. Deterministic: the same sign and period always returns the same text.
15685
15685
  */
15686
15686
  advice: string;
15687
15687
  /**
15688
- * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 120 to 180 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
15688
+ * The full column for this period, ready to run as one piece, its paragraphs, where it has more than one, separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 80 to 120 words. The six section fields each open on an event or standing planet of their own read through their life area, the one named in focus on the lead of this column, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
15689
15689
  */
15690
15690
  column: string;
15691
+ /**
15692
+ * The topic this reading is mainly about: love, career, finance or health when the lead event falls in that life area, overview for a bigger-picture period. A machine value, canonical English in every language, so a client can route its own content on it (a related article, a product, a call to action) without parsing the prose; the topic field it names reads the same lead the column opens on.
15693
+ */
15694
+ focus: 'love' | 'career' | 'finance' | 'health' | 'overview';
15691
15695
  /**
15692
15696
  * The dated astronomical events this reading is built on, earliest first. Every field in every row can be checked against an independent authority, so a column can be fact-checked before it is published. Empty on a period in which nothing exact happens, where the reading falls back to the standing positions instead.
15693
15697
  */
@@ -15697,17 +15701,46 @@ export type GetDailyHoroscopeResponses = {
15697
15701
  */
15698
15702
  type: 'aspect' | 'sign-ingress' | 'retrograde-station' | 'lunar-phase' | 'eclipse' | 'solar-season';
15699
15703
  /**
15700
- * Exact instant the event perfects, UTC, to the second. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
15704
+ * Exact instant the event perfects, ISO 8601 to the second, on the clock the reading is read on: UTC with Z by default, the offset of timezone when one is passed on a daily, weekly or monthly reading (2026-11-13T19:27:27-05:00 in New York), the same instant either way; a yearly reading is written in UTC. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
15701
15705
  */
15702
15706
  at: string;
15703
15707
  /**
15704
15708
  * Bodies involved, canonical English regardless of the requested language so the value stays safe to switch on. Two entries for an aspect, faster body first. One entry for an ingress, a station, a lunar phase, or an eclipse.
15705
15709
  */
15706
15710
  bodies: Array<string>;
15711
+ /**
15712
+ * Each participant at the enclosing event timestamp, in bodies order: two entries for an aspect and one for every other event. Names and signs stay canonical English in every language. Each entry carries its own whole-sign house, including the second body of an aspect. Event placements can differ from positions, which reports noon on the first day of the period.
15713
+ */
15714
+ placements: Array<{
15715
+ /**
15716
+ * Body name, canonical English in every language. Matches the entry at the same index in bodies.
15717
+ */
15718
+ name: string;
15719
+ /**
15720
+ * Sign this body occupies at the event timestamp, lowercase and never translated. For a sign change, the sign entered.
15721
+ */
15722
+ sign: string;
15723
+ /**
15724
+ * Whole-sign house this body occupies at the event instant, counted from the queried sign, 1 to 12.
15725
+ */
15726
+ house: number;
15727
+ }>;
15707
15728
  /**
15708
15729
  * Angle formed, on aspect events only: conjunction, sextile, square, trine, opposition, semi-sextile, quincunx, semi-square, or sesquiquadrate.
15709
15730
  */
15710
15731
  aspect?: string;
15732
+ /**
15733
+ * Exact quarter phase, on lunar-phase events only: new-moon, first-quarter, full-moon, or last-quarter. Canonical English in every language. Use to identify the phase at the event instant.
15734
+ */
15735
+ phase?: 'new-moon' | 'first-quarter' | 'full-moon' | 'last-quarter';
15736
+ /**
15737
+ * Eclipse classification at peak, on eclipse events only: penumbral, partial, annular, or total. Canonical English in every language. Sun in bodies identifies a solar eclipse and Moon a lunar eclipse.
15738
+ */
15739
+ kind?: 'penumbral' | 'partial' | 'annular' | 'total';
15740
+ /**
15741
+ * Direction the body turns at the event instant, on retrograde-station events only: retrograde starts backward motion and direct ends it. Canonical English in every language. Present even when the other end of the retrograde span cannot be dated.
15742
+ */
15743
+ direction?: 'retrograde' | 'direct';
15711
15744
  /**
15712
15745
  * Sign the event falls in, lowercase, where it has exactly one. Absent for an aspect whose two bodies stand in different signs.
15713
15746
  */
@@ -15717,24 +15750,74 @@ export type GetDailyHoroscopeResponses = {
15717
15750
  */
15718
15751
  house: number;
15719
15752
  /**
15720
- * End of the window this event holds open, UTC, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
15753
+ * End of the window this event holds open, on the same clock as at, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
15721
15754
  */
15722
15755
  through?: string;
15723
15756
  }>;
15757
+ /**
15758
+ * Where each of the ten bodies stands for this reading, one row per body, so every standing claim in the prose (a body in a house, until a date, retrograde until it turns direct, exalted or at home) can be checked against the response itself. It carries state only: every aspect, lunation, eclipse, ingress or station of the period is a row of events[]. Against events[], it adds the bodies that do nothing exact in the period (events[] names only what happens), the entry and exit of the sign each stands in (events[].through carries an exit only for an ingress inside the period), the instant a retrograde body turns direct, and dignity. Against activeTransits, which the daily prints as translated strings for the seven visible bodies, it adds Uranus, Neptune and Pluto, the lowercase sign and numeric house as values, the retrograde flag as a boolean, and the three instants. Where an instant appears in both keys it is the same string. Never translated.
15759
+ */
15760
+ positions: Array<{
15761
+ /**
15762
+ * Body, canonical English regardless of the requested language: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune or Pluto, in that order, one row each. Same key and values as planets[].name on the natal chart.
15763
+ */
15764
+ name: string;
15765
+ /**
15766
+ * Sign the body stands in at noon on the first day of the period on the reader clock, lowercase like events[].sign, never translated.
15767
+ */
15768
+ sign: string;
15769
+ /**
15770
+ * Whole-sign house that sign is for the queried sign, 1 to 12, counted as events[].house is.
15771
+ */
15772
+ house: number;
15773
+ /**
15774
+ * Whether the body moves retrograde at that noon. Same key as planets[].isRetrograde on the natal chart; the daily activeTransits prints the same flag as a translated string.
15775
+ */
15776
+ isRetrograde: boolean;
15777
+ /**
15778
+ * Essential dignity of the body in that sign, the same value planets[].dignity reports on the natal chart: domicile, exaltation, detriment, fall, or peregrine. Always English. A column or card that calls a body at home or exalted is backed by this value.
15779
+ */
15780
+ dignity: 'domicile' | 'exaltation' | 'detriment' | 'fall' | 'peregrine';
15781
+ /**
15782
+ * Instant the body entered this sign, to the second, on the same clock as events[].at. Where the entry is also a row of events[] in this response it is that row at, byte for byte. Absent only where the entry lies too far back to date.
15783
+ */
15784
+ enteredAt?: string;
15785
+ /**
15786
+ * Instant the body next leaves this sign, to the second, on the same clock as events[].at: the date a column prints in until April 15. Where it is also in events[] (the ingress that ends the stay, or the through of the ingress that began it) it is that string, byte for byte. Absent only where the exit lies too far ahead to date.
15787
+ */
15788
+ leavesAt?: string;
15789
+ /**
15790
+ * Instant the body next turns direct, to the second, on the same clock as events[].at, present only while isRetrograde is true: the date a retrograde is dated by in the prose. Where the station is also in events[] it is that row at or through, byte for byte. Absent only where the turn lies too far ahead to date.
15791
+ */
15792
+ turnsDirectAt?: string;
15793
+ }>;
15724
15794
  /**
15725
15795
  * Lucky number for the day, 1 to 9, from the traditional planetary number correspondence applied to the planet that governs this sign today. Not a random draw and not a function of the date.
15726
15796
  */
15727
15797
  luckyNumber: number;
15728
15798
  /**
15729
- * Lucky color for the day, drawn from the three colors of the sign element and selected by the planet governing the reading.
15799
+ * Lucky color for the day, the color traditionally ruled by the planet that governs this sign today: Sun gold, Moon silver, Mercury light blue, Venus green, Mars red, Jupiter purple, Saturn brown. When Uranus, Neptune or Pluto governs, the next most governing of the seven classical planets gives the color. Translated with the lang parameter.
15730
15800
  */
15731
15801
  luckyColor: string;
15732
15802
  /**
15733
- * Most compatible zodiac signs for this sign. Trine partners (same element) followed by a sextile partner (complementary element). Use for compatibility widgets, dating app onboarding, and horoscope cards.
15803
+ * Three zodiac signs most in tune with this sign today, best first. Read from the real sky of the period, so the list moves with the transits instead of repeating a fixed table, and every pick can be traced in positions[]. On a quiet sky it settles on the classic element partners. For the fixed sign-to-sign pairing, read compatibleSigns from the signs endpoint.
15734
15804
  */
15735
15805
  compatibleSigns: Array<string>;
15736
15806
  /**
15737
- * Active planetary transits affecting this sign today, with house activations. Each transit shows the planet, its current sign, and which house it activates for the queried sign. The sign and the house phrase translate with the lang parameter; the planet name stays canonical English so a caller can match on it whatever the language.
15807
+ * Crystal of the day for this sign: a stone traditionally linked to this sign and to the planet that governs it today, stepping down to the next governing planet when none is, and to any stone of the sign after that. Rotates by date among equally fitting stones, so the same sign meets a new stone on consecutive days. Use for daily crystal cards beside the horoscope.
15808
+ */
15809
+ crystal: {
15810
+ /**
15811
+ * Crystal identifier, stable in every language. Pass it to the crystal lookup endpoint, GET /crystals/{id}, for the full healing properties, chakras and affirmation.
15812
+ */
15813
+ id: string;
15814
+ /**
15815
+ * Display name of the crystal, translated with the lang parameter.
15816
+ */
15817
+ name: string;
15818
+ };
15819
+ /**
15820
+ * Active planetary transits affecting this sign today, with house activations. Each transit shows the planet, its current sign, and the house it activates for the queried sign, named by its life area as the prose names it (your house of partnership). The sign and the house phrase translate with the lang parameter; the planet name stays canonical English so a caller can match on it whatever the language.
15738
15821
  */
15739
15822
  activeTransits: Array<string>;
15740
15823
  /**
@@ -15770,7 +15853,7 @@ export type GetWeeklyHoroscopeData = {
15770
15853
  */
15771
15854
  date?: string;
15772
15855
  /**
15773
- * Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each Monday. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
15856
+ * The clock the week is read on: it decides which events fall inside the Monday to Sunday week, the day each is dated by, and which week is current when date is omitted. Defaults to UTC. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
15774
15857
  */
15775
15858
  timezone?: string;
15776
15859
  };
@@ -15912,33 +15995,37 @@ export type GetWeeklyHoroscopeResponses = {
15912
15995
  */
15913
15996
  week: string;
15914
15997
  /**
15915
- * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 40 to 80 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
15998
+ * The event of the week that most reaches home, roots and the self, or on a quiet week a standing planet, written as the five topic fields are and opening on the lead of column whenever focus is overview. Typically 120 to 160 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
15916
15999
  */
15917
16000
  overview: string;
15918
16001
  /**
15919
- * Weekly love and relationship forecast, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16002
+ * Weekly love and relationship forecast, read into the whole-sign houses of this sign. It opens on the event of the week that most reaches romance and partnership, dated by its day, or on a quiet week a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries romance and partnership; the aggregate event house remains the leading body house. Typically 120 to 160 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15920
16003
  */
15921
16004
  love: string;
15922
16005
  /**
15923
- * Weekly career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16006
+ * Weekly career and professional outlook, read into the whole-sign houses of this sign. It opens on the event of the week that most reaches career, work and reputation, dated by its day, or on a quiet week a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries career, work and reputation; the aggregate event house remains the leading body house. Typically 120 to 160 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15924
16007
  */
15925
16008
  career: string;
15926
16009
  /**
15927
- * Weekly health, energy, and wellness guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16010
+ * Weekly health, energy, and wellness guidance, read into the whole-sign houses of this sign. It opens on the event of the week that most reaches health, dated by its day, or on a quiet week a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries health; the aggregate event house remains the leading body house. Typically 120 to 160 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15928
16011
  */
15929
16012
  health: string;
15930
16013
  /**
15931
- * Weekly financial outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 80 to 120 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16014
+ * Weekly financial outlook, read into the whole-sign houses of this sign. It opens on the event of the week that most reaches finance, dated by its day, or on a quiet week a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries finance; the aggregate event house remains the leading body house. Typically 120 to 160 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
15932
16015
  */
15933
16016
  finance: string;
15934
16017
  /**
15935
- * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
16018
+ * The single actionable takeaway of the period. It opens on the event of the week that most reaches travel, belief, conversation and daily learning, or on a quiet week a standing planet, naming the bodies, the aspect and the life area, then a situation with a way through it, a conditional with a few options, and a close, in the shape of the five fields beside it. Deterministic: the same sign and period always returns the same text.
15936
16019
  */
15937
16020
  advice: string;
15938
16021
  /**
15939
- * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 250 to 450 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
16022
+ * The full column for this period, ready to run as one piece, its paragraphs, where it has more than one, separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 120 to 160 words. The six section fields each open on an event or standing planet of their own read through their life area, the one named in focus on the lead of this column, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
15940
16023
  */
15941
16024
  column: string;
16025
+ /**
16026
+ * The topic this reading is mainly about: love, career, finance or health when the lead event falls in that life area, overview for a bigger-picture period. A machine value, canonical English in every language, so a client can route its own content on it (a related article, a product, a call to action) without parsing the prose; the topic field it names reads the same lead the column opens on.
16027
+ */
16028
+ focus: 'love' | 'career' | 'finance' | 'health' | 'overview';
15942
16029
  /**
15943
16030
  * The dated astronomical events this reading is built on, earliest first. Every field in every row can be checked against an independent authority, so a column can be fact-checked before it is published. Empty on a period in which nothing exact happens, where the reading falls back to the standing positions instead.
15944
16031
  */
@@ -15948,17 +16035,46 @@ export type GetWeeklyHoroscopeResponses = {
15948
16035
  */
15949
16036
  type: 'aspect' | 'sign-ingress' | 'retrograde-station' | 'lunar-phase' | 'eclipse' | 'solar-season';
15950
16037
  /**
15951
- * Exact instant the event perfects, UTC, to the second. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
16038
+ * Exact instant the event perfects, ISO 8601 to the second, on the clock the reading is read on: UTC with Z by default, the offset of timezone when one is passed on a daily, weekly or monthly reading (2026-11-13T19:27:27-05:00 in New York), the same instant either way; a yearly reading is written in UTC. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
15952
16039
  */
15953
16040
  at: string;
15954
16041
  /**
15955
16042
  * Bodies involved, canonical English regardless of the requested language so the value stays safe to switch on. Two entries for an aspect, faster body first. One entry for an ingress, a station, a lunar phase, or an eclipse.
15956
16043
  */
15957
16044
  bodies: Array<string>;
16045
+ /**
16046
+ * Each participant at the enclosing event timestamp, in bodies order: two entries for an aspect and one for every other event. Names and signs stay canonical English in every language. Each entry carries its own whole-sign house, including the second body of an aspect. Event placements can differ from positions, which reports noon on the first day of the period.
16047
+ */
16048
+ placements: Array<{
16049
+ /**
16050
+ * Body name, canonical English in every language. Matches the entry at the same index in bodies.
16051
+ */
16052
+ name: string;
16053
+ /**
16054
+ * Sign this body occupies at the event timestamp, lowercase and never translated. For a sign change, the sign entered.
16055
+ */
16056
+ sign: string;
16057
+ /**
16058
+ * Whole-sign house this body occupies at the event instant, counted from the queried sign, 1 to 12.
16059
+ */
16060
+ house: number;
16061
+ }>;
15958
16062
  /**
15959
16063
  * Angle formed, on aspect events only: conjunction, sextile, square, trine, opposition, semi-sextile, quincunx, semi-square, or sesquiquadrate.
15960
16064
  */
15961
16065
  aspect?: string;
16066
+ /**
16067
+ * Exact quarter phase, on lunar-phase events only: new-moon, first-quarter, full-moon, or last-quarter. Canonical English in every language. Use to identify the phase at the event instant.
16068
+ */
16069
+ phase?: 'new-moon' | 'first-quarter' | 'full-moon' | 'last-quarter';
16070
+ /**
16071
+ * Eclipse classification at peak, on eclipse events only: penumbral, partial, annular, or total. Canonical English in every language. Sun in bodies identifies a solar eclipse and Moon a lunar eclipse.
16072
+ */
16073
+ kind?: 'penumbral' | 'partial' | 'annular' | 'total';
16074
+ /**
16075
+ * Direction the body turns at the event instant, on retrograde-station events only: retrograde starts backward motion and direct ends it. Canonical English in every language. Present even when the other end of the retrograde span cannot be dated.
16076
+ */
16077
+ direction?: 'retrograde' | 'direct';
15962
16078
  /**
15963
16079
  * Sign the event falls in, lowercase, where it has exactly one. Absent for an aspect whose two bodies stand in different signs.
15964
16080
  */
@@ -15968,10 +16084,47 @@ export type GetWeeklyHoroscopeResponses = {
15968
16084
  */
15969
16085
  house: number;
15970
16086
  /**
15971
- * End of the window this event holds open, UTC, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
16087
+ * End of the window this event holds open, on the same clock as at, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
15972
16088
  */
15973
16089
  through?: string;
15974
16090
  }>;
16091
+ /**
16092
+ * Where each of the ten bodies stands for this reading, one row per body, so every standing claim in the prose (a body in a house, until a date, retrograde until it turns direct, exalted or at home) can be checked against the response itself. It carries state only: every aspect, lunation, eclipse, ingress or station of the period is a row of events[]. Against events[], it adds the bodies that do nothing exact in the period (events[] names only what happens), the entry and exit of the sign each stands in (events[].through carries an exit only for an ingress inside the period), the instant a retrograde body turns direct, and dignity. Against activeTransits, which the daily prints as translated strings for the seven visible bodies, it adds Uranus, Neptune and Pluto, the lowercase sign and numeric house as values, the retrograde flag as a boolean, and the three instants. Where an instant appears in both keys it is the same string. Never translated.
16093
+ */
16094
+ positions: Array<{
16095
+ /**
16096
+ * Body, canonical English regardless of the requested language: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune or Pluto, in that order, one row each. Same key and values as planets[].name on the natal chart.
16097
+ */
16098
+ name: string;
16099
+ /**
16100
+ * Sign the body stands in at noon on the first day of the period on the reader clock, lowercase like events[].sign, never translated.
16101
+ */
16102
+ sign: string;
16103
+ /**
16104
+ * Whole-sign house that sign is for the queried sign, 1 to 12, counted as events[].house is.
16105
+ */
16106
+ house: number;
16107
+ /**
16108
+ * Whether the body moves retrograde at that noon. Same key as planets[].isRetrograde on the natal chart; the daily activeTransits prints the same flag as a translated string.
16109
+ */
16110
+ isRetrograde: boolean;
16111
+ /**
16112
+ * Essential dignity of the body in that sign, the same value planets[].dignity reports on the natal chart: domicile, exaltation, detriment, fall, or peregrine. Always English. A column or card that calls a body at home or exalted is backed by this value.
16113
+ */
16114
+ dignity: 'domicile' | 'exaltation' | 'detriment' | 'fall' | 'peregrine';
16115
+ /**
16116
+ * Instant the body entered this sign, to the second, on the same clock as events[].at. Where the entry is also a row of events[] in this response it is that row at, byte for byte. Absent only where the entry lies too far back to date.
16117
+ */
16118
+ enteredAt?: string;
16119
+ /**
16120
+ * Instant the body next leaves this sign, to the second, on the same clock as events[].at: the date a column prints in until April 15. Where it is also in events[] (the ingress that ends the stay, or the through of the ingress that began it) it is that string, byte for byte. Absent only where the exit lies too far ahead to date.
16121
+ */
16122
+ leavesAt?: string;
16123
+ /**
16124
+ * Instant the body next turns direct, to the second, on the same clock as events[].at, present only while isRetrograde is true: the date a retrograde is dated by in the prose. Where the station is also in events[] it is that row at or through, byte for byte. Absent only where the turn lies too far ahead to date.
16125
+ */
16126
+ turnsDirectAt?: string;
16127
+ }>;
15975
16128
  /**
15976
16129
  * The three most favorable days this week, from the planetary rulers of the seven weekdays, ranked by how strongly each of those planets stands for this sign.
15977
16130
  */
@@ -15981,7 +16134,7 @@ export type GetWeeklyHoroscopeResponses = {
15981
16134
  */
15982
16135
  luckyNumbers: Array<number>;
15983
16136
  /**
15984
- * Most compatible zodiac signs for this sign. Trine partners (same element) followed by a sextile partner (complementary element).
16137
+ * Three zodiac signs most in tune with this sign this week, best first. Read from the real sky of the period, so the list moves with the transits instead of repeating a fixed table, and every pick can be traced in positions[]. On a quiet sky it settles on the classic element partners. For the fixed sign-to-sign pairing, read compatibleSigns from the signs endpoint.
15985
16138
  */
15986
16139
  compatibleSigns: Array<string>;
15987
16140
  };
@@ -16005,7 +16158,7 @@ export type GetMonthlyHoroscopeData = {
16005
16158
  */
16006
16159
  date?: string;
16007
16160
  /**
16008
- * Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on the 1st. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
16161
+ * The clock the month is read on: it decides which events fall inside the calendar month, the date each is dated by, and which month is current when date is omitted. Defaults to UTC. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
16009
16162
  */
16010
16163
  timezone?: string;
16011
16164
  };
@@ -16147,33 +16300,37 @@ export type GetMonthlyHoroscopeResponses = {
16147
16300
  */
16148
16301
  month: string;
16149
16302
  /**
16150
- * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 55 to 100 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
16303
+ * The event of the month that most reaches home, roots and the self, or on a quiet month a standing planet, written as the five topic fields are and opening on the lead of column whenever focus is overview. Typically 35 to 90 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
16151
16304
  */
16152
16305
  overview: string;
16153
16306
  /**
16154
- * Monthly love and relationship forecast, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16307
+ * Monthly love and relationship forecast, read into the whole-sign houses of this sign. It is the love monthly, a full piece that reads every transit of the month that reaches romance and partnership through love, in date order, each dated, then a close. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries romance and partnership; the aggregate event house remains the leading body house. Typically 180 to 250 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16155
16308
  */
16156
16309
  love: string;
16157
16310
  /**
16158
- * Monthly career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16311
+ * Monthly career and professional outlook, read into the whole-sign houses of this sign. It opens on the event of the month that most reaches career, work and reputation, dated, or on a quiet month a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries career, work and reputation; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16159
16312
  */
16160
16313
  career: string;
16161
16314
  /**
16162
- * Monthly health and wellness guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16315
+ * Monthly health and wellness guidance, read into the whole-sign houses of this sign. It opens on the event of the month that most reaches health, dated, or on a quiet month a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries health; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16163
16316
  */
16164
16317
  health: string;
16165
16318
  /**
16166
- * Monthly financial outlook and guidance, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 120 to 200 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16319
+ * Monthly financial outlook and guidance, read into the whole-sign houses of this sign. It opens on the event of the month that most reaches finance, dated, or on a quiet month a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries finance; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16167
16320
  */
16168
16321
  finance: string;
16169
16322
  /**
16170
- * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
16323
+ * The single actionable takeaway of the period. It opens on the event of the month that most reaches travel, belief, conversation and daily learning, or on a quiet month a standing planet, naming the bodies, the aspect and the life area, then a situation with a way through it, a conditional with a few options, and a close, in the shape of the five fields beside it. Deterministic: the same sign and period always returns the same text.
16171
16324
  */
16172
16325
  advice: string;
16173
16326
  /**
16174
- * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 400 to 700 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
16327
+ * The full column for this period, ready to run as one piece, its paragraphs, where it has more than one, separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 180 to 250 words. The six section fields each open on an event or standing planet of their own read through their life area, the one named in focus on the lead of this column, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
16175
16328
  */
16176
16329
  column: string;
16330
+ /**
16331
+ * The topic this reading is mainly about: love, career, finance or health when the lead event falls in that life area, overview for a bigger-picture period. A machine value, canonical English in every language, so a client can route its own content on it (a related article, a product, a call to action) without parsing the prose; the topic field it names reads the same lead the column opens on.
16332
+ */
16333
+ focus: 'love' | 'career' | 'finance' | 'health' | 'overview';
16177
16334
  /**
16178
16335
  * The dated astronomical events this reading is built on, earliest first. Every field in every row can be checked against an independent authority, so a column can be fact-checked before it is published. Empty on a period in which nothing exact happens, where the reading falls back to the standing positions instead.
16179
16336
  */
@@ -16183,17 +16340,46 @@ export type GetMonthlyHoroscopeResponses = {
16183
16340
  */
16184
16341
  type: 'aspect' | 'sign-ingress' | 'retrograde-station' | 'lunar-phase' | 'eclipse' | 'solar-season';
16185
16342
  /**
16186
- * Exact instant the event perfects, UTC, to the second. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
16343
+ * Exact instant the event perfects, ISO 8601 to the second, on the clock the reading is read on: UTC with Z by default, the offset of timezone when one is passed on a daily, weekly or monthly reading (2026-11-13T19:27:27-05:00 in New York), the same instant either way; a yearly reading is written in UTC. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
16187
16344
  */
16188
16345
  at: string;
16189
16346
  /**
16190
16347
  * Bodies involved, canonical English regardless of the requested language so the value stays safe to switch on. Two entries for an aspect, faster body first. One entry for an ingress, a station, a lunar phase, or an eclipse.
16191
16348
  */
16192
16349
  bodies: Array<string>;
16350
+ /**
16351
+ * Each participant at the enclosing event timestamp, in bodies order: two entries for an aspect and one for every other event. Names and signs stay canonical English in every language. Each entry carries its own whole-sign house, including the second body of an aspect. Event placements can differ from positions, which reports noon on the first day of the period.
16352
+ */
16353
+ placements: Array<{
16354
+ /**
16355
+ * Body name, canonical English in every language. Matches the entry at the same index in bodies.
16356
+ */
16357
+ name: string;
16358
+ /**
16359
+ * Sign this body occupies at the event timestamp, lowercase and never translated. For a sign change, the sign entered.
16360
+ */
16361
+ sign: string;
16362
+ /**
16363
+ * Whole-sign house this body occupies at the event instant, counted from the queried sign, 1 to 12.
16364
+ */
16365
+ house: number;
16366
+ }>;
16193
16367
  /**
16194
16368
  * Angle formed, on aspect events only: conjunction, sextile, square, trine, opposition, semi-sextile, quincunx, semi-square, or sesquiquadrate.
16195
16369
  */
16196
16370
  aspect?: string;
16371
+ /**
16372
+ * Exact quarter phase, on lunar-phase events only: new-moon, first-quarter, full-moon, or last-quarter. Canonical English in every language. Use to identify the phase at the event instant.
16373
+ */
16374
+ phase?: 'new-moon' | 'first-quarter' | 'full-moon' | 'last-quarter';
16375
+ /**
16376
+ * Eclipse classification at peak, on eclipse events only: penumbral, partial, annular, or total. Canonical English in every language. Sun in bodies identifies a solar eclipse and Moon a lunar eclipse.
16377
+ */
16378
+ kind?: 'penumbral' | 'partial' | 'annular' | 'total';
16379
+ /**
16380
+ * Direction the body turns at the event instant, on retrograde-station events only: retrograde starts backward motion and direct ends it. Canonical English in every language. Present even when the other end of the retrograde span cannot be dated.
16381
+ */
16382
+ direction?: 'retrograde' | 'direct';
16197
16383
  /**
16198
16384
  * Sign the event falls in, lowercase, where it has exactly one. Absent for an aspect whose two bodies stand in different signs.
16199
16385
  */
@@ -16203,10 +16389,47 @@ export type GetMonthlyHoroscopeResponses = {
16203
16389
  */
16204
16390
  house: number;
16205
16391
  /**
16206
- * End of the window this event holds open, UTC, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
16392
+ * End of the window this event holds open, on the same clock as at, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
16207
16393
  */
16208
16394
  through?: string;
16209
16395
  }>;
16396
+ /**
16397
+ * Where each of the ten bodies stands for this reading, one row per body, so every standing claim in the prose (a body in a house, until a date, retrograde until it turns direct, exalted or at home) can be checked against the response itself. It carries state only: every aspect, lunation, eclipse, ingress or station of the period is a row of events[]. Against events[], it adds the bodies that do nothing exact in the period (events[] names only what happens), the entry and exit of the sign each stands in (events[].through carries an exit only for an ingress inside the period), the instant a retrograde body turns direct, and dignity. Against activeTransits, which the daily prints as translated strings for the seven visible bodies, it adds Uranus, Neptune and Pluto, the lowercase sign and numeric house as values, the retrograde flag as a boolean, and the three instants. Where an instant appears in both keys it is the same string. Never translated.
16398
+ */
16399
+ positions: Array<{
16400
+ /**
16401
+ * Body, canonical English regardless of the requested language: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune or Pluto, in that order, one row each. Same key and values as planets[].name on the natal chart.
16402
+ */
16403
+ name: string;
16404
+ /**
16405
+ * Sign the body stands in at noon on the first day of the period on the reader clock, lowercase like events[].sign, never translated.
16406
+ */
16407
+ sign: string;
16408
+ /**
16409
+ * Whole-sign house that sign is for the queried sign, 1 to 12, counted as events[].house is.
16410
+ */
16411
+ house: number;
16412
+ /**
16413
+ * Whether the body moves retrograde at that noon. Same key as planets[].isRetrograde on the natal chart; the daily activeTransits prints the same flag as a translated string.
16414
+ */
16415
+ isRetrograde: boolean;
16416
+ /**
16417
+ * Essential dignity of the body in that sign, the same value planets[].dignity reports on the natal chart: domicile, exaltation, detriment, fall, or peregrine. Always English. A column or card that calls a body at home or exalted is backed by this value.
16418
+ */
16419
+ dignity: 'domicile' | 'exaltation' | 'detriment' | 'fall' | 'peregrine';
16420
+ /**
16421
+ * Instant the body entered this sign, to the second, on the same clock as events[].at. Where the entry is also a row of events[] in this response it is that row at, byte for byte. Absent only where the entry lies too far back to date.
16422
+ */
16423
+ enteredAt?: string;
16424
+ /**
16425
+ * Instant the body next leaves this sign, to the second, on the same clock as events[].at: the date a column prints in until April 15. Where it is also in events[] (the ingress that ends the stay, or the through of the ingress that began it) it is that string, byte for byte. Absent only where the exit lies too far ahead to date.
16426
+ */
16427
+ leavesAt?: string;
16428
+ /**
16429
+ * Instant the body next turns direct, to the second, on the same clock as events[].at, present only while isRetrograde is true: the date a retrograde is dated by in the prose. Where the station is also in events[] it is that row at or through, byte for byte. Absent only where the turn lies too far ahead to date.
16430
+ */
16431
+ turnsDirectAt?: string;
16432
+ }>;
16210
16433
  /**
16211
16434
  * The month read one calendar week at a time, off the same ranked events as column and events[]: the life area each week turns on, and the one thing that area asks for. Two weeks may land in the same area, because two events of a month often do; the sentence beside it is always different. Use it for the week strip of a monthly page.
16212
16435
  */
@@ -16220,20 +16443,20 @@ export type GetMonthlyHoroscopeResponses = {
16220
16443
  */
16221
16444
  focus: string;
16222
16445
  /**
16223
- * What that house asks for, as one sentence in the requested language. No two weeks of one month repeat a sentence.
16446
+ * One practical sentence for that life area, in the requested language. No two weeks of one month repeat a sentence.
16224
16447
  */
16225
16448
  advice: string;
16226
16449
  }>;
16227
16450
  /**
16228
- * The dates to circle this month, earliest first: every lunation and eclipse of the month, plus the headline movements the reading is built on, which are the sign changes of the slower planets and every station with the direction it turns. Each is placed in the whole-sign house it reaches for this sign. Every row is an instant the ephemeris gives, checkable against NASA JPL Horizons or the US Naval Observatory, and every row that is not a lunation or an eclipse is also a row of events[], so the list cannot contradict the reading beside it.
16451
+ * The dates to circle this month, earliest first: every lunation and eclipse of the month, plus the headline movements the reading is built on, which are the sign changes of the slower planets and every station with the direction it turns. Each is placed in the whole-sign house it reaches for this sign. Every row is an instant the ephemeris gives, checkable against NASA JPL Horizons or the US Naval Observatory, and every row is also a row of events[], so the list cannot contradict the reading beside it.
16229
16452
  */
16230
16453
  keyDates: Array<{
16231
16454
  /**
16232
- * UTC date of the event (YYYY-MM-DD). The exact instant, to the second, is on the matching row of events[].
16455
+ * Date of the event (YYYY-MM-DD) on the clock the month is read on, the day the column names it: a station at 00:27 UTC is the previous day in New York. The exact instant, to the second, is on the matching row of events[].
16233
16456
  */
16234
16457
  date: string;
16235
16458
  /**
16236
- * The event as one sentence in the requested language, placed in the whole-sign house it reaches for this sign.
16459
+ * The event in the requested language, with the sign it falls in and the life area of the whole-sign house that sign is for this zodiac sign, as a dated calendar list prints it.
16237
16460
  */
16238
16461
  event: string;
16239
16462
  }>;
@@ -16242,11 +16465,11 @@ export type GetMonthlyHoroscopeResponses = {
16242
16465
  */
16243
16466
  luckyNumbers: Array<number>;
16244
16467
  /**
16245
- * Lucky color for the month, drawn from the three colors of the sign element and selected by the planet governing the reading.
16468
+ * Lucky color for the month, the color traditionally ruled by the planet that governs this sign this month: Sun gold, Moon silver, Mercury light blue, Venus green, Mars red, Jupiter purple, Saturn brown. When Uranus, Neptune or Pluto governs, the next most governing of the seven classical planets gives the color. Translated with the lang parameter.
16246
16469
  */
16247
16470
  luckyColor: string;
16248
16471
  /**
16249
- * Most compatible zodiac signs for this sign. Trine partners (same element) followed by a sextile partner (complementary element).
16472
+ * Three zodiac signs most in tune with this sign this month, best first. Read from the real sky of the period, so the list moves with the transits instead of repeating a fixed table, and every pick can be traced in positions[]. On a quiet sky it settles on the classic element partners. For the fixed sign-to-sign pairing, read compatibleSigns from the signs endpoint.
16250
16473
  */
16251
16474
  compatibleSigns: Array<string>;
16252
16475
  };
@@ -16412,33 +16635,37 @@ export type GetYearlyHoroscopeResponses = {
16412
16635
  */
16413
16636
  year: number;
16414
16637
  /**
16415
- * The single most relevant event of the period, whichever life area it touches, read into the whole-sign houses of this sign. The same event that leads column, at lede length rather than developed into a full movement, and checkable against the events array. Typically 70 to 120 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
16638
+ * The event of the year that most reaches home, roots and the self, or on a quiet year a standing planet, written as the five topic fields are and opening on the lead of column whenever focus is overview. Typically 35 to 90 words. Join it with love, career, health and finance for a general reading built from the six sections. Deterministic: the same sign and period always returns the same text.
16416
16639
  */
16417
16640
  overview: string;
16418
16641
  /**
16419
- * Yearly love and relationship outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to romance and partnership, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries romance and partnership, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16642
+ * Yearly love and relationship outlook, read into the whole-sign houses of this sign. It opens on the event of the year that most reaches romance and partnership, dated, or on a quiet year a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries romance and partnership; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16420
16643
  */
16421
16644
  love: string;
16422
16645
  /**
16423
- * Yearly career and professional outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to career, work and reputation, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries career, work and reputation, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16646
+ * Yearly career and professional outlook, read into the whole-sign houses of this sign. It opens on the event of the year that most reaches career, work and reputation, dated, or on a quiet year a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries career, work and reputation; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16424
16647
  */
16425
16648
  career: string;
16426
16649
  /**
16427
- * Yearly health, energy, and wellness outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to health, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries health, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16650
+ * Yearly health, energy, and wellness outlook, read into the whole-sign houses of this sign. It opens on the event of the year that most reaches health, dated, or on a quiet year a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries health; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16428
16651
  */
16429
16652
  health: string;
16430
16653
  /**
16431
- * Yearly financial outlook, read into the whole-sign houses of this sign. The same ranked events that drive column, filtered to finance, plus the standing placements that reach it. Every event named here is in the events array, so a piece can be fact-checked before it runs; this section reads an event through whichever of its houses carries finance, which for an aspect between two houses can be the other one from the house the events array leads with, and both are whole-sign houses of the bodies involved counted from this sign. Typically 150 to 260 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is the same material woven into one piece instead of split by topic. Deterministic: the same sign and period always returns the same text.
16654
+ * Yearly financial outlook, read into the whole-sign houses of this sign. It opens on the event of the year that most reaches finance, dated, or on a quiet year a standing planet, naming the bodies, the aspect and the life area and what it stirs, then a human situation of this topic with a way through it, a conditional with a few options, and a close; the topic named in focus opens on the same event as column. Every named event is in events, with each participant sign and whole-sign house in placements at the event time. This section reads whichever participant house carries finance; the aggregate event house remains the leading body house. Typically 35 to 90 words. Render it alone for a single-topic page, or alongside the other five sections for a general reading; column is a separate piece of its own. Deterministic: the same sign and period always returns the same text.
16432
16655
  */
16433
16656
  finance: string;
16434
16657
  /**
16435
- * The single actionable takeaway from the leading event of the period, read into the whole-sign houses of this sign and checkable against the events array. Drawn from the same event as overview, kept to a short, actionable pair of sentences rather than grown to match the other sections. Deterministic: the same sign and period always returns the same text.
16658
+ * The single actionable takeaway of the period. It opens on the event of the year that most reaches travel, belief, conversation and daily learning, or on a quiet year a standing planet, naming the bodies, the aspect and the life area, then a situation with a way through it, a conditional with a few options, and a close, in the shape of the five fields beside it. Deterministic: the same sign and period always returns the same text.
16436
16659
  */
16437
16660
  advice: string;
16438
16661
  /**
16439
- * The full column for this period, ready to run as one piece, with paragraphs separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 600 to 900 words. The six section fields read the same ranked events filtered to their own life area, each composed as a column of its own rather than an excerpt of this one, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
16662
+ * The full column for this period, ready to run as one piece, its paragraphs, where it has more than one, separated by a blank line. Names the events driving it and the dates they fall on, read into the whole-sign houses of this sign. Typically 190 to 320 words. The six section fields each open on an event or standing planet of their own read through their life area, the one named in focus on the lead of this column, so render either shape and never both. Deterministic: the same sign and period always returns the same column.
16440
16663
  */
16441
16664
  column: string;
16665
+ /**
16666
+ * The topic this reading is mainly about: love, career, finance or health when the lead event falls in that life area, overview for a bigger-picture period. A machine value, canonical English in every language, so a client can route its own content on it (a related article, a product, a call to action) without parsing the prose; the topic field it names reads the same lead the column opens on.
16667
+ */
16668
+ focus: 'love' | 'career' | 'finance' | 'health' | 'overview';
16442
16669
  /**
16443
16670
  * The dated astronomical events this reading is built on, earliest first. Every field in every row can be checked against an independent authority, so a column can be fact-checked before it is published. Empty on a period in which nothing exact happens, where the reading falls back to the standing positions instead.
16444
16671
  */
@@ -16448,17 +16675,46 @@ export type GetYearlyHoroscopeResponses = {
16448
16675
  */
16449
16676
  type: 'aspect' | 'sign-ingress' | 'retrograde-station' | 'lunar-phase' | 'eclipse' | 'solar-season';
16450
16677
  /**
16451
- * Exact instant the event perfects, UTC, to the second. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
16678
+ * Exact instant the event perfects, ISO 8601 to the second, on the clock the reading is read on: UTC with Z by default, the offset of timezone when one is passed on a daily, weekly or monthly reading (2026-11-13T19:27:27-05:00 in New York), the same instant either way; a yearly reading is written in UTC. Verifiable against NASA JPL Horizons for a position event and against the US Naval Observatory for a lunar phase or eclipse.
16452
16679
  */
16453
16680
  at: string;
16454
16681
  /**
16455
16682
  * Bodies involved, canonical English regardless of the requested language so the value stays safe to switch on. Two entries for an aspect, faster body first. One entry for an ingress, a station, a lunar phase, or an eclipse.
16456
16683
  */
16457
16684
  bodies: Array<string>;
16685
+ /**
16686
+ * Each participant at the enclosing event timestamp, in bodies order: two entries for an aspect and one for every other event. Names and signs stay canonical English in every language. Each entry carries its own whole-sign house, including the second body of an aspect. Event placements can differ from positions, which reports noon on the first day of the period.
16687
+ */
16688
+ placements: Array<{
16689
+ /**
16690
+ * Body name, canonical English in every language. Matches the entry at the same index in bodies.
16691
+ */
16692
+ name: string;
16693
+ /**
16694
+ * Sign this body occupies at the event timestamp, lowercase and never translated. For a sign change, the sign entered.
16695
+ */
16696
+ sign: string;
16697
+ /**
16698
+ * Whole-sign house this body occupies at the event instant, counted from the queried sign, 1 to 12.
16699
+ */
16700
+ house: number;
16701
+ }>;
16458
16702
  /**
16459
16703
  * Angle formed, on aspect events only: conjunction, sextile, square, trine, opposition, semi-sextile, quincunx, semi-square, or sesquiquadrate.
16460
16704
  */
16461
16705
  aspect?: string;
16706
+ /**
16707
+ * Exact quarter phase, on lunar-phase events only: new-moon, first-quarter, full-moon, or last-quarter. Canonical English in every language. Use to identify the phase at the event instant.
16708
+ */
16709
+ phase?: 'new-moon' | 'first-quarter' | 'full-moon' | 'last-quarter';
16710
+ /**
16711
+ * Eclipse classification at peak, on eclipse events only: penumbral, partial, annular, or total. Canonical English in every language. Sun in bodies identifies a solar eclipse and Moon a lunar eclipse.
16712
+ */
16713
+ kind?: 'penumbral' | 'partial' | 'annular' | 'total';
16714
+ /**
16715
+ * Direction the body turns at the event instant, on retrograde-station events only: retrograde starts backward motion and direct ends it. Canonical English in every language. Present even when the other end of the retrograde span cannot be dated.
16716
+ */
16717
+ direction?: 'retrograde' | 'direct';
16462
16718
  /**
16463
16719
  * Sign the event falls in, lowercase, where it has exactly one. Absent for an aspect whose two bodies stand in different signs.
16464
16720
  */
@@ -16468,10 +16724,47 @@ export type GetYearlyHoroscopeResponses = {
16468
16724
  */
16469
16725
  house: number;
16470
16726
  /**
16471
- * End of the window this event holds open, UTC, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
16727
+ * End of the window this event holds open, on the same clock as at, given only where a bounded window is a real fact about it: the orb span of an aspect, the sign span of an ingress or a season, the retrograde span of a station. Absent for a lunar phase or an eclipse, which are instants and not spans.
16472
16728
  */
16473
16729
  through?: string;
16474
16730
  }>;
16731
+ /**
16732
+ * Where each of the ten bodies stands for this reading, one row per body, so every standing claim in the prose (a body in a house, until a date, retrograde until it turns direct, exalted or at home) can be checked against the response itself. It carries state only: every aspect, lunation, eclipse, ingress or station of the period is a row of events[]. Against events[], it adds the bodies that do nothing exact in the period (events[] names only what happens), the entry and exit of the sign each stands in (events[].through carries an exit only for an ingress inside the period), the instant a retrograde body turns direct, and dignity. Against activeTransits, which the daily prints as translated strings for the seven visible bodies, it adds Uranus, Neptune and Pluto, the lowercase sign and numeric house as values, the retrograde flag as a boolean, and the three instants. Where an instant appears in both keys it is the same string. Never translated.
16733
+ */
16734
+ positions: Array<{
16735
+ /**
16736
+ * Body, canonical English regardless of the requested language: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune or Pluto, in that order, one row each. Same key and values as planets[].name on the natal chart.
16737
+ */
16738
+ name: string;
16739
+ /**
16740
+ * Sign the body stands in at noon on the first day of the period on the reader clock, lowercase like events[].sign, never translated.
16741
+ */
16742
+ sign: string;
16743
+ /**
16744
+ * Whole-sign house that sign is for the queried sign, 1 to 12, counted as events[].house is.
16745
+ */
16746
+ house: number;
16747
+ /**
16748
+ * Whether the body moves retrograde at that noon. Same key as planets[].isRetrograde on the natal chart; the daily activeTransits prints the same flag as a translated string.
16749
+ */
16750
+ isRetrograde: boolean;
16751
+ /**
16752
+ * Essential dignity of the body in that sign, the same value planets[].dignity reports on the natal chart: domicile, exaltation, detriment, fall, or peregrine. Always English. A column or card that calls a body at home or exalted is backed by this value.
16753
+ */
16754
+ dignity: 'domicile' | 'exaltation' | 'detriment' | 'fall' | 'peregrine';
16755
+ /**
16756
+ * Instant the body entered this sign, to the second, on the same clock as events[].at. Where the entry is also a row of events[] in this response it is that row at, byte for byte. Absent only where the entry lies too far back to date.
16757
+ */
16758
+ enteredAt?: string;
16759
+ /**
16760
+ * Instant the body next leaves this sign, to the second, on the same clock as events[].at: the date a column prints in until April 15. Where it is also in events[] (the ingress that ends the stay, or the through of the ingress that began it) it is that string, byte for byte. Absent only where the exit lies too far ahead to date.
16761
+ */
16762
+ leavesAt?: string;
16763
+ /**
16764
+ * Instant the body next turns direct, to the second, on the same clock as events[].at, present only while isRetrograde is true: the date a retrograde is dated by in the prose. Where the station is also in events[] it is that row at or through, byte for byte. Absent only where the turn lies too far ahead to date.
16765
+ */
16766
+ turnsDirectAt?: string;
16767
+ }>;
16475
16768
  /**
16476
16769
  * The backdrop of the year: which whole-sign house each slow-moving body occupies for this sign, Jupiter first and Pluto last. One row per unbroken stretch, so a body that stays put is a single row spanning the year and a body that changes sign is two rows with the exact date between them. Dates are the part of the stretch that falls inside this year; the full span of a change that happens inside the year is in the events array. Use it for the year-at-a-glance panel a year-ahead page opens with.
16477
16770
  */
@@ -16650,11 +16943,11 @@ export type GetYearlyHoroscopeResponses = {
16650
16943
  */
16651
16944
  luckyNumbers: Array<number>;
16652
16945
  /**
16653
- * Lucky color for the year, drawn from the three colors of the sign element and selected by the planet governing the reading.
16946
+ * Lucky color for the year, the color traditionally ruled by the planet that governs this sign this year: Sun gold, Moon silver, Mercury light blue, Venus green, Mars red, Jupiter purple, Saturn brown. When Uranus, Neptune or Pluto governs, the next most governing of the seven classical planets gives the color. Translated with the lang parameter.
16654
16947
  */
16655
16948
  luckyColor: string;
16656
16949
  /**
16657
- * Most compatible zodiac signs for this sign. Trine partners (same element) followed by a sextile partner (complementary element).
16950
+ * Three zodiac signs most in tune with this sign this year, best first. Read from the real sky of the period, so the list moves with the transits instead of repeating a fixed table, and every pick can be traced in positions[]. On a quiet sky it settles on the classic element partners. For the fixed sign-to-sign pairing, read compatibleSigns from the signs endpoint.
16658
16951
  */
16659
16952
  compatibleSigns: Array<string>;
16660
16953
  };