Remote Ziwei skill for agents

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.

Canonical Base URL
https://chatfate.life
The skill calls the same production runtime used by the website chat.
Invoke Endpoint
/api/fateclawd/invoke
Single non-streaming endpoint for Claude Code, Codex, OpenClaw-style wrappers, and custom clients.
Access Model
Anonymous access enabled
API keys stay optional until strict credit enforcement is turned on.

Install

Closest to the Cerul route: publish one hosted skill, one helper script, and let any agent install it with a single command.

Hosted install command

        

What the helper adds

Continuity
One local profile maps to one remote session by default. Follow-up questions keep context instead of re-reading from zero.
Reset
Use --new-session when you want a clean thread for the same birth profile.
Isolation
Use --profile review-2026 to keep multiple threads for the same chart without collisions.
Debug
Use --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.

1. First turn
Give birth date, birth hour, gender, and one real question. Example: “我是 1990-06-15 子时 男,先分析我的事业结构。”
2. Follow-up
After the first turn, users can ask follow-ups naturally: “那 2028 年呢?” “感情方面呢?” The helper keeps the same remote session by default.
3. Same chart, new topic
If the user wants a separate track for the same chart, use another --profile such as career, love, or family.
4. Clean restart
If the user explicitly wants a fresh consultation with no prior context bleed, add --new-session.
Direct helper usage examples
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

client_id
Stable identity for one local Claude/Codex installation. The helper generates and persists it automatically.
session_id
One remote conversation thread. Follow-up turns reuse it unless the caller asks for a reset.
profile
Local alias that lets the same chart have multiple isolated threads without collision.
user_id
Future real account identity. Not required for the current anonymous public route.

API Shape

Minimal request: birth data + question. The backend decides routing, planner, expert evidence, search steps, and final synthesis.

cURL

        

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.

OpenClaw install

        
OpenClaw config

        

Plugin assets

Hosted bundle
Quickstart
README
Configs
pro · lite

Request fields

birth_date
`YYYY-MM-DD`
birth_time_index
`0-12` where `0=子时`, `6=午时`, `12=早子时`
gender
`male` or `female`
question
Natural-language consultation question, not a rigid template.

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.