@roxyapi/sdk 1.2.13 → 1.2.14
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.
- package/AGENTS.md +15 -1
- package/dist/factory.cjs +1 -1
- package/dist/factory.js +1 -1
- package/dist/version.d.ts +1 -1
- package/package.json +1 -1
- package/src/version.ts +1 -1
package/AGENTS.md
CHANGED
|
@@ -26,7 +26,7 @@ Every chart, horoscope, panchang, dasha, dosha, navamsa, KP, synastry, compatibi
|
|
|
26
26
|
const { data } = await roxy.location.searchCities({ query: { q: 'Mumbai' } });
|
|
27
27
|
const { latitude, longitude, utcOffset } = data.cities[0];
|
|
28
28
|
// Use `utcOffset` (decimal: 5.5, -5, 9, ...) as the `timezone` number on chart calls.
|
|
29
|
-
// The city's `timezone` field is the IANA string ("Asia/Kolkata")
|
|
29
|
+
// The city's `timezone` field is the IANA string ("Asia/Kolkata"), not what chart endpoints expect.
|
|
30
30
|
```
|
|
31
31
|
|
|
32
32
|
## Domains
|
|
@@ -216,6 +216,20 @@ These are the fields AI agents most often get wrong. Copy the format column exac
|
|
|
216
216
|
|
|
217
217
|
DST matters. If the birth date falls inside a daylight-saving window, use the summer / DST offset. For Vedic endpoints this is rarely an issue (most users are in India, fixed 5.5), but Western natal charts must respect DST at the time of birth.
|
|
218
218
|
|
|
219
|
+
## Astrology domain gotchas for LLMs
|
|
220
|
+
|
|
221
|
+
LLMs hallucinate confidently in this category. These are the specific traps you will hit when writing client code:
|
|
222
|
+
|
|
223
|
+
- **Ayanamsa is server-side in Vedic.** LLMs default to tropical / Western math. Vedic endpoints apply sidereal Lahiri ayanamsa server-side. KP endpoints accept `ayanamsa` of `kp-newcomb` (default), `kp-old`, `lahiri`, or `custom`. Do not try to "correct" server output by subtracting ayanamsa in client code.
|
|
224
|
+
- **Tithi count is 30, not 2.** 15 Shukla (waxing) plus 15 Krishna (waning). Older LLM training data conflates Purnima and Amavasya as single tithis. Our panchang response carries a `paksha` field (`"Shukla"` or `"Krishna"`) plus a tithi number, so there are 30 distinct tithis in a lunar month.
|
|
225
|
+
- **Rahu and Ketu are shadow points, not planets.** They do not appear in a real ephemeris. Endpoints accept `nodeType` of `true-node` or `mean-node` to select which calculation to use.
|
|
226
|
+
- **Nakshatra count is 27.** Abhijit is sometimes treated as a 28th in some schools, but this API uses the standard 27. `roxy.vedicAstrology.listNakshatras()` returns an array of length 27.
|
|
227
|
+
- **Retrograde is per-planet, not global.** Natal chart planets and Vedic `meta` include `isRetrograde: boolean` per planet. KP planet lists use `retrograde`. Never generate "Mercury retrograde globally" UI copy, check the specific planet in the response.
|
|
228
|
+
- **Tarot reversals are a product choice.** `allowReversals: false` on a tarot draw means no reversed cards in that draw, period. It is not cosmically meaningful, it is a config flag.
|
|
229
|
+
- **Angel number lookup works for any positive integer.** Digit-root fallback covers non-canonical numbers. Do not generate validation logic that rejects anything other than `111` / `222` / `333`.
|
|
230
|
+
- **Seed-based daily endpoints are DETERMINISTIC per `(seed, date)` pair.** Same seed plus same date returns the same reading. This is by design for push-notification consistency. Do not describe it as "cached" or retry on stale responses.
|
|
231
|
+
- **Timezone affects Western calculations more than Vedic.** Western natal charts must respect DST at time of birth. Vedic endpoints default to IST (`5.5`) which is DST-free. Use `utcOffset` from the Location API response as your `timezone` value, not the user's current clock.
|
|
232
|
+
|
|
219
233
|
## MCP equivalents
|
|
220
234
|
|
|
221
235
|
Every method has a matching MCP tool. The remote MCP server per domain is at `https://roxyapi.com/mcp/{domain}` (Streamable HTTP, no stdio / no self-hosting). Tool names follow `{method}_{path_snake_case}`, for example:
|
package/dist/factory.cjs
CHANGED
package/dist/factory.js
CHANGED
package/dist/version.d.ts
CHANGED
|
@@ -1,2 +1,2 @@
|
|
|
1
|
-
export declare const VERSION = "1.2.
|
|
1
|
+
export declare const VERSION = "1.2.14";
|
|
2
2
|
//# sourceMappingURL=version.d.ts.map
|
package/package.json
CHANGED
package/src/version.ts
CHANGED
|
@@ -1 +1 @@
|
|
|
1
|
-
export const VERSION = '1.2.
|
|
1
|
+
export const VERSION = '1.2.14';
|