@roxyapi/sdk 1.2.45 → 1.2.47

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/dist/factory.cjs +1 -1
  2. package/dist/factory.js +1 -1
  3. package/dist/types.gen.d.ts +251 -69
  4. package/dist/types.gen.d.ts.map +1 -1
  5. package/dist/version.d.ts +1 -1
  6. package/docs/llms-full.txt +16 -16
  7. package/package.json +1 -1
  8. package/src/types.gen.ts +252 -70
  9. package/src/version.ts +1 -1
package/dist/types.gen.d.ts CHANGED
@@ -339,7 +339,7 @@ export type NatalChartRequest = {
339
339
  */
340
340
  longitude: number;
341
341
  /**
342
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
342
+ * 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.
343
343
  */
344
344
  timezone: number | string;
345
345
  /**
@@ -714,7 +714,7 @@ export type AspectPatternsRequest = {
714
714
  */
715
715
  longitude: number;
716
716
  /**
717
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
717
+ * 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.
718
718
  */
719
719
  timezone: number | string;
720
720
  };
@@ -1541,7 +1541,7 @@ export type ArabicLotsRequest = {
1541
1541
  */
1542
1542
  longitude: number;
1543
1543
  /**
1544
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
1544
+ * 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.
1545
1545
  */
1546
1546
  timezone: number | string;
1547
1547
  /**
@@ -1643,7 +1643,7 @@ export type AsteroidsRequest = {
1643
1643
  */
1644
1644
  longitude: number;
1645
1645
  /**
1646
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
1646
+ * 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.
1647
1647
  */
1648
1648
  timezone: number | string;
1649
1649
  /**
@@ -1749,7 +1749,7 @@ export type LilithRequest = {
1749
1749
  */
1750
1750
  longitude: number;
1751
1751
  /**
1752
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
1752
+ * 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.
1753
1753
  */
1754
1754
  timezone: number | string;
1755
1755
  /**
@@ -1889,7 +1889,7 @@ export type ProgressionsRequest = {
1889
1889
  */
1890
1890
  longitude: number;
1891
1891
  /**
1892
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
1892
+ * 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.
1893
1893
  */
1894
1894
  timezone: number | string;
1895
1895
  /**
@@ -1983,7 +1983,7 @@ export type SolarArcRequest = {
1983
1983
  */
1984
1984
  longitude: number;
1985
1985
  /**
1986
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
1986
+ * 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.
1987
1987
  */
1988
1988
  timezone: number | string;
1989
1989
  /**
@@ -2077,7 +2077,7 @@ export type ProfectionsRequest = {
2077
2077
  */
2078
2078
  longitude: number;
2079
2079
  /**
2080
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
2080
+ * 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.
2081
2081
  */
2082
2082
  timezone: number | string;
2083
2083
  /**
@@ -2852,7 +2852,7 @@ export type BirthChartRequest = {
2852
2852
  */
2853
2853
  longitude: number;
2854
2854
  /**
2855
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
2855
+ * 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.
2856
2856
  */
2857
2857
  timezone?: number | string;
2858
2858
  };
@@ -2989,7 +2989,7 @@ export type NavamsaRequest = {
2989
2989
  */
2990
2990
  longitude: number;
2991
2991
  /**
2992
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
2992
+ * 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.
2993
2993
  */
2994
2994
  timezone?: number | string;
2995
2995
  };
@@ -3147,7 +3147,7 @@ export type DivisionalChartRequest = {
3147
3147
  */
3148
3148
  longitude: number;
3149
3149
  /**
3150
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3150
+ * 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.
3151
3151
  */
3152
3152
  timezone?: number | string;
3153
3153
  /**
@@ -3245,7 +3245,7 @@ export type CompatibilityRequest = {
3245
3245
  */
3246
3246
  longitude: number;
3247
3247
  /**
3248
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3248
+ * 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.
3249
3249
  */
3250
3250
  timezone?: number | string;
3251
3251
  };
@@ -3270,7 +3270,7 @@ export type CompatibilityRequest = {
3270
3270
  */
3271
3271
  longitude: number;
3272
3272
  /**
3273
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3273
+ * 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.
3274
3274
  */
3275
3275
  timezone?: number | string;
3276
3276
  };
@@ -3383,7 +3383,7 @@ export type PlanetaryPositionsRequest = {
3383
3383
  */
3384
3384
  longitude: number;
3385
3385
  /**
3386
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3386
+ * 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.
3387
3387
  */
3388
3388
  timezone?: number | string;
3389
3389
  };
