Ephemerides
Planetary positions at the requested moment.
Adapter · Active
FENKI’s first adapter takes ephemerides, planetary positions, aspects, houses and transits and turns them into deterministic context that an LLM can inspect and interpret.
Extract
The adapter collects astronomically precise input for a selected instant and place.
Planetary positions at the requested moment.
Phase, illumination and lunar nodes.
Conjunctions, trines, squares and oppositions.
A dynamic moment compared with a saved natal chart.
Transform
Raw calculations pass through four stages before becoming meaningful model context.
Raw ephemerides become structured records.
Angles become degrees, signs become enums and intervals become ranges.
Astrological terms receive explicit descriptive markers.
The normalized chart becomes a prompt-ready context block.
Load
The export is structured, inspectable and ready for a model or another program.
Positions, houses, aspects and phases in stable fields.
A compact representation ready to insert into a prompt.
FENKI calculates facts; the model explains them instead of guessing them.
context_output.json
{
"moment": "2026-08-12T14:30:00Z",
"planets": {
"sun": { "sign": "Leo", "degree": 19.7, "house": 9 },
"moon": { "sign": "Pisces", "degree": 4.2, "house": 4 },
"mercury": { "sign": "Virgo", "degree": 2.1, "house": 10 }
},
"aspects": [
{ "a": "sun", "b": "moon", "type": "opposition", "orb": 5.5 },
{ "a": "mercury", "b": "sun", "type": "conjunction", "orb": 2.4 }
],
"moon_phase": { "phase": "waning_crescent", "illumination": 0.31 }
}START WITH ANY ASTROLOGY TASK
Give this instruction to an LLM before supplying birth data, chart references, comparison charts, or a transit period.
Use FENKI as the calculation source before interpreting any astrology request, including natal charts, current or dated transits, transit ranges, synastry-style comparisons, and other supported workflows.
1. Read https://fenki.net/llms.txt and https://fenki.net/openapi.json to identify the currently supported operations and their required parameters.
2. Ask for any missing inputs before calling the API: civil date and time, IANA time zone, coordinates or place, natal chart reference, second natal chart, and target moment or range as applicable.
3. Call only operations advertised in OpenAPI. For a natal chart, request a natal dataset. For transits, first obtain or use the natal chartRef, then request the target moment or range. For synastry-style analysis, obtain two natal datasets and compare only their returned positions and aspects unless OpenAPI advertises a dedicated synastry operation.
4. Treat FENKI's returned positions, houses, signs, aspects, orbs, applying state, settings, validation, and provenance as the authoritative calculation data.
5. Do not invent missing data, infer unsupported aspects, or recalculate ephemerides.
6. Separate calculation facts from interpretation and cite exact returned values for every conclusion.
After fetching the required FENKI data, answer the user's astrology question in the requested language and format.The result is reproducible: identical chart inputs always produce identical export context.
Open astrology workspace