Compare free chart access, conversations, published calculation rules and agent integrations, with links to the official product pages.
Compare the workflow first
Both offer free BaZi charts without an account and publish calculation conventions. FateTell also presents FateBook, AnnualBook and AI conversations. Wenbu combines BaZi, I Ching, tarot and Zi Wei with an Agent that can read references. Your choice depends on whether you want a chart, a report or a conversation you can keep developing.
Public pages checked 2026-09-29. This comparison uses official sources; paid and signed-in features have not been tested.
Scroll sideways to see the full comparison. With a keyboard, focus the table and use the arrow keys.
Dimension
Wenbu
FateTell
Main experience
Four standalone tools and an Agent for charts, reference reading and reports
BaZi calculator, AI conversations, FateBook and AnnualBook
Free access
Free tools and journal; up to five AI readings and 12 Agent turns per guest or account daily, with network abuse controls and a site budget
Simple and Professional BaZi charts are free without an account; AI readings and FateBook are separate products
Calculation rules
Published engine versions, time conventions and draw methods
Calculator publishes solar-term, time-zone, solar-time and day-boundary conventions
Data and records
Birth details go to the server for calculation; guest records stay in the browser, with optional email sign-in for cloud history and JSON export
Calculator describes browser-based calculation and storage; app records and exports were not tested in an account
Your own AI assistant
Public MCP, REST, CLI and Skill with structured results
The pages reviewed do not describe equivalent interfaces; their absence has not been established
Making a choice
Either can be a starting point for a free BaZi chart. Try Wenbu if you want to move between traditions, consult references or use the results with your own assistant. Explore FateTell’s official pages for its report products. This comparison covers public pages, without paid account testing or a test of predictive accuracy.
How to read FateTell and Wenbu charts when the birth hour is unknown
Inputs, report products and integrations: three scenarios and a checklist
Choose by task. If you want a free BaZi chart and a clear view of inputs and day-boundary conventions, both FateTell's calculator and Wenbu state that they take the Gregorian date, the local clock time at the birthplace and a time zone, and both publish day-boundary rules, so either can be a starting point. If you want a written report product, FateTell's overview presents FateBook and Book of Abundance, while Wenbu's pages centre on tools, references and an Agent. If you want to hand chart results to your own AI assistant, Wenbu publishes MCP, REST, CLI and Skill with structured output, and FateTell's overview also mentions FateTell MCP, so a page that does not describe an interface is not proof that none exists. Before choosing, align the same birth details and settings on both sides, and note that this page covers public pages only: paid and signed-in features were not tested and predictive accuracy was not compared.
Align inputs first: Gregorian date, local clock time, time zone and day-boundary setting.
A report product and a charting tool are different layers; decide whether you want a chart or a written reading.
A page that does not describe an interface only shows that page does not cover it.
From task to tool: a decision flow
01Name the task
A chart, a written report, or results inside your own assistant.
02Align inputs
Record the Gregorian date, local clock time, time zone, day boundary and true-solar-time setting.
03Confirm delivery
Check whether you get a chart, a report or structured output, and whether it can be exported.
04Mark what is unverified
Write not verified for features a page does not describe; do not infer either presence or absence.
Identify the task, align the input settings, then confirm delivery and record keeping. If a page does not state something, mark it not verified rather than denying it.
Inputs and conventions: make two charts comparable
FateTell's calculator says to use the local clock time recorded at the birthplace, and asks for a Gregorian date, a time and a birthplace time zone; it also offers a precise location for true solar time and an option for readers who do not know their birth time. Wenbu's methodology takes a Gregorian date, the local clock time and an IANA time zone or explicit UTC offset, defaults to a midnight day boundary with an optional 23:00 Zi boundary, and omits the hour pillar when the birth time is unknown. Both publish these conventions, which is exactly where a comparison should start.
Matching published conventions does not guarantee identical charts. Whether true solar time is on, which day boundary is chosen and how an unknown time is handled can change the day or hour pillar. Record the settings alongside the four pillars rather than comparing results alone. Reproducible calculation also does not mean an interpretation has been scientifically validated.
Report products and integrations: two kinds of delivery
FateTell's overview places the BaZi chart alongside AI conversations and presents FateBook and Book of Abundance, describing coverage of wealth, emotions, health and learning, plus century and decade trends. These are vendor statements about product positioning; this page did not buy or sign in to test them and cannot judge report quality. Wenbu's public pages instead emphasise four tools, an Agent that can read original references, and MCP, REST, CLI and Skill integrations, with MCP returning structured results and calculation conventions.
On integrations, state the boundary clearly: Wenbu publishes an MCP tool list and output structure, and FateTell's overview also mentions FateTell MCP for connecting charting and analysis tools to AI assistants. So a page that does not describe an API only shows that page does not cover it; it is not evidence the product lacks one. If integration is a hard requirement, read each vendor's current integration documentation rather than inferring from this page.
Scenario one, a learner: you want to understand why the same birth moment can produce different day pillars. Read Wenbu's methodology on day boundaries and true solar time, then compare FateTell's published settings and note where the difference comes from. Scenario two, a report reader: you want a long written reading, so start with FateTell's official description of FateBook and check whether it covers the topics you care about. Scenario three, a developer: you want charting inside your own assistant, so read Wenbu's MCP tools and output notes, or check FateTell's MCP page if you lean that way.
Fill the worksheet in four columns: task (chart, report or integration), input settings (date, time, time zone, day boundary, true solar time), delivery form (chart, written report, structured JSON) and record keeping (browser local, account cloud, export). Write only what a page states explicitly, and mark blanks as not verified rather than filling them with guesses.
Hypothetical example: checking one birth record in two places
This is a fictional exercise. It does not describe a real person and is not a reading. Suppose the birth details are 16 August 2000, 03:30, time zone Asia/Shanghai, with the default midnight day boundary.
First, enter the Gregorian date, local clock time and birthplace time zone in FateTell's calculator, and note whether true solar time is on.
Second, chart the same inputs in Wenbu, which defaults to a midnight day boundary, and record the four pillars and the conventions used.
Third, if the day or hour pillar differs, check the day-boundary option, true solar time and unknown-time handling before deciding anyone is wrong.
Fourth, copy the settings and results into the worksheet and mark blanks as not verified.
The observable outcome is that you can name which setting explains the difference, rather than declaring a winner. This exercise does not assess predictive accuracy.
If FateTell's page does not describe an API, does that mean there is none?
No. FateTell's overview actually mentions FateTell MCP for connecting charting and analysis tools to AI assistants. A page that omits an interface only shows that page does not cover it; check the current integration documentation before concluding anything.
The day pillars differ between two charts. Did one calculate it wrongly?
Not necessarily. The day-boundary convention, whether true solar time is on, and whether the birth time is known can all change the day or hour pillar. Compare settings item by item first; this page did not compare predictive accuracy.
FateTell's overview presents FateBook and Book of Abundance as report products, which makes it a reasonable place to start reading. This page did not purchase or sign in to test them, so rely on the official description for content.
The rule for when a day starts, which decides which day pillar a birth moment belongs to. Wenbu defaults to midnight and offers an optional 23:00 Zi boundary; different settings can change the day pillar.
Clock time adjusted approximately for longitude and the equation of time. Wenbu describes its formula as an approximation and suggests comparing settings near a day or hour boundary.
A protocol that lets AI assistants call external tools. Wenbu publishes its MCP tool list and structured output; FateTell's overview also mentions FateTell MCP.
FateTell's calculator asks for the local clock time at the birthplace, a Gregorian date and a birthplace time zone, with an optional true-solar-time setting.
Use the local clock time recorded at your birthplace.
Wenbu drafted and checked this article in Codex. The source list records the scope of the review.
Current complete zh canonical article ↗Current public original and earlier additions; add substantial coverage without repeating or replacing them. · 2026-10-30 · Fetched text
Current complete en canonical article ↗Current public original and earlier additions; add substantial coverage without repeating or replacing them. · 2026-10-30 · Fetched text
Wenbu · daily card ↗Current first-party product UI; not a personal forecast · 2026-10-30 · Fetched text
Wenbu · versioned public capabilities ↗First-party current tool, convention and privacy contract; not external endorsement or predictive validation · 2026-10-30 · Fetched text
Chart the same fictional birth details once
Enter the fictional date, time and time zone in Wenbu's charting tool, record the four pillars and conventions used, then compare settings item by item with the other page and mark blanks as not verified.
When you know the date but lack the birth time, FateTell’s calculator says it uses local noon and labels the hour pillar as assumed. Wenbu uses local noon for a provisional year and month, and leaves the hour pillar empty. Use FateTell’s documentation if you want to study an explicitly assumed fourth pillar. Use Wenbu’s three-pillar result if you want the missing time to remain visible. Keep the original note that the birth time is unknown.
FateTell’s public calculator says it uses local noon for an unknown time, skips solar correction and marks the hour as assumed. A learner can inspect the fourth column with that label. Keep the label and time zone with any screenshot of the hour pillar.
For a date-only record, Wenbu offers Time unknown — use three pillars. In the checked response, the hour item stays in the pillars array with value set to null. So is calendar.instant. The web result describes the hour as Not inferred.
The Wenbu calculation for September 16, 2025 gives Yi Si, Yi You and Wu Zi, with an empty hour. The FateTell column uses its public documentation, checked November 14, 2026. The exact FateTell stem and branch for the sample remain unverified.
Record where the birth information came from. If you verify the time later, retain the original unknown status and add the verified local time and zone in a new entry. On a solar-term date, compare the new year and month pillars with the provisional result.
I have a time range. Can I use its midpoint to make the charts agree?
Keep the recorded range. If you want to compare samples, mark every assumed time and record the date and zone. Check both sides of a relevant calendar boundary.
Should I replace the old entry if I find the actual time?
Record when and where you verified the time. Recalculate with that clock reading, and retain the original date-only record and settings so someone can trace the correction.
Wenbu drafted and checked this article in Codex. The source list records the scope of the review.
Current complete zh canonical article ↗Current public original and earlier additions; add substantial coverage without repeating or replacing them. · 2026-11-14 · Fetched text
Current complete en canonical article ↗Current public original and earlier additions; add substantial coverage without repeating or replacing them. · 2026-11-14 · Fetched text
Wenbu · versioned public capabilities ↗First-party current tool, convention and privacy contract; not external endorsement or predictive validation · 2026-11-14 · Fetched text
Wenbu · daily card ↗Current first-party product UI; not a personal forecast · 2026-11-14 · Fetched text
Check a date without a birth time in Wenbu
Enter the fictional date and choose unknown time to inspect the three pillars, empty hour and warning.