The astrology engine for builders

Astrology, as an API.

130 endpoints. Six traditions. One key. Drop birth charts, compatibility, dashas, horary, and forecasts into your matrimony, horoscope, or D2C app — without becoming an astrologer.

Get free API keyTry in playground
  • GST-compliant invoices
  • Razorpay-billed
  • Up in 2 minutes
  • Sub-arcminute accuracy
Sample requestPOST /v1/charts/birth
bash
curl -X POST https://api.astronode.dev/v1/charts/birth \
  -H "Authorization: Bearer aie_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "date": "1973-04-24",
    "time": "17:25:00",
    "tz_offset_minutes": 330,
    "lat": 19.076,
    "lng": 72.8777
  }'

Six traditions, one consistent JSON shape

Capabilities

Six traditions, one unified surface.

Each tradition ships as a coherent cluster of endpoints with the same JSON envelope and the same auth. Click into any one to browse its full surface — sample requests, the tier each endpoint sits behind, and everything you need for your integration.

🪐

Vedic

12 endpoints

Birth charts, varga, dasha, varshphal, panchang.

Explore Vedic →

🪷

KP

7 endpoints

Cuspal sub-lord theory + horary 1–249.

Explore KP →

🪔

Lal Kitab

5 endpoints

Fixed-house kundli, 7 rins, and remedies.

Explore Lal Kitab →

🔢

Numerology

5 endpoints

Pythagorean and Chaldean reductions, ank milan.

Explore Numerology →

⭐

Western

12 endpoints

Tropical natal, transits, synastry, sun-sign forecasts.

Explore Western →

💞

Compatibility

9 endpoints

Cross-tradition match: Ashtakoot, Porutham, synastry, ank milan.

Explore Compatibility →

📜

Reports

7 endpoints

Async PDF reports for chart, compatibility, varshphal, KP, LK, Western.

Explore Reports →

How it works

Three steps, fifteen minutes.

1

Sign up & get a key

Free tier covers 100 calls/day. Email-verify, generate a test key in one click.

export AIE_KEY="aie_test_..."
2

POST a birth input

Same JSON envelope across every tradition. Lat/lng/tz_offset_minutes — no place-name geocoding needed.

curl -X POST $AIE_API/v1/charts/birth -d '{...birth}'
3

Render the response

Use our SDK or your own. Every response carries request_id, engine_version, and an interpretation envelope.

{ data: { planets, houses, ... }, meta }

For developers

Integration in 15 minutes.

One bearer token. One request envelope. Same response shape across every endpoint: { request_id, data, interpretation, meta }. Sign up, paste your key into curl, get a chart back. No SDK required, no XML, no surprise auth dance.

  • · Bearer-token auth (test + live keys)
  • · Per-key rate limiting + monthly quotas
  • · Idempotency keys on every write-equivalent endpoint
  • · OpenAPI 3.1 spec auto-published at /v1/openapi.json
  • · Deterministic: same input + engine version → byte-identical output
curl
curl -X POST https://api.aie.example.com/v1/charts/birth \
  -H "Authorization: Bearer aie_test_..." \
  -H "Content-Type: application/json" \
  -d '{
    "date": "1995-08-14",
    "time": "14:32:00",
    "tz_offset_minutes": 330,
    "lat": 18.5204,
    "lng": 73.8567
  }'

For individuals

Reports a non-technical reader can actually understand.

Raw planet positions are a commodity. Meaning is the moat. Every response carries an optional interpretation block — short, plain-English narrative, deterministically composed from versioned content. No LLM hallucinations, no fortune-teller theatrics, no medical or financial claims.

  • · Three report types today: chart summary, compatibility, Mangal Dosha
  • · English at launch, Hindi as 30-day fast-follow
  • · Content-lint enforced in CI — no accidental medical or financial language ships
  • · Versioned: every report carries the engine + interpretation version
  • · Public share links: opt-in, revocable, no PII leaked unless explicitly chosen
View live sample report
“Moderate compatibility (22 / 36). The match has structural stability through friendly planetary lords, but emotional patterns differ — partners may approach decisions from different starting points. Long-term success depends on conscious communication around temperament and timing rather than instinctive alignment.”
Sample compatibility narrative · v1.0.0

Pricing

Pay for the volume you need. Nothing else.

Free

₹0

No card required

  • ·100 requests / month
  • ·Test keys only
  • ·Community support
Start free

StarterMost popular

₹999 / mo

or $15 / mo

  • ·5,000 requests / month
  • ·Live + test keys
  • ·Email support
  • ·Idempotency + 99.5% SLO target
Choose Starter

Pro

₹4,999 / mo

or $69 / mo

  • ·50,000 requests / month
  • ·Live + test keys
  • ·Priority email support
  • ·99.9% SLO target
Choose Pro

Custom

Custom

  • ·Volume pricing
  • ·SLA + dedicated support
  • ·Custom contract terms
Talk to us

All prices are exclusive of GST. Annual billing not yet available — see our refund policy.

Questions

Things people ask before they integrate.

How accurate are the planetary positions?+
Sub-arcminute. We use Swiss Ephemeris with the Lahiri ayanamsa as default, and our published charts match AstroSage and DrikPanchang within ±0.05° on every reference fixture. Determinism is guaranteed: same input + engine version = byte-identical output.
What ayanamsa and house system do you use?+
Lahiri ayanamsa and whole-sign houses by default — the most-cited Vedic convention in India. KP-Newcomb + Placidus support is on the roadmap (Phase 11). The output meta block always names the convention used so consumers can disambiguate.
Where is birth data stored?+
It isn't. By default we don't persist birth inputs beyond the request lifecycle — only request hashes for debugging. Reports the user explicitly saves are stored for 30 days, then purged. DPDP-aligned and GDPR-aligned.
Can I run this on-prem / self-host?+
Not yet. The engine is a workspace package today; we may publish it as a standalone binary in the future. Talk to us on the Custom plan if your compliance posture requires on-prem.
Do you support refunds?+
Yes — see the refund policy. Short version: pro-rata refund within 14 days of paid subscription if you haven't exceeded the free-tier quota.
Why "BPHS canonical" — and what does that mean for compatibility?+
Brihat Parashara Hora Shastra is the source text most modern Vedic software pins to. Our compatibility scoring follows BPHS verses 5–7 for the Ashtakoot tables and applies the canonical half-marks cancellation rule. Every koot exposes both the raw initial_score and the post-cancellation score so callers can render either.