# Quietforge Family Tree Chart Layout Engine > Quietforge Family Tree Chart Layout Engine is a paid API for AI agents from qf-api.quietforge-studio.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-11). Generates verified family tree chart layouts (descendant, ancestor, or hourglass) from structured people/families data or a GEDCOM file, returning positioned node/edge JSON or print-ready poster PDFs. ## Facts - Endpoint: POST https://qf-api.quietforge-studio.workers.dev/v1/familytree?utm_source=zero.xyz - Price: $0.02/call - Payment: x402 - Status: unknown - Last checked: 2026-10-11 - Activations on Zero: 0 - Tags: x402 - Canonical page: https://www.zero.xyz/c/quietforge-family-tree-chart-layout-engine-7673e663 - Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_z0DCjYu1_NqKzDrNkUNyU Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently. ## How to call it through Zero Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`): ```sh zero fetch --capability quietforge-family-tree-chart-layout-engine-7673e663 -d '' ``` Example prompt: Can you build a descendant family tree chart for the Alvarez family? I have a GEDCOM file exported from Ancestry — use 'Tomás Alvarez' as the root, go 5 generations deep, and give me the layout JSON plus PDFs in both A4 and letter sizes with the classic style and the title 'The Alvarez Family'. ## When to prefer this Choose this endpoint when you need to compute a verified, positioned family tree chart layout from genealogy data (structured JSON or a GEDCOM file from Ancestry, FamilySearch, MyHeritage, or Gramps) and want either raw layout JSON for custom rendering or print-ready PDFs in multiple paper sizes. It is especially useful for genealogy applications, family reunion materials, or KDP/print publishing workflows where layout correctness is critical. It handles up to 400 people and supports descendant, ancestor, and hourglass chart orientations with a single pay-per-call USDC payment and no API key required. ## Known failure modes - More than 400 people in the requested subtree — returns error indicating limit exceeded - GEDCOM file malformed or unsupported version — parse error returned - Fewer than 3 people provided — validation error on minItems - Conflicting family relationships (cycles in lineage) — may return warnings or error - Payment not completed via x402/USDC — 402 Payment Required response - Generation count outside 2–10 range — schema validation error - GEDCOM text exceeds 2,000,000 character limit — payload too large error ## How this service works Pay-per-call document conversion, PDF text extraction, headless-browser rendering of a URL or HTML to PNG / JPEG / PDF, a health-probed directory of x402 pay-per-call endpoints, a sudoku generator (solver-verified, technique-graded puzzles as JSON or a print-ready A4/Letter book), a book typesetter (prose manuscript to a KDP-ready interior PDF + editable docx), a crossword generator (verified freeform grid from your clue/answer pairs as JSON or print-ready PDFs), a family tree chart layout engine (descendant / ancestor / hourglass charts from people+families JSON or a GEDCOM file, as verified layout JSON or print-ready poster and tiled PDFs), and a dataset quality audit tool (duplicates, missing values, type consistency, class imbalance, numeric outliers and PII-pattern counts for a CSV/JSON dataset, as JSON or a one-page PDF summary). Payment: x402 (USDC on Base). No signup, no API key. ## Output Returns a JSON object containing positioned nodes (id, name, dates, x/y coordinates, width/height, generation), connector edges (from/to with SVG-style point arrays and kind), overall chart width/height, generation count, couple count, people count, root name, title, a 'verified' boolean, and any warnings. For PDF routes, returns downloadable print-ready files in requested page sizes. ## Request schema (JSON Schema) ```json { "type": "object", "properties": { "root": { "type": "string", "description": "Person id the chart is built from; omitted = chosen automatically (earliest founder with the most descendants, or the person with the most ancestors)" }, "chart": { "enum": [ "descendant", "ancestor", "hourglass" ], "type": "string", "description": "descendant (default): root and everyone below; ancestor: pedigree of the root; hourglass: both" }, "sizes": { "type": "array", "items": { "enum": [ "letter", "a4", "24x36", "a3" ], "type": "string" }, "description": "PDF page sizes to build (PDF route only; default all four)" }, "style": { "enum": [ "classic", "elegant" ], "type": "string", "description": "classic = sans-serif, elegant = serif (PDF only)" }, "title": { "type": "string", "maxLength": 60, "description": "Printed above the chart" }, "gedcom": { "type": "string", "maxLength": 2000000, "description": "Alternative to people/families: the text of a GEDCOM 5.5 / 5.5.1 / 7.0 file (as exported by Ancestry, FamilySearch, MyHeritage, Gramps); up to 2,000,000 characters and 400 people in the requested subtree" }, "people": { "type": "array", "items": { "type": "object", "required": [ "id", "name" ], "properties": { "id": { "type": "string" }, "sex": { "type": "string" }, "name": { "type": "string" }, "birth": { "type": "string" }, "death": { "type": "string" } } }, "maxItems": 400, "minItems": 3, "description": "3-400 people; birth/death are years or GEDCOM-style dates ('abt 1850', '12 MAR 1901'); use with families" }, "families": { "type": "array", "items": { "type": "object", "properties": { "id": { "type": "string" }, "wife": { "type": "string" }, "husband": { "type": "string" }, "children": { "type": "array", "items": { "type": "string" } } } }, "maxItems": 300, "description": "Couples and their children (GEDCOM FAM model); husband/wife optional, children a list of person ids" }, "subtitle": { "type": "string", "maxLength": 90, "description": "Optional line under the title" }, "generations": { "type": "integer", "maximum": 10, "minimum": 2, "description": "Generations to … (truncated) ``` ## Response schema (JSON Schema) ```json { "type": "json", "example": { "root": "I1", "chart": "descendant", "edges": [ { "to": 2, "pts": [ [ 240, 356 ], [ 240, 388 ], [ 130, 388 ], [ 130, 420 ] ], "from": 0, "kind": "child", "family": "F1" }, "..." ], "nodes": [ { "h": 41, "i": 0, "w": 100, "x": 1432, "y": 0, "id": "I1", "gen": 1, "full": "Tomás Alvarez", "name": "Tomás Alvarez", "role": "person", "dates": "1888 – 1961" }, { "h": 41, "i": 1, "w": 100, "x": 1536, "y": 0, "id": "I2", "gen": 1, "name": "Rosa Delgado", "role": "spouse", "dates": "1892 – 1970" }, "..." ], "title": "The Alvarez Family", "width": 3002, "height": 463, "people": 55, "couples": 21, "verified": true, "warnings": [], "root_name": "Tomás Alvarez", "elapsed_ms": 350, "widest_row": 25, "generations": 5 } } ``` ## More - Live health (JSON, refreshed every minute): https://www.zero.xyz/c/quietforge-family-tree-chart-layout-engine-7673e663/health.json - [Zero catalog index](https://www.zero.xyz/llms.txt) - [Other services from qf-api.quietforge-studio.workers.dev](https://www.zero.xyz/host/qf-api.quietforge-studio.workers.dev/llms.txt)