Your context
Date, time, place, person, tradition, event type and the exact calculation requested.
AstroCorp infrastructure · Grahvani API
The Vedic intelligence layer for your product.
Enterprise access in preparation
AstroCorp Astro Engine · charts · timing · calendar · compatibility · knowledge
Evaluation paths for developers, practitioners and companies
One governed computational spine
Build on the engine behind Grahvani itself.
The calculation layer beneath Grahvani’s professional platform and interactive academy can become infrastructure inside your own product. Start with one focused service or compose a complete Vedic experience.
Built within AstroCorp’s owned Astro Engine ecosystem, this is not a white-label horoscope paragraph generator. It is a structured service architecture for products that need real chart, calendar, timing, compatibility and allied calculation depth.
01Enterprise architecture
One API layer.
An entire Vedic world.
Your application calls a governed Grahvani service surface; Grahvani handles the specialised calculation and returns structured results for your product experience.
GRAHVANI API / REQUEST OBSERVATORY
ARCHITECTURE DEMONSTRATION · NOT LIVE TELEMETRY
TENANTdemo_enterprise_01
REGIONIllustrative · India
AUTH SCOPEcharts:compute
REQUEST IDreq_demo_7A91
01GatewayIdentity + request ID02ValidateContext + contract03RouteDomain + version04ComputeNamed engine05ProvenanceMethod + trace06GovernSchema + boundary
Ready · request not sent
VALIDATED REQUESTCompute a natal chart
POST
/v2/charts/natalv2{
"birth": {
"date": "1991-09-14",
"time": "06:42:18",
"timezone": "Asia/Kolkata"
},
"location": {
"latitude": 12.9716,
"longitude": 77.5946
},
"ayanamsa": "lahiri",
"vargas": [
"D1",
"D9",
"D10"
]
}01GATEWAYidentity · rate boundary
02DOMAIN ROUTERcharts / v2
03chart-coreversion locked
04TRACE LEDGERmethod + source context
05POLICY GATEschema + boundary
GOVERNED RESULTNot sent
{
"calculation_id": "demo_gv_2407118",
"ascendant": {
"sign": "Gemini",
"longitude": 14.4521
},
"planets": "[structured planetary positions]",
"provenance": {
"engine": "chart-core",
"method_version": "2.4.1"
}
}trace_id: trace_demo_7A91
service: charts
route: /v2/charts/natal
engine: chart-core
method_version: 2.4.1
provenance: pending requestrequired · birth.date
required · birth.time
required · birth.timezone
required · location
required · ayanamsa
required · vargas[]○
Awaiting governed requestMethod, engine version and source context attach only after validation.
Grahvani service
Validation, engine orchestration, computation, caching and the method-specific service contract.
Structured result
Values and components your interface can explain, visualise, compare, store or report.
Your experience
A web, mobile, CRM, calendar, learning or enterprise workflow designed for your customers.
ILLUSTRATIVE CONTRACT LAB
Inspect the journey
from context to provenance.
Choose a service to inspect request anatomy, response structure and integration use. These examples are explanatory—not live public API documentation, credentials or an availability promise.
POST/v1/charts/natal
ILLUSTRATIVE · VERSION UNCOMMITTEDREQUESTExplicit inputs
{
"birth": {
"datetime": "1991-09-14T06:42:18+05:30",
"latitude": 12.9716,
"longitude": 77.5946
},
"context": {
"ayanamsa": "lahiri",
"vargas": ["D1", "D9", "D10"]
}
}RESPONSEStructured output
{
"calculation": {
"chart": { "ascendant": "gemini" },
"vargas": ["D1", "D9", "D10"]
},
"provenance": {
"engine": "grahvani-core",
"method": "parashari",
"ayanamsa": "lahiri"
}
}REQUEST ANATOMYWhy each field is thereSelect a field. Nothing here is a credential, and no request is sent.
birth.datetimeThe offset is part of the value. Without it the same digits describe several different skies, and the service will not guess which one was meant.
POST/v1/panchanga/day
ILLUSTRATIVE · VERSION UNCOMMITTEDREQUESTExplicit inputs
{
"date": "2026-07-29",
"location": {
"latitude": 12.9716,
"longitude": 77.5946,
"timezone": "Asia/Kolkata"
},
"locale": "en-IN"
}RESPONSEStructured output
{
"day": {
"tithi": { "name": "illustrative" },
"vara": { "name": "illustrative" },
"nakshatra": { "name": "illustrative" },
"yoga": { "name": "illustrative" },
"karana": { "name": "illustrative" }
},
"provenance": {
"local_sunrise": true,
"timezone": "Asia/Kolkata"
}
}REQUEST ANATOMYWhy each field is thereSelect a field. Nothing here is a credential, and no request is sent.
dateA Panchanga day is a local construct that runs sunrise to sunrise, so it is addressed by the date a person would say aloud rather than by a timestamp.
POST/v1/compatibility/evidence
ILLUSTRATIVE · VERSION UNCOMMITTEDREQUESTExplicit inputs
{
"subjects": [
{ "chart_ref": "chart_a" },
{ "chart_ref": "chart_b" }
],
"include": [
"kuta_components",
"chart_evidence",
"timing_context"
]
}RESPONSEStructured output
{
"comparison": {
"convergence": [],
"contradiction": [],
"timing_context": []
},
"boundary": {
"human_judgment_required": true
}
}REQUEST ANATOMYWhy each field is thereSelect a field. Nothing here is a credential, and no request is sent.
subjects[].chart_refCharts are established once and referred to afterwards. Two people's birth details are not resent on every comparison, which keeps the sensitive record in one governed place.
POST/v1/chaldean/profile
ILLUSTRATIVE · VERSION UNCOMMITTEDREQUESTExplicit inputs
{
"name": "Illustrative Name",
"birth_date": "1991-09-14",
"include": [
"compound_numbers",
"name_analysis"
]
}RESPONSEStructured output
{
"profile": {
"compound_numbers": [],
"name_analysis": {}
},
"provenance": {
"system": "chaldean"
}
}REQUEST ANATOMYWhy each field is thereSelect a field. Nothing here is a credential, and no request is sent.
nameSpelling, spacing and transliteration all change the result, so the value is taken literally rather than normalised behind the caller's back.
01Choose serviceName the professional job.
02Construct contextSupply explicit time, place and method.
03ValidateReject ambiguity before computation.
04ComputeRoute to the named service.
05Return provenanceKeep method and context inspectable.
06Shape experienceYour product owns presentation and counsel.
02Service coverage
From a natal chart to a product ecosystem.
The Grahvani engine is conceived across the breadth of Vedic practice, allowing companies to integrate one domain without giving up the possibility of a larger roadmap.
01JĀTAKA
Charts & vargas
Natal foundations and focused divisional contexts for practitioner and consumer products.
02KĀLA
Daśā & transits
Planetary periods, nested time and the relationship between natal promise and moving sky.
03BALA
Strength systems
Ṣaḍbala, aṣṭakavarga and the quantitative evidence that qualifies interpretation.
04KP
Cusps & sub-lords
The precise significator and sub-lord vocabulary of Krishnamurti Paddhati.
05PANCHANGA
Calendar intelligence
The five limbs, local transitions, festivals and time-sensitive daily products.
06MUHŪRTA
Electional timing
Event-specific candidate windows, exclusions and explainable moment checking.
07SAṂBANDHA
Compatibility
Structured comparison for professional, matrimonial and relationship applications.
08SAṄKHYĀ
Numerology
A deep Chaldean service surface spanning 168 verified endpoints.
09JÑĀNA
Learning services
A knowledge foundation for guided lessons, interaction and educational experiences.
03Built for real products
Your market.
Grahvani depth.
The API surface can support a focused customer feature, a complete practitioner workflow or the Vedic intelligence layer of an entire company.
Astrology products
Launch web or mobile chart experiences without rebuilding the complete Vedic calculation foundation.
Practitioner platforms
Power chart workbenches, client portals, reports and specialised professional workflows.
Matrimonial services
Add a deeper compatibility layer with structured components rather than a single unexplained score.
Calendar applications
Create local Panchanga, festival, transit and electional-time experiences.
Learning companies
Connect educational products to real calculations and a structured Vedic knowledge system.
Enterprise workflows
Bring charts, reports, numerology or timing intelligence into internal products and customer journeys.
04Enterprise posture
Power is calculation.
Readiness is everything around it.
Enterprise integration requires a service to be understandable, governable and operable—not merely impressive in a demo.
Gateway fundamentals
Routing, CORS, request IDs and rate limiting exist in the operational gateway foundation.
Access boundary
Hardened authentication and approved plan enforcement remain release gates before enterprise access.
Structured contracts
Named inputs and outputs support maintainable implementation rather than screen-scraping or brittle widgets.
Calculation provenance
Outputs can preserve the vocabulary and constituents needed to understand what was computed.
Service resilience
Validation, caching and circuit-breaker behaviour exist in the calculation proxy architecture.
Tradition clarity
Methods remain named so that a product can communicate which Vedic framework produced a result.
Operating evidence
No public uptime or latency promise is made until dated production measurements and monitoring coverage are approved.
CURRENT COREGateway routing, request IDs, rate limiting, proxy validation, caching and circuit breaking
RELEASE GATESHardened authentication, approved plan enforcement, route verification and support terms
PUBLIC BOUNDARYNo SLA, uptime, latency or standardized purchasable API plan is currently announced
Clear request. Structured result.
Developer-shaped from the first call.
API contracts are designed around explicit astronomical and astrological context. The consumer chooses the requested calculation; Grahvani does not hide ambiguous assumptions inside a generic prompt.
The request shown is illustrative and not presented as a live public documentation contract. Endpoint availability and integration documentation are supplied during a qualified integration review.
POST /v1/chart/natal
{
"datetime": "1990-08-15T14:30:00+05:30",
"latitude": 28.6139,
"longitude": 77.2090,
"ayanamsa": "lahiri"
}05Integration plans
Start focused.
Scale with the product.
Grahvani is preparing access paths for individual builders, established practitioners and companies. Scope, safeguards, volume and support are qualified through an integration conversation.
Developer fit
For a focused product hypothesis that needs one named calculation domain first.
- Service-fit review
- Contract and context discussion
- Access terms unannounced
Professional fit
For a practitioner team connecting calculation to a bounded daily workflow.
- Workflow and data review
- Domain-composition discussion
- Access terms unannounced
Enterprise fit
For a company evaluating multiple services, operating safeguards and implementation support.
- Architecture qualification
- Volume and support discovery
- Commercial terms unannounced
भवतः उत्पादः · ग्रहवाणीस्य गणना
Your product.
Powered by Grahvani.
Tell us what you are building, the services you need and the scale you intend to reach.
Start an API conversation