{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/",
    "json": "https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 7 | 9 | 9 | 5 |\n\n## What counts as done\n\nThe full upstream or downstream graph to a requested depth, column level where it exists, with every edge's source system, returned complete or with a cursor to the rest, and filtered to the caller's permissions.\n\nHow agents ask for it: where does this revenue number come from; what's downstream of this table; if I drop this column what breaks\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Alation (Alation, Inc.)**: get_lineage supports column level, direction, max_depth (default 10), limit up to 1,000 and a pagination cursor, but it is beta, must be enabled by Alation support and opted into, and a buyer could not get lineage working in a trial (acc-16).\n- **Atlan (Atlan Pte. Ltd.)**: traverse_lineage goes upstream or downstream, immediate neighbours by default and deeper on request, but column-level lineage, paging and source system per edge aren't stated, and a qualifiedName in place of a GUID fails.\n- **Collibra (Collibra Inc.)**: get_lineage_upstream and get_lineage_downstream page with limit (max 100) and cursor and filter to columns, but return IDs only, take no depth parameter, and need a search_lineage_entities call first; permission filtering of neighbours is not stated.\n- **DataHub (Acryl Data, Inc. (d/b/a DataHub))**: get_lineage takes upstream, max_hops (3 means unlimited), max_results and offset, at table or column level, but column lineage is one column per call (acc-28), offset paging can refetch page 1 (issue 194) and caller filtering isn't stated.\n- **Marmot (Marmot Data Ltd)**: trace_lineage takes direction and depth 1 to 10, grouped by distance, but no column-level lineage or cursor appears in the tool, and the author says lineage across plugins is added by hand.\n- **OpenMetadata (Collate, Inc.)**: get_entity_lineage takes upstreamDepth, downstreamDepth, column, includeColumnLineage and a cursor with hasMore, so the graph is pageable, but the AI Context lineage section lists neighbours as an admin sees them (acc-31, open).\n- **Secoda (Secoda, Inc.)**: entity_lineage takes only an entity_id, with no direction, depth, column or cursor parameter, so completeness and paging can't be controlled or confirmed.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **ClicData MCP (ClicData SAS)**: No lineage tool is named on the readable page, and the tool list and help article couldn't be read.\n- **Precisely AI Studio (Precisely Incorporated)**: No lineage asset is named on the readable product page, and the asset catalogue and help centre need sign-in or JavaScript.\n\n- not this job: Basedash MCP (BaseDash Inc. (Delaware, United States)): No lineage tool or lineage graph in the MCP server's ten tools.\n- not this job: Cohere North (Cohere Inc.): No lineage feature on the product page or in the North 2 announcement; North doesn't aim at data lineage.\n- not this job: Dust (Permutation Labs): No lineage data or endpoint in the API spec or docs; Dust doesn't aim at data lineage.\n- not this job: Gemini Enterprise (Google LLC): No lineage feature in the assistant or connector docs read; Gemini Enterprise doesn't aim at data lineage.\n- not this job: Glean (Glean Technologies, Inc.): No lineage tool or field in the MCP tool list or the REST schema; Glean doesn't aim at data lineage.\n- not this job: Guru (Guru Technologies, Inc.): No data lineage; Guru holds cards and synced documents.\n- not this job: Hexis Cloud (Bevelites GmbH): No data lineage; file history covers pages, not tables or columns.\n- not this job: Onyx (DanswerAI, Inc.): No lineage data or tool; Onyx indexes documents, not data pipelines.\n- not this job: Overclock (Overclock Technologies Limited): No data lineage. oc_log and oc_diff trace a fact's versions across documents, which is not table or column lineage.\n- not this job: Procore AI Go (Procore Technologies, Inc.): No data lineage; the app reads construction project records.\n- not this job: Lens (Thought Industries) (Thought Industries, Inc.): No data lineage of any kind in the API.\n\n## What stops agents finishing\n\n- lineage across storage types has to be added by hand (Marmot, per its author)\n- column lineage truncated at a character cap with no paging\n- lineage shows neighbours the caller may not see\n\n## Around it\n\nBefore: company-knowledge.find-data-asset. After: code.change-pipeline, notifications.ask-owner.\n\n## Where this comes from\n\nWeight 9 of 100 in Company knowledge \u0026 data catalogues: 5 of 38 counted accounts (OpenMetadata lineage from Airflow, Alation procurement lineage trial, DataHub column lineage truncation, OpenMetadata lineage permissions, OpenMetadata deployment)\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/company-knowledge.lineage-trace.json, or the MCP tool get_use_case with id company-knowledge.lineage-trace. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Trace where a metric or column comes from and what breaks if it changes",
        "url": ""
      }
    ],
    "description": "Trace where a metric or column comes from and what breaks if it changes: 0 companies fully do it, 7 with a limit, 9 carry the tag. Every listing in Company knowledge \u0026 data catalogues with the reason and a source.",
    "facts": null,
    "h1": "Trace where a metric or column comes from and what breaks if it changes",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/company-knowledge.lineage-trace/",
    "published": "",
    "section": "agents",
    "title": "Trace where a metric or column comes from and what breaks if it…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 330
  },
  "version": 1
}
