A bilingual consumer product and developer platform: deterministic Bazi calculations support readable AI interpretation, while documented APIs and MCP tools make selected capabilities available to other applications and agents.
The experience starts from a reproducible Bazi calculation. True Solar Time is handled as part of input normalization so the same birth inputs produce the same chart foundation; the narrative can change, but the underlying system stays legible.
Calculation and interpretation are treated as separate layers.
The core result remains useful even when AI is unavailable.
The interface makes a complex tradition easier to approach without hiding the system underneath.
02
02 / Flow
Anonymous first, account when useful.
The product is designed to let someone begin without immediately creating an account. An optional account flow can add continuity, while the first interaction stays focused on getting to a meaningful result quickly.
Lower-friction entry for a first reading.
Clear boundaries around what is saved and why.
A path from one reading into a longer-lived personal tool.
03
03 / Information architecture
A daily starting point, room to explore.
Today, Explore, Portrait, and Me organize a growing set of readings and personal tools. Name readings, Tarot, compatibility, and other experiences share bilingual navigation and common input patterns, so additional capabilities do not each require an entirely new product shell.
Today creates a daily starting point.
Explore holds breadth without competing with the core flow.
Portrait gives the user a place to return to.
04
04 / AI behavior
AI expands the meaning, not the math.
OpenAI and Gemini integrations add interpretations around deterministic calculations, with provider fallback and structured response handling. Calculation-only tools remain separate from generated readings, so model availability does not redefine the underlying chart or blur which output came from a model.
Model output is optional, structured, and replaceable.
Fallback behavior keeps the product from depending on one generation request.
The system leaves room for attribution and privacy decisions to stay visible.
05
05 / Developer surface
Public tools and authenticated readings.
The public MCP endpoint exposes three deterministic, read-only tools without authentication or birth-data persistence. A separate API-key-protected MCP endpoint and versioned HTTP APIs provide richer readings, including compatibility, Tarot, and number energy. Authentication, AI use, quotas, and logging belong to those authenticated surfaces; the public endpoint's stateless promise does not describe the whole platform.
OpenAPI definitions and bilingual examples describe request and response contracts.
Input validation, usage limits, and explicit error responses support integrations.
Contract tests and live endpoint checks validate releases before integration examples are published.
Web product / applied AI