Astrology AI

Settings
Configured AI Providers

Configure local endpoints (LM Studio, Ollama) or cloud providers (OpenRouter, OpenAI, Groq, DeepSeek, Google Gemini).

Astrology Provider Routing & Assignment
Admin Exclusive

Configure separate astrology calculation providers for Admin and for All Other Users. Admin and users can simultaneously query separate calculation engines.

Assigned to Admin for Chat, Horoscope Kundli, Hora, Muhurta, and Compatibility calculations.
Assigned automatically to all non-admin users (the Astrology Sources tab is hidden for them).
Configured Astrology Calculation Sources

Configure calculation engines (PyJHora Local, Jagannatha Hora MCP, VedAstro, FreeAstroAPI). All enabled sources can be assigned above.

generate_horoscope get_nakshatra_pada get_divisional_chart (D1-D60) get_dasha (Vimshottari) get_gochara (Transits) get_saturn_transit (Sade Sati) get_marriage_match (Kuta) get_muhurta get_yogas get_doshas get_ashtakavarga
System Instructions & Astrological Directives

Directives provided to the AI on every conversation turn. Guides planetary calculation tool calls and authentic classical interpretation.

Overall Status Test
Laya Fast Decision Engine (System 1)
Checking...

Non-autoregressive System 1 decision engine. Delivers sub-40ms calibrated intent classification, MCP tool pruning, emotion/persona calibration, and zero-cost memory extraction gating.

When enabled, user queries are evaluated in <40ms to prune 50+ calculation tools down to the exact 2–4 needed, adapt counselor tone, and gate memory note extraction.
Default: http://127.0.0.1:8100 (Managed by Engine/run_laya_service.py & start.bat)
Live Interactive Decision Sandbox

Test any user query or astrological prompt to see real-time Laya System 1 predictions (Domain, Emotion Tone, Profile Requirement, Life Fact Gating, UI Intent).

Modular 1-Click Update Architecture

• Sub-Repository: Laya is cloned in Engine/laya/ from NandhaKishorM/laya.
• 1-Click Updates: Double-click update-engine.bat to pull the latest upstream updates for PyJHora, pyjhora-mcp, and Laya in one step without breaking anything.
• Resilient Fallback: If the Laya service is restarting or disabled, the application continues to answer queries using the standard full tool workflow.