@@ -3448,7 +3448,7 @@ export type ManglikRequest = {
3448
3448
  */
3449
3449
  longitude: number;
3450
3450
  /**
3451
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3451
+ * 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.
3452
3452
  */
3453
3453
  timezone?: number | string;
3454
3454
  };
@@ -3521,7 +3521,7 @@ export type KalsarpaRequest = {
3521
3521
  */
3522
3522
  longitude: number;
3523
3523
  /**
3524
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3524
+ * 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.
3525
3525
  */
3526
3526
  timezone?: number | string;
3527
3527
  };
@@ -3580,7 +3580,7 @@ export type SadhesatiRequest = {
3580
3580
  */
3581
3581
  longitude: number;
3582
3582
  /**
3583
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3583
+ * 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.
3584
3584
  */
3585
3585
  timezone?: number | string;
3586
3586
  };
@@ -3651,7 +3651,7 @@ export type YogaDetectRequest = {
3651
3651
  */
3652
3652
  longitude: number;
3653
3653
  /**
3654
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
3654
+ * 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.
3655
3655
  */
3656
3656
  timezone?: number | string;
3657
3657
  };
@@ -4522,7 +4522,7 @@ export type KpSublordChangesRequest = {
4522
4522
  */
4523
4523
  endDate: string;
4524
4524
  /**
4525
- * Decimal hours from UTC OR IANA name (e.g. "Asia/Kolkata"). IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).
4525
+ * IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).
4526
4526
  */
4527
4527
  timezone?: number | string;
4528
4528
  /**
@@ -4599,7 +4599,7 @@ export type KpRasiChangesRequest = {
4599
4599
  */
4600
4600
  endDate: string;
4601
4601
  /**
4602
- * Decimal hours from UTC OR IANA name (e.g. "Asia/Kolkata"). IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).
4602
+ * IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for startDate. Output times are converted to this timezone. Defaults to 0 (UTC).
4603
4603
  */
4604
4604
  timezone?: number | string;
4605
4605
  /**
@@ -4723,7 +4723,7 @@ export type KpPlanetsIntervalRequest = {
4723
4723
  */
4724
4724
  longitude: number;
4725
4725
  /**
4726
- * Decimal hours from UTC OR IANA name (e.g. "Asia/Kolkata"). IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Defaults to 0 (UTC).
4726
+ * IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset for the startDatetime date. When non-zero, all datetimes are treated as local time in this timezone (Z suffix is ignored). Defaults to 0 (UTC).
4727
4727
  */
4728
4728
  timezone?: number | string;
4729
4729
  /**
@@ -4986,7 +4986,7 @@ export type UpagrahaRequest = {
4986
4986
  */
4987
4987
  longitude: number;
4988
4988
  /**
4989
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
4989
+ * 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.
4990
4990
  */
4991
4991
  timezone?: number | string;
4992
4992
  };
@@ -5098,7 +5098,7 @@ export type AshtakavargaRequest = {
5098
5098
  */
5099
5099
  longitude: number;
5100
5100
  /**
5101
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
5101
+ * 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.
5102
5102
  */
5103
5103
  timezone?: number | string;
5104
5104
  };
@@ -5186,7 +5186,7 @@ export type ShadbalaRequest = {
5186
5186
  */
5187
5187
  longitude: number;
5188
5188
  /**
5189
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
5189
+ * 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.
5190
5190
  */
5191
5191
  timezone?: number | string;
5192
5192
  };
@@ -5383,6 +5383,20 @@ export type DrawnCard = {
5383
5383
  */
5384
5384
  imageUrl: string;
5385
5385
  };
5386
+ export type ChangingLine = {
5387
+ /**
5388
+ * Line position (1-6, bottom to top). In I-Ching, each hexagram has six lines (yao) read from bottom upward.
5389
+ */
5390
+ position: number;
5391
+ /**
5392
+ * The oracle statement for this line. It applies when this specific line comes up changing (old yin or old yang) in a casting, and it speaks in the concrete imagery of the tradition.
5393
+ */
5394
+ text: string;
5395
+ /**
5396
+ * What the line statement asks of the querent, read from its position in the hexagram (1 is the hidden beginning, 3 is the exposed threshold, 5 is the ruling line, 6 is past the peak) and from whether the line is yin or yang. This is the meaning behind the image, so a consuming agent does not have to invent one.
5397
+ */
5398
+ meaning?: string;
5399
+ };
5386
5400
  export type BasicHexagram = {
5387
5401
  /**
5388
5402
  * Hexagram number in King Wen sequence (1-64).
@@ -5482,16 +5496,6 @@ export type Interpretation = {
5482
5496
  */
5483
5497
  advice: string;
5484
5498
  };
