@roxyapi/ui-vue 0.20.0 → 0.21.0

package/dist/types/types.gen.d.ts

@@ -432,10 +432,25 @@ export type HousesResponse = {
      */
     comparison?: {
         [key: string]: {
+            /**
+             * All 12 house cusps as this system computes them. Compare the same house number across the four keys to see how far the systems disagree, which is largest at high latitudes and for the intermediate cusps.
+             */
             houses: Array<{
+                /**
+                 * House number (1-12). Each house governs specific life areas.
+                 */
                 number: number;
+                /**
+                 * Ecliptic longitude of this house cusp in degrees (0-360), as this house system places it.
+                 */
                 longitude: number;
+                /**
+                 * Zodiac sign on this house cusp in this house system.
+                 */
                 sign: string;
+                /**
+                 * Degree within the zodiac sign on this cusp (0-29.999).
+                 */
                 degree: number;
             }>;
         };
@@ -809,7 +824,7 @@ export type TransitsResponse = {
              */
             summary: string;
             /**
-             * How long this transit influence lasts based on the transiting planet speed.
+             * How long this transit influence lasts, localized. The bucket follows the speed of the transiting body: a few hours for the Moon, a few days for the Sun, Mercury, Venus and Mars, one to two weeks for Jupiter, several weeks for Saturn, and an extended period for Uranus, Neptune and Pluto.
              */
             timing: string;
             /**
@@ -873,7 +888,13 @@ export type TransitsRequest = {
          * Time in 24-hour format. Seconds are optional and default to 00 (14:30 becomes 14:30:00); a single-digit hour is zero-padded. Out-of-range values are rejected.
          */
         time: string;
+        /**
+         * Natal birth latitude in decimal degrees, positive north. Sets the local sidereal time behind the natal Ascendant and house cusps that the transits are measured against.
+         */
         latitude: number;
+        /**
+         * Natal birth longitude in decimal degrees, positive east and negative west. Example: New York -74.0060, London -0.1276, Sydney 151.2093.
+         */
         longitude: number;
         /**
          * Natal timezone: decimal hours OR IANA name (e.g. "America/New_York"). IANA resolved to the DST-correct offset for the natal date.
@@ -973,7 +994,7 @@ export type AstrocartographyResponse = {
             /**
              * Absolute latitude in degrees beyond which the body never crosses the horizon, so the line has no points past it. Null when the line spans the full sampled range.
              */
-            circumpolarBeyond: number;
+            circumpolarBeyond: number | null;
             /**
              * Plain language meaning of this rising or setting planetary line for relocation, suitable for chart reports and AI agents.
              */
@@ -999,7 +1020,7 @@ export type AstrocartographyResponse = {
             /**
              * Absolute latitude in degrees beyond which the body never crosses the horizon, so the line has no points past it. Null when the line spans the full sampled range.
              */
-            circumpolarBeyond: number;
+            circumpolarBeyond: number | null;
             /**
              * Plain language meaning of this rising or setting planetary line for relocation, suitable for chart reports and AI agents.
              */
@@ -2092,7 +2113,7 @@ export type ProfectionsRequest = {
 export type BirthChartResponse = {
     aries: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2149,7 +2170,7 @@ export type BirthChartResponse = {
     };
     taurus: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2206,7 +2227,7 @@ export type BirthChartResponse = {
     };
     gemini: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2263,7 +2284,7 @@ export type BirthChartResponse = {
     };
     cancer: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2320,7 +2341,7 @@ export type BirthChartResponse = {
     };
     leo: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2377,7 +2398,7 @@ export type BirthChartResponse = {
     };
     virgo: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2434,7 +2455,7 @@ export type BirthChartResponse = {
     };
     libra: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2491,7 +2512,7 @@ export type BirthChartResponse = {
     };
     scorpio: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2548,7 +2569,7 @@ export type BirthChartResponse = {
     };
     sagittarius: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2605,7 +2626,7 @@ export type BirthChartResponse = {
     };
     capricorn: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2662,7 +2683,7 @@ export type BirthChartResponse = {
     };
     aquarius: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2719,7 +2740,7 @@ export type BirthChartResponse = {
     };
     pisces: {
         /**
-         * Zodiac sign name in lowercase.
+         * Zodiac sign name in lowercase. Always equals the key of the block it sits in, so the aries block carries "aries" and the pisces block carries "pisces".
          */
         rashi: string;
         /**
@@ -2774,6 +2795,69 @@ export type BirthChartResponse = {
             deeptadi?: 'Dipta' | 'Svastha' | 'Pramudita' | 'Shanta' | 'Dina' | 'Duhkhita' | 'Vikala' | 'Khala' | 'Kopa';
         }>;
     };
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
+    /**
+     * Uranus, Neptune and Pluto, present only when modernPlanets true was sent. Deliberately separate from meta and deliberately without dignity, avastha, combustion or aspect fields: those are constructs of the nine-graha system and the modern planets rule no sign, so no classical value exists for them. Order is always Uranus, Neptune, Pluto.
+     */
+    modernPlanets?: Array<{
+        /**
+         * Modern planet name. These three are outside the classical Navagraha and are returned only when modernPlanets true is sent.
+         */
+        planet: 'Uranus' | 'Neptune' | 'Pluto';
+        /**
+         * Sanskrit name Indian software prints for this body: Arun for Uranus, Varun for Neptune, Yam for Pluto. Transliterated rather than translated, the same treatment as rashi and nakshatra lord names, so it is identical in every locale.
+         */
+        sanskritName: 'Arun' | 'Varun' | 'Yam';
+        /**
+         * Sidereal longitude in degrees (0-360), in the same ayanamsa frame as every other position in this response.
+         */
+        longitude: number;
+        /**
+         * Zodiac sign (rashi) the body occupies.
+         */
+        rashi: string;
+        /**
+         * Degrees advanced into the sign, 0 to 30. This is the figure a chart displays beside the sign.
+         */
+        degreeInRashi: number;
+        /**
+         * Nakshatra placement. Reported because it is purely positional; it does not imply the body participates in Vimshottari dasha, which is built on the Moon alone.
+         */
+        nakshatra: {
+            /**
+             * Nakshatra (lunar mansion, 1 of 27) the body occupies.
+             */
+            name: string;
+            /**
+             * Nakshatra pada (quarter, 1-4).
+             */
+            pada: number;
+            /**
+             * Nakshatra index (1-27) starting from Ashwini.
+             */
+            key: number;
+            /**
+             * Vimshottari ruling planet of this nakshatra.
+             */
+            lord: 'Ketu' | 'Venus' | 'Sun' | 'Moon' | 'Mars' | 'Rahu' | 'Jupiter' | 'Saturn' | 'Mercury';
+        };
+        /**
+         * True when the body appears to move backward. All three are retrograde for roughly 40 percent of each year, so this is the normal case rather than the exception.
+         */
+        isRetrograde: boolean;
+    }>;
     /**
      * The twelve bhavas (houses) in order, each with its classical name and significations. Houses are counted whole-sign from the Lagna.
      */
@@ -2873,9 +2957,17 @@ export type BirthChartResponse = {
          */
         quality: 'Positive' | 'Negative' | 'Both';
         /**
-         * True if every classical condition for the yoga is satisfied by the given chart. False if any rule fails, including "almost-present" cases where dignity is met but kendra/aspect is not, and Nabhasa cases where the yoga matched its own rule but a stronger family outranked it under the classical precedence norms. Read `evidence` to tell those apart.
+         * Classical grouping, ALWAYS present on a detection verdict: one of the four Nabhasa families (asraya, dala, akriti, sankhya) or classical for the twelve single-combination yogas such as Gajakesari and the Pancha Mahapurusha. Group the verdict list on this key to render a Nabhasa result the way the tradition arranges it. Never translated, so grouping works identically under any lang.
+         */
+        family: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
+        /**
+         * True if every classical condition for the yoga is satisfied by the given chart. False means one of TWO different things: the rule failed, or the rule held and a stronger family outranked it. Read `suppressedBy` to tell those apart, which is exact and locale-independent; `evidence` says the same thing in English prose.
          */
         present: boolean;
+        /**
+         * Set ONLY when this yoga matched its own classical rule and was then silenced by a higher-ranking family, so `present` is false for a reason a practitioner reads very differently from a failed rule. Names the family that took precedence, under the four classical norms: Akriti outranks Asraya, and Akriti, Asraya and Dala each outrank Sankhya. Absent means the rule genuinely did not hold.
+         */
+        suppressedBy?: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
         /**
          * Human-readable rationale naming the specific rule that triggered or failed the detection, including planetary positions, dignity, kendradhipati status, lordship, malefic drishti, sign modality, or whole-chart bhava distribution. For a Nabhasa yoga that matched its own rule but was outranked, this names the precedence norm that silenced it, for example that an Akriti yoga outranks Asraya or that any other Nabhasa family suppresses Sankhya.
          */
@@ -2903,11 +2995,11 @@ export type BirthChartResponse = {
              */
             nakshatra: {
                 /**
-                 * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 arcminutes each. Determines dasha lord and behavioral qualities.
+                 * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 minutes each. Determines dasha lord and behavioral qualities.
                  */
                 name: string;
                 /**
-                 * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 arcminutes. Pada determines Navamsa sign and refines personality traits.
+                 * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 minutes. Pada determines Navamsa sign and refines personality traits.
                  */
                 pada: number;
                 /**
@@ -2927,6 +3019,41 @@ export type BirthChartResponse = {
              * Bhava (house) number 1-12, counted whole-sign from the Lagna (house 1 is the Lagna rashi; Lagna itself is house 1). Present on the D1 birth chart; divisional charts omit it.
              */
             house?: number;
+            /**
+             * Localized readings for this graha avastha states, present only when avasthaInfo true was sent. Each key mirrors the state field of the same name and carries a short meaning plus a one-sentence classical interpretation, so a client can label Yuva or Swapna without a second lookup call.
+             */
+            avasthaInfo?: {
+                awastha?: {
+                    /**
+                     * One or two word gloss of the state, suitable for a table cell beside the graha.
+                     */
+                    meaning: string;
+                    /**
+                     * Single-sentence classical reading of what the state does to the graha results, sourced from BPHS ch. 45, Saravali ch. 5 and Phaladeepika ch. 9. Localized by the lang query parameter.
+                     */
+                    interpretation: string;
+                };
+                jagradadi?: {
+                    /**
+                     * One or two word gloss of the state, suitable for a table cell beside the graha.
+                     */
+                    meaning: string;
+                    /**
+                     * Single-sentence classical reading of what the state does to the graha results, sourced from BPHS ch. 45, Saravali ch. 5 and Phaladeepika ch. 9. Localized by the lang query parameter.
+                     */
+                    interpretation: string;
+                };
+                deeptadi?: {
+                    /**
+                     * One or two word gloss of the state, suitable for a table cell beside the graha.
+                     */
+                    meaning: string;
+                    /**
+                     * Single-sentence classical reading of what the state does to the graha results, sourced from BPHS ch. 45, Saravali ch. 5 and Phaladeepika ch. 9. Localized by the lang query parameter.
+                     */
+                    interpretation: string;
+                };
+            };
             /**
              * Baladi avastha, the planetary age-state set by the graha degree within its sign: Bala (infant), Kumara (child), Yuva (adult, strongest results), Vriddha (old), Mrita (dead, weakest). Bands run forward in odd signs and reversed in even signs. D1 birth chart only.
              */
@@ -2963,6 +3090,22 @@ export type BirthChartRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
+    /**
+     * Set true to include a localized meaning and one-sentence classical interpretation beside each graha avastha state, under avasthaInfo on that graha in meta. Defaults to false, so an existing integration is byte-identical until it opts in. Saves a second call to GET /avasthas and the client-side join that would otherwise be needed to turn Yuva or Swapna into readable text.
+     */
+    avasthaInfo?: boolean;
+    /**
+     * Set true to also return Uranus, Neptune and Pluto, under the Sanskrit names Arun, Varun and Yam that Indian software prints for them. They arrive in a separate modernPlanets array, NOT inside meta, because classical Jyotish is defined over nine grahas: the moderns rule no sign, so they have no dignity, avastha, combustion or aspect strength and it would be fabrication to report one. Each carries longitude, rashi, degree in sign, nakshatra with pada and lord, and retrograde status. Defaults to false, so an existing integration is byte-identical until it opts in.
+     */
+    modernPlanets?: boolean;
 };
 export type NavamsaResponse = {
     /**
@@ -2991,11 +3134,11 @@ export type NavamsaResponse = {
                  */
                 nakshatra: {
                     /**
-                     * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 arcminutes each. Determines dasha lord and behavioral qualities.
+                     * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 minutes each. Determines dasha lord and behavioral qualities.
                      */
                     name: string;
                     /**
-                     * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 arcminutes. Pada determines Navamsa sign and refines personality traits.
+                     * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 minutes. Pada determines Navamsa sign and refines personality traits.
                      */
                     pada: number;
                     /**
@@ -3022,7 +3165,7 @@ export type NavamsaResponse = {
          */
         aries: {
             /**
-             * Zodiac sign name in lowercase.
+             * Zodiac sign name in lowercase. Always equals the key of the navamsa rashi-house block it sits in.
              */
             rashi: string;
             /**
@@ -3070,6 +3213,19 @@ export type NavamsaResponse = {
         };
         [key: string]: unknown;
     };
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Planets that are Vargottama (same sign in D1 and D9)
      */
@@ -3100,6 +3256,14 @@ export type NavamsaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type DivisionalChartResponse = {
     /**
@@ -3127,6 +3291,19 @@ export type DivisionalChartResponse = {
          */
         significance: string;
     };
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Divisional chart showing planetary positions across 12 rashi houses plus a meta lookup. Same structure as birth chart and navamsa responses.
      */
@@ -3153,11 +3330,11 @@ export type DivisionalChartResponse = {
                  */
                 nakshatra: {
                     /**
-                     * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 arcminutes each. Determines dasha lord and behavioral qualities.
+                     * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 minutes each. Determines dasha lord and behavioral qualities.
                      */
                     name: string;
                     /**
-                     * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 arcminutes. Pada determines Navamsa sign and refines personality traits.
+                     * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 minutes. Pada determines Navamsa sign and refines personality traits.
                      */
                     pada: number;
                     /**
@@ -3184,7 +3361,7 @@ export type DivisionalChartResponse = {
          */
         aries: {
             /**
-             * Zodiac sign name in lowercase.
+             * Zodiac sign name in lowercase. Always equals the key of the divisional rashi-house block it sits in.
              */
             rashi: string;
             /**
@@ -3258,12 +3435,33 @@ export type DivisionalChartRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
     /**
      * Divisional chart number. Each division reveals a specific life area. Supported: 2 (Hora, wealth), 3 (Drekkana, siblings), 4 (Chaturthamsa, property), 7 (Saptamsa, children), 9 (Navamsa, marriage), 10 (Dasamsa, career), 12 (Dwadasamsa, parents), 16 (Shodasamsa, vehicles), 20 (Vimsamsa, spirituality), 24 (Chaturvimsamsa, education), 27 (Bhamsa, strength), 30 (Trimsamsa, misfortunes), 40 (Khavedamsa, merit), 45 (Akshavedamsa, character), 60 (Shashtiamsa, past life karma).
      */
     division: number;
 };
 export type CompatibilityResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Total Ashtakoot Gun Milan score out of 36. Scores above 18 are considered compatible for marriage. Higher scores indicate stronger marital harmony.
      */
@@ -3382,6 +3580,14 @@ export type CompatibilityRequest = {
          */
         timezone?: number | string;
     };
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type PlanetaryPositionsResponse = {
     [key: string]: {
@@ -3410,11 +3616,11 @@ export type PlanetaryPositionsResponse = {
          */
         nakshatra: {
             /**
-             * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 arcminutes each.
+             * Nakshatra (lunar mansion) the planet occupies. One of 27 Vedic nakshatras spanning 13 degrees 20 minutes each.
              */
             name: string;
             /**
-             * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 arcminutes. Determines Navamsa sign.
+             * Nakshatra pada (quarter, 1-4). Each nakshatra divides into 4 padas of 3 degrees 20 minutes. Determines Navamsa sign.
              */
             pada: number;
             /**
@@ -3460,7 +3666,7 @@ export type PlanetaryPositionsResponse = {
          */
         isRetrograde: boolean;
         /**
-         * Whether the planet is combust (asta, moudhya). A planet is combust when too close to the Sun, weakening its significations. Combustion orbs vary by planet: Moon 12 deg, Mars 17 deg, Mercury 14 deg (12 deg if retrograde), Jupiter 11 deg, Venus 10 deg (8 deg if retrograde), Saturn 15 deg. Sun, Rahu, Ketu, and Lagna are never combust. Based on Surya Siddhanta combustion orbs.
+         * Whether the planet is combust (asta, moudhya). A planet is combust when too close to the Sun, weakening its significations. Limits per Surya Siddhanta: Moon 12 deg, Mars 17 deg, Mercury 14 deg (12 deg if retrograde), Jupiter 11 deg, Venus 10 deg (8 deg if retrograde), Saturn 15 deg. Compared against the difference in ecliptic longitude, which is the standard interpretive convention and matches what other Vedic software reports. It is a chart judgement and not a statement about naked-eye visibility, which additionally depends on the observer latitude: for that use the heliacal endpoint, which applies the same limits in the classical degrees of time. The field is omitted entirely for Sun, Rahu, Ketu and Lagna, since the question does not apply to them rather than the answer being no.
          */
         isCombust?: boolean;
         /**
@@ -3494,8 +3700,29 @@ export type PlanetaryPositionsRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type ManglikResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Whether Manglik dosha (Kuja dosha) is present based on Mars placement from Lagna
      */
@@ -3559,8 +3786,29 @@ export type ManglikRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type KalsarpaResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Whether Kalsarpa dosha (Kalsarpa yoga) is present, all planets hemmed between Rahu-Ketu axis
      */
@@ -3632,8 +3880,29 @@ export type KalsarpaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type SadhesatiResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Whether Sade Sati is currently active, Saturn transiting 12th, 1st, or 2nd house from natal Moon
      */
@@ -3691,6 +3960,14 @@ export type SadhesatiRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type YogaDetail = {
     /**
@@ -3713,6 +3990,10 @@ export type YogaDetail = {
      * Overall nature. Auspicious yogas (Pancha Mahapurusha, Gajakesari) bestow benefits; inauspicious yogas (Kemadruma) indicate challenges; Both denotes context-dependent effects.
      */
     quality: 'Positive' | 'Negative' | 'Both';
+    /**
+     * Nabhasa family this yoga belongs to, present only on the 32 Nabhasa distribution yogas: asraya (3, sign modality), dala (2, benefic or malefic kendra tenancy), akriti (20, bhava shape) and sankhya (7, count of occupied rasis). Absent on every other glossary row, which is most of the catalog, since those are single-combination yogas outside the Nabhasa scheme. Group or filter the catalog on this key; it is never translated.
+     */
+    family?: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
 };
 export type YogaDetectResponse = {
     /**
@@ -3740,14 +4021,35 @@ export type YogaDetectResponse = {
          */
         quality: 'Positive' | 'Negative' | 'Both';
         /**
-         * True if every classical condition for the yoga is satisfied by the given chart. False if any rule fails, including "almost-present" cases where dignity is met but kendra/aspect is not, and Nabhasa cases where the yoga matched its own rule but a stronger family outranked it under the classical precedence norms. Read `evidence` to tell those apart.
+         * Classical grouping, ALWAYS present on a detection verdict: one of the four Nabhasa families (asraya, dala, akriti, sankhya) or classical for the twelve single-combination yogas such as Gajakesari and the Pancha Mahapurusha. Group the verdict list on this key to render a Nabhasa result the way the tradition arranges it. Never translated, so grouping works identically under any lang.
+         */
+        family: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
+        /**
+         * True if every classical condition for the yoga is satisfied by the given chart. False means one of TWO different things: the rule failed, or the rule held and a stronger family outranked it. Read `suppressedBy` to tell those apart, which is exact and locale-independent; `evidence` says the same thing in English prose.
          */
         present: boolean;
+        /**
+         * Set ONLY when this yoga matched its own classical rule and was then silenced by a higher-ranking family, so `present` is false for a reason a practitioner reads very differently from a failed rule. Names the family that took precedence, under the four classical norms: Akriti outranks Asraya, and Akriti, Asraya and Dala each outrank Sankhya. Absent means the rule genuinely did not hold.
+         */
+        suppressedBy?: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
         /**
          * Human-readable rationale naming the specific rule that triggered or failed the detection, including planetary positions, dignity, kendradhipati status, lordship, malefic drishti, sign modality, or whole-chart bhava distribution. For a Nabhasa yoga that matched its own rule but was outranked, this names the precedence norm that silenced it, for example that an Akriti yoga outranks Asraya or that any other Nabhasa family suppresses Sankhya.
          */
         evidence?: string;
     }>;
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Count of yogas where present === true in this chart. Range 0-44, though real charts sit in the low single digits: the Nabhasa families are mutually constrained by the precedence norms, and most shape yogas are rare.
      */
@@ -3756,10 +4058,25 @@ export type YogaDetectResponse = {
      * Echo of the resolved birth data used for detection. Timezone is the numeric offset that the chart engine consumed (IANA names are resolved upstream).
      */
     birthDetails: {
+        /**
+         * Birth date the kundli was cast for, YYYY-MM-DD, echoed back from the request.
+         */
         date: string;
+        /**
+         * Birth time the kundli was cast for, 24-hour HH:MM:SS, echoed back from the request. Lagna moves roughly one rashi every two hours, so this is what pins the bhava-dependent yogas.
+         */
         time: string;
+        /**
+         * Birth latitude in decimal degrees, echoed back from the request. Feeds the local sidereal time behind the Lagna.
+         */
         latitude: number;
+        /**
+         * Birth longitude in decimal degrees, echoed back from the request. East is positive, west is negative.
+         */
         longitude: number;
+        /**
+         * Numeric UTC offset in decimal hours that the chart engine actually consumed. An IANA name sent on the request is resolved to its DST-correct offset upstream, so this is always a number.
+         */
         timezone: number;
     };
 };
@@ -3784,6 +4101,14 @@ export type YogaDetectRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 export type KpAyanamsaResponse = {
     /**
@@ -3893,9 +4218,9 @@ export type KpPlanetsRequest = {
      */
     timezone?: number | string;
     /**
-     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
      */
-    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
     /**
      * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
      */
@@ -3966,6 +4291,10 @@ export type KpCuspsResponse = {
     houseThemes: {
         [key: string]: Array<string>;
     };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus: 'general' | 'finance';
 };
 export type KpCuspsRequest = {
     /**
@@ -3989,9 +4318,9 @@ export type KpCuspsRequest = {
      */
     timezone?: number | string;
     /**
-     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
      */
-    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
     /**
      * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
      */
@@ -4027,7 +4356,7 @@ export type KpChartResponse = {
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used (KP Newcomb).
+         * Ayanamsa system used, echoing the ayanamsa field of the request: "kp-newcomb", "kp-old", "lahiri", "raman" or "custom".
          */
         ayanamsaType: string;
         /**
@@ -4316,6 +4645,10 @@ export type KpChartResponse = {
     houseThemes: {
         [key: string]: Array<string>;
     };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus: 'general' | 'finance';
 };
 export type KpChartRequest = {
     /**
@@ -4339,9 +4672,9 @@ export type KpChartRequest = {
      */
     timezone?: number | string;
     /**
-     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
      */
-    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
     /**
      * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
      */
@@ -4360,8 +4693,17 @@ export type KpRulingPlanetsResponse = {
      * Observer location coordinates
      */
     location: {
+        /**
+         * Observer latitude in decimal degrees, echoed back from the request. Sets the local sidereal time behind the KP ascendant and therefore the Lagna sublord.
+         */
         latitude: number;
+        /**
+         * Observer longitude in decimal degrees, echoed back from the request. East is positive, west is negative.
+         */
         longitude: number;
+        /**
+         * Numeric UTC offset in decimal hours the calculation consumed. An IANA name sent on the request is resolved to its DST-correct offset upstream, so this is always a number.
+         */
         timezone: number;
     };
     /**
@@ -4423,6 +4765,10 @@ export type KpRulingPlanetsResponse = {
     houseThemes?: {
         [key: string]: Array<string>;
     };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus?: 'general' | 'finance';
 };
 export type KpRulingPlanetsIntervalResponse = {
     /**
@@ -4618,6 +4964,10 @@ export type KpRulingPlanetsIntervalResponse = {
     houseThemes: {
         [key: string]: Array<string>;
     };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus: 'general' | 'finance';
 };
 export type KpSublordChangesResponse = {
     /**
@@ -4696,9 +5046,9 @@ export type KpSublordChangesRequest = {
      */
     timezone?: number | string;
     /**
-     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. Defaults to "kp-newcomb".
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to "kp-newcomb".
      */
-    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri';
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman';
     /**
      * Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to "mean".
      */
@@ -4773,9 +5123,9 @@ export type KpRasiChangesRequest = {
      */
     timezone?: number | string;
     /**
-     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. Defaults to "kp-newcomb".
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to "kp-newcomb".
      */
-    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri';
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman';
     /**
      * Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to "mean".
      */
@@ -4897,9 +5247,291 @@ export type KpPlanetsIntervalRequest = {
      */
     timezone?: number | string;
     /**
-     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. Defaults to "kp-newcomb".
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to "kp-newcomb".
      */
-    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri';
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman';
+    /**
+     * Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to "mean".
+     */
+    nodeType?: 'mean' | 'true';
+};
+/**
+ * A complete KP horary (Prashna) chart: the Ascendant from the number, the cusps and planets from the moment of the question, plus ruling planets and four-level significators.
+ */
+export type KpHoraryResponse = {
+    /**
+     * The number that was asked for, echoed so a stored chart is self describing.
+     */
+    horaryNumber: number;
+    /**
+     * UTC instant the chart was cast for, resolved from the date, time and timezone.
+     */
+    questionTime: string;
+    /**
+     * Sidereal frame used, echoed back.
+     */
+    ayanamsaType: string;
+    /**
+     * Degrees subtracted from every tropical longitude to produce this chart. Compare it against your reference software before treating a placement difference as a disagreement.
+     */
+    ayanamsaDegrees: number;
+    /**
+     * The Ascendant the horary number produced. This is the ONLY part of the chart that comes from the number; everything else comes from the sky at the moment of the question.
+     */
+    ascendant: {
+        /**
+         * Sidereal longitude of the horary Ascendant, taken as the MIDPOINT of the sub division the number names.
+         */
+        longitude: number;
+        /**
+         * Degrees into the sign, 0 to 30, which is what a chart displays.
+         */
+        degreeInSign: number;
+        /**
+         * Zodiac sign (rashi) of this point.
+         */
+        sign: string;
+        /**
+         * Nakshatra (star) this point falls in.
+         */
+        star: string;
+        /**
+         * Nakshatra lord (star lord), the second level of the KP hierarchy.
+         */
+        starLord: string;
+        /**
+         * Sub lord, the decisive level in KP. A cusp sub lord is what answers the question: it is read for whether the matter is promised, before any timing is attempted.
+         */
+        subLord: string;
+        /**
+         * KP horary number 1 to 249 of the sub division holding this point. Matches the standard published KP table.
+         */
+        kpNumber: number;
+        /**
+         * Sidereal longitude where this numbered sub division begins.
+         */
+        spanFrom: number;
+        /**
+         * Sidereal longitude where it ends. The Ascendant sits midway between this and spanFrom.
+         */
+        spanTo: number;
+    };
+    /**
+     * Twelve Placidus cusps, house 1 first. House 1 is the horary Ascendant; the other eleven follow from the house frame that Ascendant implies at this latitude.
+     */
+    cusps: Array<{
+        /**
+         * House (bhava) number 1 to 12.
+         */
+        house: number;
+        /**
+         * Sidereal longitude of the cusp.
+         */
+        longitude: number;
+        /**
+         * Zodiac sign (rashi) of this point.
+         */
+        sign: string;
+        /**
+         * Nakshatra (star) this point falls in.
+         */
+        star: string;
+        /**
+         * Nakshatra lord (star lord), the second level of the KP hierarchy.
+         */
+        starLord: string;
+        /**
+         * Sub lord, the decisive level in KP. A cusp sub lord is what answers the question: it is read for whether the matter is promised, before any timing is attempted.
+         */
+        subLord: string;
+        /**
+         * KP horary number 1 to 249 of the sub division holding this point. Matches the standard published KP table.
+         */
+        kpNumber: number;
+    }>;
+    /**
+     * The nine grahas at the moment of the question, placed against the horary cusps. These come from the real sky, not from the number.
+     */
+    planets: Array<{
+        /**
+         * Graha name.
+         */
+        planet: string;
+        /**
+         * Sidereal longitude at the moment of the question.
+         */
+        longitude: number;
+        /**
+         * Placidus house the graha occupies in this horary chart, counted against the cusps above rather than by whole sign.
+         */
+        house: number;
+        /**
+         * Retrograde motion flag.
+         */
+        isRetrograde: boolean;
+        /**
+         * Sub-sub lord, the fourth KP level, used to refine timing.
+         */
+        subSubLord: string;
+        /**
+         * Zodiac sign (rashi) of this point.
+         */
+        sign: string;
+        /**
+         * Nakshatra (star) this point falls in.
+         */
+        star: string;
+        /**
+         * Nakshatra lord (star lord), the second level of the KP hierarchy.
+         */
+        starLord: string;
+        /**
+         * Sub lord, the decisive level in KP. A cusp sub lord is what answers the question: it is read for whether the matter is promised, before any timing is attempted.
+         */
+        subLord: string;
+        /**
+         * KP horary number 1 to 249 of the sub division holding this point. Matches the standard published KP table.
+         */
+        kpNumber: number;
+    }>;
+    /**
+     * Ruling planets at the moment of the question. NOTE the lagna values here are from the TIME-based ascendant, which is the classical ruling-planet definition, not from the horary number.
+     */
+    rulingPlanets: {
+        /**
+         * Lord of the Hindu weekday, counted from sunrise.
+         */
+        dayLord: string;
+        /**
+         * Sign lord of the Moon.
+         */
+        moonSignLord: string;
+        /**
+         * Star lord of the Moon.
+         */
+        moonStarLord: string;
+        /**
+         * Sub lord of the Moon.
+         */
+        moonSublord: string;
+        /**
+         * Sub-sub lord of the Moon.
+         */
+        moonSubSublord: string;
+        /**
+         * Sign lord of the ascendant at the question moment.
+         */
+        lagnaSignLord: string;
+        /**
+         * Star lord of that ascendant.
+         */
+        lagnaStarLord: string;
+        /**
+         * Sub lord of that ascendant.
+         */
+        lagnaSublord: string;
+        /**
+         * Sub-sub lord of that ascendant.
+         */
+        lagnaSubSublord: string;
+        /**
+         * The distinct ruling planets in KP order of strength. They validate the chart: when they repeat the significators of the houses the question needs, the judgment is considered reliable.
+         */
+        rulingPlanets: Array<string>;
+    };
+    /**
+     * KP significators for event prediction and timing. Shows which planets signify each house (house-wise) and which houses each planet signifies (planet-wise). Strength order: Level 1 (planets in star of occupant) > Level 2 (occupants) > Level 3 (planets in star of owner) > Level 4 (house owner).
+     */
+    significators: {
+        houseWise: Array<{
+            /**
+             * House number 1-12
+             */
+            house: number;
+            significators: Array<{
+                /**
+                 * KP significator strength level (1-4). L1: planets in star of occupant (strongest). L2: occupant itself. L3: planets in star of owner. L4: sign owner. Lower number = stronger signification for this house.
+                 */
+                level: number;
+                /**
+                 * Human-readable label for this KP significator level.
+                 */
+                description: string;
+                /**
+                 * Planets signifying this house at this strength level.
+                 */
+                planets: Array<string>;
+            }>;
+            /**
+             * All significators in order of strength
+             */
+            all: Array<string>;
+        }>;
+        planetWise: Array<{
+            /**
+             * Vedic graha (planet) being analyzed for its house significations.
+             */
+            planet: string;
+            signifies: Array<{
+                /**
+                 * KP significator strength level (1-4). L1 strongest, L4 weakest.
+                 */
+                level: number;
+                /**
+                 * House numbers this planet signifies at this strength level.
+                 */
+                houses: Array<number>;
+            }>;
+            /**
+             * All houses signified in order of strength
+             */
+            allHouses: Array<number>;
+        }>;
+    };
+    /**
+     * Significations of each of the twelve bhavas (houses), keyed by house number 1 to 12, as short keywords. Bhava 1 is the Lagna (self, body, vitality), 2 wealth and speech, 4 home and mother, 7 marriage and partnership, 10 career and status, 11 gains. Use it to label the house numbers returned elsewhere in the response: a Vimshottari dasha period signifying houses 2, 7 and 8, or a KP significator carrying houses 11 and 6, becomes readable text without a separate lookup call. Returned once per response rather than repeated per period, and localized by the lang query parameter alongside every other interpretation field.
+     */
+    houseThemes: {
+        [key: string]: Array<string>;
+    };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus: 'general' | 'finance';
+};
+export type KpHoraryRequest = {
+    /**
+     * Horary number from 1 to 249, given by the querent while focused on their question. It maps to one of the 249 KP sub divisions of the zodiac, and that division sets the Ascendant of the chart. The querent should give the first number that comes to mind and use it once for that question; the astrologer never chooses it. Numbers outside 1 to 249 are rejected rather than wrapped, because a wrapped number would silently answer a different question.
+     */
+    horaryNumber: number;
+    /**
+     * Date the question was taken up for judgment, YYYY-MM-DD. Not a birth date: a horary chart needs no birth details at all, which is the point of the method.
+     */
+    date: string;
+    /**
+     * Time the question was taken up for judgment, 24-hour HH:MM:SS. In KP practice this is the moment the astrologer receives and understands the question, not the moment the querent first thought of it. It sets every planetary position and all twelve cusps except the Ascendant.
+     */
+    time: string;
+    /**
+     * Latitude where the question is judged, decimal degrees. The house cusps are Placidus and therefore latitude dependent, so this is the place of judgment, not the querent birthplace.
+     */
+    latitude: number;
+    /**
+     * Longitude where the question is judged, decimal degrees.
+     */
+    longitude: number;
+    /**
+     * Timezone: IANA name (e.g. "Asia/Kolkata") OR decimal hours from UTC. Defaults to 5.5.
+     */
+    timezone?: number | string;
+    /**
+     * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula (most common for KP). "kp-old" uses the Krishnamurti original table. "lahiri" uses Lahiri/Chitrapaksha ayanamsa matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa, about 1.45 degrees below Lahiri. "custom" allows providing your own value via ayanamsaValue. Defaults to "kp-newcomb".
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
     /**
      * Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to "mean".
      */
@@ -5071,6 +5703,19 @@ export type NakshatraResponse = {
  * Complete upagraha positions for a birth chart
  */
 export type UpagrahaResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Time-based upagrahas derived from the 8-part division of day or night. Gulika and Mandi are from Saturn segment, others from Sun, Mars, Mercury, Jupiter segments. Positions depend on birth time, location, and weekday.
      */
@@ -5159,11 +5804,32 @@ export type UpagrahaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 /**
  * Complete Ashtakavarga analysis for a birth chart
  */
 export type AshtakavargaResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Individual planetary strength grids (Bhinnashtakavarga). Eight entries: one for each of the 7 classical planets plus Lagna. Each entry shows how many of the 8 contributors (7 planets + Lagna) give benefic points to that planet in each of the 12 signs.
      */
@@ -5271,11 +5937,115 @@ export type AshtakavargaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 /**
  * Complete Shadbala (six-fold planetary strength) analysis for a birth chart per Brihat Parashara Hora Shastra (BPHS).
  */
 export type ShadbalaResponse = {
+    /**
+     * Localized name and one-line meaning for each of the six Shadbala components, keyed by the same field names each planet entry uses. Join it to render a readable strength breakdown in any of the eight supported languages instead of showing six untranslated Sanskrit terms.
+     */
+    balaThemes: {
+        /**
+         * Localized label and meaning for one Shadbala component.
+         */
+        sthanaBala: {
+            /**
+             * Localized name of this Shadbala component, suitable for a table header or a bar label.
+             */
+            name: string;
+            /**
+             * One-line localized explanation of what this component measures.
+             */
+            meaning: string;
+        };
+        /**
+         * Localized label and meaning for one Shadbala component.
+         */
+        digBala: {
+            /**
+             * Localized name of this Shadbala component, suitable for a table header or a bar label.
+             */
+            name: string;
+            /**
+             * One-line localized explanation of what this component measures.
+             */
+            meaning: string;
+        };
+        /**
+         * Localized label and meaning for one Shadbala component.
+         */
+        kalaBala: {
+            /**
+             * Localized name of this Shadbala component, suitable for a table header or a bar label.
+             */
+            name: string;
+            /**
+             * One-line localized explanation of what this component measures.
+             */
+            meaning: string;
+        };
+        /**
+         * Localized label and meaning for one Shadbala component.
+         */
+        chestaBala: {
+            /**
+             * Localized name of this Shadbala component, suitable for a table header or a bar label.
+             */
+            name: string;
+            /**
+             * One-line localized explanation of what this component measures.
+             */
+            meaning: string;
+        };
+        /**
+         * Localized label and meaning for one Shadbala component.
+         */
+        naisargikaBala: {
+            /**
+             * Localized name of this Shadbala component, suitable for a table header or a bar label.
+             */
+            name: string;
+            /**
+             * One-line localized explanation of what this component measures.
+             */
+            meaning: string;
+        };
+        /**
+         * Localized label and meaning for one Shadbala component.
+         */
+        drikBala: {
+            /**
+             * Localized name of this Shadbala component, suitable for a table header or a bar label.
+             */
+            name: string;
+            /**
+             * One-line localized explanation of what this component measures.
+             */
+            meaning: string;
+        };
+    };
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Shadbala analysis for all 7 classical planets. Ordered: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn. Each entry contains all 6 strength components, total strength in virupas and Rupas, Ishta/Kashta Phala, minimum required threshold, strength ratio, and relative rank.
      */
@@ -5297,7 +6067,7 @@ export type ShadbalaResponse = {
          */
         kalaBala: number;
         /**
-         * Chesta Bala (Motional Strength) in virupas. Based on planetary motion and retrogression. Retrograde planets score higher. Sun uses Ayana Chesta Bala (declination arc), Moon uses elongation from Sun. Other planets use Sheeghrochcha (mean anomaly) from Surya Siddhanta elements. Range 0 to 60.
+         * Chesta Bala (Motional Strength) in virupas. Based on planetary motion, so a retrograde graha scores higher because it is closer to Earth and working hardest. The Sun uses its Ayana Bala and the Moon its elongation from the Sun, per BPHS. Mars, Mercury, Jupiter, Venus and Saturn use the Sheeghra Kendra, the arc between the sheeghrochcha and the mean of the true and mean longitudes, with the roles of the mean Sun and the graha swapped for Mercury and Venus. Range 0 to 60.
          */
         chestaBala: number;
         /**
@@ -5305,7 +6075,7 @@ export type ShadbalaResponse = {
          */
         naisargikaBala: number;
         /**
-         * Drik Bala (Aspectual Strength) in virupas. Strength gained or lost from aspects received by other planets. Benefic aspects (Jupiter, Venus) add strength, malefic aspects (Sun, Mars, Saturn) reduce it. Can be negative when malefic aspects dominate. Uses Sputa Drishti with Vishesha (special) aspects for Mars, Jupiter, and Saturn.
+         * Drik Bala (Aspectual Strength) in virupas. Strength gained or lost from the aspects a graha receives. Benefic aspects add strength and malefic aspects reduce it, so this value is negative when malefics dominate. Mercury counts as benefic or malefic by the company it keeps in its own sign, decided by count with the nearest graha breaking a tie, and the Moon by its paksha. Uses the graded Sputa Drishti curve of BPHS Ch. 26 with the Vishesha (special) aspects of Mars, Jupiter and Saturn applied at their precise DEGREE ranges rather than by whole sign.
          */
         drikBala: number;
         /**
@@ -5359,11 +6129,32 @@ export type ShadbalaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 /**
  * The twelve Arudha padas of a birth chart, computed per the Jaimini rule with the classical exception applied.
  */
 export type ArudhaResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Zodiac sign of the Ascendant (Lagna), which anchors the twelve bhavas the padas are derived from.
      */
@@ -5451,11 +6242,32 @@ export type ArudhaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
 };
 /**
  * Chara Karakas for a birth chart: the movable significators of Jaimini astrology, ranked by how far each graha has advanced into its sign.
  */
 export type CharaKarakaResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
     /**
      * Scheme the ranking used, echoed back so a cached or logged response is self describing.
      */
@@ -5535,11 +6347,372 @@ export type CharaKarakaRequest = {
      * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
      */
     timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
     /**
      * Which Chara Karaka scheme to rank. "eight" includes Rahu, counting its degree in reverse because it moves retrograde, and returns eight offices including Pitrikaraka. "seven" ranks only the seven classical grahas and drops Pitrikaraka. Ketu is excluded from both, since it always mirrors the Rahu degree exactly. The two schemes can produce a different Atmakaraka for the same chart, so select the one your reference software uses. Defaults to "eight".
      */
     scheme?: 'seven' | 'eight';
 };
+/**
+ * Complete Bhava Bala (house strength) analysis per Brihat Parashara Hora Shastra, with a localized house-meaning legend.
+ */
+export type BhavaBalaResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
+    /**
+     * House frame the bhavas were built on. Always sripati: Bhava Bala is defined on unequal bhava madhyas, not on whole signs.
+     */
+    houseSystem: string;
+    /**
+     * Bhava Bala for all twelve houses in order, house 1 first. Each entry carries its own components so a client can explain a score rather than just display it.
+     */
+    bhavas: Array<{
+        /**
+         * Bhava (house) number 1 to 12, counted from the Lagna. House 1 is the Ascendant bhava, house 10 the career bhava, house 7 the partnership bhava.
+         */
+        house: number;
+        /**
+         * Zodiac sign holding this bhavas madhya (mid-cusp). Under the Sripati house system the bhavas are unequal, so this is NOT always the nth sign from the Lagna, and two bhavas can share a sign while another sign holds none.
+         */
+        rashi: string;
+        /**
+         * Bhava madhya (mid-cusp) longitude in degrees, sidereal Lahiri. The point every strength component below is measured at. Bhavas 1, 4, 7 and 10 sit on the Ascendant, IC, Descendant and Midheaven; the rest trisect the quadrants between them.
+         */
+        madhya: number;
+        /**
+         * Bhavadhipati (house lord), the ruler of the sign holding the madhya. Its Shadbala is what this bhava inherits, so a house ruled by a strong graha starts strong.
+         */
+        lord: string;
+        /**
+         * Bhavadhipati Bala in virupas: the total Shadbala of the house lord, carried across unchanged. The dominant term of the three, typically 250 to 650. Two bhavas ruled by the same graha therefore share this value exactly.
+         */
+        bhavadhipatiBala: number;
+        /**
+         * Bhava Digbala (directional strength) in virupas, 0 to 60 in steps of 10. Each rashi class is strongest in one cardinal bhava (human signs at the Lagna, quadruped at the 10th, watery at the 4th, Scorpio at the 7th) and loses 10 virupas per bhava of separation, reaching 0 at the seventh from it.
+         */
+        digBala: number;
+        /**
+         * Bhava Drishti Bala (aspectual strength) in virupas, computed on the bhava madhya exactly as Graha Drik Bala is computed on a graha. Benefic aspects add and malefic aspects subtract, so this term is often negative.
+         */
+        drishtiBala: number;
+        /**
+         * Total Bhava Bala in virupas, the sum of the three components above. Use it to compare houses within one chart: the strongest bhavas are the life areas that unfold with least resistance.
+         */
+        totalVirupas: number;
+        /**
+         * Total Bhava Bala in rupas (totalVirupas / 60). 1 rupa equals 60 virupas. Rupas are the conventional unit in classical tables.
+         */
+        totalRupas: number;
+        /**
+         * Strength rank among the twelve bhavas, 1 = strongest. Ranked on totalVirupas, so it never disagrees with the published totals.
+         */
+        rank: number;
+    }>;
+    /**
+     * Significations of each of the twelve bhavas (houses), keyed by house number 1 to 12, as short keywords. Bhava 1 is the Lagna (self, body, vitality), 2 wealth and speech, 4 home and mother, 7 marriage and partnership, 10 career and status, 11 gains. Use it to label the house numbers returned elsewhere in the response: a Vimshottari dasha period signifying houses 2, 7 and 8, or a KP significator carrying houses 11 and 6, becomes readable text without a separate lookup call. Returned once per response rather than repeated per period, and localized by the lang query parameter alongside every other interpretation field.
+     */
+    houseThemes: {
+        [key: string]: Array<string>;
+    };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus: 'general' | 'finance';
+};
+export type BhavaBalaRequest = {
+    /**
+     * Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).
+     */
+    date: string;
+    /**
+     * Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.
+     */
+    time: string;
+    /**
+     * Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.
+     */
+    latitude: number;
+    /**
+     * Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
+     */
+    longitude: number;
+    /**
+     * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
+     */
+    timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
+};
+/**
+ * Bhav Chalit (Chalit Kundli): every graha placed by unequal Sripati bhava, with the whole-sign placement beside it for comparison.
+ */
+export type BhavChalitResponse = {
+    /**
+     * The sidereal frame this response was computed in, so a cached or forwarded payload is self describing.
+     */
+    frame: {
+        /**
+         * Sidereal frame this chart was cast in, echoing the ayanamsa request field. "lahiri" when the field was omitted.
+         */
+        ayanamsa: string;
+        /**
+         * Degrees actually subtracted from every tropical longitude to produce this chart, read at the birth instant. Subtract it back to recover the tropical positions, or compare it against your reference software to confirm you are in the same frame before chasing a placement difference.
+         */
+        ayanamsaDegrees: number;
+    };
+    /**
+     * House frame used to build the bhavas. Always sripati for the Chalit chart.
+     */
+    houseSystem: string;
+    /**
+     * Sidereal Lahiri Ascendant in degrees. The madhya of bhava 1.
+     */
+    ascendant: number;
+    /**
+     * Sidereal Lahiri Midheaven in degrees. The madhya of bhava 10.
+     */
+    midheaven: number;
+    /**
+     * The twelve Sripati bhavas in order with their boundaries and occupants.
+     */
+    bhavas: Array<{
+        /**
+         * Bhava number 1 to 12.
+         */
+        house: number;
+        /**
+         * Bhava sandhi (junction) opening this bhava, in degrees. The midpoint between this madhya and the previous one. A graha exactly on a sandhi belongs to the bhava it opens.
+         */
+        start: number;
+        /**
+         * Bhava madhya (mid-cusp) in degrees. Bhavas 1, 4, 7 and 10 sit exactly on the Ascendant, IC, Descendant and Midheaven; the other eight trisect the quadrant arcs between them.
+         */
+        madhya: number;
+        /**
+         * Bhava sandhi closing this bhava. Identical to the next bhavas start, so the twelve bhavas tile the zodiac with no gap.
+         */
+        end: number;
+        /**
+         * Width of the bhava in degrees. Rarely 30: the Ascendant and Midheaven are only 90 degrees apart by coincidence of latitude and epoch, so quadrants stretch and squeeze and the bhavas with them.
+         */
+        span: number;
+        /**
+         * Sign holding the madhya. Because bhavas are unequal, two bhavas can share a sign while another sign holds no madhya at all.
+         */
+        rashi: string;
+        /**
+         * Grahas falling inside this bhava. Empty when the bhava is unoccupied.
+         */
+        grahas: Array<string>;
+    }>;
+    /**
+     * All nine grahas with both their Chalit bhava and their whole-sign Rashi house, plus a moved flag.
+     */
+    grahas: Array<{
+        /**
+         * Graha name. All nine are placed, the seven classical grahas plus the lunar nodes Rahu and Ketu.
+         */
+        graha: string;
+        /**
+         * Sidereal Lahiri longitude in degrees.
+         */
+        longitude: number;
+        /**
+         * Zodiac sign the graha occupies. Identical to the Rashi (D1) chart.
+         */
+        rashi: string;
+        /**
+         * Bhava the graha falls in under the unequal Sripati cusps. This is the Bhav Chalit placement and the reason the chart exists.
+         */
+        bhava: number;
+        /**
+         * House the same graha occupies in the whole-sign Rashi chart, counted from the Lagna sign. Returned alongside bhava so the difference is visible without a second request.
+         */
+        rashiHouse: number;
+        /**
+         * True when bhava and rashiHouse disagree, i.e. the graha changes house between the Rashi chart and the Chalit chart. These are the placements a practitioner opens this chart to check.
+         */
+        moved: boolean;
+    }>;
+    /**
+     * How many of the nine grahas change house between the Rashi chart and the Chalit chart. Zero is a perfectly normal result and means the two charts agree for this nativity.
+     */
+    movedCount: number;
+    /**
+     * Significations of each of the twelve bhavas (houses), keyed by house number 1 to 12, as short keywords. Bhava 1 is the Lagna (self, body, vitality), 2 wealth and speech, 4 home and mother, 7 marriage and partnership, 10 career and status, 11 gains. Use it to label the house numbers returned elsewhere in the response: a Vimshottari dasha period signifying houses 2, 7 and 8, or a KP significator carrying houses 11 and 6, becomes readable text without a separate lookup call. Returned once per response rather than repeated per period, and localized by the lang query parameter alongside every other interpretation field.
+     */
+    houseThemes: {
+        [key: string]: Array<string>;
+    };
+    /**
+     * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+     */
+    focus: 'general' | 'finance';
+};
+export type BhavChalitRequest = {
+    /**
+     * Birth date in YYYY-MM-DD format. Date determines planetary positions and nakshatra calculations for Vedic kundli (janam patri). Accurate birth date is essential for dashas, yoga calculations, and divisional charts (vargas).
+     */
+    date: string;
+    /**
+     * Birth time in 24-hour HH:MM:SS format. Time is CRITICAL for Lagna (Ascendant) calculation and house divisions. It changes every two hours roughly. Even minutes matter for accurate nakshatra pada and divisional chart (D9, D10) calculations. Without exact time, Lagna and house-based predictions will be incorrect.
+     */
+    time: string;
+    /**
+     * Birth location latitude in decimal degrees. Location determines local sidereal time for Lagna calculation and affects bhava (house) cusps. Example: Delhi 28.6139, Mumbai 19.0760, Kathmandu 27.7172.
+     */
+    latitude: number;
+    /**
+     * Birth location longitude in decimal degrees. Affects local time calculations and ayanamsha adjustments. Example: Delhi 77.2090, Mumbai 72.8777, Kathmandu 85.3240.
+     */
+    longitude: number;
+    /**
+     * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC (e.g. -5 for EST, 1 for CET). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly. Defaults to 5.5.
+     */
+    timezone?: number | string;
+    /**
+     * Sidereal frame (ayanamsa) the chart is cast in. "lahiri" is Lahiri/Chitrapaksha, the traditional Vedic standard used by most software, and is the default. "raman" is the B.V. Raman ayanamsa from Hindu Predictive Astrology, about 1.45 degrees below Lahiri. "kp-newcomb" and "kp-old" are the two Krishnamurti Paddhati frames. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. The frame rotates the whole zodiac, so a graha sitting within 1.45 degrees of a boundary can change rashi or nakshatra when you switch: pick the one your reference software uses and keep it.
+     */
+    ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
+    /**
+     * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
+     */
+    ayanamsaValue?: number;
+};
+/**
+ * Heliacal rising and setting status of the six visible grahas.
+ */
+export type HeliacalResponse = {
+    /**
+     * Local calendar date the verdicts were read for, echoed from the request.
+     */
+    date: string;
+    /**
+     * One entry per visible graha, in classical order. A graha is omitted only when no horizon crossing exists for it at this latitude on this day.
+     */
+    grahas: Array<{
+        /**
+         * Graha name. Only the six with a visible body appear: Moon, Mars, Mercury, Jupiter, Venus and Saturn. The Sun cannot be lost in his own glare, and Rahu and Ketu are computed points with nothing to see.
+         */
+        graha: string;
+        /**
+         * Whether the graha clears the Sun glare on this day. False is the state a practitioner calls asta or combust, during which classical muhurta withholds auspicious ceremonies, most strictly marriage while Jupiter or Venus is invisible.
+         */
+        visible: boolean;
+        /**
+         * Horizon this graha is currently judged at. West means it sets after the Sun and is an evening object, east that it rises before him and is a morning one.
+         */
+        horizon: 'east' | 'west';
+        /**
+         * Separation from the Sun in degrees of TIME (kalamsa), measured along the equator between the two bodies horizon crossings. This is the quantity Surya Siddhanta actually compares against the limit, and it is not the same as the difference of ecliptic longitudes: the two diverge by roughly 3 degrees at Mumbai and by more than 15 further north, because it accounts for the angle the ecliptic makes with the local horizon.
+         */
+        timeDegrees: number;
+        /**
+         * The limit in degrees of time this graha must clear to be seen, per Surya Siddhanta ch. IX vv.6-8 and ch. X.1: Moon 12, Jupiter 11, Saturn 15, Mars 17, Venus 10 or 8, Mercury 14 or 12. Larger means the graha is fainter and needs more distance from the Sun.
+         */
+        kalamsa: number;
+        /**
+         * Whether the graha is retrograde, which for Mercury and Venus tightens the limit (Venus 10 to 8, Mercury 14 to 12). Retrograde puts them near inferior conjunction where they are far closer to Earth, so the larger brighter disk survives closer to the Sun.
+         */
+        retrograde: boolean;
+        /**
+         * Plain angular separation of the two ecliptic longitudes, in degrees. Returned beside timeDegrees so the two measures can be compared: this is what a combustion flag on a birth chart uses, and the gap between them is precisely what a location-aware heliacal calculation adds.
+         */
+        longitudeSeparation: number;
+        /**
+         * The event that produced the current state, or null when none falls inside the search horizon (up to about one synodic period, so Mars can legitimately have none).
+         */
+        lastEvent: {
+            /**
+             * Udaya is heliacal rising, the graha re-emerging from the Sun rays and becoming visible again. Asta (also called lopa, moudhya or moudyami) is heliacal setting, the graha disappearing into them. Stable Sanskrit keys, never translated.
+             */
+            type: 'udaya' | 'asta';
+            /**
+             * Horizon the event happens at. East means it is read before sunrise, so the graha is a morning object; west means after sunset, an evening object. A graha crosses to the other horizon as it passes the Sun, which is why an asta and the udaya that follows it are usually on opposite horizons.
+             */
+            horizon: 'east' | 'west';
+            /**
+             * Local civil datetime of the event (YYYY-MM-DDTHH:MM:SS), being the moment the graha itself crosses the horizon on the day its verdict changes. That instant, rather than sunrise or sunset, is what published Asta tables print.
+             */
+            datetime: string;
+            /**
+             * Separation from the Sun in degrees of time on the event day, measured the way the classical rule requires. Sits just either side of kalamsa, since that crossing is what defines the event.
+             */
+            timeDegrees: number;
+            /**
+             * The limit that was crossed. Can differ from the current reading limit for Mercury and Venus, whose limit tightens when they are retrograde, so an asta entered while retrograde may be left at a different threshold.
+             */
+            kalamsa: number;
+        } | null;
+        /**
+         * The event that will end the current state, or null when none falls inside the search horizon. For an invisible graha this is the udaya a practitioner is waiting for, so it answers when Guru Asta or Shukra Asta lifts.
+         */
+        nextEvent: {
+            /**
+             * Udaya is heliacal rising, the graha re-emerging from the Sun rays and becoming visible again. Asta (also called lopa, moudhya or moudyami) is heliacal setting, the graha disappearing into them. Stable Sanskrit keys, never translated.
+             */
+            type: 'udaya' | 'asta';
+            /**
+             * Horizon the event happens at. East means it is read before sunrise, so the graha is a morning object; west means after sunset, an evening object. A graha crosses to the other horizon as it passes the Sun, which is why an asta and the udaya that follows it are usually on opposite horizons.
+             */
+            horizon: 'east' | 'west';
+            /**
+             * Local civil datetime of the event (YYYY-MM-DDTHH:MM:SS), being the moment the graha itself crosses the horizon on the day its verdict changes. That instant, rather than sunrise or sunset, is what published Asta tables print.
+             */
+            datetime: string;
+            /**
+             * Separation from the Sun in degrees of time on the event day, measured the way the classical rule requires. Sits just either side of kalamsa, since that crossing is what defines the event.
+             */
+            timeDegrees: number;
+            /**
+             * The limit that was crossed. Can differ from the current reading limit for Mercury and Venus, whose limit tightens when they are retrograde, so an asta entered while retrograde may be left at a different threshold.
+             */
+            kalamsa: number;
+        } | null;
+    }>;
+};
+export type HeliacalRequest = {
+    /**
+     * Local calendar date to judge, in YYYY-MM-DD format. There is deliberately no time field: heliacal visibility is a once-a-day verdict read at that day sunrise or sunset, so a clock time could only pick a different day.
+     */
+    date: string;
+    /**
+     * Observer latitude in decimal degrees, restricted to -60 to 60. Visibility depends on the observer, unlike the longitude orb every chart API reports, because the angle the ecliptic makes with the horizon decides how long a graha lingers after the Sun. Beyond this band the classical rule stops describing solar glare and starts describing polar horizon geometry, so it is declined rather than answered wrongly.
+     */
+    latitude: number;
+    /**
+     * Observer longitude in decimal degrees. Sets local sunrise and sunset, which are the instants the verdict is read at. Example: Mumbai 72.8777, Delhi 77.2090, London -0.1278.
+     */
+    longitude: number;
+    /**
+     * Timezone: IANA name (e.g. "Asia/Kolkata", "Europe/London") OR decimal hours from UTC. Fixes which local day the date refers to, and every datetime in the response is returned in it. Defaults to 5.5.
+     */
+    timezone?: number | string;
+};
 export type BasicCard = {
     /**
      * Unique card identifier in kebab-case (e.g. fool, ace-of-cups, queen-of-swords).
@@ -8746,7 +9919,7 @@ export type CalculateTransitAspectsResponses = {
                  */
                 summary: string;
                 /**
-                 * When this transit is most active and how long its influence lasts.
+                 * When this transit is most active and how long its influence lasts, localized. The bucket follows the speed of the transiting body: a few hours for the Moon, a few days for the Sun, Mercury, Venus and Mars, one to two weeks for Jupiter, several weeks for Saturn, and an extended period for Uranus, Neptune and Pluto.
                  */
                 timing: string;
                 /**
@@ -8819,7 +9992,7 @@ export type CalculateTransitAspectsResponses = {
                  * Aspect nature. Harmonious (trine, sextile) flows easily. Challenging (square, opposition) creates tension and growth. Neutral (conjunction) blends energies.
                  */
                 interpretation: 'harmonious' | 'challenging' | 'neutral';
-            };
+            } | null;
             /**
              * Transit aspect counts grouped by aspect type (conjunction, trine, square, opposition, sextile, etc.). Useful for quickly assessing the transit weather.
              */
@@ -10414,7 +11587,7 @@ export type CalculateCompatibilityResponses = {
             /**
              * Dominant element shared by both charts, or null if dominant elements differ.
              */
-            sharedElement: string;
+            sharedElement: string | null;
             /**
              * How the elemental balance between charts shapes the relationship dynamic.
              */
@@ -11908,7 +13081,7 @@ export type GenerateFixedStarsData = {
         /**
          * Conjunction orb in degrees, the maximum separation for a star to count as conjunct a chart point. Defaults to 1, maximum 3. Widen it to surface looser contacts or tighten it for only the closest hits.
          */
-        orb?: number;
+        orb?: number | null;
     };
     url: '/astrology/fixed-stars';
 };
@@ -12860,7 +14033,7 @@ export type GenerateBirthChartErrors = {
 export type GenerateBirthChartError = GenerateBirthChartErrors[keyof GenerateBirthChartErrors];
 export type GenerateBirthChartResponses = {
     /**
-     * D1 Rashi birth chart with all 12 houses, 9 grahas plus Lagna, combustion analysis (Surya Siddhanta orbs), planetary war detection, bhava interpretations, and a meta lookup keyed by planet name.
+     * D1 Rashi birth chart with all 12 houses, 9 grahas plus Lagna, combustion analysis (Surya Siddhanta limits, applied as the standard ecliptic longitude orb), planetary war detection, bhava interpretations, and a meta lookup keyed by planet name.
      */
     200: BirthChartResponse;
 };
@@ -13539,9 +14712,9 @@ export type GetCurrentDashaData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
+         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
          */
@@ -13681,6 +14854,10 @@ export type GetCurrentDashaResponses = {
         houseThemes?: {
             [key: string]: Array<string>;
         };
+        /**
+         * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+         */
+        focus?: 'general' | 'finance';
         /**
          * Birth Moon nakshatra number (1-27). This nakshatra determines the starting dasha lord in the Vimshottari 120-year cycle.
          */
@@ -13704,7 +14881,7 @@ export type GetCurrentDashaResponses = {
         /**
          * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old" or "custom". Echoed so a client can confirm which frame produced these dates without re-deriving it. When it reads "custom" the ayanamsa field above carries the exact value you supplied.
          */
-        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Mahadasha (major planetary period) in the 120-year Vimshottari dasha cycle. Start and end dates are determined by Moon nakshatra at birth.
          */
@@ -14349,9 +15526,9 @@ export type GetMajorDashasData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
+         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
          */
@@ -14491,6 +15668,10 @@ export type GetMajorDashasResponses = {
         houseThemes?: {
             [key: string]: Array<string>;
         };
+        /**
+         * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+         */
+        focus?: 'general' | 'finance';
         /**
          * Birth Moon nakshatra number (1-27) that determines the Vimshottari starting point.
          */
@@ -14514,7 +15695,7 @@ export type GetMajorDashasResponses = {
         /**
          * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old" or "custom". Echoed so a client can confirm which frame produced these dates without re-deriving it. When it reads "custom" the ayanamsa field above carries the exact value you supplied.
          */
-        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Remaining balance of the first Mahadasha at birth. Based on Moon degree within the birth nakshatra. partial dasha already elapsed before birth.
          */
@@ -14658,9 +15839,9 @@ export type GetSubDashasData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
+         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
          */
@@ -14805,6 +15986,10 @@ export type GetSubDashasResponses = {
         houseThemes?: {
             [key: string]: Array<string>;
         };
+        /**
+         * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+         */
+        focus?: 'general' | 'finance';
         /**
          * Ruling planet of the requested Mahadasha period.
          */
@@ -14820,7 +16005,7 @@ export type GetSubDashasResponses = {
         /**
          * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old" or "custom". Echoed so a client can confirm which frame produced these dates without re-deriving it. When it reads "custom" the ayanamsa field above carries the exact value you supplied.
          */
-        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Full details of the parent Mahadasha including start/end dates and duration.
          */
@@ -15035,9 +16220,9 @@ export type GetPratyantardashasData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
+         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
          */
@@ -15186,6 +16371,10 @@ export type GetPratyantardashasResponses = {
         houseThemes?: {
             [key: string]: Array<string>;
         };
+        /**
+         * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+         */
+        focus?: 'general' | 'finance';
         /**
          * Ruling planet of the requested Mahadasha period.
          */
@@ -15205,7 +16394,7 @@ export type GetPratyantardashasResponses = {
         /**
          * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old" or "custom". Echoed so a client can confirm which frame produced these dates without re-deriving it. When it reads "custom" the ayanamsa field above carries the exact value you supplied.
          */
-        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Full details of the parent Antardasha including start/end dates and duration.
          */
@@ -15428,9 +16617,9 @@ export type GetSookshmaDashasData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
+         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
          */
@@ -15583,6 +16772,10 @@ export type GetSookshmaDashasResponses = {
         houseThemes?: {
             [key: string]: Array<string>;
         };
+        /**
+         * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+         */
+        focus?: 'general' | 'finance';
         /**
          * Ruling planet of the requested Mahadasha period.
          */
@@ -15606,7 +16799,7 @@ export type GetSookshmaDashasResponses = {
         /**
          * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old" or "custom". Echoed so a client can confirm which frame produced these dates without re-deriving it. When it reads "custom" the ayanamsa field above carries the exact value you supplied.
          */
-        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Full details of the parent Pratyantardasha including start/end dates and duration.
          */
@@ -15837,9 +17030,9 @@ export type GetPranaDashasData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
+         * Ayanamsa system used to place the birth Moon in its nakshatra, which sets every dasha start and end date. "lahiri" uses Lahiri/Chitrapaksha, the traditional Vedic standard, and is the default. "kp-newcomb" uses the KP-Newcomb dynamic formula, matching Krishnamurti Paddhati software. "kp-old" uses the Krishnamurti original table from KP Reader-1. "raman" uses the B.V. Raman ayanamsa, the second frame traditional Indian software commonly offers beside Lahiri. "custom" takes your own value in degrees via ayanamsaValue, for reconciling exactly against a specific reference program. Switching frames shifts every dasha boundary by weeks, so pick the one your reference software uses.
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Custom ayanamsa value in degrees. When provided, overrides the computed ayanamsa from the selected type. Use for testing with specific ayanamsa values or matching a particular reference source.
          */
@@ -15996,6 +17189,10 @@ export type GetPranaDashasResponses = {
         houseThemes?: {
             [key: string]: Array<string>;
         };
+        /**
+         * Which signification vocabulary produced the houseThemes keywords in this response, echoing the focus query parameter. Always present, and "general" when the parameter was omitted. Read it to label a rendered house legend, or to tell two cached responses apart when only one asked for the finance lens.
+         */
+        focus?: 'general' | 'finance';
         /**
          * Ruling planet of the requested Mahadasha period.
          */
@@ -16023,7 +17220,7 @@ export type GetPranaDashasResponses = {
         /**
          * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old" or "custom". Echoed so a client can confirm which frame produced these dates without re-deriving it. When it reads "custom" the ayanamsa field above carries the exact value you supplied.
          */
-        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman' | 'custom';
         /**
          * Full details of the parent Sookshma dasha including start/end dates and duration.
          */
@@ -16654,30 +17851,34 @@ export type GetDetailedPanchangResponses = {
          */
         vara: {
             /**
-             * Hindu weekday name. Vara begins at local sunrise, not midnight.
+             * Weekday name in English. Vara begins at local sunrise, not at midnight, so a time before sunrise belongs to the previous vara.
              */
             name: string;
+            /**
+             * Vara name transliterated from Sanskrit: Ravivara, Somavara, Mangalavara, Budhavara, Guruvara, Shukravara, Shanivara. Use this rather than name for a Jyotish-facing reading, since it is the form the classical texts use and it does not change with the lang parameter.
+             */
+            sanskritName: string;
             /**
              * Ruling planet of the day (Vara lord). Influences day-level auspiciousness.
              */
             lord: string;
         };
         /**
-         * Local sunrise time in UTC. Marks the start of the Hindu day.
+         * Local sunrise in the requested timezone as YYYY-MM-DDTHH:MM:SS, with no zone suffix. Marks the start of the Hindu day.
          */
         sunrise: string;
         /**
-         * Local sunset time in UTC. Marks the transition to night muhurtas.
+         * Local sunset in the requested timezone as YYYY-MM-DDTHH:MM:SS, with no zone suffix. Marks the transition to night muhurtas.
          */
         sunset: string;
         /**
          * Moonrise time in the requested timezone. Can be null if Moon does not rise on this date.
          */
-        moonrise: string;
+        moonrise: string | null;
         /**
          * Moonset time in the requested timezone. Can be null if Moon does not set on this date.
          */
-        moonset: string;
+        moonset: string | null;
         /**
          * Moon sign (Chandra Rashi) at sunrise. Central to Vedic astrology. determines daily emotional tone, Chandrabalam, and Tarabalam.
          */
@@ -16842,11 +18043,11 @@ export type GetDetailedPanchangResponses = {
              */
             number: number;
             /**
-             * Start time of the current hora in UTC.
+             * Start time of the current hora, as local civil time in the requested timezone offset. The first hora of any day begins at local sunrise, so this equals the sunrise field when the hora number is 1.
              */
             start: string;
             /**
-             * End time of the current hora in UTC.
+             * End time of the current hora, as local civil time in the requested timezone offset. Day horas and night horas have different lengths, so a hora is only approximately 60 minutes.
              */
             end: string;
         };
@@ -16901,7 +18102,7 @@ export type GetDetailedPanchangResponses = {
              * Period end time in ISO 8601 format. Timezone-adjusted based on the input timezone offset.
              */
             end: string;
-        };
+        } | null;
         /**
          * Brahma Muhurta, sacred pre-dawn period approximately 96 minutes before sunrise (14th of 15 night muhurtas). Considered the best time for meditation, mantra japa, Vedic study, and spiritual sadhana. Referenced in Ashtanga Hridaya and Dharmashastra texts.
          */
@@ -16953,7 +18154,7 @@ export type GetDetailedPanchangResponses = {
              * Period end time in ISO 8601 format. Timezone-adjusted based on the input timezone offset.
              */
             end: string;
-        };
+        } | null;
         /**
          * Pratah Sandhya, morning twilight junction period for Sandhyavandanam prayer. Spans 3 night ghatis before sunrise to sunrise. Duration varies by location and season based on ratrimana (night duration). One of the three daily Sandhya prayer times prescribed in Dharmashastra.
          */
@@ -16966,7 +18167,7 @@ export type GetDetailedPanchangResponses = {
              * Period end time in ISO 8601 format. Timezone-adjusted based on the input timezone offset.
              */
             end: string;
-        };
+        } | null;
         /**
          * Sayahna Sandhya, evening twilight junction period for Sandhyavandanam prayer. Spans sunset to 3 night ghatis after sunset. Duration varies by location and season based on ratrimana (night duration). One of the three daily Sandhya prayer times prescribed in Dharmashastra.
          */
@@ -16979,7 +18180,7 @@ export type GetDetailedPanchangResponses = {
              * Period end time in ISO 8601 format. Timezone-adjusted based on the input timezone offset.
              */
             end: string;
-        };
+        } | null;
         /**
          * Dur Muhurta (Dur Muhurtam), inauspicious muhurta periods determined by the weekday. The daytime is divided into 15 muhurtas from sunrise to sunset. Specific muhurta numbers are inauspicious each weekday per Muhurta Chintamani. Each period lasts ~48 minutes. Most days have 2 Dur Muhurtas, Wednesday and Sunday have 1. Avoid initiating important activities during these periods.
          */
@@ -17056,15 +18257,15 @@ export type GetDetailedPanchangResponses = {
             /**
              * Panchaka dosha, set by the weekday the period BEGINS (not the nakshatra): Roga (Sunday, disease), Raja (Monday, government), Agni (Tuesday, fire), Chora (Friday, theft), Mrityu (Saturday, death). Null when Panchaka begins on Wednesday or Thursday (no dosha) or when no Panchaka touches this date.
              */
-            type: string;
+            type: string | null;
             /**
              * When the Panchaka period starts (Moon enters 300 degrees, Dhanishta 3rd pada). May predate this date when Panchaka is already running. Null when no Panchaka is in force or begins on this date. In requested timezone.
              */
-            startsAt: string;
+            startsAt: string | null;
             /**
              * When the Panchaka period ends (Moon exits Revati at 360 degrees), about five days after it starts. Null when no Panchaka. In requested timezone.
              */
-            endsAt: string;
+            endsAt: string | null;
         };
         /**
          * Bhadra (Vishti Karana), the 7th movable karana, avoided for all auspicious activities. Bhadra recurs roughly every 3 to 5 days and lasts about half a tithi. active is true whenever a Bhadra is attributed to this date; startsAt and endsAt give the window, which may end on the next calendar day.
@@ -17077,11 +18278,11 @@ export type GetDetailedPanchangResponses = {
             /**
              * When the Bhadra (Vishti) period that begins on this date starts. Null when no Bhadra begins on this date. In requested timezone.
              */
-            startsAt: string;
+            startsAt: string | null;
             /**
              * When the Bhadra (Vishti) period that begins on this date ends. May fall on the next calendar day. Null when no Bhadra begins on this date. In requested timezone.
              */
-            endsAt: string;
+            endsAt: string | null;
         };
         /**
          * Panchang element transition times. exact timing of when each element (tithi, yoga, karana, nakshatra, Moon sign) changes. Calculated using binary search for ~1 minute precision. Essential for precise muhurta determination and panchang calendars.
@@ -17294,6 +18495,9 @@ export type GetChoghadiyaResponses = {
      * 8 daytime and 8 nighttime Choghadiya muhurta periods with names, ruling planets, auspiciousness ratings (Good/Bad), and exact start/end times based on sunrise and sunset.
      */
     200: {
+        /**
+         * Calendar date the choghadiya muhurta table was computed for, YYYY-MM-DD, echoed back from the request. The day periods run from that date sunrise to its sunset, and the night periods run on to the next sunrise.
+         */
         date: string;
         /**
          * 8 daytime choghadiya periods (sunrise to sunset)
@@ -17530,7 +18734,12 @@ export type GetHoraResponse = GetHoraResponses[keyof GetHoraResponses];
 export type CheckManglikDoshaData = {
     body?: ManglikRequest;
     path?: never;
-    query?: never;
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+    };
     url: '/vedic-astrology/dosha/manglik';
 };
 export type CheckManglikDoshaErrors = {
@@ -17645,7 +18854,12 @@ export type CheckManglikDoshaResponse = CheckManglikDoshaResponses[keyof CheckMa
 export type CheckKalsarpaDoshaData = {
     body?: KalsarpaRequest;
     path?: never;
-    query?: never;
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+    };
     url: '/vedic-astrology/dosha/kalsarpa';
 };
 export type CheckKalsarpaDoshaErrors = {
@@ -17760,7 +18974,12 @@ export type CheckKalsarpaDoshaResponse = CheckKalsarpaDoshaResponses[keyof Check
 export type CheckSadhesatiData = {
     body?: SadhesatiRequest;
     path?: never;
-    query?: never;
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+    };
     url: '/vedic-astrology/dosha/sadhesati';
 };
 export type CheckSadhesatiErrors = {
@@ -17880,6 +19099,10 @@ export type ListYogasData = {
          * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
          */
         lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+        /**
+         * Filter the catalog to one Nabhasa family: asraya (3), dala (2), akriti (20) or sankhya (7). Omit for the full catalog. `classical` is accepted but matches nothing here, because it is a detection-verdict value for single-combination yogas rather than a catalog grouping.
+         */
+        family?: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
     };
     url: '/vedic-astrology/yoga';
 };
@@ -17991,20 +19214,24 @@ export type ListYogasResponses = {
      */
     200: {
         /**
-         * Array of all planetary yogas with basic identifiers. Use GET /yogas/:id for formation rules, effects, and quality classification.
+         * Array of planetary yogas with basic identifiers, narrowed by `family` when that filter is supplied. Use GET /yoga/{id} for formation rules, effects, and quality classification.
          */
         yogas: Array<{
             /**
-             * Unique yoga identifier in lowercase kebab-case. Use this to fetch full details via GET /yogas/:id.
+             * Unique yoga identifier in lowercase kebab-case. Use this to fetch full details via GET /yoga/{id}.
              */
             id: string;
             /**
              * Traditional Sanskrit name of the planetary yoga combination.
              */
             name: string;
+            /**
+             * Nabhasa family, present only on the 32 Nabhasa distribution yogas and absent on every other catalog row. Never translated, so it groups identically under any lang.
+             */
+            family?: 'classical' | 'asraya' | 'dala' | 'akriti' | 'sankhya';
         }>;
         /**
-         * Total count of planetary yogas in the database. Includes Raj Yogas, Dhan Yogas, Pancha Mahapurusha Yogas, Nabhasa Yogas, and more.
+         * Number of yogas in this response, which is the filtered count when `family` is supplied and the full catalog size otherwise. Includes Raj Yogas, Dhan Yogas, Pancha Mahapurusha Yogas, Nabhasa Yogas, and more.
          */
         total: number;
     };
@@ -18939,9 +20166,9 @@ export type GetKpRulingIntervalData = {
          */
         timezone?: number | string;
         /**
-         * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. Defaults to "kp-newcomb".
+         * Ayanamsa system for sidereal conversion. "kp-newcomb" uses the KP-Newcomb dynamic formula, the most common choice for KP astrology. "kp-old" uses the Krishnamurti original table from KP Reader-1 with constant precession rate. "lahiri" uses Lahiri/Chitrapaksha ayanamsa, matching most traditional Vedic software. "raman" uses the B.V. Raman ayanamsa from Hindu Predictive Astrology, a recognised traditional school that sits about 1.45 degrees below Lahiri. Defaults to "kp-newcomb".
          */
-        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'raman';
         /**
          * Lunar node type for Rahu and Ketu positions. "mean" uses the smooth mean node (traditional Vedic astrology default). "true" uses the osculating node with perturbation corrections, oscillating up to 1.5 degrees from mean with a 173-day period. Impacts KP sub-lord assignments in narrow boundary cases. Defaults to "mean".
          */
@@ -19414,6 +20641,130 @@ export type GetKpPlanetsIntervalResponses = {
     200: KpPlanetsIntervalResponse;
 };
 export type GetKpPlanetsIntervalResponse = GetKpPlanetsIntervalResponses[keyof GetKpPlanetsIntervalResponses];
+export type CastKpHoraryChartData = {
+    body?: KpHoraryRequest;
+    path?: never;
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+        /**
+         * Which signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use "finance" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to "general".
+         */
+        focus?: 'general' | 'finance';
+    };
+    url: '/vedic-astrology/kp/horary';
+};
+export type CastKpHoraryChartErrors = {
+    /**
+     * Validation error. `issues[]` lists every failed field.
+     */
+    400: {
+        /**
+         * First issue summary.
+         */
+        error: string;
+        code: 'validation_error';
+        /**
+         * Every validation failure. Use this to rebuild a valid request.
+         */
+        issues: Array<{
+            /**
+             * Dot-separated field path, or "(root)" for top-level.
+             */
+            path: string;
+            message: string;
+            /**
+             * Zod issue code (invalid_type, too_small, too_big, invalid_string, ...).
+             */
+            code?: string;
+            /**
+             * Expected type for invalid_type.
+             */
+            expected?: string;
+            /**
+             * Minimum bound for too_small issues.
+             */
+            minimum?: number | string;
+            /**
+             * Maximum bound for too_big issues.
+             */
+            maximum?: number | string;
+            inclusive?: boolean;
+            /**
+             * Format name for string issues (regex, email, url, uuid).
+             */
+            format?: string;
+            /**
+             * Regex pattern when format is regex.
+             */
+            pattern?: string;
+        }>;
+    };
+    /**
+     * Invalid or missing API key
+     */
+    401: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
+     */
+    405: {
+        error: string;
+        code: 'method_not_allowed';
+        /**
+         * Allowed HTTP methods for this path. Mirrors the Allow response header.
+         */
+        allow: Array<string>;
+        /**
+         * Link to the product page for this domain.
+         */
+        docs?: string;
+    };
+    /**
+     * Monthly rate limit exceeded
+     */
+    429: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Internal server error
+     */
+    500: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+};
+export type CastKpHoraryChartError = CastKpHoraryChartErrors[keyof CastKpHoraryChartErrors];
+export type CastKpHoraryChartResponses = {
+    /**
+     * Horary chart with the Ascendant from the number, Placidus cusps, planets at the question moment, ruling planets, and four-level significators.
+     */
+    200: KpHoraryResponse;
+};
+export type CastKpHoraryChartResponse = CastKpHoraryChartResponses[keyof CastKpHoraryChartResponses];
 export type CalculateDrishtiData = {
     body?: {
         /**
@@ -20167,11 +21518,11 @@ export type CalculateTransitResponses = {
      */
     200: {
         /**
-         * Birth datetime used for the natal chart (UTC ISO 8601).
+         * Birth datetime used for the natal chart, echoed as the local civil date and time supplied in the request (YYYY-MM-DDTHH:MM:SS). Combine it with the timezone field to recover the UTC instant.
          */
         birthDatetime: string;
         /**
-         * Transit datetime being analyzed (UTC ISO 8601).
+         * Transit datetime being analyzed, echoed as the local civil date and time supplied in the request (YYYY-MM-DDTHH:MM:SS). Gochar positions are computed for this moment and overlaid on the natal chart.
          */
         transitDatetime: string;
         /**
@@ -20179,7 +21530,7 @@ export type CalculateTransitResponses = {
          */
         natalPlanets: Array<{
             /**
-             * Planet name (Sun through Ketu plus Lagna).
+             * Graha name, Sun through Ketu. The Lagna is not one of these entries; it is a house frame rather than a body, and the natal house numbers on every entry are counted from it.
              */
             name: string;
             /**
@@ -20196,7 +21547,7 @@ export type CalculateTransitResponses = {
             house: number;
         }>;
         /**
-         * Current planetary positions overlaid on the natal chart with house placements and aspects.
+         * Current planetary positions overlaid on the natal chart with house placements, aspects, and the Gochara Kaksha verdict for each graha.
          */
         transitingPlanets: Array<{
             /**
@@ -20232,6 +21583,35 @@ export type CalculateTransitResponses = {
                  */
                 orb: number;
             }>;
+            /**
+             * Gochara Kaksha: the ashtakavarga-qualified reading of this transit. The sign says where a graha is, this says whether the exact stretch it currently occupies is one its own Bhinnashtakavarga supports, which is the classical way of refining a transit verdict from sign-level to under four degrees.
+             */
+            kaksha: {
+                /**
+                 * Kaksha number 1-8 within the current sign. Each sign divides into eight kakshas of 3 degrees 45 minutes, crossed in order, so this is how far through the sign the graha has travelled.
+                 */
+                number: number;
+                /**
+                 * Graha ruling this kaksha. The eight lords run Saturn, Jupiter, Mars, Sun, Venus, Mercury, Moon, Lagna from the start of every sign, ordered by how long each takes to cross a sign.
+                 */
+                lord: string;
+                /**
+                 * Degree within the sign where this kaksha begins (0, 3.75, 7.5 and so on).
+                 */
+                startDegree: number;
+                /**
+                 * Degree within the sign where this kaksha ends.
+                 */
+                endDegree: number;
+                /**
+                 * Whether this kaksha lord gave the transiting graha a bindu in the sign being transited, which is the Gochara Kaksha verdict: true reads as a favourable stretch of the transit, false as an unfavourable one. Null means the question does not apply rather than that the answer is no, because Rahu and Ketu have no Bhinnashtakavarga to read. Never render null as unfavourable.
+                 */
+                bindu: boolean | null;
+                /**
+                 * Bindus the transiting graha holds in this whole sign, 0-8, or null for Rahu and Ketu. Context for the verdict, since the same kaksha reads differently in a sign worth 7 than in one worth 1.
+                 */
+                binduCount: number | null;
+            };
         }>;
         /**
          * Highlighted transits from slow-moving planets (Jupiter, Saturn, Rahu, Ketu), most impactful for Gochar analysis.
@@ -20587,7 +21967,7 @@ export type CalculateParallelsResponses = {
      */
     200: {
         /**
-         * UTC datetime used for declination calculation (ISO 8601).
+         * Datetime used for the declination calculation, echoed as the local civil date and time supplied in the request (YYYY-MM-DDTHH:MM:SS). The timezone field of the request is what converts it to the instant the declinations are computed for.
          */
         datetime: string;
         /**
@@ -21610,21 +22990,141 @@ export type GetUpagrahaPositionsErrors = {
         code: string;
     };
 };
-export type GetUpagrahaPositionsError = GetUpagrahaPositionsErrors[keyof GetUpagrahaPositionsErrors];
-export type GetUpagrahaPositionsResponses = {
+export type GetUpagrahaPositionsError = GetUpagrahaPositionsErrors[keyof GetUpagrahaPositionsErrors];
+export type GetUpagrahaPositionsResponses = {
+    /**
+     * All 11 upagraha positions with rashi, nakshatra, and pada details.
+     */
+    200: UpagrahaResponse;
+};
+export type GetUpagrahaPositionsResponse = GetUpagrahaPositionsResponses[keyof GetUpagrahaPositionsResponses];
+export type CalculateAshtakavargaData = {
+    body?: AshtakavargaRequest;
+    path?: never;
+    query?: never;
+    url: '/vedic-astrology/ashtakavarga';
+};
+export type CalculateAshtakavargaErrors = {
+    /**
+     * Validation error. `issues[]` lists every failed field.
+     */
+    400: {
+        /**
+         * First issue summary.
+         */
+        error: string;
+        code: 'validation_error';
+        /**
+         * Every validation failure. Use this to rebuild a valid request.
+         */
+        issues: Array<{
+            /**
+             * Dot-separated field path, or "(root)" for top-level.
+             */
+            path: string;
+            message: string;
+            /**
+             * Zod issue code (invalid_type, too_small, too_big, invalid_string, ...).
+             */
+            code?: string;
+            /**
+             * Expected type for invalid_type.
+             */
+            expected?: string;
+            /**
+             * Minimum bound for too_small issues.
+             */
+            minimum?: number | string;
+            /**
+             * Maximum bound for too_big issues.
+             */
+            maximum?: number | string;
+            inclusive?: boolean;
+            /**
+             * Format name for string issues (regex, email, url, uuid).
+             */
+            format?: string;
+            /**
+             * Regex pattern when format is regex.
+             */
+            pattern?: string;
+        }>;
+    };
+    /**
+     * Invalid or missing API key
+     */
+    401: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
+     */
+    405: {
+        error: string;
+        code: 'method_not_allowed';
+        /**
+         * Allowed HTTP methods for this path. Mirrors the Allow response header.
+         */
+        allow: Array<string>;
+        /**
+         * Link to the product page for this domain.
+         */
+        docs?: string;
+    };
+    /**
+     * Monthly rate limit exceeded
+     */
+    429: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Internal server error
+     */
+    500: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+};
+export type CalculateAshtakavargaError = CalculateAshtakavargaErrors[keyof CalculateAshtakavargaErrors];
+export type CalculateAshtakavargaResponses = {
     /**
-     * All 11 upagraha positions with rashi, nakshatra, and pada details.
+     * Complete Ashtakavarga with Bhinnashtakavarga, Sarvashtakavarga (337-point), Reduced Ashtakavarga (Trikona + Ekadipati Shodhana), and Shodhya Pinda planetary strength.
      */
-    200: UpagrahaResponse;
+    200: AshtakavargaResponse;
 };
-export type GetUpagrahaPositionsResponse = GetUpagrahaPositionsResponses[keyof GetUpagrahaPositionsResponses];
-export type CalculateAshtakavargaData = {
-    body?: AshtakavargaRequest;
+export type CalculateAshtakavargaResponse = CalculateAshtakavargaResponses[keyof CalculateAshtakavargaResponses];
+export type CalculateShadbalaData = {
+    body?: ShadbalaRequest;
     path?: never;
-    query?: never;
-    url: '/vedic-astrology/ashtakavarga';
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+    };
+    url: '/vedic-astrology/shadbala';
 };
-export type CalculateAshtakavargaErrors = {
+export type CalculateShadbalaErrors = {
     /**
      * Validation error. `issues[]` lists every failed field.
      */
@@ -21725,21 +23225,30 @@ export type CalculateAshtakavargaErrors = {
         code: string;
     };
 };
-export type CalculateAshtakavargaError = CalculateAshtakavargaErrors[keyof CalculateAshtakavargaErrors];
-export type CalculateAshtakavargaResponses = {
+export type CalculateShadbalaError = CalculateShadbalaErrors[keyof CalculateShadbalaErrors];
+export type CalculateShadbalaResponses = {
     /**
-     * Complete Ashtakavarga with Bhinnashtakavarga, Sarvashtakavarga (337-point), Reduced Ashtakavarga (Trikona + Ekadipati Shodhana), and Shodhya Pinda planetary strength.
+     * Complete Shadbala with 6 strength components, Ishta/Kashta Phala, strength ratios, and relative ranking for all 7 planets.
      */
-    200: AshtakavargaResponse;
+    200: ShadbalaResponse;
 };
-export type CalculateAshtakavargaResponse = CalculateAshtakavargaResponses[keyof CalculateAshtakavargaResponses];
-export type CalculateShadbalaData = {
-    body?: ShadbalaRequest;
+export type CalculateShadbalaResponse = CalculateShadbalaResponses[keyof CalculateShadbalaResponses];
+export type ListAvasthasData = {
+    body?: never;
     path?: never;
-    query?: never;
-    url: '/vedic-astrology/shadbala';
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+        /**
+         * Return only the states of one system: "baladi" (5), "jagradadi" (3) or "deeptadi" (9). Omit for all 17.
+         */
+        system?: 'baladi' | 'jagradadi' | 'deeptadi';
+    };
+    url: '/vedic-astrology/avasthas';
 };
-export type CalculateShadbalaErrors = {
+export type ListAvasthasErrors = {
     /**
      * Validation error. `issues[]` lists every failed field.
      */
@@ -21840,30 +23349,52 @@ export type CalculateShadbalaErrors = {
         code: string;
     };
 };
-export type CalculateShadbalaError = CalculateShadbalaErrors[keyof CalculateShadbalaErrors];
-export type CalculateShadbalaResponses = {
+export type ListAvasthasError = ListAvasthasErrors[keyof ListAvasthasErrors];
+export type ListAvasthasResponses = {
     /**
-     * Complete Shadbala with 6 strength components, Ishta/Kashta Phala, strength ratios, and relative ranking for all 7 planets.
+     * Avastha states with their labels and interpretations, in system order.
      */
-    200: ShadbalaResponse;
+    200: Array<{
+        /**
+         * Unique slug for the avastha state. It is the lowercased form of the state name the birth chart returns, so a chart value maps straight onto this record.
+         */
+        id: string;
+        /**
+         * Sanskrit name of the state, exactly as it appears in the `awastha`, `jagradadi` or `deeptadi` field of a birth chart.
+         */
+        name: string;
+        /**
+         * Which avastha system the state belongs to, and therefore which birth-chart field it appears in. "baladi" is the five-fold age state set by degree within the sign and appears in `awastha`. "jagradadi" is the three-fold waking state set by sign dignity. "deeptadi" is the nine-fold dispositional state. Baladi applies to every body; the other two apply to the seven classical grahas only.
+         */
+        system: 'baladi' | 'jagradadi' | 'deeptadi';
+        /**
+         * Short label for the state, sized for a table cell beside the graha.
+         */
+        meaning: string;
+        /**
+         * What the state means for the results the graha delivers, which is the whole purpose of reading an avastha: the chart says where a graha is, the avastha says how much of its promise it can keep.
+         */
+        interpretation: string;
+    }>;
 };
-export type CalculateShadbalaResponse = CalculateShadbalaResponses[keyof CalculateShadbalaResponses];
-export type ListAvasthasData = {
+export type ListAvasthasResponse = ListAvasthasResponses[keyof ListAvasthasResponses];
+export type GetAvasthaData = {
     body?: never;
-    path?: never;
+    path: {
+        /**
+         * Avastha slug. Baladi: bala, kumara, yuva, vriddha, mrita. Jagradadi: jagrat, swapna, sushupti. Deeptadi: dipta, svastha, pramudita, shanta, dina, duhkhita, vikala, khala, kopa.
+         */
+        id: 'bala' | 'kumara' | 'yuva' | 'vriddha' | 'mrita' | 'jagrat' | 'swapna' | 'sushupti' | 'dipta' | 'svastha' | 'pramudita' | 'shanta' | 'dina' | 'duhkhita' | 'vikala' | 'khala' | 'kopa';
+    };
     query?: {
         /**
          * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
          */
         lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
-        /**
-         * Return only the states of one system: "baladi" (5), "jagradadi" (3) or "deeptadi" (9). Omit for all 17.
-         */
-        system?: 'baladi' | 'jagradadi' | 'deeptadi';
     };
-    url: '/vedic-astrology/avasthas';
+    url: '/vedic-astrology/avasthas/{id}';
 };
-export type ListAvasthasErrors = {
+export type GetAvasthaErrors = {
     /**
      * Validation error. `issues[]` lists every failed field.
      */
@@ -21922,6 +23453,19 @@ export type ListAvasthasErrors = {
          */
         code: string;
     };
+    /**
+     * No avastha state matches that slug.
+     */
+    404: {
+        /**
+         * Human-readable error message. May change wording — do not parse programmatically.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier for programmatic error handling.
+         */
+        code: string;
+    };
     /**
      * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
@@ -21964,12 +23508,12 @@ export type ListAvasthasErrors = {
         code: string;
     };
 };
-export type ListAvasthasError = ListAvasthasErrors[keyof ListAvasthasErrors];
-export type ListAvasthasResponses = {
+export type GetAvasthaError = GetAvasthaErrors[keyof GetAvasthaErrors];
+export type GetAvasthaResponses = {
     /**
-     * Avastha states with their labels and interpretations, in system order.
+     * The avastha state with its system, label and interpretation.
      */
-    200: Array<{
+    200: {
         /**
          * Unique slug for the avastha state. It is the lowercased form of the state name the birth chart returns, so a chart value maps straight onto this record.
          */
@@ -21990,26 +23534,21 @@ export type ListAvasthasResponses = {
          * What the state means for the results the graha delivers, which is the whole purpose of reading an avastha: the chart says where a graha is, the avastha says how much of its promise it can keep.
          */
         interpretation: string;
-    }>;
-};
-export type ListAvasthasResponse = ListAvasthasResponses[keyof ListAvasthasResponses];
-export type GetAvasthaData = {
-    body?: never;
-    path: {
-        /**
-         * Avastha slug. Baladi: bala, kumara, yuva, vriddha, mrita. Jagradadi: jagrat, swapna, sushupti. Deeptadi: dipta, svastha, pramudita, shanta, dina, duhkhita, vikala, khala, kopa.
-         */
-        id: 'bala' | 'kumara' | 'yuva' | 'vriddha' | 'mrita' | 'jagrat' | 'swapna' | 'sushupti' | 'dipta' | 'svastha' | 'pramudita' | 'shanta' | 'dina' | 'duhkhita' | 'vikala' | 'khala' | 'kopa';
     };
+};
+export type GetAvasthaResponse = GetAvasthaResponses[keyof GetAvasthaResponses];
+export type CalculateArudhaPadasData = {
+    body?: ArudhaRequest;
+    path?: never;
     query?: {
         /**
          * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
          */
         lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
     };
-    url: '/vedic-astrology/avasthas/{id}';
+    url: '/vedic-astrology/arudha';
 };
-export type GetAvasthaErrors = {
+export type CalculateArudhaPadasErrors = {
     /**
      * Validation error. `issues[]` lists every failed field.
      */
@@ -22069,15 +23608,122 @@ export type GetAvasthaErrors = {
         code: string;
     };
     /**
-     * No avastha state matches that slug.
+     * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
      */
-    404: {
+    405: {
+        error: string;
+        code: 'method_not_allowed';
         /**
-         * Human-readable error message. May change wording — do not parse programmatically.
+         * Allowed HTTP methods for this path. Mirrors the Allow response header.
+         */
+        allow: Array<string>;
+        /**
+         * Link to the product page for this domain.
+         */
+        docs?: string;
+    };
+    /**
+     * Monthly rate limit exceeded
+     */
+    429: {
+        /**
+         * Human-readable error message. May change wording.
          */
         error: string;
         /**
-         * Machine-readable error code. Stable identifier for programmatic error handling.
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Internal server error
+     */
+    500: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+};
+export type CalculateArudhaPadasError = CalculateArudhaPadasErrors[keyof CalculateArudhaPadasErrors];
+export type CalculateArudhaPadasResponses = {
+    /**
+     * All twelve Arudha padas with derivation detail, plus the Arudha Lagna and Upapada lifted to the top level.
+     */
+    200: ArudhaResponse;
+};
+export type CalculateArudhaPadasResponse = CalculateArudhaPadasResponses[keyof CalculateArudhaPadasResponses];
+export type CalculateCharaKarakasData = {
+    body?: CharaKarakaRequest;
+    path?: never;
+    query?: {
+        /**
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
+         */
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+    };
+    url: '/vedic-astrology/chara-karakas';
+};
+export type CalculateCharaKarakasErrors = {
+    /**
+     * Validation error. `issues[]` lists every failed field.
+     */
+    400: {
+        /**
+         * First issue summary.
+         */
+        error: string;
+        code: 'validation_error';
+        /**
+         * Every validation failure. Use this to rebuild a valid request.
+         */
+        issues: Array<{
+            /**
+             * Dot-separated field path, or "(root)" for top-level.
+             */
+            path: string;
+            message: string;
+            /**
+             * Zod issue code (invalid_type, too_small, too_big, invalid_string, ...).
+             */
+            code?: string;
+            /**
+             * Expected type for invalid_type.
+             */
+            expected?: string;
+            /**
+             * Minimum bound for too_small issues.
+             */
+            minimum?: number | string;
+            /**
+             * Maximum bound for too_big issues.
+             */
+            maximum?: number | string;
+            inclusive?: boolean;
+            /**
+             * Format name for string issues (regex, email, url, uuid).
+             */
+            format?: string;
+            /**
+             * Regex pattern when format is regex.
+             */
+            pattern?: string;
+        }>;
+    };
+    /**
+     * Invalid or missing API key
+     */
+    401: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
          */
         code: string;
     };
@@ -22123,47 +23769,154 @@ export type GetAvasthaErrors = {
         code: string;
     };
 };
-export type GetAvasthaError = GetAvasthaErrors[keyof GetAvasthaErrors];
-export type GetAvasthaResponses = {
+export type CalculateCharaKarakasError = CalculateCharaKarakasErrors[keyof CalculateCharaKarakasErrors];
+export type CalculateCharaKarakasResponses = {
     /**
-     * The avastha state with its system, label and interpretation.
+     * Karaka offices in descending rank with the ranking degree for each, plus the Atmakaraka and Darakaraka lifted to the top level.
      */
-    200: {
+    200: CharaKarakaResponse;
+};
+export type CalculateCharaKarakasResponse = CalculateCharaKarakasResponses[keyof CalculateCharaKarakasResponses];
+export type CalculateBhavaBalaData = {
+    body?: BhavaBalaRequest;
+    path?: never;
+    query?: {
         /**
-         * Unique slug for the avastha state. It is the lowercased form of the state name the birth chart returns, so a chart value maps straight onto this record.
+         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
          */
-        id: string;
+        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
         /**
-         * Sanskrit name of the state, exactly as it appears in the `awastha`, `jagradadi` or `deeptadi` field of a birth chart.
+         * Which signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use "finance" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to "general".
          */
-        name: string;
+        focus?: 'general' | 'finance';
+    };
+    url: '/vedic-astrology/bhava-bala';
+};
+export type CalculateBhavaBalaErrors = {
+    /**
+     * Validation error. `issues[]` lists every failed field.
+     */
+    400: {
         /**
-         * Which avastha system the state belongs to, and therefore which birth-chart field it appears in. "baladi" is the five-fold age state set by degree within the sign and appears in `awastha`. "jagradadi" is the three-fold waking state set by sign dignity. "deeptadi" is the nine-fold dispositional state. Baladi applies to every body; the other two apply to the seven classical grahas only.
+         * First issue summary.
          */
-        system: 'baladi' | 'jagradadi' | 'deeptadi';
+        error: string;
+        code: 'validation_error';
         /**
-         * Short label for the state, sized for a table cell beside the graha.
+         * Every validation failure. Use this to rebuild a valid request.
          */
-        meaning: string;
+        issues: Array<{
+            /**
+             * Dot-separated field path, or "(root)" for top-level.
+             */
+            path: string;
+            message: string;
+            /**
+             * Zod issue code (invalid_type, too_small, too_big, invalid_string, ...).
+             */
+            code?: string;
+            /**
+             * Expected type for invalid_type.
+             */
+            expected?: string;
+            /**
+             * Minimum bound for too_small issues.
+             */
+            minimum?: number | string;
+            /**
+             * Maximum bound for too_big issues.
+             */
+            maximum?: number | string;
+            inclusive?: boolean;
+            /**
+             * Format name for string issues (regex, email, url, uuid).
+             */
+            format?: string;
+            /**
+             * Regex pattern when format is regex.
+             */
+            pattern?: string;
+        }>;
+    };
+    /**
+     * Invalid or missing API key
+     */
+    401: {
         /**
-         * What the state means for the results the graha delivers, which is the whole purpose of reading an avastha: the chart says where a graha is, the avastha says how much of its promise it can keep.
+         * Human-readable error message. May change wording.
          */
-        interpretation: string;
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Method not allowed. The path exists but only responds to the methods listed in `allow[]` and the `Allow` response header.
+     */
+    405: {
+        error: string;
+        code: 'method_not_allowed';
+        /**
+         * Allowed HTTP methods for this path. Mirrors the Allow response header.
+         */
+        allow: Array<string>;
+        /**
+         * Link to the product page for this domain.
+         */
+        docs?: string;
+    };
+    /**
+     * Monthly rate limit exceeded
+     */
+    429: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
+    };
+    /**
+     * Internal server error
+     */
+    500: {
+        /**
+         * Human-readable error message. May change wording.
+         */
+        error: string;
+        /**
+         * Machine-readable error code. Stable identifier.
+         */
+        code: string;
     };
 };
-export type GetAvasthaResponse = GetAvasthaResponses[keyof GetAvasthaResponses];
-export type CalculateArudhaPadasData = {
-    body?: ArudhaRequest;
+export type CalculateBhavaBalaError = CalculateBhavaBalaErrors[keyof CalculateBhavaBalaErrors];
+export type CalculateBhavaBalaResponses = {
+    /**
+     * Bhava Bala for all twelve houses with the three components, totals in virupas and rupas, ranking, and the localized house-theme legend.
+     */
+    200: BhavaBalaResponse;
+};
+export type CalculateBhavaBalaResponse = CalculateBhavaBalaResponses[keyof CalculateBhavaBalaResponses];
+export type CalculateBhavChalitData = {
+    body?: BhavChalitRequest;
     path?: never;
     query?: {
         /**
          * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
          */
         lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
+        /**
+         * Which signification vocabulary the houseThemes map returns. "general" gives the classical bhava significations (self, wealth, siblings, home, and so on). "finance" gives the money reading of the same twelve bhavas, so house 2 returns income and savings, 5 speculation and risk appetite, 8 sudden money and leverage, 11 gains and profits, and 12 expenses and capital outflow. Use "finance" for wealth, income, business and market timing questions in Krishnamurti Paddhati, where the significator house groups 2, 6, 10, 11 for earned income and 5, 8, 11 for speculation are read against a running dasha. Defaults to "general".
+         */
+        focus?: 'general' | 'finance';
     };
-    url: '/vedic-astrology/arudha';
+    url: '/vedic-astrology/bhav-chalit';
 };
-export type CalculateArudhaPadasErrors = {
+export type CalculateBhavChalitErrors = {
     /**
      * Validation error. `issues[]` lists every failed field.
      */
@@ -22264,26 +24017,21 @@ export type CalculateArudhaPadasErrors = {
         code: string;
     };
 };
-export type CalculateArudhaPadasError = CalculateArudhaPadasErrors[keyof CalculateArudhaPadasErrors];
-export type CalculateArudhaPadasResponses = {
+export type CalculateBhavChalitError = CalculateBhavChalitErrors[keyof CalculateBhavChalitErrors];
+export type CalculateBhavChalitResponses = {
     /**
-     * All twelve Arudha padas with derivation detail, plus the Arudha Lagna and Upapada lifted to the top level.
+     * Bhav Chalit chart with the twelve Sripati bhavas, every graha in both frames, and the localized house-theme legend.
      */
-    200: ArudhaResponse;
+    200: BhavChalitResponse;
 };
-export type CalculateArudhaPadasResponse = CalculateArudhaPadasResponses[keyof CalculateArudhaPadasResponses];
-export type CalculateCharaKarakasData = {
-    body?: CharaKarakaRequest;
+export type CalculateBhavChalitResponse = CalculateBhavChalitResponses[keyof CalculateBhavChalitResponses];
+export type GetHeliacalVisibilityData = {
+    body?: HeliacalRequest;
     path?: never;
-    query?: {
-        /**
-         * Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
-         */
-        lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
-    };
-    url: '/vedic-astrology/chara-karakas';
+    query?: never;
+    url: '/vedic-astrology/heliacal';
 };
-export type CalculateCharaKarakasErrors = {
+export type GetHeliacalVisibilityErrors = {
     /**
      * Validation error. `issues[]` lists every failed field.
      */
@@ -22384,14 +24132,14 @@ export type CalculateCharaKarakasErrors = {
         code: string;
     };
 };
-export type CalculateCharaKarakasError = CalculateCharaKarakasErrors[keyof CalculateCharaKarakasErrors];
-export type CalculateCharaKarakasResponses = {
+export type GetHeliacalVisibilityError = GetHeliacalVisibilityErrors[keyof GetHeliacalVisibilityErrors];
+export type GetHeliacalVisibilityResponses = {
     /**
-     * Karaka offices in descending rank with the ranking degree for each, plus the Atmakaraka and Darakaraka lifted to the top level.
+     * Heliacal visibility and the surrounding udaya and asta events for each graha.
      */
-    200: CharaKarakaResponse;
+    200: HeliacalResponse;
 };
-export type CalculateCharaKarakasResponse = CalculateCharaKarakasResponses[keyof CalculateCharaKarakasResponses];
+export type GetHeliacalVisibilityResponse = GetHeliacalVisibilityResponses[keyof GetHeliacalVisibilityResponses];
 export type GenerateTimelineData = {
     body?: {
         /**
@@ -22582,9 +24330,9 @@ export type GenerateTimelineResponses = {
              */
             time: string;
             /**
-             * IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.
+             * Decimal UTC offset the forecast was computed with, resolved from whatever the request sent. An IANA name is resolved to the DST-correct offset for the birth date, so this is the literal number applied, never the name.
              */
-            timezone: number | string;
+            timezone: number;
             /**
              * Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.
              */
@@ -22839,9 +24587,9 @@ export type ForecastTransitsResponses = {
              */
             time: string;
             /**
-             * IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.
+             * Decimal UTC offset the forecast was computed with, resolved from whatever the request sent. An IANA name is resolved to the DST-correct offset for the birth date, so this is the literal number applied, never the name.
              */
-            timezone: number | string;
+            timezone: number;
             /**
              * Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.
              */
@@ -23117,9 +24865,9 @@ export type FindSignificantDatesResponses = {
              */
             time: string;
             /**
-             * IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.
+             * Decimal UTC offset the forecast was computed with, resolved from whatever the request sent. An IANA name is resolved to the DST-correct offset for the birth date, so this is the literal number applied, never the name.
              */
-            timezone: number | string;
+            timezone: number;
             /**
              * Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.
              */
@@ -23395,9 +25143,9 @@ export type GenerateDigestResponses = {
              */
             time: string;
             /**
-             * IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the DST-correct offset for the birth date, while a fixed offset or decimal is taken literally and will be wrong if it does not match the daylight-saving state on that date. Invalid timezones return 400 with a validation error.
+             * Decimal UTC offset the forecast was computed with, resolved from whatever the request sent. An IANA name is resolved to the DST-correct offset for the birth date, so this is the literal number applied, never the name.
              */
-            timezone: number | string;
+            timezone: number;
             /**
              * Birth latitude in decimal degrees. Optional and does not affect the timeline. Defaults to 0.
              */
@@ -23439,20 +25187,50 @@ export type GenerateDigestResponses = {
              * Count of events in this window broken down by domain. Only domains with at least one event in the window are present. The values sum to count.
              */
             byDomain: {
+                /**
+                 * Number of events in this window produced by this forecast domain. Absent when the domain contributed nothing, so a zero is never written.
+                 */
                 western?: number;
+                /**
+                 * Number of events in this window produced by this forecast domain. Absent when the domain contributed nothing, so a zero is never written.
+                 */
                 vedic?: number;
+                /**
+                 * Number of events in this window produced by this forecast domain. Absent when the domain contributed nothing, so a zero is never written.
+                 */
                 biorhythm?: number;
             };
             /**
              * Count of events in this window broken down by event type. Only types with at least one event in the window are present. The values sum to count.
              */
             byType: {
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 'transit-aspect'?: number;
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 'sign-ingress'?: number;
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 'retrograde-station'?: number;
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 eclipse?: number;
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 'lunar-phase'?: number;
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 'dasha-change'?: number;
+                /**
+                 * Number of events in this window of this event type. Absent when the type did not occur, so a zero is never written.
+                 */
                 'critical-day'?: number;
             };
             /**
@@ -25463,7 +27241,7 @@ export type GetGateData = {
         /**
          * Gate number from 1 to 64.
          */
-        number: number;
+        number: number | null;
     };
     query?: {
         /**
@@ -26560,7 +28338,13 @@ export type CalculateVariablesResponses = {
              * Cognition, the strongest sense, read off the Determination Tone. Present on the determination arrow ONLY: no authority supports reading Cognition from the other three arrows, so it is omitted rather than invented.
              */
             cognition?: {
+                /**
+                 * Name of the Cognition, the strongest sense. One of six read off the Determination Tone: Smell, Taste, Outer Vision, Inner Vision, Feeling, Touch.
+                 */
                 label: string;
+                /**
+                 * How this Cognition discriminates what is correct for the body, and the conditions that sharpen it. Renderable as the Cognition paragraph of a Variables or Primary Health System report.
+                 */
                 description: string;
             };
             /**
@@ -29770,7 +31554,7 @@ export type GenerateNumerologyChartResponses = {
                 /**
                  * Age when this phase ends. Null for the 4th Pinnacle (lasts rest of life).
                  */
-                endAge: number;
+                endAge: number | null;
                 /**
                  * Meaning and interpretation for this Pinnacle number.
                  */
@@ -29812,7 +31596,7 @@ export type GenerateNumerologyChartResponses = {
                 /**
                  * Age when this period ends. Null for the 4th Challenge.
                  */
-                endAge: number;
+                endAge: number | null;
                 /**
                  * Meaning and resolution guidance for this Challenge number.
                  */
@@ -30535,7 +32319,7 @@ export type CalculateChaldeanResponses = {
             /**
              * The interpretable compound number (10 to 52), the hidden influence behind the name, or null when the total resolves below 10.
              */
-            compound: number;
+            compound: number | null;
             /**
              * The single-digit root (1 to 9), the outward expression. Chaldean does not preserve master numbers.
              */
@@ -30555,7 +32339,7 @@ export type CalculateChaldeanResponses = {
                 /**
                  * Classical symbolic title from Cheiro, or null when the number has no named symbol.
                  */
-                name: string;
+                name: string | null;
                 /**
                  * Overall tenor of the compound. "mixed" covers conditional numbers that are fortunate only alongside a favorable single number or in a specific domain.
                  */
@@ -30568,7 +32352,7 @@ export type CalculateChaldeanResponses = {
                  * For numbers 33 to 52, the lower compound in the same series whose meaning this number shares.
                  */
                 sameAs?: number;
-            };
+            } | null;
         };
         /**
          * The Soul Urge number from the vowels, revealing inner desire. Root may be 0 when the name has no vowels.
@@ -30581,7 +32365,7 @@ export type CalculateChaldeanResponses = {
             /**
              * The interpretable compound number (10 to 52), the hidden influence behind the name, or null when the total resolves below 10.
              */
-            compound: number;
+            compound: number | null;
             /**
              * The single-digit root (1 to 9), the outward expression. Chaldean does not preserve master numbers.
              */
@@ -30601,7 +32385,7 @@ export type CalculateChaldeanResponses = {
                 /**
                  * Classical symbolic title from Cheiro, or null when the number has no named symbol.
                  */
-                name: string;
+                name: string | null;
                 /**
                  * Overall tenor of the compound. "mixed" covers conditional numbers that are fortunate only alongside a favorable single number or in a specific domain.
                  */
@@ -30614,7 +32398,7 @@ export type CalculateChaldeanResponses = {
                  * For numbers 33 to 52, the lower compound in the same series whose meaning this number shares.
                  */
                 sameAs?: number;
-            };
+            } | null;
         };
         /**
          * The Personality number from the consonants, revealing the outer impression. Root may be 0 when the name has no consonants.
@@ -30627,7 +32411,7 @@ export type CalculateChaldeanResponses = {
             /**
              * The interpretable compound number (10 to 52), the hidden influence behind the name, or null when the total resolves below 10.
              */
-            compound: number;
+            compound: number | null;
             /**
              * The single-digit root (1 to 9), the outward expression. Chaldean does not preserve master numbers.
              */
@@ -30647,7 +32431,7 @@ export type CalculateChaldeanResponses = {
                 /**
                  * Classical symbolic title from Cheiro, or null when the number has no named symbol.
                  */
-                name: string;
+                name: string | null;
                 /**
                  * Overall tenor of the compound. "mixed" covers conditional numbers that are fortunate only alongside a favorable single number or in a specific domain.
                  */
@@ -30660,7 +32444,7 @@ export type CalculateChaldeanResponses = {
                  * For numbers 33 to 52, the lower compound in the same series whose meaning this number shares.
                  */
                 sameAs?: number;
-            };
+            } | null;
         };
         numberMeaning: {
             /**
@@ -30829,7 +32613,7 @@ export type GetCompoundNumberResponses = {
         /**
          * Classical symbolic title from Cheiro, or null when none is given.
          */
-        name: string;
+        name: string | null;
         /**
          * Overall tenor of the number. "mixed" marks conditional numbers, fortunate only with a favorable single number or in one domain.
          */
@@ -31002,7 +32786,7 @@ export type CalculateDualResponses = {
             /**
              * Chaldean compound number (10 to 52), the hidden influence, or null.
              */
-            compound: number;
+            compound: number | null;
             /**
              * Chaldean root (1 to 9).
              */
@@ -31038,7 +32822,7 @@ export type CalculateDualResponses = {
                 /**
                  * Symbolic title.
                  */
-                name: string;
+                name: string | null;
                 /**
                  * Tenor of the compound.
                  */
@@ -31051,7 +32835,7 @@ export type CalculateDualResponses = {
                  * Series equivalent for 33 to 52.
                  */
                 sameAs?: number;
-            };
+            } | null;
         };
         /**
          * True when both systems reduce to the same single-digit energy (Pythagorean number reduced to one digit equals the Chaldean root). Agreement is read as a name whose vibrations are in harmony.
@@ -31198,7 +32982,7 @@ export type CalculateBusinessNameResponses = {
         /**
          * Chaldean compound number (10 to 52), the hidden influence, or null.
          */
-        compound: number;
+        compound: number | null;
         /**
          * Single-digit business root (1 to 9), the outward commercial expression.
          */
@@ -31238,7 +33022,7 @@ export type CalculateBusinessNameResponses = {
             /**
              * Symbolic title, if any.
              */
-            name: string;
+            name: string | null;
             /**
              * Tenor of the compound.
              */
@@ -31251,7 +33035,7 @@ export type CalculateBusinessNameResponses = {
              * Series equivalent for 33 to 52.
              */
             sameAs?: number;
-        };
+        } | null;
         /**
          * One-line plain-language verdict for the business name.
          */
@@ -31274,7 +33058,7 @@ export type ListCardsData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
         /**
          * Filter by arcana type. Major arcana (0-21) represents life lessons and spiritual themes. Minor arcana (Ace-King in 4 suits) represents daily situations and practical matters.
          */
@@ -31286,7 +33070,7 @@ export type ListCardsData = {
         /**
          * Filter by card number. Major Arcana: 0 (The Fool) through 21 (The World). Minor Arcana: 1 (Ace) through 14 (King). Combine with arcana or suit filters for precise results.
          */
-        number?: number;
+        number?: number | null;
     };
     url: '/tarot/cards';
 };
@@ -31974,6 +33758,10 @@ export type CastYesNoResponses = {
          * The querent question that was asked, if one was provided.
          */
         question?: string;
+        /**
+         * The seed used for this draw, echoed back when one was supplied. Present only if the request carried a seed. Makes a cached or forwarded response self describing, so a reading can be reproduced or shared without the original request beside it.
+         */
+        seed?: string;
         /**
          * Tarot-derived answer. Yes = upright card supports a positive outcome. No = reversed card suggests obstacles. Maybe = inherently ambiguous card drawn (The Hanged Man, Wheel of Fortune, Temperance, Two of Swords, Four of Swords) signaling pause, reflection, or shifting circumstances.
          */
@@ -32173,7 +33961,7 @@ export type CastThreeCardResponses = {
             card: DrawnCard;
         }>;
         /**
-         * AI-generated narrative connecting all cards in the spread into a cohesive reading.
+         * Narrative summary that connects the cards drawn across the spread positions into one cohesive reading.
          */
         summary?: string;
     };
@@ -32181,7 +33969,13 @@ export type CastThreeCardResponses = {
 export type CastThreeCardResponse = CastThreeCardResponses[keyof CastThreeCardResponses];
 export type CastCelticCrossData = {
     body: {
+        /**
+         * Optional querent question to focus the Celtic Cross. It is echoed back on the reading and gives the ten positions their context. Omit for a general reading of the situation.
+         */
         question?: string;
+        /**
+         * Optional seed for reproducible results. The same seed always draws the same ten cards into the same Celtic Cross positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.
+         */
         seed?: string;
     };
     path?: never;
@@ -32331,7 +34125,7 @@ export type CastCelticCrossResponses = {
             card: DrawnCard;
         }>;
         /**
-         * AI-generated narrative connecting all cards in the spread into a cohesive reading.
+         * Narrative summary that connects the cards drawn across the spread positions into one cohesive reading.
          */
         summary?: string;
     };
@@ -32339,7 +34133,13 @@ export type CastCelticCrossResponses = {
 export type CastCelticCrossResponse = CastCelticCrossResponses[keyof CastCelticCrossResponses];
 export type CastLoveSpreadData = {
     body: {
+        /**
+         * Optional querent question to focus the love spread. It is echoed back on the reading and gives the five relationship positions their context. Omit for general relationship guidance.
+         */
         question?: string;
+        /**
+         * Optional seed for reproducible results. The same seed always draws the same five cards into the same love positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.
+         */
         seed?: string;
     };
     path?: never;
@@ -32489,7 +34289,7 @@ export type CastLoveSpreadResponses = {
             card: DrawnCard;
         }>;
         /**
-         * AI-generated narrative connecting all cards in the spread into a cohesive reading.
+         * Narrative summary that connects the cards drawn across the spread positions into one cohesive reading.
          */
         summary?: string;
     };
@@ -32497,7 +34297,13 @@ export type CastLoveSpreadResponses = {
 export type CastLoveSpreadResponse = CastLoveSpreadResponses[keyof CastLoveSpreadResponses];
 export type CastCareerSpreadData = {
     body: {
+        /**
+         * Optional querent question to focus the career spread. It is echoed back on the reading and gives the five career positions their context. Omit for general work and vocation guidance.
+         */
         question?: string;
+        /**
+         * Optional seed for reproducible results. The same seed always draws the same five cards into the same career positions, which is what lets a reading be shared or re-rendered. Omit for a random draw.
+         */
         seed?: string;
     };
     path?: never;
@@ -32647,7 +34453,7 @@ export type CastCareerSpreadResponses = {
             card: DrawnCard;
         }>;
         /**
-         * AI-generated narrative connecting all cards in the spread into a cohesive reading.
+         * Narrative summary that connects the cards drawn across the spread positions into one cohesive reading.
          */
         summary?: string;
     };
@@ -32827,10 +34633,6 @@ export type CastCustomSpreadResponses = {
             interpretation: string;
             card: DrawnCard;
         }>;
-        /**
-         * AI-generated narrative connecting all cards in the spread into a cohesive reading.
-         */
-        summary?: string;
     };
 };
 export type CastCustomSpreadResponse = CastCustomSpreadResponses[keyof CastCustomSpreadResponses];
@@ -33456,7 +35258,7 @@ export type GetCriticalDaysResponses = {
         /**
          * Date where all 3 primary cycles cross zero simultaneously. Extremely rare event. Null if none found in range.
          */
-        tripleCriticalDay: string;
+        tripleCriticalDay: string | null;
     };
 };
 export type GetCriticalDaysResponse = GetCriticalDaysResponses[keyof GetCriticalDaysResponses];
@@ -34545,7 +36347,7 @@ export type ListHexagramsData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/iching/hexagrams';
 };
@@ -35509,7 +37311,7 @@ export type GetCrystalsByZodiacData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/crystals/zodiac/{sign}';
 };
@@ -35651,11 +37453,11 @@ export type GetCrystalsByZodiacResponses = {
             /**
              * URL to crystal photograph for visual identification.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Primary colors of this crystal variety. Null when color data is unavailable.
              */
-            colors: Array<string>;
+            colors: Array<string> | null;
         }>;
     };
 };
@@ -35680,7 +37482,7 @@ export type GetCrystalsByChakraData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/crystals/chakra/{chakra}';
 };
@@ -35822,11 +37624,11 @@ export type GetCrystalsByChakraResponses = {
             /**
              * URL to crystal photograph for visual identification.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Primary colors of this crystal variety. Null when color data is unavailable.
              */
-            colors: Array<string>;
+            colors: Array<string> | null;
         }>;
     };
 };
@@ -35851,7 +37653,7 @@ export type GetCrystalsByElementData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/crystals/element/{element}';
 };
@@ -35993,11 +37795,11 @@ export type GetCrystalsByElementResponses = {
             /**
              * URL to crystal photograph for visual identification.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Primary colors of this crystal variety. Null when color data is unavailable.
              */
-            colors: Array<string>;
+            colors: Array<string> | null;
         }>;
     };
 };
@@ -36152,11 +37954,11 @@ export type GetBirthstonesResponses = {
             /**
              * URL to crystal photograph for visual identification.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Primary colors of this crystal variety. Null when color data is unavailable.
              */
-            colors: Array<string>;
+            colors: Array<string> | null;
         }>;
     };
 };
@@ -36180,7 +37982,7 @@ export type SearchCrystalsData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/crystals/search';
 };
@@ -36322,11 +38124,11 @@ export type SearchCrystalsResponses = {
             /**
              * URL to crystal photograph for visual identification.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Primary colors of this crystal variety. Null when color data is unavailable.
              */
-            colors: Array<string>;
+            colors: Array<string> | null;
         }>;
     };
 };
@@ -36494,7 +38296,7 @@ export type GetCrystalPairingsResponses = {
             /**
              * URL to paired crystal photograph.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Brief overview of the paired crystal.
              */
@@ -36506,7 +38308,7 @@ export type GetCrystalPairingsResponses = {
             /**
              * Healing property keywords for the paired crystal. Null when keyword data is unavailable.
              */
-            keywords: Array<string>;
+            keywords: Array<string> | null;
         }>;
     };
 };
@@ -36657,7 +38459,7 @@ export type GetDailyCrystalResponses = {
         /**
          * URL to crystal photograph. Use for daily crystal card display and visual features.
          */
-        imageUrl: string;
+        imageUrl: string | null;
         /**
          * Overview of the crystal covering primary healing purpose and benefits.
          */
@@ -36669,7 +38471,7 @@ export type GetDailyCrystalResponses = {
         /**
          * Zodiac signs this crystal is traditionally associated with. Null when zodiac data is unavailable.
          */
-        zodiacSigns: Array<string>;
+        zodiacSigns: Array<string> | null;
         /**
          * Positive affirmation aligned with the selected crystal. Use for daily affirmation features and meditation guidance.
          */
@@ -36806,7 +38608,7 @@ export type GetRandomCrystalResponses = {
         /**
          * URL to crystal photograph for visual display.
          */
-        imageUrl: string;
+        imageUrl: string | null;
         /**
          * Overview of the crystal covering primary healing purpose and benefits.
          */
@@ -36818,7 +38620,7 @@ export type GetRandomCrystalResponses = {
         /**
          * Zodiac signs this crystal is traditionally associated with. Null when zodiac data is unavailable.
          */
-        zodiacSigns: Array<string>;
+        zodiacSigns: Array<string> | null;
         /**
          * Positive affirmation aligned with the selected crystal energy.
          */
@@ -37109,7 +38911,7 @@ export type ListCrystalsData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/crystals';
 };
@@ -37247,11 +39049,11 @@ export type ListCrystalsResponses = {
             /**
              * URL to crystal photograph for visual identification.
              */
-            imageUrl: string;
+            imageUrl: string | null;
             /**
              * Primary colors of this crystal variety. Null when color data is unavailable.
              */
-            colors: Array<string>;
+            colors: Array<string> | null;
             /**
              * Chakra energy centers this crystal resonates with. One of: Root, Sacral, Solar Plexus, Heart, Throat, Third Eye, Crown.
              */
@@ -37407,7 +39209,7 @@ export type GetCrystalResponses = {
         /**
          * URL to a high-quality crystal photograph. Use for visual crystal guides, product listings, and crystal identification features.
          */
-        imageUrl: string;
+        imageUrl: string | null;
         /**
          * Overview of the crystal covering its primary healing purpose, spiritual significance, and key benefits.
          */
@@ -37419,7 +39221,7 @@ export type GetCrystalResponses = {
             /**
              * Spiritual and metaphysical healing properties including energy work, meditation benefits, and higher consciousness connections. Null when spiritual interpretation is unavailable.
              */
-            spiritual: string;
+            spiritual: string | null;
             /**
              * Emotional healing properties including stress relief, relationship support, and emotional balance benefits.
              */
@@ -37427,7 +39229,7 @@ export type GetCrystalResponses = {
             /**
              * Physical healing associations traditionally attributed to this crystal in crystal healing practice. Null when physical healing data is unavailable.
              */
-            physical: string;
+            physical: string | null;
         };
         /**
          * Chakra energy centers this crystal resonates with. One of: Root, Sacral, Solar Plexus, Heart, Throat, Third Eye, Crown.
@@ -37436,19 +39238,19 @@ export type GetCrystalResponses = {
         /**
          * Zodiac signs this crystal is traditionally associated with. Null when zodiac data is unavailable. Useful for personalized crystal recommendations based on birth chart.
          */
-        zodiacSigns: Array<string>;
+        zodiacSigns: Array<string> | null;
         /**
          * Ruling planet or celestial body associated with this crystal in astrological tradition. Null when planetary association is unavailable.
          */
-        planet: string;
+        planet: string | null;
         /**
          * Elemental associations (Earth, Water, Fire, Air, Storm) connecting the crystal to natural forces and energy types. Null when elemental data is unavailable.
          */
-        elements: Array<string>;
+        elements: Array<string> | null;
         /**
          * Primary colors of this crystal variety. Null when color data is unavailable. Useful for color-based crystal selection and filtering.
          */
-        colors: Array<string>;
+        colors: Array<string> | null;
         /**
          * Mohs hardness scale rating (1-10). Indicates durability for jewelry use. Quartz family is 7, Diamond is 10, Selenite is 2.
          */
@@ -37458,13 +39260,13 @@ export type GetCrystalResponses = {
          */
         numericalVibration: number;
         /**
-         * Five to nine keywords capturing the core healing properties and spiritual themes of this crystal. Null when keyword data is unavailable.
+         * Keywords capturing the core healing properties and spiritual themes of this crystal. The count varies by stone, from a single keyword up to twenty. Null when keyword data is unavailable.
          */
-        keywords: Array<string>;
+        keywords: Array<string> | null;
         /**
          * Birth month (1-12) if this crystal is a traditional birthstone. Null if not a birthstone. January is 1, December is 12.
          */
-        birthMonth: number;
+        birthMonth: number | null;
         /**
          * Positive affirmation aligned with this crystal energy. Use for meditation, journaling, or daily affirmation features.
          */
@@ -37495,7 +39297,7 @@ export type SearchDreamSymbolsData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/dreams/symbols';
 };
@@ -38176,7 +39978,7 @@ export type ListAngelNumbersData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
         /**
          * Filter results by angel number pattern type. "repeating" returns numbers like 111, 444, 7777. "sequential" returns patterns like 1234. "mirror" returns palindrome or alternating patterns like 1212, 717. "master" returns 11, 22, 33. "root" returns single digits 0-9. "compound" returns mixed sequences with no pure pattern like 911, 1122.
          */
@@ -38759,7 +40561,7 @@ export type AnalyzeNumberSequenceResponses = {
              * Actionable steps when you see this number.
              */
             actionSteps: Array<string>;
-        };
+        } | null;
         /**
          * The foundational meaning of this number based on its digit root. Every number reduces to a root digit (0-9) or master number (11, 22, 33), which provides the base interpretation even for unknown sequences.
          */
@@ -38780,10 +40582,25 @@ export type AnalyzeNumberSequenceResponses = {
              * Full life-area interpretation of the underlying root digit. For an unknown sequence this is the substantive reading to display, so a synchronicity app never dead-ends on an arbitrary number.
              */
             meaning: {
+                /**
+                 * Spiritual interpretation of the root digit, covering divine guidance, higher purpose, and metaphysical significance.
+                 */
                 spiritual: string;
+                /**
+                 * Love and relationship interpretation of the root digit, for singles, couples, and those healing from past relationships.
+                 */
                 love: string;
+                /**
+                 * Career and vocation guidance for the root digit. Money and finances are returned separately in the money field.
+                 */
                 career: string;
+                /**
+                 * Money, finances, and material abundance guidance for the root digit, kept distinct from career.
+                 */
                 money: string;
+                /**
+                 * Twin flame interpretation of the root digit, covering union, separation, and spiritual growth.
+                 */
                 twinFlame: string;
             };
             /**
@@ -38794,7 +40611,7 @@ export type AnalyzeNumberSequenceResponses = {
              * Affirmation for the root digit.
              */
             affirmation: string;
-        };
+        } | null;
         /**
          * Present only when the context query parameter is supplied. A short reading layered on top of the meaning that accounts for WHERE the number was seen (clock, receipt, license plate, phone, address, price), since the place of a sighting shifts its emphasis.
          */
@@ -39024,7 +40841,7 @@ export type SearchCitiesData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/location/search';
 };
@@ -39202,7 +41019,7 @@ export type ListCountriesData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/location/countries';
 };
@@ -39365,7 +41182,7 @@ export type GetCitiesByCountryData = {
         /**
          * Number of items to skip for pagination. Default 0.
          */
-        offset?: number;
+        offset?: number | null;
     };
     url: '/location/countries/{iso2}';
 };
@@ -39651,12 +41468,33 @@ export type GetUsageStatsResponses = {
      * Usage statistics retrieved
      */
     200: {
+        /**
+         * Name of the subscription plan the API key belongs to. One flat plan covers every domain and the Remote MCP servers, so this is a quota tier, never a per product entitlement.
+         */
         plan: string;
+        /**
+         * Billable requests counted against the current calendar month. Read from the same counter the rate limiter enforces on, so it never reports a rosier number than the limit that will 429 you. Cached responses still count.
+         */
         usedThisMonth: number;
+        /**
+         * Monthly request allowance for the plan. One request, API or MCP, equals one unit: there is no credit weighting and no per domain fee.
+         */
         requestsPerMonth: number;
+        /**
+         * Requests left before the monthly allowance is exhausted, floored at zero. Equal to requestsPerMonth minus usedThisMonth.
+         */
         remainingThisMonth: number;
+        /**
+         * Billing email the subscription is registered under.
+         */
         email: string;
+        /**
+         * Subscription lifecycle state. Values: active, cancelled (no longer renewing but usable until endDate), suspended (payment failed, usable until endDate), expired (past endDate), pending (checkout started, payment not captured).
+         */
         status: string;
+        /**
+         * ISO 8601 timestamp when the current billing period ends. A renewal extends this date in place. API access survives a cancelled or suspended status until this moment passes.
+         */
         endDate: string;
     };
 };