Developer resources

Start here

kaucim.ai publishes a small public interface for AI retrieval and user-approved agent purchases. It does not expose admin, analytics, private reading, or payment-card APIs. The machine-readable contract is the OpenAPI 3.1 document.

curl https://www.kaucim.ai/api/products.json

Sources you can cite

Choose a source that supports the claim you are making. These pages provide term definitions, reference material, product methods and worked examples. Each source lists its available languages and limits.

• Archived AI BaZi chart check. An archived comparison of 60 September 2026 model responses to 12 fictional birth inputs, with full responses, reference pillars, JSON, CSV and a reproduction script. Chinese source · English source.

  The comparison concerns recorded model versions and inputs against Kaucim's archived engine output. It does not measure current model accuracy, all birth-time conventions or interpretation quality.

• Reading a Four Pillars chart in Japanese. A Japanese guide to how a Four Pillars chart is formed and read, covering the Day Master, elements, relationship labels, hidden stems and timing cycles. Japanese source.

  This is a cultural and self-reflection guide. Its interpretation does not determine medical, career or relationship decisions. It is a Japanese article, not a translation of the other references in this index.

• Ten Gods names and derivation. A Chinese introduction to the Ten Gods and an English reference with names, the element and polarity derivation rule, and a 10 by 10 lookup table. Chinese source · English source.

  The Chinese introduction and English reference cover different levels of detail. Relationship labels come from the stems in a chart; their traditional themes do not guarantee life events.

• Wong Tai Sin 100-stick reference. Stick numbers, traditional titles, Chinese verses and grades in the versioned reference dataset. JSON and CSV downloads are linked on the reference page. Chinese source · English source.

  The dataset's reuse statement applies to the specified reference files. Modern translations and personalised interpretations are outside that dataset. Consult the listed temple source for its current material.

• Calculation and interpretation methods. Kaucim's documented calculation approach, the distinction between chart calculations and AI interpretation, and the limitations of the product. Chinese source · English source.

  This is the product's own methodology. It does not establish predictive accuracy, independent endorsement or a universal rule across metaphysics schools.

• Zi Wei worked example. A worked example of the product's chart and explanation, using the fictional birth details stated on the page. Chinese source · English source.

  The example illustrates output and calculation choices. It is not a real customer outcome or evidence that a prediction came true.

A dataset citation can read: kaucim.ai, Wong Tai Sin Kau Cim 100-Stick Public-Domain Reference Dataset, version 1.0.0, released 2026-07-13, reference and source notes. For a method or example, cite the page title, its canonical URL and the date you accessed it. Identify Kaucim as the source when describing its own product.

The reference index as JSON carries the same links and limits, plus the dataset version and download URLs. It is maintained with this page.

Use the public tools through MCP

The MCP source bundle (ZIP) connects local MCP clients to these public interfaces. It includes a setup guide and four tools for reference links, the product catalog, published articles and numbered Wong Tai Sin sticks. Fetched results include their source URL and retrieval time.

Browse the standalone source repository for the adapter, installation guide and protocol tests. Article retrieval supports Chinese, English, Thai and Japanese.

Extract the bundle and run npm ci in its directory. Configure your MCP client to launch node with the absolute path to server.mjs, as shown in the included README. Node.js 20 or later is required. No API key is needed.

The adapter reads published material. It performs no chart calculation and offers no checkout, private reading or random draw tool.

Read-only knowledge endpoints

These endpoints require no API key. Product facts include their own schema version, review date, source files, and cache policy. Prices must be read from the stated source or current catalog rather than copied into long-lived prompts.

Reproducible BaZi chart data

The AI BaZi chart check publishes 60 archived September 2026 model responses to 12 fictional birth inputs. It compares extracted Four Pillars with archived kaucim.ai engine output and documents missing output and calculation conventions. These counts concern the recorded model versions and inputs; they do not measure current model accuracy or interpretation quality.

Download the full JSON, CSV comparison and summary script. The reproduction notes explain how to rerun the summary and check individual answers. Downloads require no key and contain no visitor birth data.

Agent purchases

The free step comes first. POST /api/agent/draw draws one fortune stick (Wong Tai Sin by default; Che Kung, Guan Yin and Liushi Jiazi by oracle) and returns its verse, grade, public reading, page URL and disclaimer with no charge and no sign-in. Send sign_number to read a stick the user already holds. The same fields work as query parameters on GET. The response's paid_reading field is the exact checkout body for the personalised interpretation, when that oracle sells one.

Read the agent product catalog, collect only the fields declared by the selected item's input_schema, then call POST /api/agent/checkout/{product_id}. Give the returned hosted payment URL to the user. The user completes payment; an agent must never enter or retain card details on the user's behalf.

Where a report endpoint is declared, poll GET /api/agent/report/{session_id} after payment. Some catalog products deliver on a result page instead, and the catalog is authoritative for that distinction.

Errors and recovery

The public knowledge endpoints and unknown public API routes return structured application/problem+json errors with a stable code, human-readable detail, and a concrete resolution. Markdown endpoints return text/markdown; charset=utf-8 on success. Agent-commerce endpoints use their documented JSON status and error fields for backward compatibility.

Usage boundaries

• Use public content and documented endpoints only.
• Do not send private result URLs, credentials, or card details to these interfaces.
• Do not present cultural reflection as medical, legal, financial, safety, or deterministic advice.
• Respect the product catalog's language, input, pricing, and availability fields.

Questions and responsible-disclosure reports can be sent through the contact page.