Give your agent a fate-reading tool, not a fixed script.
ChatFate exposes Ziwei consultation as a remote skill. Your website and external agents hit the same backend, so routing, expert rules, search, memory, credits, and future billing all stay on the server side.
Install
Closest to the Cerul route: publish one hosted skill, one helper script, and let any agent install it with a single command.
What the helper adds
--new-session when you want a clean thread for the same birth profile.--profile review-2026 to keep multiple threads for the same chart without collisions.--json when you need the raw server payload plus local session metadata for inspection.How people should use it
There are two layers: natural conversation for normal users, and explicit thread controls for advanced users or debugging.
--profile such as career, love, or family.--new-session.python3 scripts/chatfate_query.py \ --birth-date 1990-06-15 \ --birth-time 子时 \ --gender male \ --question "分析我的事业结构" python3 scripts/chatfate_query.py \ --birth-date 1990-06-15 \ --birth-time 子时 \ --gender male \ --question "那未来三年的财运呢" python3 scripts/chatfate_query.py \ --birth-date 1990-06-15 \ --birth-time 子时 \ --gender male \ --profile love \ --new-session \ --question "单独看未来十年的感情走势"
Identity model
API Shape
Minimal request: birth data + question. The backend decides routing, planner, expert evidence, search steps, and final synthesis.
Suggested prompts
- 分析我的事业
- 回溯一下前十年
- 我哪一年财运最好
- 看看我的感情与婚姻模式
- 分析未来十年的家庭与房产走势
- 验证一下我 2020 年的事业变化
OpenClaw Plugin
If the host understands OpenClaw plugins rather than `SKILL.md`, use the packaged plugin bundle. It still hits the same ChatFate runtime.
Plugin assets
Request fields
Agent route
- Website chat and external skills call the same runtime.
- Credits and API keys stay on the server, not in the prompt layer.
- Server-side memory remains available through `session_id / client_id / anonymous_id`.
- The public website is the product. The skill is a thin distribution surface.