5485
- export type ChangingLine = {
5486
- /**
5487
- * Line position (1-6, bottom to top). In I-Ching, each hexagram has six lines (yao) read from bottom upward.
5488
- */
5489
- position: number;
5490
- /**
5491
- * Changing line interpretation text. Applies only when this specific line is a changing line (old yin or old yang) in a casting.
5492
- */
5493
- text: string;
5494
- };
5495
5499
  export type BasicTrigram = {
5496
5500
  /**
5497
5501
  * Trigram number (1-8)
@@ -5524,7 +5528,7 @@ export type BasicTrigram = {
5524
5528
  };
5525
5529
  export type Trigram = {
5526
5530
  /**
5527
- * Trigram number (1-8) in the traditional I-Ching ordering.
5531
+ * Stable identifier for the trigram, 1 to 8. This is our lookup key, not a canonical sequence: the tradition has several orderings (King Wen, Fu Xi, Earlier and Later Heaven) and they disagree, so do not read ranking or precedence into it.
5528
5532
  */
5529
5533
  number: number;
5530
5534
  /**
@@ -6710,7 +6714,7 @@ export type GetAstrologyMoonPhaseCurrentData = {
6710
6714
  */
6711
6715
  time?: string;
6712
6716
  /**
6713
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata"). IANA resolved to the DST-correct offset for the given date. Defaults to 0 (UTC).
6717
+ * 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).
6714
6718
  */
6715
6719
  timezone?: number | string | unknown;
6716
6720
  };
@@ -7200,7 +7204,7 @@ export type PostAstrologySynastryData = {
7200
7204
  */
7201
7205
  longitude: number;
7202
7206
  /**
7203
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
7207
+ * 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.
7204
7208
  */
7205
7209
  timezone: number | string;
7206
7210
  /**
@@ -7226,7 +7230,7 @@ export type PostAstrologySynastryData = {
7226
7230
  */
7227
7231
  longitude: number;
7228
7232
  /**
7229
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
7233
+ * 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.
7230
7234
  */
7231
7235
  timezone: number | string;
7232
7236
  /**
@@ -8069,7 +8073,7 @@ export type PostAstrologyTransitAspectsData = {
8069
8073
  */
8070
8074
  longitude: number;
8071
8075
  /**
8072
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
8076
+ * 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.
8073
8077
  */
8074
8078
  timezone: number | string;
8075
8079
  };
@@ -9193,7 +9197,7 @@ export type PostAstrologyCompositeChartData = {
9193
9197
  */
9194
9198
  longitude: number;
9195
9199
  /**
9196
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
9200
+ * 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.
9197
9201
  */
9198
9202
  timezone: number | string;
9199
9203
  };
@@ -9218,7 +9222,7 @@ export type PostAstrologyCompositeChartData = {
9218
9222
  */
9219
9223
  longitude: number;
9220
9224
  /**
9221
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
9225
+ * 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.
9222
9226
  */
9223
9227
  timezone: number | string;
9224
9228
  };
@@ -9582,7 +9586,7 @@ export type PostAstrologyCompatibilityScoreData = {
9582
9586
  */
9583
9587
  longitude: number;
9584
9588
  /**
9585
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
9589
+ * 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.
9586
9590
  */
9587
9591
  timezone: number | string;
9588
9592
  };
@@ -9607,7 +9611,7 @@ export type PostAstrologyCompatibilityScoreData = {
9607
9611
  */
9608
9612
  longitude: number;
9609
9613
  /**
9610
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
9614
+ * 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.
9611
9615
  */
9612
9616
  timezone: number | string;
9613
9617
  };
@@ -11045,7 +11049,7 @@ export type PostAstrologyAstrocartographyData = {
11045
11049
  */
11046
11050
  longitude: number;
11047
11051
  /**
11048
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
11052
+ * 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.
11049
11053
  */
11050
11054
  timezone: number | string;
11051
11055
  };
@@ -11455,7 +11459,7 @@ export type PostAstrologyFixedStarsData = {
11455
11459
  */
11456
11460
  longitude: number;
11457
11461
  /**
11458
- * Timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York", "Asia/Kolkata"). IANA strings are resolved to the DST-correct offset for the given date, so you can pass `cities[0].timezone` from /location/search directly.
11462
+ * 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.
11459
11463
  */
11460
11464
  timezone: number | string;
11461
11465
  };
@@ -13091,7 +13095,7 @@ export type PostVedicAstrologyDashaCurrentData = {
13091
13095
  */
13092
13096
  longitude: number;
13093
13097
  /**
13094
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
13098
+ * 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.
13095
13099
  */
13096
13100
  timezone?: number | string;
13097
13101
  };
