{"version":1,"scope":"full","truncated":false,"id":"editorial-compare-fatetell-update","url":"https://wenbu.app/en/compare/fatetell/","locale":"en","revision":"09ec57b7924af753ce323578af8f04cc28cc94d9d018ec44dd01df007d8c9bd6","updated":"2026-11-14T01:09:34.125Z","content":"# Wenbu or FateTell: what do you want to do?\n\nCompare free chart access, conversations, published calculation rules and agent integrations, with links to the official product pages.\n\nCanonical: https://wenbu.app/en/compare/fatetell/\n\nPublic pages checked 2026-09-29. This comparison uses official sources; paid and signed-in features have not been tested.\n\nAuthorship: Wenbu · AI-assisted editorial. Listed sources have not been fetched again by this read; predictive accuracy was not compared.\n\n## Compare the workflow first\n\nBoth 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.\n\nPublic pages checked 2026-09-29. This comparison uses official sources; paid and signed-in features have not been tested.\n\n## Product comparison\n\n| Dimension | Wenbu | FateTell |\n| --- | --- | --- |\n| Main experience | Four standalone tools and an Agent for charts, reference reading and reports | BaZi calculator, AI conversations, FateBook and AnnualBook |\n| 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 |\n| Calculation rules | Published engine versions, time conventions and draw methods | Calculator publishes solar-term, time-zone, solar-time and day-boundary conventions |\n| 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 |\n| 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 |\n\n## Making a choice\n\nEither 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.\n\n## Sources and their scope\n\n- [FateTell · product overview](https://fatetell.com/)\n- [FateTell · free BaZi calculator and calculation rules](https://fatetell.com/bazi-calculator)\n- [Wenbu · Methodology](https://wenbu.app/en/methodology/)\n- [Wenbu · Free-use policy](https://wenbu.app/en/free/)\n\n[Find your starting point](https://wenbu.app/en/learn/choose-a-tool/)\n\n---\n\n# Inputs, report products and integrations: three scenarios and a checklist\n\nA focused addition comparing the chart inputs, published conventions, report products and integration notes on FateTell's and Wenbu's public pages, with three reader scenarios and a short worksheet. Paid and signed-in features were not tested, and predictive accuracy was not compared.\n\nUpdated: 2026-10-30 · Wenbu AI-assisted editorial\n\nChoose 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.\n\n[FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/) · [FateTell · official overview](https://fatetell.com/) · [Wenbu · agent integrations](https://wenbu.app/agents/)\n\n- Align inputs first: Gregorian date, local clock time, time zone and day-boundary setting.\n\n- A report product and a charting tool are different layers; decide whether you want a chart or a written reading.\n\n- A page that does not describe an interface only shows that page does not cover it.\n\n## From task to tool: a decision flow\n\n1. **Name the task** — A chart, a written report, or results inside your own assistant.\n\n2. **Align inputs** — Record the Gregorian date, local clock time, time zone, day boundary and true-solar-time setting.\n\n3. **Confirm delivery** — Check whether you get a chart, a report or structured output, and whether it can be exported.\n\n4. **Mark what is unverified** — Write not verified for features a page does not describe; do not infer either presence or absence.\n\nIdentify 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.\n\n[Wenbu · calculation conventions](https://wenbu.app/methodology/) · [FateTell · official overview](https://fatetell.com/) · [Wenbu · agent integrations](https://wenbu.app/agents/)\n\n## Inputs and conventions: make two charts comparable\n\nFateTell'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.\n\nMatching 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.\n\n[FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Report products and integrations: two kinds of delivery\n\nFateTell'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.\n\nOn 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.\n\n[FateTell · official overview](https://fatetell.com/) · [Wenbu · agent integrations](https://wenbu.app/agents/) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Three reader scenarios and a short worksheet\n\nScenario 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.\n\nFill 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.\n\n[Wenbu · calculation conventions](https://wenbu.app/methodology/) · [FateTell · official overview](https://fatetell.com/) · [Wenbu · agent integrations](https://wenbu.app/agents/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator)\n\n## Checking both public pages by task\n\n| Check | Wenbu public pages | FateTell public pages |\n| --- | --- | --- |\n| Chart inputs | Gregorian date, local clock time, IANA zone or UTC offset | Gregorian date, local clock time, birthplace time zone, optional precise location |\n| Day boundary and solar time | Midnight default, optional 23:00; true solar time as an approximation | True-solar-time option described as adjusting for longitude, historical zone and equation of time |\n| Report products | Pages emphasise tools, references and an Agent | Overview presents FateBook and Book of Abundance |\n| Integration notes | MCP, REST, CLI and Skill published | Overview mentions FateTell MCP |\n| What was tested here | Paid and signed-in features not tested | Report products not purchased or tested |\n\n[Wenbu · calculation conventions](https://wenbu.app/methodology/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [FateTell · official overview](https://fatetell.com/) · [Wenbu · agent integrations](https://wenbu.app/agents/)\n\n## Hypothetical example: checking one birth record in two places\n\nThis 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.\n\n1. First, enter the Gregorian date, local clock time and birthplace time zone in FateTell's calculator, and note whether true solar time is on.\n\n2. Second, chart the same inputs in Wenbu, which defaults to a midnight day boundary, and record the four pillars and the conventions used.\n\n3. 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.\n\n4. Fourth, copy the settings and results into the worksheet and mark blanks as not verified.\n\nThe observable outcome is that you can name which setting explains the difference, rather than declaring a winner. This exercise does not assess predictive accuracy.\n\n[FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## FAQ\n\n### If FateTell's page does not describe an API, does that mean there is none?\n\nNo. 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.\n\n[FateTell · official overview](https://fatetell.com/)\n\n### The day pillars differ between two charts. Did one calculate it wrongly?\n\nNot 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.\n\n[Wenbu · calculation conventions](https://wenbu.app/methodology/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator)\n\n### Which side should I look at for a written report?\n\nFateTell'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.\n\n[FateTell · official overview](https://fatetell.com/)\n\n## Glossary\n\n- **Day-boundary convention**: 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. [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n- **True solar time**: 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. [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n- **MCP**: 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. [Wenbu · agent integrations](https://wenbu.app/agents/) · [FateTell · official overview](https://fatetell.com/)\n\n## Evidence notes\n\n- 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.” (fact); [FateTell · official calculator](https://fatetell.com/bazi-calculator)\n\n- Wenbu publishes its BaZi input range, time-zone format and default day boundary so results can be checked. — “默认在 00:00 换日” (fact); [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n- FateTell's overview presents report products and also mentions FateTell MCP. — “FateTell MCP” (fact); [FateTell · official overview](https://fatetell.com/)\n\n## Sources\n\n- [Current complete zh canonical article](https://wenbu.app/knowledge/zh/compare-fatetell.md) — Current public original and earlier additions; add substantial coverage without repeating or replacing them.; fetched 2026-10-30T01:00:35.983Z; complete response\n\n- [Current complete en canonical article](https://wenbu.app/knowledge/en/compare-fatetell.md) — Current public original and earlier additions; add substantial coverage without repeating or replacing them.; fetched 2026-10-30T01:00:36.853Z; complete response\n\n- [Wenbu · current free access](https://wenbu.app/free/) — First-party access and quota documentation; fetched 2026-10-30T01:00:37.020Z; complete response\n\n- [Wenbu · calculation conventions](https://wenbu.app/methodology/) — First-party implementation; not evidence of predictive accuracy; fetched 2026-10-30T01:00:37.023Z; complete response\n\n- [Wenbu · agent integrations](https://wenbu.app/agents/) — Current first-party product documentation; fetched 2026-10-30T01:00:37.037Z; complete response\n\n- [FateTell · official overview](https://fatetell.com/) — Vendor statements; public page only, no paid account testing; fetched 2026-10-30T01:00:38.530Z; excerpt\n\n- [FateTell · official calculator](https://fatetell.com/bazi-calculator) — Vendor calculator documentation; fetched 2026-10-30T01:00:38.530Z; excerpt\n\n- [Wenbu · daily card](https://wenbu.app/daily/) — Current first-party product UI; not a personal forecast; fetched 2026-10-30T01:00:37.023Z; complete response\n\n- [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) — First-party current tool, convention and privacy contract; not external endorsement or predictive validation; fetched 2026-10-30T01:00:37.023Z; complete response\n\n[Chart the same fictional birth details once](https://wenbu.app/en/bazi/)\n\n# How to read FateTell and Wenbu charts when the birth hour is unknown\n\nCompare a documented assumed hour with a verified omitted hour, and learn how to preserve the precision of a date-only record.\n\nUpdated: 2026-11-14 · Wenbu AI-assisted editorial\n\nWhen 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.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n- Write “date known, time unknown” next to both records.\n\n- Keep the assumption label from FateTell or the empty hour from Wenbu with the original inputs.\n\n- If you find a reliable time later, recalculate from it and record why the first result was provisional.\n\n## Keep the record and calculation assumption in separate fields\n\n1. **Copy the known inputs** — Record the Gregorian date, the birthplace time zone and that the time is unknown.\n\n2. **Add the output convention** — FateTell documents a noon assumption. The checked Wenbu result has an empty hour.\n\n3. **Keep a place for new evidence** — When you verify the local clock time, recalculate using the recorded zone and settings.\n\nA later reader needs to see what the source supplied and what the calculator assumed.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Decide what the next reader needs to see\n\nFateTell’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.\n\nFor 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.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Record the substitute clock time on its own line\n\nThe 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.\n\nRecord 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.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Four items to preserve for review\n\n| Check | FateTell calculator documentation | Wenbu calculation and documentation |\n| --- | --- | --- |\n| Missing input | Birth time is unknown | Birth time is unknown |\n| Temporary time | Local noon, solar correction skipped | Local noon for provisional year and month |\n| How to record the hour | Keep the assumed label | The hour value is null |\n| Review evidence | Retain the label and calculation settings | Retain the date, empty field and solar-term warning |\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Annotate a date-only record\n\nThe exercise uses a fictional birth date of September 16, 2025 and the Shanghai time zone. No birth time is provided.\n\n1. In Wenbu, enter the date and Asia/Shanghai. Choose the unknown-time option, use the midnight boundary and leave solar correction off.\n\n2. Check the Yi Si, Yi You and Wu Zi pillars and the empty hour. Mark the record “date known, birth time unknown” and save the warning.\n\n3. Open FateTell’s calculator documentation and find the rule for an unknown time. Add “local noon, hour assumed” to the other column.\n\n4. When sharing the record for review, give the inputs, the settings and the outputs their own fields. Make the missing detail visible.\n\nKeep “birth time unknown” on both records. The assumption label or empty field makes the next piece of evidence easy to identify.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## FAQ\n\n### I have a time range. Can I use its midpoint to make the charts agree?\n\nKeep 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.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n### Should I replace the old entry if I find the actual time?\n\nRecord 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.\n\n[FateTell · official overview](https://fatetell.com/) · [FateTell · official calculator](https://fatetell.com/bazi-calculator) · [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Glossary\n\n- **Assumed hour pillar**: The pillar obtained from a declared substitute clock time. Record that condition beside the stem and branch. [FateTell · official calculator](https://fatetell.com/bazi-calculator)\n\n- **Empty hour pillar**: Wenbu leaves the hour value empty when the date is supplied without a birth time. [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Evidence notes\n\n- FateTell’s home calculator offers an unknown birth time option. — “I don’t know my birth time” (fact); [FateTell · official overview](https://fatetell.com/)\n\n- FateTell’s calculator documentation labels an hour based on assumed time. — “marks the hour as assumed” (fact); [FateTell · official calculator](https://fatetell.com/bazi-calculator)\n\n- Wenbu leaves out the hour pillar and uses local noon provisionally. — “出生时间未知时不生成时柱，年、月柱以当地中午暂定” (fact); [Wenbu · calculation conventions](https://wenbu.app/methodology/)\n\n## Sources\n\n- [Current complete zh canonical article](https://wenbu.app/knowledge/zh/compare-fatetell.md) — Current public original and earlier additions; add substantial coverage without repeating or replacing them.; fetched 2026-11-14T00:56:40.319Z; complete response\n\n- [Current complete en canonical article](https://wenbu.app/knowledge/en/compare-fatetell.md) — Current public original and earlier additions; add substantial coverage without repeating or replacing them.; fetched 2026-11-14T00:56:40.348Z; complete response\n\n- [FateTell · official overview](https://fatetell.com/) — Vendor statements; public page only, no paid account testing; fetched 2026-11-14T00:56:43.075Z; excerpt\n\n- [FateTell · official calculator](https://fatetell.com/bazi-calculator) — Vendor calculator documentation; fetched 2026-11-14T00:56:42.892Z; excerpt\n\n- [Wenbu · calculation conventions](https://wenbu.app/methodology/) — First-party implementation; not evidence of predictive accuracy; fetched 2026-11-14T00:56:40.404Z; complete response\n\n- [Wenbu · versioned public capabilities](https://wenbu.app/capabilities.json) — First-party current tool, convention and privacy contract; not external endorsement or predictive validation; fetched 2026-11-14T00:56:40.422Z; complete response\n\n- [Wenbu · daily card](https://wenbu.app/daily/) — Current first-party product UI; not a personal forecast; fetched 2026-11-14T00:56:40.411Z; complete response\n\n[Check a date without a birth time in Wenbu](https://wenbu.app/en/bazi/)","edition":{"title":"How to read FateTell and Wenbu charts when the birth hour is unknown","description":"Compare a documented assumed hour with a verified omitted hour, and learn how to preserve the precision of a date-only record.","answer":"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.","answerSourceIds":["fatetell","fatetellCalculator","methods"],"evidence":[{"claim":"FateTell’s home calculator offers an unknown birth time option.","sourceId":"fatetell","quote":"I don’t know my birth time","kind":"fact"},{"claim":"FateTell’s calculator documentation labels an hour based on assumed time.","sourceId":"fatetellCalculator","quote":"marks the hour as assumed","kind":"fact"},{"claim":"Wenbu leaves out the hour pillar and uses local noon provisionally.","sourceId":"methods","quote":"出生时间未知时不生成时柱，年、月柱以当地中午暂定","kind":"fact"}],"takeaways":["Write “date known, time unknown” next to both records.","Keep the assumption label from FateTell or the empty hour from Wenbu with the original inputs.","If you find a reliable time later, recalculate from it and record why the first result was provisional."],"sections":[{"heading":"Decide what the next reader needs to see","paragraphs":["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."],"sourceIds":["fatetell","fatetellCalculator","methods"]},{"heading":"Record the substitute clock time on its own line","paragraphs":["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."],"sourceIds":["fatetell","fatetellCalculator","methods"]}],"figure":{"title":"Keep the record and calculation assumption in separate fields","caption":"A later reader needs to see what the source supplied and what the calculator assumed.","sourceIds":["fatetell","fatetellCalculator","methods"],"steps":[{"label":"Copy the known inputs","detail":"Record the Gregorian date, the birthplace time zone and that the time is unknown."},{"label":"Add the output convention","detail":"FateTell documents a noon assumption. The checked Wenbu result has an empty hour."},{"label":"Keep a place for new evidence","detail":"When you verify the local clock time, recalculate using the recorded zone and settings."}]},"table":{"title":"Four items to preserve for review","columns":["Check","FateTell calculator documentation","Wenbu calculation and documentation"],"rows":[["Missing input","Birth time is unknown","Birth time is unknown"],["Temporary time","Local noon, solar correction skipped","Local noon for provisional year and month"],["How to record the hour","Keep the assumed label","The hour value is null"],["Review evidence","Retain the label and calculation settings","Retain the date, empty field and solar-term warning"]],"sourceIds":["fatetell","fatetellCalculator","methods"]},"example":{"title":"Annotate a date-only record","intro":"The exercise uses a fictional birth date of September 16, 2025 and the Shanghai time zone. No birth time is provided.","steps":["In Wenbu, enter the date and Asia/Shanghai. Choose the unknown-time option, use the midnight boundary and leave solar correction off.","Check the Yi Si, Yi You and Wu Zi pillars and the empty hour. Mark the record “date known, birth time unknown” and save the warning.","Open FateTell’s calculator documentation and find the rule for an unknown time. Add “local noon, hour assumed” to the other column.","When sharing the record for review, give the inputs, the settings and the outputs their own fields. Make the missing detail visible."],"conclusion":"Keep “birth time unknown” on both records. The assumption label or empty field makes the next piece of evidence easy to identify.","sourceIds":["fatetell","fatetellCalculator","methods"]},"faq":[{"question":"I have a time range. Can I use its midpoint to make the charts agree?","answer":"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.","sourceIds":["fatetell","fatetellCalculator","methods"]},{"question":"Should I replace the old entry if I find the actual time?","answer":"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.","sourceIds":["fatetell","fatetellCalculator","methods"]}],"glossary":[{"term":"Assumed hour pillar","definition":"The pillar obtained from a declared substitute clock time. Record that condition beside the stem and branch.","sourceIds":["fatetellCalculator"]},{"term":"Empty hour pillar","definition":"Wenbu leaves the hour value empty when the date is supplied without a birth time.","sourceIds":["methods"]}],"cta":{"label":"Check a date without a birth time in Wenbu","reason":"Enter the fictional date and choose unknown time to inspect the three pillars, empty hour and warning."}},"editionScope":"addition","sources":[{"id":"current-zh","title":"Current complete zh canonical article","url":"https://wenbu.app/knowledge/zh/compare-fatetell.md","role":"Current public original and earlier additions; add substantial coverage without repeating or replacing them.","fetchedAt":"2026-11-14T00:56:40.319Z","hash":"bac1f4d9467c5955454be6cf38ab38cec2fa7776305e018c34671d181606f587","truncated":false},{"id":"current-en","title":"Current complete en canonical article","url":"https://wenbu.app/knowledge/en/compare-fatetell.md","role":"Current public original and earlier additions; add substantial coverage without repeating or replacing them.","fetchedAt":"2026-11-14T00:56:40.348Z","hash":"eace77fa7c7e18a8e6df7c61cdb20a6ffccfb3ff987809d9b41dd39fa3084572","truncated":false},{"id":"fatetell","title":"FateTell · official overview","url":"https://fatetell.com/","role":"Vendor statements; public page only, no paid account testing","fetchedAt":"2026-11-14T00:56:43.075Z","hash":"a108e81d5841782cc54eb4caf4ee19ef1fa7388dc39581c8ba76ac21009004fe","truncated":true},{"id":"fatetellCalculator","title":"FateTell · official calculator","url":"https://fatetell.com/bazi-calculator","role":"Vendor calculator documentation","fetchedAt":"2026-11-14T00:56:42.892Z","hash":"3c674df502b4681344e671d69e7f7519a8f506fb4007f7ac1a0f40c80c3a24b0","truncated":true},{"id":"methods","title":"Wenbu · calculation conventions","url":"https://wenbu.app/methodology/","role":"First-party implementation; not evidence of predictive accuracy","fetchedAt":"2026-11-14T00:56:40.404Z","hash":"21a7f433eb1571ce23e4c4e96f09d0da54c2f9030469f4b8ecfc294a13344de5","truncated":false},{"id":"capabilities","title":"Wenbu · versioned public capabilities","url":"https://wenbu.app/capabilities.json","role":"First-party current tool, convention and privacy contract; not external endorsement or predictive validation","fetchedAt":"2026-11-14T00:56:40.422Z","hash":"557485b2f5513f237e8258ecf9d0a1fbbf5aa19a30c726f9199bf3817e021546","truncated":false},{"id":"daily","title":"Wenbu · daily card","url":"https://wenbu.app/daily/","role":"Current first-party product UI; not a personal forecast","fetchedAt":"2026-11-14T00:56:40.411Z","hash":"d0aa0ed4d2a4b181cb0f77100aa04017e4d946adc62304495a3ca39a674020cb","truncated":false}],"previousAdditions":[{"zh":{"title":"排盘输入、报告产品与接入：三个场景和一张核对表","description":"补充比较 FateTell 与问卜公开页面写明的排盘输入、计算约定、报告产品与接入说明，并用三个读者场景和一张工作表帮助选择。未登录测试付费功能，也未比较预测准确率。","answer":"先按任务选：若你要的是免费排一张八字盘并核对输入与换日约定，FateTell 计算器与问卜都写明使用出生地当地钟表时间、公历日期和时区，也都公开换日等规则，两者都可作入口。若你要的是成体系的书面报告，FateTell 官方页介绍 FateBook 与 Book of Abundance 等报告产品，问卜页面则把重点放在工具、资料与 Agent 上。若你要把排盘结果交给自己的 AI 助手，问卜公开了 MCP、REST、CLI 与 Skill 及结构化输出；FateTell 概览页也提到 FateTell MCP，因此不能因为某一页没写接口就断定它没有。选择前请核对同一出生资料在两处的输入设置，并记住本页只核对公开页面，未测试登录后或付费体验，也未比较预测准确率。","answerSourceIds":["fatetellCalculator","methods","fatetell","agents"],"evidence":[{"claim":"FateTell 计算器要求输入出生地当地钟表时间、公历日期与出生地时区，并可选真太阳时。","sourceId":"fatetellCalculator","quote":"Use the local clock time recorded at your birthplace.","kind":"fact"},{"claim":"问卜公开八字输入范围、时区写法与默认换日约定，便于核对两份结果。","sourceId":"methods","quote":"默认在 00:00 换日","kind":"fact"},{"claim":"FateTell 概览页介绍 FateBook 等报告产品，并提到 FateTell MCP。","sourceId":"fatetell","quote":"FateTell MCP","kind":"fact"}],"takeaways":["排盘前先统一输入：公历日期、当地钟表时间、时区与换日设置。","报告产品与排盘工具是不同层次，先确认你要的是盘还是成文解读。","页面未描述某接口不等于该接口不存在，只能说明该页没有覆盖。"],"sections":[{"heading":"输入与约定：先让两份盘可比","paragraphs":["FateTell 计算器写明使用出生地记录的当地钟表时间，输入公历日期、时刻与出生地时区，并可选择精确地点以使用真太阳时；它还提供「不知道出生时间」的选项。问卜的计算说明同样以公历日期、出生地钟表时间和 IANA 时区或明确 UTC 偏移为输入，默认 00:00 换日，也可选 23:00 子初换日，出生时间未知时不生成时柱。两边都把约定写在页面上，这正是核对两份结果时该先看的部分。","需要提醒的是，公开约定一致不代表排出的盘必然相同。真太阳时是否开启、换日选项、未知时间如何处理，都会改变日柱或时柱。比较时请把同一组设置记录下来，而不是只看四柱结果。计算能按约定复现，也不等于解释已获科学验证。"],"sourceIds":["fatetellCalculator","methods"]},{"heading":"报告产品与接入方式：两种不同的交付","paragraphs":["FateTell 概览页把八字盘与 AI 对话放在一起，并介绍 FateBook 与 Book of Abundance 等报告产品，描述其覆盖财富、情感、健康与学习等领域，以及世纪与十年运势概览。这些是厂商自述的产品定位，本页没有购买或登录测试，无法评价报告内容质量。问卜的公开页面则强调四种工具、可查阅原创资料的 Agent，以及 MCP、REST、CLI 与 Skill 等接入方式，MCP 返回结构化结果与计算约定。","关于接入，需要说清边界：问卜公开了 MCP 工具清单与输出结构；FateTell 概览页也提到 FateTell MCP，可把排盘与分析工具接到 AI 助手。因此「某页没写 API」只能说明该页未覆盖，不能据此认定产品没有接口。若接入是你的硬性需求，应分别查阅两家当前的接入文档，而不是依据本页推断。"],"sourceIds":["fatetell","agents","methods"]},{"heading":"三个读者场景与一张核对表","paragraphs":["场景一，学习者：想弄懂为什么同一出生时刻会排出不同日柱。可先用问卜的计算说明读换日与真太阳时规则，再用 FateTell 计算器对照其公开设置，记录差异来源。场景二，报告读者：想要一份成文的长篇解读，可先看 FateTell 对 FateBook 的官方介绍，确认它是否覆盖你关心的主题。场景三，开发者：想把排盘接进自己的助手，可先读问卜的 MCP 工具与输出说明；若倾向 FateTell，则查其 MCP 页面确认能力范围。","工作表可按四栏填写：任务（排盘／报告／接入）、输入设置（日期、时刻、时区、换日、真太阳时）、交付形式（盘面、成文报告、结构化 JSON）、记录方式（浏览器本地、账号云端、导出）。每栏只写页面明确写出的内容，空白处标「未核实」，不要用推测填补。"],"sourceIds":["methods","fatetell","agents","fatetellCalculator"]}],"figure":{"title":"从任务到工具的判断流程","caption":"先确定任务类型，再核对输入设置，最后确认交付与记录方式；任何一步页面未写明，都标为未核实而非否定。","sourceIds":["methods","fatetell","agents"],"steps":[{"label":"确定任务","detail":"排盘、读成文报告，还是把结果接入自己的助手。"},{"label":"统一输入","detail":"记录公历日期、当地钟表时间、时区、换日与真太阳时设置。"},{"label":"核对交付","detail":"确认得到的是盘面、报告还是结构化结果，以及能否导出保存。"},{"label":"标注未核实","detail":"页面未描述的功能写为未核实，不推断其存在或不存在。"}]},"table":{"title":"按任务核对两家公开页面","columns":["核对项","问卜公开页面","FateTell 公开页面"],"rows":[["排盘输入","公历日期、当地钟表时间、IANA 时区或 UTC 偏移","公历日期、当地钟表时间、出生地时区，可选精确地点"],["换日与太阳时","默认 00:00 换日，可选 23:00；真太阳时为近似校正","提供真太阳时选项，说明按经度、历史时区与均时差调整"],["报告产品","页面侧重工具、资料与 Agent","概览页介绍 FateBook 与 Book of Abundance"],["接入说明","公开 MCP、REST、CLI 与 Skill","概览页提到 FateTell MCP"],["本次测试范围","未测试付费与登录功能","未购买或登录测试报告产品"]],"sourceIds":["methods","fatetellCalculator","fatetell","agents"]},"example":{"title":"假设示例：同一出生资料的两处核对","intro":"以下为虚构练习，不对应任何真实个人，也不构成命理结论。假设某人的出生资料为 2000 年 8 月 16 日 03:30，时区 Asia/Shanghai，换日采用默认 00:00。","steps":["第一步，在 FateTell 计算器填入公历日期、当地钟表时间与出生地时区，记录是否开启真太阳时。","第二步，在问卜以同一组输入排盘，默认 00:00 换日，记录四柱与所用约定。","第三步，若两处日柱或时柱不同，先检查换日选项、真太阳时与未知时间处理，而不是直接判断谁算错。","第四步，把设置与结果抄进工作表，空白项标「未核实」。"],"conclusion":"可观察的结果是：你能说清差异来自哪一项设置，而不是得到一个「谁更准」的结论。本练习不评价预测准确率。","sourceIds":["fatetellCalculator","methods"]},"faq":[{"question":"FateTell 页面没写 API，是不是就没有接口？","answer":"不能这样推断。FateTell 概览页实际提到了 FateTell MCP，可把排盘与分析工具接到 AI 助手。某一页未描述接口，只说明该页没有覆盖这项内容，应查阅其当前接入文档再判断。","sourceIds":["fatetell"]},{"question":"两处排出的日柱不同，是哪个算错了吗？","answer":"先别下结论。换日约定、真太阳时是否开启、出生时间是否已知，都会影响日柱或时柱。把两边的设置逐项对照，再判断差异来源；本页未比较预测准确率。","sourceIds":["methods","fatetellCalculator"]},{"question":"想要一份成文报告，该看哪边？","answer":"FateTell 概览页介绍 FateBook 与 Book of Abundance 等报告产品，可作为了解入口。本页未购买或登录测试，无法评价报告内容，请以其官方说明为准。","sourceIds":["fatetell"]}],"glossary":[{"term":"换日约定","definition":"确定一天从何时开始、从而决定日柱归属的规则。问卜默认 00:00 换日，也可选 23:00 子初换日；不同设置可能改变日柱。","sourceIds":["methods"]},{"term":"真太阳时","definition":"按经度与均时差对钟表时间作近似校正的时间。问卜说明其为近似公式，临近换日或时辰边界时建议对照不同设置。","sourceIds":["methods"]},{"term":"MCP","definition":"一种让 AI 助手调用外部工具的协议。问卜公开其 MCP 工具清单与结构化输出；FateTell 概览页也提到 FateTell MCP。","sourceIds":["agents","fatetell"]}],"cta":{"label":"用同一组虚构出生资料各排一次盘","reason":"在问卜排盘页填入虚构的日期、时刻与时区，记录四柱与所用约定，再与另一处的设置逐项对照，把空白项标为未核实。"}},"en":{"title":"Inputs, report products and integrations: three scenarios and a checklist","description":"A focused addition comparing the chart inputs, published conventions, report products and integration notes on FateTell's and Wenbu's public pages, with three reader scenarios and a short worksheet. Paid and signed-in features were not tested, and predictive accuracy was not compared.","answer":"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.","answerSourceIds":["fatetellCalculator","methods","fatetell","agents"],"evidence":[{"claim":"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.","sourceId":"fatetellCalculator","quote":"Use the local clock time recorded at your birthplace.","kind":"fact"},{"claim":"Wenbu publishes its BaZi input range, time-zone format and default day boundary so results can be checked.","sourceId":"methods","quote":"默认在 00:00 换日","kind":"fact"},{"claim":"FateTell's overview presents report products and also mentions FateTell MCP.","sourceId":"fatetell","quote":"FateTell MCP","kind":"fact"}],"takeaways":["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."],"sections":[{"heading":"Inputs and conventions: make two charts comparable","paragraphs":["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."],"sourceIds":["fatetellCalculator","methods"]},{"heading":"Report products and integrations: two kinds of delivery","paragraphs":["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."],"sourceIds":["fatetell","agents","methods"]},{"heading":"Three reader scenarios and a short worksheet","paragraphs":["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."],"sourceIds":["methods","fatetell","agents","fatetellCalculator"]}],"figure":{"title":"From task to tool: a decision flow","caption":"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.","sourceIds":["methods","fatetell","agents"],"steps":[{"label":"Name the task","detail":"A chart, a written report, or results inside your own assistant."},{"label":"Align inputs","detail":"Record the Gregorian date, local clock time, time zone, day boundary and true-solar-time setting."},{"label":"Confirm delivery","detail":"Check whether you get a chart, a report or structured output, and whether it can be exported."},{"label":"Mark what is unverified","detail":"Write not verified for features a page does not describe; do not infer either presence or absence."}]},"table":{"title":"Checking both public pages by task","columns":["Check","Wenbu public pages","FateTell public pages"],"rows":[["Chart inputs","Gregorian date, local clock time, IANA zone or UTC offset","Gregorian date, local clock time, birthplace time zone, optional precise location"],["Day boundary and solar time","Midnight default, optional 23:00; true solar time as an approximation","True-solar-time option described as adjusting for longitude, historical zone and equation of time"],["Report products","Pages emphasise tools, references and an Agent","Overview presents FateBook and Book of Abundance"],["Integration notes","MCP, REST, CLI and Skill published","Overview mentions FateTell MCP"],["What was tested here","Paid and signed-in features not tested","Report products not purchased or tested"]],"sourceIds":["methods","fatetellCalculator","fatetell","agents"]},"example":{"title":"Hypothetical example: checking one birth record in two places","intro":"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.","steps":["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."],"conclusion":"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.","sourceIds":["fatetellCalculator","methods"]},"faq":[{"question":"If FateTell's page does not describe an API, does that mean there is none?","answer":"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.","sourceIds":["fatetell"]},{"question":"The day pillars differ between two charts. Did one calculate it wrongly?","answer":"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.","sourceIds":["methods","fatetellCalculator"]},{"question":"Which side should I look at for a written report?","answer":"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.","sourceIds":["fatetell"]}],"glossary":[{"term":"Day-boundary convention","definition":"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.","sourceIds":["methods"]},{"term":"True solar time","definition":"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.","sourceIds":["methods"]},{"term":"MCP","definition":"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.","sourceIds":["agents","fatetell"]}],"cta":{"label":"Chart the same fictional birth details once","reason":"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."}},"topic":{"id":"compare-fatetell-update","slug":"fatetell","category":"compare","mode":"extend","tool":"bazi","zh":"问卜与 FateTell：排盘、报告产品与接入方式","en":"Wenbu vs FateTell: charts, report products and integrations","task":"Help a reader decide between Wenbu and FateTell for a concrete charting, learning or record-keeping task.","unique":"The earlier proposal was blocked; this version keeps the existing comparison evidence and adds only what both public pages document: calculator inputs and conventions, report products, and whether an integration is described. It states explicitly that a page not describing an API is not proof the API is absent, and adds three reader scenarios and a short worksheet.","sources":["wenbu","methods","agents","fatetell","fatetellCalculator"],"priority":75,"search":{"pillar":"agent-choice","intent":"compare","zh":["FateTell 对比","八字排盘工具对比","八字报告产品"],"en":["FateTell vs Wenbu","BaZi calculator comparison","BaZi report products"],"basis":"research_hypothesis"}},"revision":"81ac66507868c6714fbaab5a9965cfc0fa4b11d80e18d1e65abb8427f89c3ec3","updatedAt":"2026-10-30T01:01:37.618Z","sources":[{"id":"current-zh","title":"Current complete zh canonical article","url":"https://wenbu.app/knowledge/zh/compare-fatetell.md","role":"Current public original and earlier additions; add substantial coverage without repeating or replacing them.","fetchedAt":"2026-10-30T01:00:35.983Z","hash":"b6f95d5de70768250d86ef24f2922639e31759cd08802a8aabbd1371a16e9d4b","truncated":false},{"id":"current-en","title":"Current complete en canonical article","url":"https://wenbu.app/knowledge/en/compare-fatetell.md","role":"Current public original and earlier additions; add substantial coverage without repeating or replacing them.","fetchedAt":"2026-10-30T01:00:36.853Z","hash":"469cfc60e1aa41be5911b4c126e6b2b848c8dfb9358efded792c9f3761305a4c","truncated":false},{"id":"wenbu","title":"Wenbu · current free access","url":"https://wenbu.app/free/","role":"First-party access and quota documentation","fetchedAt":"2026-10-30T01:00:37.020Z","hash":"db9ca0345476ac248c364369edcc1736928f02903c6de6c3a9653fa610d6d2f7","truncated":false},{"id":"methods","title":"Wenbu · calculation conventions","url":"https://wenbu.app/methodology/","role":"First-party implementation; not evidence of predictive accuracy","fetchedAt":"2026-10-30T01:00:37.023Z","hash":"5452dbc076e1c31aa334fa49949d682ad7851e75a5cf9396b6682530b30f0f0c","truncated":false},{"id":"agents","title":"Wenbu · agent integrations","url":"https://wenbu.app/agents/","role":"Current first-party product documentation","fetchedAt":"2026-10-30T01:00:37.037Z","hash":"93a965358202f2256f2d430a517a7cc192c950b3e6f6157a242a234d3c24a7d8","truncated":false},{"id":"fatetell","title":"FateTell · official overview","url":"https://fatetell.com/","role":"Vendor statements; public page only, no paid account testing","fetchedAt":"2026-10-30T01:00:38.530Z","hash":"03a529fe6748d09898eded14995722f5518cafecf57520bcbc12f708a083fa20","truncated":true},{"id":"fatetellCalculator","title":"FateTell · official calculator","url":"https://fatetell.com/bazi-calculator","role":"Vendor calculator documentation","fetchedAt":"2026-10-30T01:00:38.530Z","hash":"ac850f19055ffa99cb3ec47887c17f7374da38c61896087924fd18424fa3df5a","truncated":true},{"id":"daily","title":"Wenbu · daily card","url":"https://wenbu.app/daily/","role":"Current first-party product UI; not a personal forecast","fetchedAt":"2026-10-30T01:00:37.023Z","hash":"b2bab9f05c80e8d1d3298bad705319173d94b421ad87546cfe94f8eb0ecc9999","truncated":false},{"id":"capabilities","title":"Wenbu · versioned public capabilities","url":"https://wenbu.app/capabilities.json","role":"First-party current tool, convention and privacy contract; not external endorsement or predictive validation","fetchedAt":"2026-10-30T01:00:37.023Z","hash":"557485b2f5513f237e8258ecf9d0a1fbbf5aa19a30c726f9199bf3817e021546","truncated":false}]}]}