Docs · MCP

MCP tool catalog.

Vedaksha exposes a Model Context Protocol surface of 17 tools, natal charts, dashas, vargas, transits, muhurta, ashtakavarga, gochara, graph emit. The catalog below is fetched live from the introspection mirror at vedaksha.net/api/mcp, which mirrors the canonical schema snapshot in the source repository (drift-tested in CI). To run these tools, self-host the library or build from source.

17 tools · live from vedaksha.net/api/mcp · canonical snapshot tools/mcp-tools.json

Discover

One curl, every tool.

The introspection mirror is no-auth. List every tool, its parameters, and its description with one request.

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

tools/call

Calls run where you host the library.

Vedaksha is a BUSL-1.1 library. The introspection mirror documents the surface; to actually call these tools, self-host the library or build from source. Four package paths, one Rust codebase.

cargo install vedaksha-mcp Rust binary, native MCP server, all tools.

pip install vedaksha Python package running the real engine via WebAssembly (wasmtime); library, CLI, MCP server (stdio + HTTP), and an optional FastAPI REST projection. Any OS, Python ≥ 3.9, no Rust toolchain.

npm i vedaksha-wasm WASM build for browser and edge, no data files.

ghcr.io/arthiqlabs/vedaksha-mcp pre-built Docker image of the MCP server, linux/amd64 + linux/arm64.

Self-hosted HTTP mode requires auth as of v4.0.0: every POST must carry Authorization: Bearer with the token from VEDAKSHA_MCP_TOKEN. The server refuses to start without a token unless --insecure-no-auth is passed; /health and the informational GET stay open. stdio mode is unchanged.

Build from source · BUSL-1.1 commercial-use terms · KundaliMCP fully-packaged production-ready MCP (full Vedic suite, narrative generation, multilingual, Parashari interpretation). Built on Vedaksha core by the same team at ArthIQ Labs.

Catalog

17 tools.

Each tool is a JSON-RPC method. Click a tool to expand its parameter list. Required parameters are unmarked; optional parameters have a trailing ?.

compute_natal_chart

Compute a natal astrological chart for a given time and location. Returns a ChartGraph in JSON format containing planetary positions, house cusps, aspects, nakshatras, and dignities.

