GalacticMist API

The computation engine behind GalacticMist, over JSON. Every value labeled with its convention, every response carrying its settingsDigest, every uncertainty carried — never hidden.

Looking for charts, not JSON? The product lives at galacticmist.pages.dev — it computes on-device and never sends birth data anywhere, including to this API.

Base URL

https://galacticmist-api.troutberger.workers.dev

POST JSON to the endpoints below (60 requests/min per IP; the limit is per edge isolate and the 429 body says so — we'd rather explain the limitation than pretend it's global). CORS is open. No accounts, no keys, no logging of request bodies.

Endpoints

/v1/chartnatal chart + aspect graph
/v1/progressions/secondary{natal, target} → progressed chart
/v1/progressions/solar-arc{natal, target} → directed chart + arc
/v1/returns/solar{natal, nthYear, relocation?} → return instant + chart
/v1/time-lords/profections{natal, years} → annual profection timeline
/v1/time-lords/vimshottari{time, ayanamshaId?, levels?} → dasha timeline
/v1/time-lords/zr{natal, lot?, years?} → zodiacal releasing L1+L2 + computed lot
/v1/time-lords/firdaria{natal, nodeVariant?} → firdaria timeline (sect auto-detected)
/v1/mundane/cyclic-index{time} or {fromYear, toYear, sampling} → Barbault index
/v1/relational/synastry{a, b} → both charts + inter-aspects + house overlays
/v1/relational/composite{a, b, houseSystem?} → midpoint chart (whole-sign/equal/porphyry)
/v1/relational/davison{a, b} → spacetime-midpoint chart + midpoint place
/v1/search/transits{natal, from, to, bodies?} → transit contacts (enter/exact/leave)
/v1/electional/search{from, to, constraints} → satisfying intervals
/v1/vedic/vargas{natal, schemes?} → D3/D9/D10 + Sripati bhava chalita
/v1/vedic/panchanga{time, ayanamshaId?, utcOffsetMinutes?} → tithi/karana/yoga/vara
/v1/directions/zodiacal{natal, maxYears?} → primary directions, Ptolemy + Naibod dated

Machine-readable surface: OpenAPI 3.1 · provider meta

Example

curl -s -X POST https://galacticmist-api.troutberger.workers.dev/v1/chart \
  -H 'content-type: application/json' \
  -d '{"time":{"year":1990,"month":6,"day":15,"hour":14,"minute":32,"utcOffsetMinutes":-240},
       "place":{"latitudeDegrees":40.7128,"longitudeDegreesEast":-74.006},
       "houses":"placidus"}'

Accuracy & provenance

Positions come from an astronomy-engine provider behind a provider interface; accuracy is measured, not claimed — see the measured accuracy report (vs JPL Horizons and a dev-only Swiss Ephemeris oracle). Every response carries provider, convention ids, ΔT model and uncertainty, and a SHA-256 settingsDigest over every convention that shaped it. Old share links from this page redirect to the product and keep working.