Developer reference

Vedaksha API documentation

Generate kundli charts, compute panchanga and dasha timelines, and connect an astrology MCP server to your AI agent.

Python quick start

Generate a kundli with Python

Install with pip install vedaksha, then specify a sidereal ayanamsha and house system. This example computes an IndianOfficial (Lahiri) whole-sign chart.

from vedaksha import Vedaksha

vk = Vedaksha()
chart = vk.natal_chart(julian_day=2451545.0, latitude=28.6139, longitude=77.2090,
                       ayanamsha="IndianOfficial", house_system="WholeSign")
print(chart["houses"]["asc"], [(p["name"], p["sign"]) for p in chart["planets"]])

julian_day is UT1, not TT or TDB. The MCP and Python natal-chart interfaces default to tropical, so state the ayanamsha explicitly for a kundli. The WASM natal-chart interface takes UTC calendar fields and defaults to IndianOfficial.

Source: v10.0.0 Python quick start

Panchanga API

Compute panchanga for a time and place

The five limbs are tithi, vara, nakshatra, yoga and karana. The MCP compute_panchanga tool needs planetary longitudes as well as a time and observer.

Pass jd in UT1, sun and moon as sidereal longitudes in degrees, and observer latitude and east-positive longitude. Optional elevation_m and tz_offset_minutes describe the observer.

Vara is reckoned from local sunrise. Check vara.from_sunrise: true means an actual sunrise was used; false means the local civil weekday is a fallback because no sunrise was available. A null vara.rahu_kalam is a different signal: Kalam windows can be unavailable even when from_sunrise is true.

Panchanga inputs and output schema

Dasha API

Compute Vimshottari and other dasha timelines

Select the system before assembling its inputs. Every system takes birth_jd in UT1; the required chart data varies.

  • Vimshottari, Ashtottari and Yogini take the natal sidereal moon_longitude.
  • Chara and Narayana take lagna_sign and graha_signs.
  • Sthira, Niryana Shoola and Maheshwara take lagna_sign and graha_longitudes.

Sign indices are zero-based. The graha maps contain the seven classical grahas and Rahu; Ketu is derived and must not be supplied. Narayana is documented as an alias of Chara. Optional arguments also depend on the selected system.

In WASM v10.0.0, compute_dasha takes one serialized JSON object with the MCP arguments. compute_shadbala likewise takes one JSON object, requiring julian_day, latitude, longitude and a sidereal ayanamsha.

Dasha inputs and output schemas

Start here

Discover the surface.

One unauthenticated curl returns the canonical tool catalog as JSON-RPC 2.0.

curl -sS -X POST https://vedaksha.net/api/mcp \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | jq

RECEIPT · https://vedaksha.net/api/mcp · canonical introspection mirror · drift-tested in CI · last verified 2026-08-16

Try it live

Two ways to evaluate.

Run the engine in your browser, or browse the canonical tool catalog. To execute the full surface, self-host the engine.

Install + reference

Install for each runtime.

The bindings use the same Rust engine. Bit-level reproducibility depends on the computation and target architecture. Each row links to the canonical registry or documentation for that runtime.

Questions

Common questions about Vedaksha

What is Vedaksha?

Vedaksha is a Rust engine for astronomical ephemeris and Vedic astrology, with Python and WebAssembly bindings and a self-hosted MCP server. It computes planetary positions, natal charts, panchanga, dashas, vargas and shadbala.

Can Vedaksha generate a kundli or kundali?

Yes. Specify a sidereal ayanamsha such as IndianOfficial and a house system such as WholeSign. The MCP and Python natal-chart interfaces default to tropical; the WASM interface defaults to IndianOfficial.

Which dasha systems are supported?

Vimshottari, Ashtottari, Yogini, Chara, Narayana, Sthira, Niryana Shoola and Maheshwara. Required inputs vary by system. Narayana is documented as an alias of Chara.

Does it need ephemeris data files?

AnalyticalProvider evaluates VSOP87A and ELP/MPP02 from compiled constants. SpkReader reads a JPL kernel. The providers have separate accuracy measurements.

Does Vedaksha contain AGPL code?

No. Vedaksha is source-available under BUSL-1.1 and contains no AGPL code. Non-commercial use is free. Commercial use requires a one-time $500 license per organization, covering the licensed version and subsequent versions. Each release converts to Apache-2.0 four years after release.

Can I calculate charts through vedaksha.net/api/mcp?

That endpoint provides introspection. It lists tools but does not execute chart calculations. Run the MCP server yourself to execute them.