DivineAPI sells astrology, tarot, and numerology APIs as separate product suites with their own price tiers. If you only need one suite, the entry pricing is reasonable. If you need multiple, the math gets more complex than a flat plan. This is how the two providers compare as of May 2026.
TL;DR comparison
| Dimension | Astrology API | DivineAPI |
|---|---|---|
| Free tier | 50 requests/month (permanent, no card) | 14-day free trial (card required) |
| Paid entry | $11/mo (1,000 requests, all endpoints) | $19/mo (Vedic Sampoorna, 100K requests) |
| Pricing model | Flat per-request, all endpoints included | Per-suite pricing (separate Western, Vedic, Tarot plans) |
| Endpoints | 100+ unique calculation types | 300+ counted across all suites |
| House systems | 23 | ~12 in Western endpoints |
| Languages | 9+ output languages | 25+ supported |
| Response time | ~300ms median | ~72ms claimed (verify in your region) |
| Ephemeris | Swiss Ephemeris (DE431-derived) | Swiss Ephemeris-based |
| Uptime SLA | 99.9%+ on paid tiers | 99.9% advertised |
| White-label PDF reports | Available on Business+ | 125+ pre-built types |
| OpenAPI spec | Yes | No public OpenAPI file |
| Best for | Multi-tradition apps, all-endpoint single bill | Single-suite focus, PDF reports, wide language coverage |
What each provider is
The model difference is the key story: DivineAPI's suite pricing is great if you only need one suite, awkward if you need three.
Pricing in detail
- Starter: $49/mo, 300,000 requests
- Pro: $79/mo, 1,000,000 requests
- Nova: $39/mo, 1,000,000 requests
- Atlas: $79/mo, 2,500,000 requests
- Lumen: $149/mo, 5,000,000 requests
- Sampoorna: $19/mo, 100,000 requests
- Ananta: $79/mo, 600,000 requests
- Prakash: $149/mo, 2,000,000 requests
- Basic: $19/mo, 300,000 requests
- Essentials: $39/mo, 1,000,000 requests
- Gold: $79/mo, 2,500,000 requests
Annual billing saves up to 25%. Half-yearly saves up to 15%. The 14-day free trial requires a credit card and converts to paid at the end of the trial.
Astrology API's tiers:
- Free: $0/mo, 50 requests (permanent, no card)
- Starter: $11/mo, 1,000 requests
- Professional: $37/mo, 55,000 requests
- Business: $99/mo, 220,000 requests (all endpoints â Western, Vedic, Chinese, Tarot, Numerology)
- Enterprise: $399+/mo, unlimited with dedicated capacity
Cost at two scale points
The honest summary: DivineAPI is cost-competitive for single-suite high-volume traffic. Astrology API is cost-competitive for multi-suite traffic at any volume, and for low-volume traffic generally.
Endpoint coverage
- Horoscope: daily, weekly, monthly, yearly predictions for 12 Western signs, Chinese horoscope, Numeroscope, love/career/health/travel insights
- Western Astrology: planetary positions, house cusps, natal wheel charts as SVG, synastry, composite, transits, progressions
- Vedic Astrology: planetary positions, divisional charts, dasha/dosha/yoga analysis, matchmaking, panchang in 8 languages
- Numerology: name and date-based calculations, personal year, life path
- Tarot: card draws, spreads, interpretations
- PDF reports: 125+ pre-built white-label report types
Astrology API's endpoint set:
- Natal: 23 house systems, 97+ Arabic parts, fixed stars, asteroids, midpoints, antiscia, dignities
- Predictive: secondary progressions, solar arc, primary directions, profections, zodiacal releasing, ingresses, returns (solar/lunar/Venus)
- Synastry, composite, Davison, harmonics, draconic
- Astrocartography: ACG lines, parans, local space, relocation, paran detail
- Vedic: kundli, divisional charts (D1, D9, D12, others), vimshottari dasha, nakshatra, navamsa, panchang
- KP astrology: chart with significators
- Chinese: BaZi (Four Pillars), Zi Wei Dou Shu, flying stars, Chinese zodiac, Feng Shui
- Tarot: multiple spreads (three-card, Celtic Cross, transit, synastry)
- Numerology: Pythagorean, Chaldean, Lo Shu
- Human Design, palm reading
Where each wins:
- DivineAPI's strength is pre-built PDF reports (125+ types). If you sell direct-to-consumer personalized PDFs, this is a fast path.
- DivineAPI has wider language coverage for horoscope text (25+ versus 9+).
- Astrology API has deeper Western advanced techniques (Arabic parts at 97+, primary directions, zodiacal releasing) and more uniform endpoint shape.
- Astrology API ships Chinese BaZi and Zi Wei Dou Shu, which DivineAPI does not expose.
Performance and accuracy
Response times:
- Astrology API: ~300ms median for natal endpoints from US/EU
- DivineAPI: 72ms average claimed in marketing material; real-world numbers depend on region and endpoint complexity. Run your own benchmarks before committing.
The 72ms claim is unusually fast for an astrology API and likely reflects a specific endpoint (probably a cached horoscope lookup) rather than full natal chart computation. Always test with your own representative payloads.
Developer experience
DivineAPI provides:
- REST API with API key authentication
- Per-endpoint documentation with curl and language examples
- WordPress, Shopify, and Wix native plugins
- Embeddable widgets for non-developer integration
- 14-day free trial (card required) for hands-on testing
Astrology API provides:
- REST API with bearer token authentication
- OpenAPI 3.0 specification for client generation
- Consistent JSON envelope across all endpoints
- Inline "try it" panels in docs
- Always-free 50-request-per-month tier (no card)
If you are building on WordPress or Shopify and want a turnkey plugin, DivineAPI's integration story is faster. If you are building a custom mobile app or SaaS backend with strict typing, Astrology API's OpenAPI spec saves time on client generation and validation.
When to choose Astrology API
Pick Astrology API if any of these apply:
- You need more than one tradition (Western + Vedic + Chinese + Tarot) and want one bill
- You need advanced Western techniques (97+ Arabic parts, primary directions, zodiacal releasing)
- You want flat per-request pricing without per-suite quota tracking
- You want a permanent free tier (no card, no trial expiration)
- You need 23 house systems for professional astrologer users
- You want an OpenAPI spec for IDE autocomplete and client generation
- You need Chinese BaZi or Zi Wei Dou Shu endpoints
When to choose DivineAPI
Pick DivineAPI if any of these apply:
- You only need one tradition (Western only, or Vedic only) at high volume
- You want pre-built white-label PDF reports as a delivered output (125+ types)
- You need horoscope text in 25+ languages out of the box
- You are integrating into WordPress, Shopify, or Wix and want a plugin
- Your team prefers per-suite billing because it maps to your product structure
- You need Indian regional language coverage with native panchang in 8 languages
DivineAPI's per-suite pricing genuinely rewards focused products. A Western-only horoscope app at 1M requests/month gets a great rate.
Migration notes
Both APIs use Swiss Ephemeris, so calculation output aligns once settings match. High-level mapping for migration to Astrology API:
| DivineAPI | Astrology API equivalent |
|---|---|
/western/natal-chart | /v1/natal/chart |
/western/synastry | /v1/synastry/chart |
/western/composite | /v1/composite/chart |
/western/transits | /v1/transits/current |
/western/progressions | /v1/progressions/secondary |
/vedic/kundli | /v1/vedic/birth-chart |
/vedic/divisional-charts | /v1/vedic/divisional-charts |
/vedic/dasha | /v1/vedic/vimshottari-dasha |
/vedic/panchang | /v1/vedic/panchang |
/horoscope/daily | /v1/horoscope/daily |
/numerology/calculate | /v1/numerology/core |
/tarot/three-card | /v1/tarot/three-card |
Auth: DivineAPI uses an API key in the header. Astrology API uses a bearer token. One-line change.
Date format: both accept ISO 8601. Confirm timezone handling.
PDF reports: if you used DivineAPI's pre-built PDF outputs, those are delivered as a finished PDF. Astrology API returns structured JSON, which you then render to PDF with your own template engine. This gives you full design control but requires the template work.
FAQ
Is DivineAPI cheaper than Astrology API?
Does DivineAPI offer Chinese astrology?
What about DivineAPI's PDF reports?
DivineAPI has 125+ pre-built PDF report types delivered as finished PDF files. This is genuinely useful if you sell direct-to-consumer reports. Astrology API returns structured JSON; you render PDFs yourself with full template control. Different trade-offs.
Which API has better Vedic coverage?
DivineAPI and Astrology API have comparable Vedic endpoint coverage for the standard set (kundli, dashas, divisional charts, panchang, matchmaking). DivineAPI has slightly more pre-built report variants. Astrology API has stricter response schemas and a published OpenAPI spec.
Is DivineAPI's 72ms response time real?
The 72ms figure is from DivineAPI's marketing. It likely reflects a cached or simple lookup endpoint. Full natal chart computation is typically slower. Always benchmark with your real payload before committing.
