Are the endpoints format-compatible with other Vedic astrology APIs?
Yes. Our endpoint paths, request parameters, and response shapes are designed for drop-in compatibility. The request format (dob, tob, lat, lon, tz, api_key) is identical to the industry standard. The response adds one field: remaining_api_calls. Most migrations require changing only the base URL environment variable.
Why is local Swiss Ephemeris computation better than external API dependency?
When a Vedic API relies on an external computation service, your uptime depends on that third party. If it goes down, your app goes down — even if our API is running perfectly. We run Swiss Ephemeris directly on our infrastructure, eliminating that dependency entirely. This is a structural reliability advantage that no configuration can replicate in external-dependency architectures.
What is the natal chart cache and why does it matter for pricing?
For any given birth date, time, and location, the natal chart never changes. We compute it once, store it permanently with a SHA-256 cache key, and return the cached result for all future calls with the same inputs. This means repeat requests for the same birth data do not consume API calls. Other providers typically charge per call even for identical birth data — you pay more as your user base grows.
Do you offer a migration support?
Yes. If you are switching from another Vedic astrology API and encounter any response format differences, our support team will help map the fields. Contact us at support@predintel.zohodesk.in with your current provider and we will provide a specific migration guide within 24 hours.