@@ -13395,7 +13399,7 @@ export type PostVedicAstrologyDashaMajorData = {
13395
13399
  */
13396
13400
  longitude: number;
13397
13401
  /**
13398
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
13402
+ * 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.
13399
13403
  */
13400
13404
  timezone?: number | string;
13401
13405
  };
@@ -13599,7 +13603,7 @@ export type PostVedicAstrologyDashaSubByMahadashaData = {
13599
13603
  */
13600
13604
  longitude: number;
13601
13605
  /**
13602
- * Timezone: decimal hours from UTC (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "Asia/Kolkata", "America/New_York"). 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 (IST).
13606
+ * 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.
13603
13607
  */
13604
13608
  timezone?: number | string;
13605
13609
  };
@@ -16316,7 +16320,7 @@ export type PostVedicAstrologyKpRulingPlanetsData = {
16316
16320
  */
16317
16321
  longitude: number;
16318
16322
  /**
16319
- * Timezone: decimal hours from UTC OR IANA name (e.g. "Asia/Kolkata"). IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5 (IST).
16323
+ * Timezone: IANA name (e.g. "America/New_York", "Europe/London") OR decimal hours from UTC. IANA resolved to the DST-correct offset based on birthDate or datetime. Defaults to 5.5.
16320
16324
  */
16321
16325
  timezone?: number | string;
16322
16326
  /**
@@ -25638,7 +25642,7 @@ export type PostHumanDesignBodygraphData = {
25638
25642
  */
25639
25643
  time: string;
25640
25644
  /**
25641
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
25645
+ * 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.
25642
25646
  */
25643
25647
  timezone: number | string;
25644
25648
  /**
@@ -25770,14 +25774,30 @@ export type PostHumanDesignBodygraphResponses = {
25770
25774
  * Human Design energy type. One of Manifestor, Generator, Manifesting Generator, Projector, Reflector.
25771
25775
  */
25772
25776
  type: string;
25777
+ /**
25778
+ * What the aura of this type does and how it is designed to engage life. The grounding text for the type label, so a consuming agent does not have to supply the meaning itself.
25779
+ */
25780
+ typeDescription: string;
25781
+ /**
25782
+ * The aura mechanic of the type: how the energy field itself operates, for example open and enveloping, or closed and repelling.
25783
+ */
25784
+ aura: string;
25773
25785
  /**
25774
25786
  * The aura strategy for engaging life correctly for this type.
25775
25787
  */
25776
25788
  strategy: string;
25789
+ /**
25790
+ * How to actually apply the strategy. The strategy field alone is a bare label such as Respond or Inform; this is the operating instruction behind it.
25791
+ */
25792
+ strategyDescription: string;
25777
25793
  /**
25778
25794
  * Inner authority for decision making. One of Emotional, Sacral, Splenic, Ego, Self-Projected, Mental, Lunar.
25779
25795
  */
25780
25796
  authority: string;
25797
+ /**
25798
+ * How the decision is made, the timing it requires, and the characteristic trap. Inner authority is the most actionable output of a Human Design chart, so this is the field to lean on when grounding a reading.
25799
+ */
25800
+ authorityDescription: string;
25781
25801
  /**
25782
25802
  * The signature feeling of living in alignment with the type.
25783
25803
  */
@@ -25790,10 +25810,45 @@ export type PostHumanDesignBodygraphResponses = {
25790
25810
  * Profile in conscious/unconscious form from the Personality Sun line over the Design Sun line.
25791
25811
  */
25792
25812
  profile: string;
25813
+ /**
25814
+ * The two line keynotes the profile is built from, conscious over unconscious, so the profile is readable without a separate lookup.
25815
+ */
25816
+ profileKeynotes: {
25817
+ /**
25818
+ * Line number 1 to 6 of the conscious Personality Sun, the first digit of the profile.
25819
+ */
25820
+ personalityLine: number;
25821
+ /**
25822
+ * Line number 1 to 6 of the unconscious Design Sun, the second digit of the profile.
25823
+ */
25824
+ designLine: number;
25825
+ /**
25826
+ * Keynote of the conscious Personality line. The half of the life role the person is aware of and can speak to.
25827
+ */
25828
+ personality: string;
25829
+ /**
25830
+ * Keynote of the unconscious Design line. The half of the life role others see operating in the body, which the person does not directly experience.
25831
+ */
25832
+ design: string;
25833
+ };
25834
+ /**
25835
+ * Meaning of the combined profile. A profile is not the sum of its two lines: 6/2 has its own meaning that neither the line 6 nor the line 2 keynote carries alone.
25836
+ */
25837
+ profileDescription: string;
25793
25838
  /**
25794
25839
  * Definition type from the number of connected components among defined centers. One of None, Single, Split, Triple Split, Quadruple Split.
25795
25840
  */
25796
25841
  definition: string;
25842
+ /**
25843
+ * How energy flows through the defined centers in this configuration, and what the configuration needs. For a split, this is where the bridging gates of other people matter.
25844
+ */
25845
+ definitionDescription: string;
25846
+ /**
25847
+ * What the two chart sides are: personality is the conscious mind side, design is the unconscious body side computed 88 degrees of solar arc before birth. Returned once at the top level rather than repeated across all 26 activations.
25848
+ */
25849
+ sides: {
25850
+ [key: string]: string;
25851
+ };
25797
25852
  /**
25798
25853
  * The incarnation cross built from the four cardinal gates and the profile angle.
25799
25854
  */
@@ -25814,6 +25869,10 @@ export type PostHumanDesignBodygraphResponses = {
25814
25869
  * Canonical published name of the incarnation cross, determined by the Personality Sun gate and the angle. Falls back to a name composed from the angle and the four gates if no canonical name exists.
25815
25870
  */
25816
25871
  name: string;
25872
+ /**
25873
+ * The life theme of the cross, synthesized from its four gates and the orientation the angle gives them. The same Sun gate under a different angle is a genuinely different theme: Right Angle is personal destiny, Left Angle is worked out through other people, Juxtaposition is a fixed fate.
25874
+ */
25875
+ description?: string;
25817
25876
  };
25818
25877
  /**
25819
25878
  * All nine centers with their defined state and active gates.
@@ -25843,6 +25902,14 @@ export type PostHumanDesignBodygraphResponses = {
25843
25902
  * Theme text describing the center in its current defined or undefined state.
25844
25903
  */
25845
25904
  theme: string;
25905
+ /**
25906
+ * The conditioning trap of this center when it is open. Returned on every center so a consumer can surface it the moment `defined` is false, which is where the not-self operates.
25907
+ */
25908
+ notSelfQuestion: string;
25909
+ /**
25910
+ * The gland, organ, or system this center corresponds to in the body.
25911
+ */
25912
+ biology: string;
25846
25913
  /**
25847
25914
  * Active gate numbers that sit in this center.
25848
25915
  */
@@ -25872,6 +25939,14 @@ export type PostHumanDesignBodygraphResponses = {
25872
25939
  * The two centers this channel connects and defines.
25873
25940
  */
25874
25941
  centers: Array<string>;
25942
+ /**
25943
+ * What this channel wires between its two centers and the nature of the energy it carries.
25944
+ */
25945
+ description: string;
25946
+ /**
25947
+ * What the circuit family of this channel governs.
25948
+ */
25949
+ circuitDescription: string;
25875
25950
  }>;
25876
25951
  /**
25877
25952
  * All 26 activations, 13 Personality and 13 Design.
@@ -25897,6 +25972,18 @@ export type PostHumanDesignBodygraphResponses = {
25897
25972
  * Human Design keynote name of the gate, describing its bodygraph function.
25898
25973
  */
25899
25974
  gateName: string;
25975
+ /**
25976
+ * Bodygraph function of the gate: what it does in the center it sits in and the channel it forms. This is NOT the meaning of the I-Ching hexagram that shares its number. They share a number, not a definition.
25977
+ */
25978
+ gateDescription: string;
25979
+ /**
25980
+ * Meaning of this gate at this specific line, one of 384. The finest interpretive layer in the chart and the one that makes a reading specific rather than generic. This is not the six abstract line archetypes: gate 41 line 3 carries its own meaning that neither the gate keynote nor the line-3 archetype holds alone.
25981
+ */
25982
+ lineMeaning: string;
25983
+ /**
25984
+ * What this planetary activation contributes in Human Design specifically, which is not its meaning in western astrology.
25985
+ */
25986
+ planetDescription: string;
25900
25987
  /**
25901
25988
  * Cross-reference to the I-Ching hexagram that shares this gate number.
25902
25989
  */
@@ -25929,7 +26016,7 @@ export type PostHumanDesignConnectionData = {
25929
26016
  */
25930
26017
  time: string;
25931
26018
  /**
25932
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
26019
+ * 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.
25933
26020
  */
25934
26021
  timezone: number | string;
25935
26022
  /**
@@ -25954,7 +26041,7 @@ export type PostHumanDesignConnectionData = {
25954
26041
  */
25955
26042
  time: string;
25956
26043
  /**
25957
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
26044
+ * 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.
25958
26045
  */
25959
26046
  timezone: number | string;
25960
26047
  /**
@@ -26188,7 +26275,7 @@ export type PostHumanDesignPentaData = {
26188
26275
  */
26189
26276
  time: string;
26190
26277
  /**
26191
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
26278
+ * 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.
26192
26279
  */
26193
26280
  timezone: number | string;
26194
26281
  /**
@@ -26422,7 +26509,7 @@ export type PostHumanDesignTransitData = {
26422
26509
  */
26423
26510
  time: string;
26424
26511
  /**
26425
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
26512
+ * 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.
26426
26513
  */
26427
26514
  timezone: number | string;
26428
26515
  /**
@@ -26677,7 +26764,7 @@ export type PostHumanDesignTypeData = {
26677
26764
  */
26678
26765
  time: string;
26679
26766
  /**
26680
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
26767
+ * 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.
26681
26768
  */
26682
26769
  timezone: number | string;
26683
26770
  /**
@@ -26809,14 +26896,30 @@ export type PostHumanDesignTypeResponses = {
26809
26896
  * Human Design energy type. One of Manifestor, Generator, Manifesting Generator, Projector, Reflector.
26810
26897
  */
26811
26898
  type: string;
26899
+ /**
26900
+ * What the aura of this type does and how it is designed to engage life. The grounding text for the type label, so a consuming agent does not have to supply the meaning itself.
26901
+ */
26902
+ typeDescription: string;
26903
+ /**
26904
+ * The aura mechanic of the type: how the energy field itself operates, for example open and enveloping, or closed and repelling.
26905
+ */
26906
+ aura: string;
26812
26907
  /**
26813
26908
  * The aura strategy for engaging life correctly for this type.
26814
26909
  */
26815
26910
  strategy: string;
26911
+ /**
26912
+ * How to actually apply the strategy. The strategy field alone is a bare label such as Respond or Inform; this is the operating instruction behind it.
26913
+ */
26914
+ strategyDescription: string;
26816
26915
  /**
26817
26916
  * Inner authority for decision making. One of Emotional, Sacral, Splenic, Ego, Self-Projected, Mental, Lunar.
26818
26917
  */
26819
26918
  authority: string;
26919
+ /**
26920
+ * How the decision is made, the timing it requires, and the characteristic trap. Inner authority is the most actionable output of a Human Design chart.
26921
+ */
26922
+ authorityDescription: string;
26820
26923
  /**
26821
26924
  * The signature feeling of living in alignment.
26822
26925
  */
@@ -26843,7 +26946,7 @@ export type PostHumanDesignGatesData = {
26843
26946
  */
26844
26947
  time: string;
26845
26948
  /**
26846
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
26949
+ * 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.
26847
26950
  */
26848
26951
  timezone: number | string;
26849
26952
  /**
@@ -26995,6 +27098,18 @@ export type PostHumanDesignGatesResponses = {
26995
27098
  * Human Design keynote name of the gate, describing its bodygraph function.
26996
27099
  */
26997
27100
  gateName: string;
27101
+ /**
27102
+ * Bodygraph function of the gate: what it does in the center it sits in and the channel it forms. This is NOT the meaning of the I-Ching hexagram that shares its number. They share a number, not a definition.
27103
+ */
27104
+ gateDescription: string;
27105
+ /**
27106
+ * Meaning of this gate at this specific line, one of 384. The finest interpretive layer in the chart and the one that makes a reading specific rather than generic. This is not the six abstract line archetypes: gate 41 line 3 carries its own meaning that neither the gate keynote nor the line-3 archetype holds alone.
27107
+ */
27108
+ lineMeaning: string;
27109
+ /**
27110
+ * What this planetary activation contributes in Human Design specifically, which is not its meaning in western astrology.
27111
+ */
27112
+ planetDescription: string;
26998
27113
  /**
26999
27114
  * Cross-reference to the I-Ching hexagram that shares this gate number.
27000
27115
  */
@@ -27033,6 +27148,18 @@ export type PostHumanDesignGatesResponses = {
27033
27148
  * Human Design keynote name of the gate, describing its bodygraph function.
27034
27149
  */
27035
27150
  gateName: string;
27151
+ /**
27152
+ * Bodygraph function of the gate: what it does in the center it sits in and the channel it forms. This is NOT the meaning of the I-Ching hexagram that shares its number. They share a number, not a definition.
27153
+ */
27154
+ gateDescription: string;
27155
+ /**
27156
+ * Meaning of this gate at this specific line, one of 384. The finest interpretive layer in the chart and the one that makes a reading specific rather than generic. This is not the six abstract line archetypes: gate 41 line 3 carries its own meaning that neither the gate keynote nor the line-3 archetype holds alone.
27157
+ */
27158
+ lineMeaning: string;
27159
+ /**
27160
+ * What this planetary activation contributes in Human Design specifically, which is not its meaning in western astrology.
27161
+ */
27162
+ planetDescription: string;
27036
27163
  /**
27037
27164
  * Cross-reference to the I-Ching hexagram that shares this gate number.
27038
27165
  */
@@ -27242,7 +27369,7 @@ export type PostHumanDesignChannelsData = {
27242
27369
  */
27243
27370
  time: string;
27244
27371
  /**
27245
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
27372
+ * 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.
27246
27373
  */
27247
27374
  timezone: number | string;
27248
27375
  /**
@@ -27394,6 +27521,14 @@ export type PostHumanDesignChannelsResponses = {
27394
27521
  * The two centers this channel connects and defines.
27395
27522
  */
27396
27523
  centers: Array<string>;
27524
+ /**
27525
+ * What this channel wires between its two centers and the nature of the energy it carries.
27526
+ */
27527
+ description: string;
27528
+ /**
27529
+ * What the circuit family of this channel governs.
27530
+ */
27531
+ circuitDescription: string;
27397
27532
  }>;
27398
27533
  /**
27399
27534
  * Number of defined channels in the bodygraph.
@@ -27417,7 +27552,7 @@ export type PostHumanDesignCentersData = {
27417
27552
  */
27418
27553
  time: string;
27419
27554
  /**
27420
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
27555
+ * 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.
27421
27556
  */
27422
27557
  timezone: number | string;
27423
27558
  /**
@@ -27573,6 +27708,14 @@ export type PostHumanDesignCentersResponses = {
27573
27708
  * Theme text describing the center in its current defined or undefined state.
27574
27709
  */
27575
27710
  theme: string;
27711
+ /**
27712
+ * The conditioning trap of this center when it is open. Returned on every center so a consumer can surface it the moment `defined` is false, which is where the not-self operates.
27713
+ */
27714
+ notSelfQuestion: string;
27715
+ /**
27716
+ * The gland, organ, or system this center corresponds to in the body.
27717
+ */
27718
+ biology: string;
27576
27719
  /**
27577
27720
  * Active gate numbers that sit in this center.
27578
27721
  */
@@ -27746,7 +27889,7 @@ export type PostHumanDesignProfileData = {
27746
27889
  */
27747
27890
  time: string;
27748
27891
  /**
27749
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
27892
+ * 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.
27750
27893
  */
27751
27894
  timezone: number | string;
27752
27895
  /**
@@ -27908,7 +28051,7 @@ export type PostHumanDesignVariablesData = {
27908
28051
  */
27909
28052
  time: string;
27910
28053
  /**
27911
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
28054
+ * 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.
27912
28055
  */
27913
28056
  timezone: number | string;
27914
28057
  /**
@@ -28093,6 +28236,37 @@ export type PostHumanDesignVariablesResponses = {
28093
28236
  * Keynote of the arrow direction for this arrow, for example Active or Passive for Determination, Focused or Peripheral for Perspective.
28094
28237
  */
28095
28238
  directionLabel: string;
28239
+ /**
28240
+ * What this arrow is and what it governs.
28241
+ */
28242
+ description: string;
28243
+ /**
28244
+ * What the layer this arrow belongs to governs, the body side or the mind side.
28245
+ */
28246
+ layerDescription: string;
28247
+ /**
28248
+ * Meaning of the Color for THIS arrow. The same Color number means something different under Determination than under Motivation, so this is the reading of colorLabel in context, not a generic gloss.
28249
+ */
28250
+ colorMeaning: string;
28251
+ /**
28252
+ * Meaning of the Tone. The six Tones are shared across all four arrows: the arrow does not change the Tone, it changes what the Tone qualifies.
28253
+ */
28254
+ toneMeaning: string;
28255
+ /**
28256
+ * Meaning of the left or right direction for THIS arrow, the reading of directionLabel.
28257
+ */
28258
+ directionMeaning: string;
28259
+ /**
28260
+ * Name of the Base. Informational only: the Base is finer than any civil birth time can resolve.
28261
+ */
28262
+ baseName: string;
28263
+ /**
28264
+ * 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.
28265
+ */
28266
+ cognition?: {
28267
+ label: string;
28268
+ description: string;
28269
+ };
28096
28270
  /**
28097
28271
  * Whether this arrow is far enough from a Color or Tone boundary to be reliable. When false the activation sits on a knife edge where the Color label or the arrow direction could flip with a more precise birth time, and the arrow should not be presented as fact.
28098
28272
  */
@@ -28106,6 +28280,10 @@ export type PostHumanDesignVariablesResponses = {
28106
28280
  * Boundary margin in degrees of ecliptic longitude used for the per-arrow confidence flag, the solar arc over a few minutes of clock time. An activation within this distance of a Color or Tone boundary is flagged low-confidence.
28107
28281
  */
28108
28282
  confidenceMarginDeg: number;
28283
+ /**
28284
+ * What the Base layer is. Returned once at the top level rather than repeated on every arrow, since the Base layer is the same concept for all four. No per-Base meaning is returned: every one in circulation traces back to a single origin, so it fails the two-source bar this package holds.
28285
+ */
28286
+ baseDescription: string;
28109
28287
  };
28110
28288
  };
28111
28289
  export type PostHumanDesignVariablesResponse = PostHumanDesignVariablesResponses[keyof PostHumanDesignVariablesResponses];
@@ -28124,7 +28302,7 @@ export type PostForecastTimelineData = {
28124
28302
  */
28125
28303
  time: string;
28126
28304
  /**
28127
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
28305
+ * 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.
28128
28306
  */
28129
28307
  timezone: number | string;
28130
28308
  /**
@@ -28299,7 +28477,7 @@ export type PostForecastTimelineResponses = {
28299
28477
  */
28300
28478
  time: string;
28301
28479
  /**
28302
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
28480
+ * 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.
28303
28481
  */
28304
28482
  timezone: number | string;
28305
28483
  /**
@@ -28402,7 +28580,7 @@ export type PostForecastTransitsData = {
28402
28580
  */
28403
28581
  time: string;
28404
28582
  /**
28405
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
28583
+ * 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.
28406
28584
  */
28407
28585
  timezone: number | string;
28408
28586
  /**
@@ -28556,7 +28734,7 @@ export type PostForecastTransitsResponses = {
28556
28734
  */
28557
28735
  time: string;
28558
28736
  /**
28559
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
28737
+ * 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.
28560
28738
  */
28561
28739
  timezone: number | string;
28562
28740
  /**
@@ -28659,7 +28837,7 @@ export type PostForecastSignificantDatesData = {
28659
28837
  */
28660
28838
  time: string;
28661
28839
  /**
28662
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
28840
+ * 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.
28663
28841
  */
28664
28842
  timezone: number | string;
28665
28843
  /**
@@ -28834,7 +29012,7 @@ export type PostForecastSignificantDatesResponses = {
28834
29012
  */
28835
29013
  time: string;
28836
29014
  /**
28837
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
29015
+ * 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.
28838
29016
  */
28839
29017
  timezone: number | string;
28840
29018
  /**
@@ -28937,7 +29115,7 @@ export type PostForecastDigestData = {
28937
29115
  */
28938
29116
  time: string;
28939
29117
  /**
28940
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
29118
+ * 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.
28941
29119
  */
28942
29120
  timezone: number | string;
28943
29121
  /**
@@ -29112,7 +29290,7 @@ export type PostForecastDigestResponses = {
29112
29290
  */
29113
29291
  time: string;
29114
29292
  /**
29115
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
29293
+ * 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.
29116
29294
  */
29117
29295
  timezone: number | string;
29118
29296
  /**
@@ -29260,7 +29438,7 @@ export type PostForecastSolarReturnData = {
29260
29438
  */
29261
29439
  longitude: number;
29262
29440
  /**
29263
- * Decimal hours (e.g. 5.5 for IST, -5 for EST) OR IANA name (e.g. "America/New_York", "UTC"). IANA is resolved to the DST-correct offset for the request date. Invalid timezones return 400 with a validation error.
29441
+ * 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.
29264
29442
  */
29265
29443
  timezone: number | string;
29266
29444
  /**
@@ -31223,6 +31401,10 @@ export type PostIchingDailyCastResponses = {
31223
31401
  * Positions of changing lines (1-6, bottom to top). These lines transform yin to yang or vice versa.
31224
31402
  */
31225
31403
  changingLinePositions: Array<number>;
31404
+ /**
31405
+ * The oracle statement and meaning of each line that came up CHANGING, and only those. The changing lines are what the cast is actually about, so this saves a second call to read them and stops a consuming agent from having to invent them.
31406
+ */
31407
+ changingLines?: Array<ChangingLine>;
31226
31408
  /**
31227
31409
  * Hexagram after transformation (if changing lines present)
31228
31410
  */