5 parameters
ayanamsha?stringSidereal zodiac system. Eleven systems, each derived forward from a primary source and none tuned to match another implementation. The chart's true_ayanamsha_value output field reports the TRUE ayanamsha (mean plus nutation in longitude) already applied — nutation is included, do not add it yourself. Pass Tropical for no rotation. Systems: IndianOfficial = Indian Astronomical Ephemeris 2022, AYANAMSA section: 23 deg 51 min 25.53 sec at J2000.0, propagated by P03 general precession | FaganBradley = Fagan & Firebrace, Primer of Sidereal Astrology: synetic vernal point 335 deg 57 min 28.64 sec at B1950.0, ayanamsha = 360 deg minus SVP | Krishnamurti = Krishnamurti Padhdhati Vol-I: 22 deg 22 min 00 sec on the 1st of Chitra 1900, propagated at KSK's stated 50.2388475 arcsec/yr | Raman = Raman, A Manual of Hindu Astrology (1935), Ch. III Art. 49 | SuryaSiddhanta = Surya Siddhanta Ch. 3 vv. 9-12 | Yukteshwar = Yukteswar, The Holy Science (1894) | RevatiPaksha [star] = Revati at the sidereal initial point, the majority reading against Surya Siddhanta Ch. 8's own 359 deg 50 min, zeta Piscium per Hipparcos | PushyaPaksha [star] = Narasimha Rao, Introducing Pushya-paksha Ayanamsa | TrueChitra [star] = Self-describing condition; Spica per Hipparcos | ChandraHari [star] = Chandra Hari, Indian J. History of Science 33(4), 1998 | GalacticCenter0Sag [star] = Self-describing condition; Sgr A* per Gordon, de Witt & Jacobs (2023), AJ 165, 49.
house_system?stringHouse system: Placidus, Koch, Equal, WholeSign, etc.
julian_daynumberJulian Day number in UT1 (Universal Time) — not TT, not TDB. The engine converts to TT internally for the dynamical terms (planetary positions, nutation, obliquity) and evaluates the Earth-rotation term — sidereal time, and hence the ascendant, the MC and all twelve house cusps — at this UT1 value directly. Supplying a TDB Julian Day rotates every cusp by 0.289° (17.3') at today's ΔT ≈ 69 s.
latitudenumberGeographic latitude in degrees [-90, +90]
longitudenumberGeographic longitude in degrees [-180, +180], east positive
compute_dasha

Compute Vedic dasha (planetary period) sequences. Supports five classical systems: Vimshottari, Ashtottari, Yogini (Moon-longitude based, require `moon_longitude`); Chara, Narayana (sign based, require BOTH `lagna_sign` AND `graha_signs`, since each sign's period length is counted to the sign its lord occupies in this chart). `graha_signs` takes the eight `sign_index` values compute_natal_chart already returns; Ketu is derived from Rahu and must not be supplied. Returns a JSON dasha tree with start/end Julian Days.

6 parameters
birth_jdnumberBirth Julian Day used as the dasha epoch, in UT1 (Universal Time) — not TT, not TDB, i.e. the same scale as compute_natal_chart's julian_day. This epoch is only added to, never converted: every returned start_jd/end_jd is on the same UT1 scale as the input.
graha_signs?objectNatal sign positions of the seven classical grahas plus Rahu, 0-11 each (0 = Aries), as served by compute_natal_chart's sign_index. Required for Chara, Narayana, whose period lengths are chart-dependent — each sign's duration is the count from that sign to the sign its lord actually occupies. Sign indices are used rather than longitudes: they chain directly from compute_natal_chart's sign_index with no conversion, carry no tropical-vs-sidereal ambiguity, and avoid the boundary question of a planet at exactly 30.0 degrees. Ketu is not a field: it is derived as (rahu + 6) mod 12, since the two lunar nodes are always exactly opposite.
lagna_sign?integerLagna (ascendant) sign 0–11 (0 = Aries). Required for Chara, Narayana. This is the same 0-indexed convention compute_natal_chart, compute_bhavas and compute_vargas all serve as `sign_index`, so an ascendant read from any of them passes straight through. Through v8.1.0 this one parameter was 1-indexed while every other tool was 0-indexed; that mismatch is resolved here.
levels?integerNumber of nested dasha levels (1–5). Ignored by Chara and Narayana.
moon_longitude?numberNatal Moon sidereal longitude in degrees [0, 360). Required for Vimshottari, Ashtottari, Yogini.
system?stringDasha system selector
compute_karakas

Compute Jaimini Chara Karaka assignments from sidereal planet longitudes. Ranks planets by degrees within their current sign: highest = Atmakaraka (soul significator), lowest = Darakaraka (spouse significator). Supports 7-karaka (Sun–Saturn) and 8-karaka (adds Rahu) schemes.

9 parameters
jupiternumberSidereal longitude of Jupiter [0, 360)
marsnumberSidereal longitude of Mars [0, 360)
mercurynumberSidereal longitude of Mercury [0, 360)
moonnumberSidereal longitude of Moon [0, 360)
rahu?numberSidereal longitude of Rahu [0, 360). Required for scheme '8'.
saturnnumberSidereal longitude of Saturn [0, 360)
scheme?stringKaraka scheme: '7' (default, Sun–Saturn) or '8' (adds Rahu + Pitrikaraka)
sunnumberSidereal longitude of Sun [0, 360)
venusnumberSidereal longitude of Venus [0, 360)
compute_combustion

Compute combustion state for each planet relative to the Sun per BPHS Ch.7 vv.28-29. Returns Combust, DeeplyCombust, or None for Moon, Mars, Mercury, Jupiter, Venus, Saturn with degrees of separation. This is a low-level tool over already-known positions, not a natal-chart tool: call compute_natal_chart first and pass its planets[].longitude (matched by planets[].name) and planets[].retrograde values straight through as this tool's inputs — do not recompute or re-derive them.

12 parameters
jupiternumberSidereal longitude of Jupiter [0, 360). From compute_natal_chart's planets[] entry where name == "Jupiter", field longitude.
jupiter_retrograde?booleanTrue if Jupiter is retrograde. Accepted for symmetry; Jupiter's orb is 11 deg either way, so this does not change the result. From compute_natal_chart's Jupiter entry, field retrograde.
marsnumberSidereal longitude of Mars [0, 360). From compute_natal_chart's planets[] entry where name == "Mars", field longitude.
mars_retrograde?booleanTrue if Mars is retrograde, which narrows its combustion orb from 17 deg to 8 deg. From compute_natal_chart's Mars entry, field retrograde.
mercurynumberSidereal longitude of Mercury [0, 360). From compute_natal_chart's planets[] entry where name == "Mercury", field longitude.
mercury_retrograde?booleanTrue if Mercury is retrograde, which narrows its combustion orb from 14 deg to 12 deg (BPHS Ch. 7 vv. 28-29). From compute_natal_chart's Mercury entry, field retrograde.
moonnumberSidereal longitude of Moon [0, 360). From compute_natal_chart's planets[] entry where name == "Moon", field longitude.
saturnnumberSidereal longitude of Saturn [0, 360). From compute_natal_chart's planets[] entry where name == "Saturn", field longitude.
saturn_retrograde?booleanTrue if Saturn is retrograde. Accepted for symmetry; Saturn's orb is 16 deg either way, so this does not change the result. From compute_natal_chart's Saturn entry, field retrograde.
sunnumberSidereal longitude of Sun [0, 360). From compute_natal_chart's planets[] entry where name == "Sun", field longitude.
venusnumberSidereal longitude of Venus [0, 360). From compute_natal_chart's planets[] entry where name == "Venus", field longitude.
venus_retrograde?booleanTrue if Venus is retrograde, which narrows its combustion orb from 10 deg to 8 deg. From compute_natal_chart's Venus entry, field retrograde.
compute_shadbala

Compute six-fold Shadbala (Sthana, Dig, Kala, Cheshta, Naisargika, Drik Bala) per planet, with the Sthana sub-components (uccha, ojhayugma, kendradi, drekkana) and ishta/kashta phala, per BPHS Ch.27-28. Sthana Bala omits Saptavargaja Bala and Kala Bala covers Nathonnatha and Paksha only.

3 parameters
is_daytime?booleanTrue if the birth moment falls between sunrise and sunset. Feeds Nathonnatha Bala within Kala Bala.
moon_phase_waxing?booleanTrue during shukla paksha (waxing Moon). Feeds Paksha Bala within Kala Bala.
planetsarrayArray of planet data objects.
compute_vargas

Compute Vedic divisional charts (vargas). Given a time and place, returns one chart per requested division: the varga lagna, and for each of the ten bodies compute_natal_chart returns — the seven grahas plus the mean, true and osculating lunar node — its rashi longitude, the sign it occupies within that varga, its dignity in that sign, and its whole-sign bhava counted from the varga lagna. Ketu is not listed separately: it is the node's opposite point, 180 degrees away. The nodes carry no dignity, so that field is absent for them. Supply planet_longitude instead to divide a single longitude without an ephemeris lookup, in which case no graha name, dignity or bhava is returned because none is defined. Vargas are classically read on a sidereal zodiac: pass an ayanamsha, or accept the Tropical default this surface uses everywhere. Source: BPHS Ch. 6-7.

7 parameters
ayanamsha?stringSidereal zodiac system. Eleven systems, each derived forward from a primary source and none tuned to match another implementation. The chart's true_ayanamsha_value output field reports the TRUE ayanamsha (mean plus nutation in longitude) already applied — nutation is included, do not add it yourself. Pass Tropical for no rotation. Systems: IndianOfficial = Indian Astronomical Ephemeris 2022, AYANAMSA section: 23 deg 51 min 25.53 sec at J2000.0, propagated by P03 general precession | FaganBradley = Fagan & Firebrace, Primer of Sidereal Astrology: synetic vernal point 335 deg 57 min 28.64 sec at B1950.0, ayanamsha = 360 deg minus SVP | Krishnamurti = Krishnamurti Padhdhati Vol-I: 22 deg 22 min 00 sec on the 1st of Chitra 1900, propagated at KSK's stated 50.2388475 arcsec/yr | Raman = Raman, A Manual of Hindu Astrology (1935), Ch. III Art. 49 | SuryaSiddhanta = Surya Siddhanta Ch. 3 vv. 9-12 | Yukteshwar = Yukteswar, The Holy Science (1894) | RevatiPaksha [star] = Revati at the sidereal initial point, the majority reading against Surya Siddhanta Ch. 8's own 359 deg 50 min, zeta Piscium per Hipparcos | PushyaPaksha [star] = Narasimha Rao, Introducing Pushya-paksha Ayanamsa | TrueChitra [star] = Self-describing condition; Spica per Hipparcos | ChandraHari [star] = Chandra Hari, Indian J. History of Science 33(4), 1998 | GalacticCenter0Sag [star] = Self-describing condition; Sgr A* per Gordon, de Witt & Jacobs (2023), AJ 165, 49.
divisionsarrayVarga division codes to compute, e.g. ["D1", "D9", "D10"]
julian_daynumberJulian Day number in UT1 (Universal Time) — not TT, not TDB. Same scale as compute_natal_chart's julian_day: the engine converts to TT internally for the dynamical terms and uses UT1 directly for the Earth-rotation term.
latitudenumberGeographic latitude in degrees [-90, +90]
longitudenumberGeographic longitude in degrees [-180, +180], east positive
planet_longitude?numberSidereal longitude of a single body in degrees [0, 360). When supplied, only this longitude is divided and no ephemeris is consulted; the result carries no graha name, dignity or bhava.
tradition?stringWhich Parashari reading to use where the texts diverge. 'modality' (default) starts the division from a movable/fixed/dual sign; 'element' starts it from a fire/earth/air/water sign. This changes D16, D20, D30 and D45 only; every other varga is identical under both. Source: BPHS Ch. 6; Phala Deepika Ch. 2.
emit_graph

Turn a chart into a queryable property graph. Accepts the output of compute_natal_chart directly (pass latitude and longitude alongside it), or an existing ChartGraph. Emits Neo4j Cypher, SurrealDB SurrealQL, JSON-LD, plain JSON, or RAG embedding text.

5 parameters
chart_jsonobjectEither the output of compute_natal_chart ({planets, houses, aspects, ...}), which is converted to a graph here, or an existing ChartGraph ({nodes, edges, chart_id, classification})
classification?stringOptional label or session ID attached to emitted nodes
formatstringTarget output format
latitude?numberObserver latitude, degrees north. Required when chart_json is a computed chart; a chart result does not record where it was cast. Ignored for an existing ChartGraph.
longitude?numberObserver longitude, degrees east. Required when chart_json is a computed chart.
compute_transit

Compute transiting planet positions relative to a natal chart at a specific moment. Returns planet longitudes for the transit time alongside natal positions, enabling aspect calculation between transit and natal placements.

4 parameters
natal_jdnumberJulian Day of the natal chart in UT1 (Universal Time) — not TT, not TDB. The engine converts to TT internally for the dynamical terms.
natal_latnumberNatal geographic latitude in degrees [-90, +90]
natal_lonnumberNatal geographic longitude in degrees [-180, +180], east positive
transit_jdnumberJulian Day of the transit moment to compute, in UT1 (Universal Time) — not TT, not TDB. The engine converts to TT internally for the dynamical terms.
search_transits

Search for transiting planet–natal planet aspects within a time window. Supply natal positions and a Julian Day range; receive a list of exact transit moments with aspect type, orb, and applying/separating status.

6 parameters
aspects?arrayAspect types to filter (e.g. conjunction, opposition, trine). Defaults to major aspects.
bodies?arrayTransiting bodies to include. Defaults to all planets.
end_jdnumberEnd of the search window as a Julian Day in UT1 (Universal Time) — not TT, not TDB.
max_orb?numberMaximum orb in degrees (default 1.0)
natal_positionsarrayArray of natal planet positions to check transits against
start_jdnumberStart of the search window as a Julian Day in UT1 (Universal Time) — not TT, not TDB. The engine converts to TT internally for the dynamical terms; each event's exact_jd is returned on this same UT1 scale.
search_muhurta

Search for auspicious time windows (muhurta) within a given period for a geographic location. Returns ranked muhurta candidates with quality scores based on tithi, nakshatra, yoga, karana, and planetary positions. The search window is capped at 30 days (see MUHURTA_SEARCH_RANGE_TOO_LARGE) — the per-candidate vara and tithi/nakshatra refinement make this tool far more expensive per day of range than a transit search, so a wider span would make a single call take minutes.

7 parameters
elevation_m?numberObserver elevation in metres above sea level [-500, 9000] (default 0). Lowers the horizon by the dip and so moves sunrise, which is what each candidate's vara is reckoned from — at 3650 m (Lhasa) 9.2 minutes earlier. Pass the same value as compute_panchanga for the same observer, or the two tools can report different weekdays for one instant.
end_jdnumberEnd of the search window as a Julian Day in UT1 (Universal Time) — not TT, not TDB. The span from start_jd to end_jd must not exceed 30 days.
latitudenumberGeographic latitude in degrees [-90, +90]
longitudenumberGeographic longitude in degrees [-180, +180], east positive
min_quality?numberMinimum quality score [0.0, 1.0] for muhurta inclusion (default 0.5)
start_jdnumberStart of the search window as a Julian Day in UT1 (Universal Time) — not TT, not TDB. The engine converts to TT internally for the dynamical terms and uses UT1 directly for sunrise, which each candidate's vara is reckoned from; every returned jd, tithi_end_jd and nakshatra_end_jd is on this same UT1 scale. The span from start_jd to end_jd must not exceed 30 days.
tz_offset_minutes?integerOffset of the observer's civil clock from UT, in minutes. Names the vara (weekday) reported for each candidate — it does not change which sunrise bounds the vara, only what that vara is called. Default 0 (UT).
compute_ashtakavarga

Compute Bhinna Ashtakavarga (raw bindu tables) and Sarvashtakavarga for all 7 planets from sign positions. Source: BPHS Ch.66 vv.13-68. Trikona/Ekadhipatya Shodhana and Pinda Sadhana are not included.

8 parameters
jupiterintegerSign index of Jupiter (0=Aries…11=Pisces)
lagnaintegerSign index of Lagna (Ascendant)
marsintegerSign index of Mars (0=Aries…11=Pisces)
mercuryintegerSign index of Mercury (0=Aries…11=Pisces)
moonintegerSign index of Moon (0=Aries…11=Pisces)
saturnintegerSign index of Saturn (0=Aries…11=Pisces)
sunintegerSign index of Sun (0=Aries…11=Pisces)
venusintegerSign index of Venus (0=Aries…11=Pisces)
compute_gochara

Compute Gochara (transit interpretation) for the seven grahas against a natal reference sign per BPHS Ch.29. Returns favourable/unfavourable verdict, house from natal, and raw vedha (obstruction) candidates per planet. The natal reference sign is the caller's choice — typically the natal Moon's sign (Chandra Gochara) or the natal Lagna's sign. Rahu and Ketu are not included.

10 parameters
jupiterintegerTransit sign index of Jupiter
marsintegerTransit sign index of Mars
mercuryintegerTransit sign index of Mercury
moonintegerTransit sign index of Moon
natal_reference_signintegerSign index of the natal reference point — natal Moon for Chandra Gochara, natal Lagna for Lagna-based Gochara
saturnintegerTransit sign index of Saturn
school?stringExemption profile applied to the raw vedha candidate list
sunintegerTransit sign index of Sun (0=Aries … 11=Pisces)
vedha_table?stringVedha pair table source
venusintegerTransit sign index of Venus
compute_panchanga

Compute the panchanga — the five limbs of the Vedic almanac — for an instant: tithi (lunar day, with paksha and lord), vara (weekday reckoned from local sunrise, with its lord and the Rahu and Gulika Kalam windows as Julian Days), nakshatra (with pada), yoga (one of the 27 nithya yogas, with degrees remaining), and karana (half-tithi). Takes sidereal longitudes; all returned instants are Julian Days (UT). vara.from_sunrise reports HOW the weekday was reckoned: true means it was taken from an actual local sunrise (the Vedic definition); false means no sunrise exists to reckon from — the polar day or polar night, above about ±66.5° latitude — and the value is the observer's local CIVIL weekday as a documented fallback, which is a different quantity. Check it before presenting the vara at high latitude. vara.rahu_kalam being null is NOT the same signal: the Kalam windows can also be null while from_sunrise is true.

7 parameters
elevation_m?numberObserver elevation in metres above sea level [-500, 9000] (default 0). Lowers the horizon by the dip and so moves sunrise — at 3650 m (Lhasa) 9.2 minutes earlier, enough to change the vara in that window. Pass the same value as search_muhurta for the same observer, or the two tools can report different weekdays for one instant.
jdnumberJulian Day number in UT1 (Universal Time) — not TT, not TDB. The engine converts to TT internally for the dynamical terms and uses UT1 directly for sunrise, which the vara is reckoned from; every returned instant, the Rahu and Gulika Kalam bounds included, is on this same UT1 scale. Supplying a TT/TDB Julian Day shifts sunrise by ΔT (≈ 69 s today), enough to move the vara for an instant near sunrise.
latitudenumberObserver latitude in degrees. Required — the vara is reckoned from local sunrise, so it depends on the observer.
longitudenumberObserver longitude in degrees, east positive. Required.
moonnumberSidereal longitude of Moon [0, 360)
sunnumberSidereal longitude of Sun [0, 360)
tz_offset_minutes?integerOffset of the observer's civil clock from UT, in minutes, in [-720, 840] (UTC-12:00 to UTC+14:00). Used only to name the vara's weekday.
compute_drishti

Compute graha drishti — Vedic sign aspects — for all nine grahas. Unlike Western aspects, drishti is cast from sign to sign and is asymmetric: every graha aspects the 7th from itself, and Mars additionally aspects the 4th and 8th, Jupiter the 5th and 9th, Saturn the 3rd and 10th. Returns each aspect with its graded strength (Full, ThreeQuarter, Half, Quarter) and the house distance.

9 parameters
jupiternumberSidereal longitude of Jupiter [0, 360)
ketunumberSidereal longitude of Ketu [0, 360)
marsnumberSidereal longitude of Mars [0, 360)
mercurynumberSidereal longitude of Mercury [0, 360)
moonnumberSidereal longitude of Moon [0, 360)
rahunumberSidereal longitude of Rahu [0, 360)
saturnnumberSidereal longitude of Saturn [0, 360)
sunnumberSidereal longitude of Sun [0, 360)
venusnumberSidereal longitude of Venus [0, 360)
compute_bhavas

Compute the whole-sign bhava (house) chart from an ascendant. In the Vedic whole-sign system the entire sign containing the ascendant is the 1st bhava, the next sign the 2nd, and so on — houses do not have cusps within signs. Returns the sign of each of the twelve bhavas with its kendra / trikona / dusthana / upachaya classification, and optionally places supplied grahas into their bhavas.

2 parameters
ascendantnumberSidereal longitude of the ascendant [0, 360)
planets?objectOptional map of graha name to sidereal longitude, e.g. {"Mars": 200.4}. Each is placed into its bhava.
compute_synastry

Compute synastry — the aspects each graha in one chart makes to each graha in another chart. Every graha in chart A is tested against every graha in chart B (the two charts do not need the same graha names), and each hit is returned with its aspect type, orb in degrees and strength (1.0 at exact, falling linearly to 0.0 at the orb boundary). Orbs are the traditional Lilly values — conjunction, trine and opposition 8°, square 7°, sextile 6°, minors 2° — scaled by orb_factor. Longitudes only: this tool needs no birth time, place or ephemeris.

4 parameters
aspect_set?string'major' (default) tests the five Ptolemaic aspects; 'all' adds semi-sextile, semi-square, quintile, sesquiquadrate, bi-quintile and quincunx.
chart_aobjectMap of graha name to sidereal longitude [0, 360) for the first chart, e.g. {"Sun": 10.0, "Moon": 130.0}.
chart_bobjectMap of graha name to sidereal longitude [0, 360) for the second chart. Need not use the same names as chart_a.
orb_factor?numberMultiplier on the default orbs. 1.0 (default) is standard, 0.5 is tight. Must be greater than 0 and at most 5.0, above which the major-aspect windows cover every separation.
compute_composite

Compute the midpoint composite chart of two charts: for each graha, the shorter-arc midpoint of its longitude in the two charts, and the arithmetic mean of its two speeds. The two charts must carry the SAME graha names — each graha is paired with its namesake, not with whatever happens to sit at the same position in a list — and a name present in one chart but not the other is an error naming that graha. Longitudes only: this tool needs no birth time, place or ephemeris.

2 parameters
chart_aobjectMap of graha name to position for the first chart, e.g. {"Sun": {"longitude": 350.0, "speed": 1.0}}. `speed` is optional and defaults to 0.
chart_bobjectMap of graha name to position for the second chart. Must have exactly the same graha names as chart_a.

Next

Where to go from here.