# TimePortal Future — LLM query guide Use this interface when a user asks you to query Future and report a text table. An HTTP-capable LLM or agent can use GET or POST; no browser automation is required. - Endpoint: https://timeportal.pro/future/query.php - OpenAPI schema: https://timeportal.pro/future/openapi.json - Human application: https://timeportal.pro/future/ - GET without arguments returns capability metadata and links. `OPTIONS` is supported for browser clients. - `format=markdown` returns plain UTF-8 text containing Markdown tables. `format=json` (default) returns named tables, metadata, normalized query options, and the same `markdown` report. - Every table row is a calculated result or annotation from the existing application. Readings are not generated by an LLM. ## How an agent should work 1. Obtain the required dates and any requested options from the user. Use unambiguous YYYY-MM-DD dates; do not guess missing personal dates. 2. Prefer a structured request using the fields below. For an ordinary language request, send `query` with explicit ISO dates; the site's Jev model selects typed arguments. Explicit structured fields override the interpreted fields. Jev's shortcut covers dates, hemisphere flags, language, aspect selection, masking for Saju, and primary/market-context flags for Future. Supply exact relationship filters, minimum durations, and display names through their structured fields. 3. Submit the request once. Requests use the site's existing access controls and reading limits. Do not automatically retry a limited request. 4. Check HTTP status and `success`. A 422 response asks for corrected inputs; 429 means the existing reading limit; 502/504 means an upstream problem. Never invent a replacement reading. 5. Return the supplied text tables, preserving directions, dates, units, score labels, missing-data notes, and the distinction between the site's symbolic interpretation and a factual prediction. Do not present symbolic scores as measured real-world probabilities. 6. If a result is large, use explicit aspect/date filters with the user's intent and state those filters. Do not silently omit unfavorable rows or turn all features into a single summary. ## Credentials and privacy If the user already has a site access credential, send it as `Authorization: Bearer `, `X-Timeportal-Code`, or the `access_code` field of a JSON POST. Do not put credentials in URLs. The server preserves the backend's access decision; this API does not grant additional privileges. The Jev API key is configured on the server; callers do not supply it. Natural-language `query` text is sent to TypeSafe/Jev for interpretation. Do not put any access credential in that text. Structured queries do not call Jev. Natural-language interpretation is limited to 24 requests per minute across this interface; a busy response also uses HTTP 429. Responses use `Cache-Control: no-store` and are not stored by these endpoints. Treat returned personal readings as private; do not publish or cache them. Return the requested one-off report to the user. Query-side display names never cause a saved-name write. ## Future fields | Field | Type / default | Meaning | | --- | --- | --- | | birthdate | required ISO date | Person's date | | current_date | ISO date / today UTC | Timeline reference date, equivalent to Current Date in the app | | southern | boolean / false | Southern hemisphere; backend applies its existing seasonal adjustment | | from, to | optional ISO dates | Output window; from includes midnight, to includes its entire UTC day. Filters the backend's existing timeline coverage | | aspects | array or comma-separated names / all | Aspect rows to return | | relationships | array or comma-separated names / all | Include matching legend relationships | | exclude_relationships | array or comma-separated names / none | Exclude matching legend relationships | | primary_only | boolean / false | Return only the site's primary-energy segments; primary status is always included as a column | | min_duration_days | number / 0 | Minimum full segment duration. Zero includes every short segment; there is no pixel-based chart thinning | | include_markets | boolean / false | Existing market milestones within the requested window | | include_spx | boolean / false | Recorded S&P 500 daily closes in the selected historical window; maximum ten years. Missing and future prices stay missing | | language | en or ko / en | Aspect labels; underlying timeline descriptions remain the source text | | format | json or markdown / json | Response representation | | query | optional text | Natural-language query with explicit ISO dates, interpreted by Jev | Available aspects: Actions & Movement; Body & Money; Heart & Love; Communication Style; Mind & Vision; Spirituality & Philosophy; Self Esteem & Inner Self; Nerves & Sensitivity; Popularity & Leadership; Wisdom & Vision; Emotions by Season. The result includes the query summary, timeline segment table, relationship legend, and birthdate elements when the existing backend permits them. Optional sections include market milestones and S&P closes. Segment rows carry the clipped visible window and original boundaries, full duration, period and personal elements, primary status, color, and interpretation. Missing premium fields remain unavailable. Zoom/pan correspond to `from` and `to`; legend visibility corresponds to relationship filters; row selection corresponds to `aspects`. PNG, screen height, opacity, logarithmic display, and full screen are visual controls; the table returns underlying values without needing those controls. The S&P table can be aligned by date to the segment ranges and colors. ### Full-feature structured example POST https://timeportal.pro/future/query.php Content-Type: application/json ```json {"birthdate":"1990-01-01","current_date":"2026-09-21","southern":false,"from":"2026-01-01","to":"2026-12-31","aspects":"all","primary_only":false,"min_duration_days":0,"include_markets":true,"include_spx":true,"language":"en","format":"markdown"} ``` GET example (all reading aspects, one year): https://timeportal.pro/future/query.php?birthdate=1990-01-01¤t_date=2026-09-21&from=2026-01-01&to=2026-12-31&include_markets=true&include_spx=true&format=markdown Jev example: `{"query":"For birthdate 1990-01-01 in the southern hemisphere, use reference date 2026-09-21. Show all features from 2026-01-01 through 2026-12-31, including S&P 500 and market milestones.","format":"markdown"}` Copyable user prompt: “Read https://timeportal.pro/future/llms.txt. Submit a full-feature query for my birthdate [YYYY-MM-DD], reference date [YYYY-MM-DD], hemisphere [north/south], and window [YYYY-MM-DD to YYYY-MM-DD]. Return the results as text tables, including all aspects, relationship explanations, and available market context. Ask me for any missing required information.”