Professional Astrology APIs and Platforms — Competitor Analysis

Major Astrology API Providers

Takeaway

Hosted SaaS APIs compete on pricing, tradition coverage, agent readiness and licence exposure, while most of them sit on the self-hosted Swiss Ephemeris library.

Cited Findings

AstrologyAPI.com: 300+ endpoints on one credit wallet — Vedic, Western, KP, Human Design, Tarot, Numerology, Vastu; MCP server (109 tools); chart-grounded AI chat; white-label PDFs; used by Snap, Bumble, Shaadi.com and AstroTalk — Source
Prokerala: ₹0 free/5K credits → ₹4,999 Sapphire/1M credits per month at 300 req/min; 20+ chart types; Vedic + Western; white-label; WordPress plugin; batch compatibility up to 500 — Source
Astrology-API.io (AstroAPI): 100+ calculations, 23 house systems, ~300ms responses, Swiss Ephemeris (NASA JPL), Western-first with Vedic, 9+ languages, AI horoscopes, MCP server, flat plans from $11/mo — Source
Vedika.io: 1,128 documented endpoints in 16 categories; Vedic, Western, KP plus Jaimini/Tajaka/Lal Kitab; 30 languages; wallet pricing $12–$240/mo; per-query tiers (Eco $0.01, Standard $0.01–0.03, Swift $0.02–0.05, Pro Ultra by contract); MCP (36 tools); Apache-2.0 XALEN engine; voice AI; white-label PDFs — Source
FreeAstrologyAPI.com: 500 req/day free forever; paid from ₹1,000/mo (50K req) to ₹6,500/mo (500K req); Vedic + Western core, divisional charts, panchang, match making, shadbala, vimshottari dasha — Source
AstroAPI.cloud: €39.99–299.99/mo or build-your-own from €4.50/module; NASA JPL ephemeris; 12 languages; Western focus (natal, transits, synastry, composite, progressions, returns, Chinese); PDF reports, AI chatbot, SVG charts — Source
RoxyAPI: flat ₹2,492–20,750/mo for 50K–3M req/mo; 18+ domains on one key (Western, Vedic, Forecast, Human Design, Chinese, Feng Shui, Mesoamerican, Vastu, Numerology, Kabbalah, Tarot, Biorhythm, Ayurveda, I-Ching, Crystals, Dreams, Angel Numbers, Location); MIT Roxy Ephemeris; Remote MCP (18 servers); typed SDKs (TS/Python/PHP/C#/Go/Rust); EU-hosted with Article 28 DPA — Source
VedicAstroAPI: ₹1,499–10,999/mo; Vedic/Western/Tarot; 21 languages; AI chat beta (₹1/credit + BYOLLM); PDF reports ₹2–45 each; WordPress plugin; self-hosted MCP — Source
OpenEphemeris: NASA JPL DE440 kernel; 120 endpoints; 4 systems (Western, Vedic, BaZi, Human Design); format=llm; MCP server (92 tools); claude.ai connector; 150 free credits; sub-arcsecond precision; commercial terms — Source
Swiss Ephemeris: AGPL-3.0 or CHF 700 one-time commercial; DE441-based; 13,201 BCE–17,191 CE; 0.001″ precision; used by AstrologyAPI.com, Prokerala, AstroAPI.cloud, Kerykeion, flatlib, immanuel and VedAstro — Source; Source

Inferences

Credit wallets (Prokerala, AstrologyAPI.com, VedicAstroAPI) hide true per-operation cost. Flat subscriptions (RoxyAPI, AstroAPI.cloud bundles, Vedika wallet tiers) budget more predictably.
Only Vedika (XALEN, Apache-2.0), RoxyAPI (Roxy Ephemeris, MIT) and OpenEphemeris (commercial API terms) avoid AGPL exposure. The rest inherit Swiss Ephemeris AGPL unless they hold commercial licences.
Agent readiness separates the leaders: Vedika (MCP, voice, streaming, format=llm equivalent), OpenEphemeris (format=llm, MCP, claude.ai connector), AstrologyAPI.com (MCP, grounded AI chat) and RoxyAPI (Remote MCP).
Vedika (3+ traditions plus subsystems), RoxyAPI (18 domains), OpenEphemeris (4 systems) and AstrologyAPI.com cover the widest range. Prokerala and FreeAstrologyAPI are Vedic-first; AstroAPI.cloud is Western-first.

Gaps

Exact credit burn rates per endpoint type for AstrologyAPI.com and Prokerala.
Current rate limits on specific tiers. Vedika publishes targets by contract; RoxyAPI publishes 600–3,000 req/min; OpenEphemeris 30–1,000 req/min.
Whether AstroAPI.cloud and VedicAstroAPI hold Swiss Ephemeris commercial licences or run under AGPL.
Enterprise terms (SLAs, support, custom calculations, bulk processing) — almost all “contact sales”.

API Capabilities: Calculations, Chart Types, Planets, Aspects, Houses, Transits, Progressions, Synastry, Composite

Takeaway

Every provider covers natal charts, but Western-first APIs lead on predictive technique, Vedic-first APIs lead on dasha and varga depth, and only a few combine both.

Cited Findings

AstrologyAPI.com: Birth Chart (planets, houses, aspects, elements); Kundali (D1–D60, Vimshottari dasha, Shadbala, Ashtakavarga, Bhavbala, Gochara); Compatibility (Ashtakoot/Dashkoot, Western synastry/composite); Transits (personal, global, progressions, HD gates); Progressions/Arc; AstroCartoGraphy (planetary lines, parans, city scoring); Human Design (BodyGraph, compatibility); KP/Lal Kitab (sub-lords, cusps, multiple ayanamsas); Muhurta/Panchang (18 life events) — Source
Prokerala: Vedic horoscope (charts, dasha, yogas), Daily Panchang, KP astrology (chart, positions, significators), Calendar (Amanta, Purnimanta, Vikram Samvat), Marriage Matching (Ashta Kuta, Dasha Kuta), Western natal/aspects/synastry/positions, Numerology (Pythagorean, Chaldean), PDF reports — Source
Astrology-API.io: 100+ calculation types; natal, synastry, composite, transit, solar/lunar returns, progressions, directions; aspects across 12 houses; 23 house systems; 97+ Arabic Parts; essential dignities; annual profections; reception analysis; sect distinctions; astrocartography (relocation, paran lines, power zones, SVG); fixed stars; asteroid goddesses; Black Moon Lilith; aspect pattern detection — Source
Vedika: charts with planets, houses, ascendant and D1–D60; 50 ayanamsas; 23 house systems; 104–131 computed yogas/doshas; Vimshottari plus conditional dashas; 36-guna matching, Lal Kitab and KP compatibility; panchang; muhurta; transit timeline merging Western transits with Vimshottari boundaries and biorhythm critical days; BaZi, I-Ching, numerology, kabbalah, tarot, vastu — Source; Source
FreeAstrologyAPI: Vedic core (D9/D10/D60, panchang, match making, shadbala, vimshottari dasha), Western core, geo location, time zone — Source
AstroAPI.cloud: natal charts (4 house systems on Basic, all on Premium), positions Sun–Pluto, aspects, compatibility, numerology, moon phases; Premium adds transits, solar/lunar returns, synastry, composite, secondary progressions, retrogrades, Chinese horoscope; Deluxe adds full interpretation, daily/weekly/yearly horoscopes, Chinese forecast, 12 languages — Source
RoxyAPI: Western advanced layer (fixed stars, asteroids, Arabic lots, aspect patterns, secondary progressions, solar arc, annual profections, astrocartography, relocation/local space, solar/lunar/planetary returns); Vedic with reasoning (48 machine-readable yoga verdicts with evidence and precedence, shadbala, bhava bala, ashtakavarga, Arudha padas, Chara Karakas, 3 avastha systems, KP sub-lords); Human Design Variables (Color/Tone/Base), Penta groups, connection charts, transit overlays; Forecast merges Western transits with Vimshottari and biorhythm — Source
VedicAstroAPI: 100+ Vedic/Tarot APIs; Vedic Complete (kundali, matching, panchang); Western & Tarot (daily, love, career, yes/no); PDF reports (Vedic small/medium/large/matching/prediction/12-month/life analysis; Western coming soon) — Source
OpenEphemeris: Western (7 house systems), Vedic (Lahiri and other ayanamsas, nakshatra placements), BaZi (four-pillars), Human Design (bodygraph, type, authority, channels); natal chart, transit search, angles/points endpoint — Source

Inferences

“100+ calculations” and “300+ endpoints” usually count chart types, languages and variants separately. Unique astronomical computations are fewer.
Vedic depth (dashas, vargas, yogas, doshas, panchang, muhurta) is the moat for Indian-origin providers: Prokerala, AstrologyAPI.com, VedicAstroAPI, FreeAstrologyAPI and Vedika.
Western advanced technique (progressions, returns, astrocartography, Arabic parts, dignities, profections) is the moat for Astrology-API.io, AstroAPI.cloud, RoxyAPI and OpenEphemeris.
Synastry and composite are table stakes on paid tiers. Interpretation text is often gated to higher tiers.
Only RoxyAPI and Vedika document cross-tradition composition — for example Forecast merging Western transits, Vimshottari and biorhythm, or Human Design computed from the Western ephemeris plus I-Ching.

Gaps

No standard endpoint-by-endpoint comparison matrix; vendors publish different formats.
Exact house system lists. Astrology-API.io claims 23; AstroAPI.cloud Basic has 4; Vedika claims 23; RoxyAPI implies the full set; OpenEphemeris claims 7 Western plus Vedic.
Ayanamsa options per provider. Vedika publishes 50; AstrologyAPI.com lists multiple including Lahiri; Prokerala likely defaults to Lahiri; others are unspecified.
Asteroid and fixed-star coverage beyond “major asteroids” marketing.

Technical Specifications: Response Formats, Rate Limits, Authentication, SDKs

Takeaway

All providers use REST/JSON over HTTPS with API keys, but rate-limit transparency, SDK maturity and MCP support vary widely.

Cited Findings

AstrologyAPI.com: Authorization: Basic base64(userId:apiKey); JSON; React/Flutter SDKs; WordPress plugins; Postman collection; MCP at mcp.astrologyapi.com/mcp (109 tools, Streamable HTTP); rate limits unpublished — Source
Prokerala: API key header; JSON; sample clients in PHP, C#, Python and Ruby on GitHub; WordPress plugin; limits of 5 req/min free, 60 Ruby, 120 Emerald, 300 Sapphire — Source; Source
Astrology-API.io: API key; JSON; ~300ms average; 99.9% uptime; MCP server; SDKs not prominently listed — Source
Vedika: API key; JSON; keyless sandbox; MCP (36 tools, Streamable HTTP); SDKs @vedika-io/sdk (JS/TS), @vedika-io/react, vedika-sdk (Python), Flutter on GitHub, Java via HttpClient + OpenAPI; spec at api.vedika.io/openapi.json; signed webhooks; WordPress plugin; Postman collection; CLI (@vedika-io/cli); limits by contract — Source
FreeAstrologyAPI: API key; JSON; Postman collection; SDKs not listed — Source
AstroAPI.cloud: API key; JSON plus SVG charts; 12 languages; 7-day Deluxe trial; SDKs not listed — Source
RoxyAPI: API key; JSON; typed SDKs (TypeScript, Python, PHP, C#, Go, Rust) generated from OpenAPI; Remote MCP (18 domain servers plus Docs MCP) over Streamable HTTP; drop-in UI components (React, Next.js, Vue, Svelte, Angular, HTML); embeddable widgets with publishable keys; 13 MIT templates; WordPress plugin; limits of 600 Starter, 1,200 Professional, 3,000 Business req/min; EU-hosted (Germany) with Article 28 DPA on every plan — Source
VedicAstroAPI: API key; JSON; Postman docs; self-hosted MCP (GitHub); third-party WordPress plugin; SDKs not listed — Source
OpenEphemeris: X-API-Key header; JSON; ?format=llm for token-optimised output (~500–800 tokens against 4K–8K); MCP (92 tools); claude.ai custom connector; limits of 30 Explorer, 180 Pro, 1,000 Scale req/min — Source
Swiss Ephemeris: C library (DLL/so) with a sweph.h API; wrappers for Python (pyswisseph, swisseph), Node (swisseph, @swisseph/browser), Rust and Java; no network API — Source

Inferences

MCP is the emerging agent standard: 4 of 10 providers (Vedika, AstrologyAPI.com, OpenEphemeris, RoxyAPI) maintain servers.
SDK maturity tracks company size. RoxyAPI and Vedika invest in typed, generated SDKs; others ship samples or leave it to the community.
Rate-limit transparency: RoxyAPI and OpenEphemeris publish clear tiers; Vedika defers to contract; AstrologyAPI.com and Prokerala publish credit or request limits for named tiers; AstroAPI.cloud and FreeAstrologyAPI publish none.
OpenAPI specs exist for Vedika, RoxyAPI and OpenEphemeris. The rest use Postman collections or custom docs.

Gaps

Webhook and event streaming: only Vedika documents signed webhooks.
Batch/bulk APIs: Prokerala mentions 500-batch compatibility; the rest are unclear.
GraphQL or gRPC: none found, all REST.
SLA detail beyond “99.9% uptime”. RoxyAPI cites a 99.95% SLA with service credits on Enterprise; Vedika has an SLA page.

Supported Calculations: Tropical/Sidereal Zodiacs, Ayanamsa Options, House Systems

Takeaway

Every provider supports tropical and sidereal zodiacs, but ayanamsa and house-system breadth ranges from four options to fifty.

Cited Findings

Vedika: 50 ayanamsas, 23 house systems, 60 divisional charts (D1–D60) — Source
Astrology-API.io: 23 house systems; “Universal, Classical, Psychological, Event-Oriented interpretations” across traditions — Source
AstrologyAPI.com: “Multiple ayanamshas” for KP/Lal Kitab; Vedic charts with divisional charts — Source
Prokerala: KP astrology with “multiple ayanamshas” implied; Vedic charts — Source
AstroAPI.cloud: Basic includes Placidus, Koch, Meridian and Whole Sign (4 systems); higher tiers likely expand — Source
RoxyAPI: Vedic engine returns “48 machine-readable yoga verdicts… shadbala, bhava bala, ashtakavarga, Arudha padas, Chara Karakas, three avastha systems, KP sub-lords”, implying full house and ayanamsa support — Source
OpenEphemeris: 7 Western house systems; Vedic with Lahiri and other ayanamsas, nakshatra placements — Source
FreeAstrologyAPI: D9, D10 and D60 mentioned; ayanamsa unspecified — Source
VedicAstroAPI: “Available in 20+ languages”; house systems and ayanamsa not detailed — Source
Swiss Ephemeris: all major house systems (Placidus, Koch, Regiomontanus, Campanus, Equal, Whole Sign, Meridian, Porphyry, Morinus, Polich-Page, Alcabitius and more) and ayanamsas (Lahiri, Raman, Krishnamurti and more) via swe_houses_ex, swe_set_sid_mode — Source

Inferences

Swiss Ephemeris wrappers technically reach every house system and ayanamsa but may not expose them all.
Vedika’s 50 ayanamsas and 60 vargas suggest XALEN goes beyond Swiss defaults.
RoxyAPI’s evidence-backed yoga verdicts imply a custom computation layer, not raw ephemeris output.
OpenEphemeris’s 7 Western house systems is narrower than the 23 claimed by Astrology-API.io and Vedika.

Gaps

Complete house lists for AstrologyAPI.com, Prokerala, FreeAstrologyAPI and VedicAstroAPI.
Exact ayanamsa lists; only Vedika publishes a count (50).
Whether providers accept custom ayanamsa offsets or user-defined houses.
Southern-hemisphere house handling, which few document.

Enterprise Features: White-Label, Custom Calculations, Bulk Processing

Takeaway

White-label reports and embeddable widgets are the real enterprise products; bulk processing and custom calculation remain sales conversations.

Cited Findings

AstrologyAPI.com: “White label astrology solutions to power your mobile apps, websites all under your brand”; AstroPages product; PDF API for branded reports; used by Snap, Bumble, Shaadi.com and AstroTalk — Source; Source
Prokerala: white-label solutions; batch compatibility up to 500; Enterprise “custom built to suit your needs” — Source
Vedika: “White-label reports on eligible plans”; branded widgets (birth chart, panchang, horoscope, numerology in dark/light/custom colours and North/South/KP/Western styles); Enterprise ($240/mo) adds “custom endpoints and limits: current contract” — Source
AstroAPI.cloud: “White-label PDF reports with complete interpretations”; embeddable widgets (moon calendar, natal chart) in one line of HTML; custom plan builder — Source
RoxyAPI: 13 MIT templates to “clone, brand, and ship as your own product”; embeddable widgets with browser-safe publishable keys; drop-in UI components; Enterprise adds custom integration support, priority feature requests, on-demand training, completed security questionnaires, contract redlines and a named data-protection contact with response SLA — Source
VedicAstroAPI: PDF reports as an add-on (₹2–45 by size); free third-party WordPress plugin, maintained yearly; “Contact Us” for custom work — Source
FreeAstrologyAPI: “Enterprise Scale” at ₹6,500/mo for 500K req/mo; custom plans for higher limits, dedicated support and integrations — Source
Astrology-API.io: enterprise not detailed; “Contact us” — Source
OpenEphemeris: Scale tier at 1,000 req/min; “Enterprise” not detailed — Source
Swiss Ephemeris: CHF 700 professional licence for unlimited closed-source distribution; source included; 4 hours support; valid 99 years — Source

Inferences

White-label PDFs are the most common enterprise deliverable: AstrologyAPI.com, Prokerala, Vedika, AstroAPI.cloud and VedicAstroAPI.
Publishable-key widgets (Vedika, AstroAPI.cloud, RoxyAPI) let front ends keep the brand without proxying calls.
RoxyAPI’s templates, widgets and UI components form the most complete “ship your own branded app” kit without backend work.
Custom calculation and bulk processing stay manual. No provider publishes async job queues, webhook callbacks for long reports or bulk chart generation.
EU residency with an Article 28 DPA is unique to RoxyAPI (Germany, all plans). Vedika has security and SLA pages but no residency claim; the rest are silent.

Gaps

Enterprise contract terms (SLAs, uptime, support response times, DPAs) for all providers.
Bulk API specs: async submission, status polling, result delivery, bulk rate limits.
Custom calculation process: lead time, cost model, IP ownership.
On-premise or air-gapped deployment. Only Swiss Ephemeris self-hosting and RoxyAPI’s self-hosted MCP server qualify; Vedika mentions on-prem without detail.
Data export and portability guarantees.

Swiss Ephemeris vs. Custom Calculation Engines

Takeaway

Seven of ten providers wrap Swiss Ephemeris and inherit its AGPL exposure; Vedika, RoxyAPI and OpenEphemeris built independent engines with permissive or commercial terms.

Cited Findings

Swiss Ephemeris: AGPL-3.0 or CHF 700 one-time commercial; DE441-based since May 2026; 0.001″ precision; 13,201 BCE–17,191 CE; 97 MB compressed files; 895,000+ asteroids; 0.3ms per full planetary set; used by Astrodienst, Solar Fire, Astro-Seek, Kerykeion, flatlib, immanuel, VedAstro and most commercial APIs — Source; Source
Vedika XALEN: Apache-2.0; analytic theories (VSOP87A planets, truncated ELP2000-82 Moon, Meeus algorithms, IAU 2006 precession, 2000B nutation); optional JPL DE440 SPK reader; sub-arcsecond planets (Sun 0.08″, Mercury 0.08″, Venus 0.09″, Mars 0.08″, Jupiter 0.16″, Saturn 0.17″, Uranus 0.40″, Neptune 0.62″, Pluto 0.35″); Moon ~2.2″ mean and 2.8″ RMS; 336µs per full chart; compiles to wasm32; 15 crates on crates.io, npm, PyPI — Source
RoxyAPI Roxy Ephemeris: MIT licence; reads NASA JPL DE440 directly; verified against Horizons DE441 (13,746 tests per deploy, 3,647 gold-standard pinned to Horizons); not a Swiss wrapper — Source; Source
OpenEphemeris: computes directly from the JPL DE440 kernel; sub-arcsecond; 1550–2650 CE; closed source; commercial terms — Source
AstrologyAPI.com: Astrology-API.io comparisons call it “NASA-grade astronomical calculations with Swiss Ephemeris”; its homepage does not name an engine — Source
Prokerala: comparison articles note “Swiss based, licence unverifiable” — Source
AstroAPI.cloud: advertises “NASA JPL ephemeris data”; unclear whether direct or via Swiss Ephemeris. A comparison blog says “You’ll license Swiss Ephemeris (CHF 750)…” — Source
Kerykeion: Python library wrapping Swiss Ephemeris, so AGPL is inherited — Source; Source

Inferences

CHF 700 is modest for funded companies but creates upstream dependency; the AGPL path risks source disclosure for SaaS.
Custom engines compete on licensing freedom, not accuracy. All match Swiss/JPL to sub-arcsecond for classical planets; the Moon is the main variance (analytic ~2–3″ against kernel ~0.001″).
XALEN is unique in pairing a permissive engine with a full interpretation platform (yogas, dashas, matching, voice, AI). RoxyAPI and OpenEphemeris focus on the astronomy layer.
“NASA JPL ephemeris” claims do not distinguish direct kernel computation from Swiss wrapping. Buyers must ask.

Gaps

Independent accuracy audits for XALEN and Roxy Ephemeris; both self-validate, and OpenEphemeris publishes methodology.
Long-term maintenance commitments. Swiss Ephemeris has 25+ years behind it; the newer engines do not.
Swiss Ephemeris licence status for AstrologyAPI.com, Prokerala, AstroAPI.cloud, FreeAstrologyAPI and VedicAstroAPI.
Asteroid coverage in custom engines. Swiss Ephemeris has 895K+; the others focus on major bodies.