@roxyapi/sdk 1.2.53 → 1.2.54

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const VERSION = "1.2.53";
+export declare const VERSION = "1.2.54";
 //# sourceMappingURL=version.d.ts.map

package/docs/llms-full.txt

@@ -223,13 +223,22 @@ const { data } = await roxy.astrology.calculateCompatibility({
 });
 
 // Daily horoscope by zodiac sign - Transit-based forecast with house activations
-const { data } = await roxy.astrology.getDailyHoroscope({ path: { sign: 'aries' }, query: { date: '2026-04-03' } });
+const { data } = await roxy.astrology.getDailyHoroscope({
+  path: { sign: 'aries' },
+  query: { date: '2026-04-03', timezone: 'America/New_York' },
+});
 
 // Weekly horoscope by zodiac sign - 7-day transit forecast
-const { data } = await roxy.astrology.getWeeklyHoroscope({ path: { sign: 'aries' } });
+const { data } = await roxy.astrology.getWeeklyHoroscope({
+  path: { sign: 'aries' },
+  query: { date: '2026-04-03', timezone: 'America/New_York' },
+});
 
 // Monthly horoscope by zodiac sign - 30-day transit forecast with key dates
-const { data } = await roxy.astrology.getMonthlyHoroscope({ path: { sign: 'aries' } });
+const { data } = await roxy.astrology.getMonthlyHoroscope({
+  path: { sign: 'aries' },
+  query: { date: '2026-04-03', timezone: 'America/New_York' },
+});
 
 // Planetary Return Chart - Saturn return, Jupiter return, and inner planet cycles
 const { data } = await roxy.astrology.generatePlanetaryReturn({
@@ -457,6 +466,7 @@ const { data } = await roxy.vedicAstrology.getCurrentDasha({
     longitude: 77.209,
     timezone: 5.5,
     ayanamsa: 'lahiri',
+    ayanamsaValue: 24,
     significators: false,
     nodeType: 'mean',
   },
@@ -472,6 +482,7 @@ const { data } = await roxy.vedicAstrology.getMajorDashas({
     longitude: 77.209,
     timezone: 5.5,
     ayanamsa: 'lahiri',
+    ayanamsaValue: 24,
     significators: false,
     nodeType: 'mean',
   },
@@ -488,6 +499,7 @@ const { data } = await roxy.vedicAstrology.getSubDashas({
     longitude: 77.209,
     timezone: 5.5,
     ayanamsa: 'lahiri',
+    ayanamsaValue: 24,
     significators: false,
     nodeType: 'mean',
   },
@@ -504,6 +516,7 @@ const { data } = await roxy.vedicAstrology.getPratyantardashas({
     longitude: 77.209,
     timezone: 5.5,
     ayanamsa: 'lahiri',
+    ayanamsaValue: 24,
     significators: false,
     nodeType: 'mean',
   },
@@ -524,6 +537,7 @@ const { data } = await roxy.vedicAstrology.getSookshmaDashas({
     longitude: 77.209,
     timezone: 5.5,
     ayanamsa: 'lahiri',
+    ayanamsaValue: 24,
     significators: false,
     nodeType: 'mean',
   },
@@ -545,6 +559,7 @@ const { data } = await roxy.vedicAstrology.getPranaDashas({
     longitude: 77.209,
     timezone: 5.5,
     ayanamsa: 'lahiri',
+    ayanamsaValue: 24,
     significators: false,
     nodeType: 'mean',
   },
@@ -642,7 +657,9 @@ const { data } = await roxy.vedicAstrology.detectYogas({
 });
 
 // Get KP-Newcomb ayanamsa - Dynamic daily calculation
-const { data } = await roxy.vedicAstrology.getKpAyanamsa({ query: { date: '2025-12-26' } });
+const { data } = await roxy.vedicAstrology.getKpAyanamsa({
+  query: { date: '2025-12-26', time: '09:00:00', timezone: 5.5 },
+});
 
 // Get KP planetary positions with sub-lords
 const { data } = await roxy.vedicAstrology.getKpPlanets({
@@ -660,6 +677,7 @@ const { data } = await roxy.vedicAstrology.getKpPlanets({
 
 // Get KP Placidus house cusps with sub-lords
 const { data } = await roxy.vedicAstrology.getKpCusps({
+  query: { focus: 'general' },
   body: {
     date: '1990-07-04',
     time: '10:12:00',
@@ -688,6 +706,7 @@ const { data } = await roxy.vedicAstrology.generateKpChart({
 
 // Get KP ruling planets with optional significators
 const { data } = await roxy.vedicAstrology.getKpRulingPlanets({
+  query: { focus: 'general' },
   body: {
     latitude: 28.6139,
     longitude: 77.209,
@@ -701,6 +720,7 @@ const { data } = await roxy.vedicAstrology.getKpRulingPlanets({
 
 // Get KP ruling planets with significators at intervals
 const { data } = await roxy.vedicAstrology.getKpRulingInterval({
+  query: { focus: 'general' },
   body: {
     startDatetime: '2026-02-03T00:00:00Z',
     endDatetime: '2026-02-03T01:00:00Z',

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@roxyapi/sdk",
-	"version": "1.2.53",
+	"version": "1.2.54",
 	"description": "TypeScript SDK for Roxy — the multi-domain spiritual intelligence API",
 	"type": "module",
 	"exports": {

package/src/sdk.gen.ts

@@ -345,7 +345,7 @@ export class Astrology extends HeyApiClient {
     /**
      * Daily horoscope by zodiac sign - Transit-based forecast with house activations
      *
-     * Get the daily horoscope for any zodiac sign. Forecast is generated from real-time planetary transits using whole-sign house positions, so every sign receives unique content. Returns love, career, health, finance, overview with active transits, Moon sign, Moon phase, energy rating, lucky number, lucky color, and compatible signs. Supports date parameter for editorial scheduling. Daily horoscope API, zodiac forecast, sun sign horoscope, astrology prediction.
+     * Get the daily horoscope for any zodiac sign. Forecast is generated from real-time planetary transits using whole-sign house positions, so every sign receives unique content. Returns love, career, health, finance, overview with active transits, Moon sign, Moon phase, energy rating, lucky number, lucky color, and compatible signs. Content is fixed for a given date and rolls over at midnight, by default UTC. Pass date for editorial scheduling, or timezone to roll over on a local clock. Daily horoscope API, zodiac forecast, sun sign horoscope, astrology prediction.
      */
     public getDailyHoroscope<ThrowOnError extends boolean = false>(options: Options<GetAstrologyHoroscopeBySignDailyData, ThrowOnError>) {
         return (options.client ?? this.client).get<GetAstrologyHoroscopeBySignDailyResponses, GetAstrologyHoroscopeBySignDailyErrors, ThrowOnError>({
@@ -358,7 +358,7 @@ export class Astrology extends HeyApiClient {
     /**
      * Weekly horoscope by zodiac sign - 7-day transit forecast
      *
-     * Get weekly horoscope for any zodiac sign. Forecast covers a full 7-day period based on planetary transits with house-based content unique to each sign, with love, career, health, finance guidance plus lucky days, lucky numbers, and compatible signs. Weekly horoscope API, zodiac weekly forecast, astrology weekly prediction.
+     * Get weekly horoscope for any zodiac sign. Forecast covers a full Monday to Sunday period based on planetary transits with house-based content unique to each sign, with love, career, health, finance guidance plus lucky days, lucky numbers, and compatible signs. Pass any date inside a week to retrieve that week, or timezone to roll over on a local clock. Weekly horoscope API, zodiac weekly forecast, astrology weekly prediction.
      */
     public getWeeklyHoroscope<ThrowOnError extends boolean = false>(options: Options<GetAstrologyHoroscopeBySignWeeklyData, ThrowOnError>) {
         return (options.client ?? this.client).get<GetAstrologyHoroscopeBySignWeeklyResponses, GetAstrologyHoroscopeBySignWeeklyErrors, ThrowOnError>({
@@ -371,7 +371,7 @@ export class Astrology extends HeyApiClient {
     /**
      * Monthly horoscope by zodiac sign - 30-day transit forecast with key dates
      *
-     * Get monthly horoscope for any zodiac sign with sign-specific week-by-week breakdown and real lunar phase key dates. Based on planetary transits with house activations unique to each sign, covering love, career, health, and finance for the entire month. Key dates include actual New Moon, Full Moon, and retrograde dates from ephemeris calculations. Monthly horoscope API, zodiac monthly forecast, astrology monthly prediction.
+     * Get monthly horoscope for any zodiac sign with sign-specific week-by-week breakdown and real lunar phase key dates. Based on planetary transits with house activations unique to each sign, covering love, career, health, and finance for the entire month. Key dates include actual New Moon, Full Moon, and retrograde dates from ephemeris calculations. Pass any date inside a month to retrieve that month, or timezone to roll over on a local clock. Monthly horoscope API, zodiac monthly forecast, astrology monthly prediction.
      */
     public getMonthlyHoroscope<ThrowOnError extends boolean = false>(options: Options<GetAstrologyHoroscopeBySignMonthlyData, ThrowOnError>) {
         return (options.client ?? this.client).get<GetAstrologyHoroscopeBySignMonthlyResponses, GetAstrologyHoroscopeBySignMonthlyErrors, ThrowOnError>({
@@ -939,7 +939,7 @@ export class VedicAstrology extends HeyApiClient {
     /**
      * Get KP-Newcomb ayanamsa - Dynamic daily calculation
      *
-     * Get the KP-Newcomb (Krishnamurti) ayanamsa for any date, computed continuously from Newcomb precession theory rather than looked up in a preset table, so it tracks the date you ask for instead of the calendar year. This is the precession offset subtracted from a tropical longitude to obtain the sidereal one, and it is what makes a KP chart reproduce the reference software your practitioners already use. Returns the same value every KP endpoint applies internally. KP Newcomb ayanamsa API, dynamic ayanamsa calculator, Krishnamurti ayanamsa today, current KP ayanamsa
+     * Get the KP-Newcomb (Krishnamurti) ayanamsa for any instant, computed continuously from Newcomb precession theory rather than looked up in a preset table, so it tracks the exact moment you ask for instead of the calendar year. Supply date alone for midnight UTC, or add time and timezone to pin a birth moment exactly. This is the precession offset subtracted from a tropical longitude to obtain the sidereal one, and it is what makes a KP chart reproduce the reference software your practitioners already use. Returns the same value every KP endpoint applies internally. KP Newcomb ayanamsa API, dynamic ayanamsa calculator, Krishnamurti ayanamsa today, current KP ayanamsa
      */
     public getKpAyanamsa<ThrowOnError extends boolean = false>(options?: Options<GetVedicAstrologyKpAyanamsaData, ThrowOnError>) {
         return (options?.client ?? this.client).get<GetVedicAstrologyKpAyanamsaResponses, GetVedicAstrologyKpAyanamsaErrors, ThrowOnError>({

package/src/types.gen.ts

@@ -3839,6 +3839,10 @@ export type KpAyanamsaResponse = {
      * Date for which ayanamsa was calculated
      */
     date: string;
+    /**
+     * The exact UTC instant the value was computed for, after applying the time and timezone. Echoed so a client reconciling to the arcsecond can confirm the moment rather than infer it from the date alone. Equals midnight UTC of the date when no time was supplied.
+     */
+    instant: string;
     /**
      * KP-Newcomb ayanamsa value in degrees
      */
@@ -4008,6 +4012,12 @@ export type KpCuspsResponse = {
          */
         kpNumber: 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>;
+    };
 };
 
 export type KpCuspsRequest = {
@@ -4463,6 +4473,12 @@ export type KpRulingPlanetsResponse = {
          */
         signifies: 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>;
+    };
 };
 
 export type KpRulingPlanetsIntervalResponse = {
@@ -4653,6 +4669,12 @@ export type KpRulingPlanetsIntervalResponse = {
             L4: 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>;
+    };
 };
 
 export type KpSublordChangesResponse = {
@@ -7161,9 +7183,9 @@ export type GetAstrologyMoonPhaseCurrentData = {
          */
         time?: string;
         /**
-         * IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours (e.g. -5 for EST, 1 for CET). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC).
+         * IANA name (e.g. "America/New_York", "Europe/London"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00"). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC).
          */
-        timezone?: number | string | unknown;
+        timezone?: string;
     };
     url: '/astrology/moon-phase/current';
 };
@@ -10678,9 +10700,13 @@ export type GetAstrologyHoroscopeBySignDailyData = {
          */
         lang?: 'en' | 'tr' | 'de' | 'es' | 'hi' | 'pt' | 'fr' | 'ru';
         /**
-         * Forecast date in YYYY-MM-DD format. Defaults to today. Supports future and past dates for editorial scheduling.
+         * Forecast date in YYYY-MM-DD format. Past and future dates are both supported, for editorial scheduling and backfill. Defaults to the current period in the timezone parameter.
          */
         date?: string;
+        /**
+         * Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each day. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
+         */
+        timezone?: string;
     };
     url: '/astrology/horoscope/{sign}/daily';
 };
@@ -10872,6 +10898,14 @@ export type GetAstrologyHoroscopeBySignWeeklyData = {
          * 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';
+        /**
+         * Any date inside the target week, in YYYY-MM-DD format. The forecast covers the Monday to Sunday week containing it. Defaults to the current period in the timezone parameter.
+         */
+        date?: string;
+        /**
+         * Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on each Monday. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
+         */
+        timezone?: string;
     };
     url: '/astrology/horoscope/{sign}/weekly';
 };
@@ -11047,6 +11081,14 @@ export type GetAstrologyHoroscopeBySignMonthlyData = {
          * 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';
+        /**
+         * Any date inside the target month, in YYYY-MM-DD format. The forecast covers the whole calendar month containing it. Defaults to the current period in the timezone parameter.
+         */
+        date?: string;
+        /**
+         * Selects which period counts as current when date is omitted. Defaults to UTC, so the forecast rolls over at 00:00 UTC on the 1st. Pass the timezone of the end user to roll over on their local clock instead. Ignored when date is set. Accepts an IANA name (e.g. "America/New_York"), decimal hours (e.g. 5.5 for IST), or a fixed UTC offset (e.g. "-05:00").
+         */
+        timezone?: string;
     };
     url: '/astrology/horoscope/{sign}/monthly';
 };
@@ -13781,9 +13823,13 @@ export type PostVedicAstrologyDashaCurrentData = {
          */
         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. 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. "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';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | '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 attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.
          */
@@ -13943,9 +13989,9 @@ export type PostVedicAstrologyDashaCurrentResponses = {
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.
+         * 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';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
         /**
          * Mahadasha (major planetary period) in the 120-year Vimshottari dasha cycle. Start and end dates are determined by Moon nakshatra at birth.
          */
@@ -14592,9 +14638,13 @@ export type PostVedicAstrologyDashaMajorData = {
          */
         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. 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. "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';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | '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 attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.
          */
@@ -14754,9 +14804,9 @@ export type PostVedicAstrologyDashaMajorResponses = {
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.
+         * 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';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
         /**
          * Remaining balance of the first Mahadasha at birth. Based on Moon degree within the birth nakshatra. partial dasha already elapsed before birth.
          */
@@ -14902,9 +14952,13 @@ export type PostVedicAstrologyDashaSubByMahadashaData = {
          */
         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. 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. "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';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | '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 attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.
          */
@@ -15061,9 +15115,9 @@ export type PostVedicAstrologyDashaSubByMahadashaResponses = {
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.
+         * 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';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
         /**
          * Full details of the parent Mahadasha including start/end dates and duration.
          */
@@ -15280,9 +15334,13 @@ export type PostVedicAstrologyDashaSubByMahadashaByAntardashaData = {
          */
         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. 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. "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';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | '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 attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.
          */
@@ -15447,9 +15505,9 @@ export type PostVedicAstrologyDashaSubByMahadashaByAntardashaResponses = {
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.
+         * 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';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
         /**
          * Full details of the parent Antardasha including start/end dates and duration.
          */
@@ -15674,9 +15732,13 @@ export type PostVedicAstrologyDashaSubByMahadashaByAntardashaByPratyantardashaDa
          */
         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. 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. "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';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | '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 attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.
          */
@@ -15849,9 +15911,9 @@ export type PostVedicAstrologyDashaSubByMahadashaByAntardashaByPratyantardashaRe
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.
+         * 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';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
         /**
          * Full details of the parent Pratyantardasha including start/end dates and duration.
          */
@@ -16084,9 +16146,13 @@ export type PostVedicAstrologyDashaSubByMahadashaByAntardashaByPratyantardashaBy
          */
         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. 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. "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';
+        ayanamsa?: 'kp-newcomb' | 'kp-old' | 'lahiri' | '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 attach the KP significators of each period lord: its star lord, sub lord, occupied house, the houses it signifies at levels L1 to L4, and a strength grade. Off by default, so responses stay exactly as they are for clients that only need dates. Requires the birth latitude and longitude, since significators are read off a Placidus house chart, and uses the same ayanamsa frame selected above.
          */
@@ -16267,9 +16333,9 @@ export type PostVedicAstrologyDashaSubByMahadashaByAntardashaByPratyantardashaBy
          */
         ayanamsa: number;
         /**
-         * Ayanamsa system used, echoing the request field. One of "lahiri", "kp-newcomb", "kp-old". Echoed so a client can confirm which frame produced these dates without re-deriving it.
+         * 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';
+        ayanamsaType: 'kp-newcomb' | 'kp-old' | 'lahiri' | 'custom';
         /**
          * Full details of the parent Sookshma dasha including start/end dates and duration.
          */
@@ -18574,6 +18640,14 @@ export type GetVedicAstrologyKpAyanamsaData = {
          * Date for ayanamsa calculation in YYYY-MM-DD format. Defaults to today if not provided. Ayanamsa changes by ~0.01 degrees per month due to the precession of Earth.
          */
         date?: string;
+        /**
+         * Time of day in 24-hour HH:MM:SS format, interpreted in the timezone below. Omit for midnight UTC. The ayanamsa moves about 0.14 arcseconds across a day, so supplying the time matters only when reconciling a chart against reference software to the arcsecond.
+         */
+        time?: string;
+        /**
+         * IANA name (e.g. "Asia/Kolkata", "America/New_York"), decimal hours (e.g. 5.5 for IST, -5 for EST), or a fixed UTC offset (e.g. "+05:30"). IANA resolved to the DST-correct offset for the given date. Applies to the time field above. Defaults to 0 (UTC).
+         */
+        timezone?: string;
     };
     url: '/vedic-astrology/kp/ayanamsa';
 };
@@ -18814,7 +18888,16 @@ export type PostVedicAstrologyKpPlanetsResponse = PostVedicAstrologyKpPlanetsRes
 export type PostVedicAstrologyKpCuspsData = {
     body?: KpCuspsRequest;
     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';
+        /**
+         * 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/cusps';
 };
 
@@ -19092,7 +19175,16 @@ export type PostVedicAstrologyKpRulingPlanetsData = {
         nodeType?: 'mean' | 'true';
     };
     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';
+        /**
+         * 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/ruling-planets';
 };
 
@@ -19245,7 +19337,16 @@ export type PostVedicAstrologyKpRulingPlanetsIntervalData = {
         nodeType?: 'mean' | 'true';
     };
     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';
+        /**
+         * 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/ruling-planets-interval';
 };
 

package/src/version.ts

@@ -1 +1 @@
-export const VERSION = '1.2.53';
+export const VERSION = '1.2.54';