Developer GuideApril 202615 min migration

How to Switch from VedicAstroAPI
to VedIntel™ AstroAPI

This is a complete code-level migration guide. No hand-waving. If you currently call VedicAstroAPI and want to switch, this shows you exactly what changes — and what stays identical.

TL;DR
  • Change your base URL from api.vedicastroapi.com/v3-json to vedintelastroapi.com/v3-json
  • All parameter names stay identical: api_key, dob, tob, lat, lon, tz, ayanamsa, lang
  • All response fields stay identical: status, response — plus we add remaining_api_calls
  • Existing tests pass unchanged. Existing TypeScript types work.

1. Update Your Base URL

The entire migration is a one-line change to your environment variable. Every other line of code in your application stays exactly the same.

.env.local
# Remove this line:
VEDIC_API_BASE=https://api.vedicastroapi.com/v3-json
# Add this line:
VEDIC_API_BASE=https://vedintelastroapi.com/v3-json

Our /v3-json/* routes are configured as rewrites to /api/v1/* internally. You can call either path — the v3-json paths exist specifically for migration compatibility.

2. Replace Your API Key

Create a free account at vedintelastroapi.com/auth/signup and copy your API key from the dashboard. The parameter name is identical: api_key.

.env.local
# Remove:
VEDIC_API_KEY=vak_your_old_key
# Add:
VEDIC_API_KEY=vai_your_new_key
# The parameter name in every API call stays identical:
?api_key={process.env.VEDIC_API_KEY}

3. Parameter Mapping (Nothing Changes)

Every parameter name is identical. This table is for reference — you do not need to rename anything.

ParameterVedicAstroAPIVedIntel™ AstroAPINotes
api_keyapi_key✓ api_keyIdentical — just swap the key value
dobdob✓ dobDD/MM/YYYY format — identical
tobtob✓ tobHH:MM 24hr format — identical
latlat✓ latDecimal degrees — identical
lonlon✓ lonDecimal degrees — identical
tztz✓ tzDecimal offset e.g. 5.5 — identical
ayanamsaayanamsa✓ ayanamsalahiri / raman / kp — identical
langlang✓ langLanguage code — identical

4. Response Field Mapping

The response envelope is identical. We add one field: remaining_api_calls — which you can use or ignore.

Response comparison
// VedicAstroAPI response:
{ "status": 200, "response": { ...planet data... } }
// VedIntel™ AstroAPI response (identical + 1 new field):
{ "status": 200, "response": { ...same planet data... }, "remaining_api_calls": 498 // ← new, optional to use }

5. Endpoint Mapping (Phase 1 — All Core PredIntel Paths)

All core endpoints are available. Both path formats work — /v3-json/* rewrites to /api/v1/* transparently.

VedicAstroAPI pathVedIntel™ AstroAPI pathStatus
/v3-json/horoscope/planet-details/api/v1/horoscope/planet-details✓ Live
/v3-json/horoscope/divisional-charts/api/v1/horoscope/divisional-charts✓ Live
/v3-json/horoscope/chart-image/api/v1/horoscope/chart-image✓ Live
/v3-json/extended-horoscope/find-ascendant/api/v1/extended-horoscope/find-ascendant✓ Live
/v3-json/dashas/current-mahadasha-full/api/v1/dashas/current-mahadasha-full✓ Live
/v3-json/dashas/mahadasha/api/v1/dashas/mahadasha✓ Live
/v3-json/panchang/panchang/api/v1/panchang/panchang✓ Live
/v3-json/panchang/choghadiya-muhurta/api/v1/panchang/choghadiya-muhurta✓ Live
/v3-json/dosha/mangal-dosh/api/v1/dosha/mangal-dosh✓ Live
/v3-json/dosha/kaalsarp-dosh/api/v1/dosha/kaalsarp-dosh✓ Live
/v3-json/extended-horoscope/yoga-list/api/v1/extended-horoscope/yoga-list✓ Live — 30+ yogas

6. Verify With the Reference Chart

After migration, run this reference request and verify the output matches Jagannatha Hora. This is the exact chart we use for all internal accuracy tests.

Terminal
curl "https://vedintelastroapi.com/api/v1/horoscope/planet-details?api_key=YOUR_KEY&dob=01/10/1977&tob=11:40&lat=11&lon=77&tz=5.5"
Expected output (verified against Jagannatha Hora):
  • Ascendant: Sagittarius
  • Sun: Virgo (House 10), Nakshatra: Hasta
  • Moon: Aries (House 5), Nakshatra: Bharani
  • Mars: Cancer (House 8)
  • Venus: Leo (House 9)
  • All 10 planets at 0.0000° deviation from JHora reference

7. What You Get That VedicAstroAPI Cannot Offer

✓
Local Swiss Ephemeris
Zero external compute dependency. Their uptime issues never become your uptime issues.
✓
Permanent Natal Chart Cache
Same birth data is cached in Supabase forever. Second call returns in under 50ms. Never recomputed.
✓
Claude AI Narratives
Call /api/v1/ai/interpret/chart for a written chart interpretation. No competitor has this live.
✓
30+ Yoga Detection
Parashari engine migrated from PredIntel. Deeper yoga analysis than any public Vedic API.
✓
BPHS-Correct Divisional Charts
D9 Navamsa, D10 Dashamsha, D30 Trimshamsha — correct trikona and BPHS formulas. We published the verification.

Start the migration

500 free calls. All core endpoints. No credit card.

Create Free AccountFull Comparison →