TKS Ephemeris · engine & API

TKS engine & API — live examples with output

The complete TKS stack: Engine A (reference DE path) and Engine B (independent N-body), and every public endpoint with a live request and its JSON output.

Architecture

Engine A

reference

JPL DE440/DE441 read through an independent DAF/SPK evaluator (Chebyshev type-2), then apparent-place reduction, ecliptic-of-date and sidereal. Used by all Pañcāṅga, heliacal, eclipse and observation endpoints.

Engine B

dynamics

Independent N-body integration (DOPRI5; Newtonian + 1PN EIH + J2–J6 + C22/S22). Initial states and GM from DE440; the trajectory thereafter is self-computed.

Shared API

trait

Both engines expose the same state/position interface; all higher layers (apparent, pañcāṅga, events) are engine-independent.

Endpoints

Date Time Lat Lon Place Body