The astrology engine, as an API
Raw astrological computation for your product or AI agent. 390+ calculators across Vedic, Western and Hellenistic traditions — over REST and native MCP, with results localized into four languages.
What you can compute
One generic endpoint exposes every calculator in the registry by name — natal, time-based and symbolic techniques. No hand-maintained endpoint list.
🕉️Vedic (sidereal)
Yogas, doshas, dashas, divisional charts, nakshatras, KP, Jaimini — from classical catalogs with citations.
♀Western & Hellenistic
Aspects, dignities, midpoints, fixed stars, Arabic parts, timelords, predictive timelines.
🃏Symbolic systems
Tarot and I Ching engines driven by declarative catalogs.
🔢Numerology
Life-path, expression and soul numbers, personal-year forecasts.
🌍Mundane & remedies
Country profiles, Lal Kitab remedies, heliacal phenomena.
🪐Ephemeris core
Swiss Ephemeris positions, houses, ingresses, eclipses and stations.
Two ways to integrate
REST HTTP for any stack
Send parameters, get structured JSON back. Universal and understood by any developer.
X-API-Key: acx_…
{ "birth_date": "1990-06-15", "birth_time": "14:30",
"latitude": 55.75, "longitude": 37.62,
"timezone_offset": "+03:00" }
MCP Native for AI agents
Model Context Protocol lets AI assistants like Claude and ChatGPT discover and call our tools directly inside a conversation — no glue code.
{ "method": "tools/list" }
{ "method": "tools/call", … }
Connect AstroCodex to your own AI
- 1Subscribe to a plan that includes MCP and issue an API key in your profile.
- 2Add the AstroCodex MCP connector to your AI client (Claude, ChatGPT or any MCP-aware agent) with your key.
- 3Ask in plain language — "build my chart and analyze Venus". The agent calls our tools and interprets the result.
Pricing
Pay for compute, not subscriptions. Volume and rate-limit scale with the plan; MCP unlocks from Business.
Business
- 150,000 calls / month
- 300 requests / min
- REST + MCP
- Pay-as-you-go overage
Indicative pricing — final tiers are confirmed at launch. Computation never leaves our servers; agents receive only the result.
Localized results
Catalog engines return every name in all four languages at once — name_en, name_ru, name_es, name_hi — and accept a "lang" parameter in the request body ("en", "ru", "es" or "hi"; default "en") for a localized primary name. The platform UI ships in 30+ languages.
Build on the engine
Issue a key from your profile and start calling calculators in minutes.