FENKI.net

Foundational Exporters Neural Kit Interface

Prepare specialist data for LLMs

FENKI is a deterministic preparation layer between specialist tools and neural systems. Turn reproducible calculations into model-ready datasets with explicit structure, validation, settings, and provenance.

Launch workspace Inspect the workflow

From domain input to reliable context

A deterministic preparation pipeline

The same input and settings produce the same normalized output, so prompts, agents, evaluations, notebooks, and databases can reason over traceable facts instead of screenshots or prose fragments.

01

Capture

Collect precise civil time, location, coordinates, mode, and calculation settings through accessible structured controls.

02

Calculate

Run the specialist engine locally and retain the assumptions, precision, versions, and validation result beside the values.

03

Package

Normalize entities and relationships into stable JSON, Markdown, and TSV with complete provenance for downstream use.

First production kit

Astrology exporter.

Build natal, current-sky, and transit datasets in the browser. Export planets, houses, signs, aspects, chart angles, civil input, UTC conversion, and calculation metadata—without sending birth data to a calculation server.

One calculation, several consumers

Portable output formats.

Choose the representation that fits the next system while preserving the same source dataset.

JSON

Typed nested data for APIs, retrieval pipelines, agents, validators, and application code.

Markdown

Readable structured context for prompts, research notes, reviews, and collaborative analysis.

TSV

Flat tables for spreadsheets, notebooks, data checks, and lightweight database import.

Agent-ready usage

Prompt pattern: fetch, then interpret

For any astrology question involving current or future transits, fetch the calculated FENKI artifact before interpreting the chart. The API is stateless and returns canonical JSON, Markdown, or compact text.

Natal charthttps://fenki.net/llm/astrology/natal?date=YYYY-MM-DD&time=HH:mm&timezone=AREA/CITY&latitude=LAT&longitude=LON

Current skyhttps://fenki.net/llm/astrology/chart?at=now&place=PLACE

Current transitshttps://fenki.net/llm/astrology/transits?chart=CHART_REF&at=now

Transit periodhttps://fenki.net/llm/astrology/events?chart=CHART_REF&from=TIME&to=TIME

Formal OpenAPI specification
  1. Fetch the FENKI transit endpoint before interpreting the chart.
  2. Treat planetary positions, houses, aspects, exact times, applying or separating status, and orbs returned by FENKI as authoritative.
  3. Do not recalculate astronomical positions yourself.
  4. Distinguish natal placements from transiting placements.
  5. Base interpretation only on aspects and positions present in the returned data.
  6. For a period rather than a moment, use the FENKI range endpoint instead of sampling arbitrary dates.
  7. Mention the exact observation time and timezone used by FENKI when relevant.

START WITH ANY ASTROLOGY TASK

Reusable FENKI prompt

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.

Local-first by default

Private by architecture

The FENKI workspace keeps sensitive chart requests and saved history in this browser. No account is required. The optional machine API receives only requests explicitly sent to its URL, stores no chart history, and analytics remains disabled unless the site operator configures it.

Provenance

Every export explains where values came from and which engine settings produced them.

Validation

Machine-readable status and stable error codes make bad civil-time or coordinate inputs visible.

Portability

Open formats keep the dataset usable outside FENKI and independent of a single model vendor.

FENKI · ASTRO

Prepare a traceable astrology dataset.

Start with a demo, enter a known chart, or reopen local history—then copy or download the complete dataset.

Open the astrology workspace