# Trace where a metric or column comes from and what breaks if it changes

> 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 & data catalogues with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/
- Markdown: https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/index.md (~1,500 tokens)
- Slim: https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/index.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/company-knowledge.lineage-trace/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 0 | 7 | 9 | 9 | 5 |

## What counts as done

The 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.

How agents ask for it: where does this revenue number come from; what's downstream of this table; if I drop this column what breaks

## Does the job, with a limit

It 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.

- **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).
- **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.
- **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.
- **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.
- **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.
- **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).
- **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.

## Couldn't check

The docs were closed to us, or silent. These carry no mark either way.

- **ClicData MCP (ClicData SAS)**: No lineage tool is named on the readable page, and the tool list and help article couldn't be read.
- **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.

- not this job: Basedash MCP (BaseDash Inc. (Delaware, United States)): No lineage tool or lineage graph in the MCP server's ten tools.
- 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.
- not this job: Dust (Permutation Labs): No lineage data or endpoint in the API spec or docs; Dust doesn't aim at data lineage.
- 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.
- 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.
- not this job: Guru (Guru Technologies, Inc.): No data lineage; Guru holds cards and synced documents.
- not this job: Hexis Cloud (Bevelites GmbH): No data lineage; file history covers pages, not tables or columns.
- not this job: Onyx (DanswerAI, Inc.): No lineage data or tool; Onyx indexes documents, not data pipelines.
- 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.
- not this job: Procore AI Go (Procore Technologies, Inc.): No data lineage; the app reads construction project records.
- not this job: Lens (Thought Industries) (Thought Industries, Inc.): No data lineage of any kind in the API.

## What stops agents finishing

- lineage across storage types has to be added by hand (Marmot, per its author)
- column lineage truncated at a character cap with no paging
- lineage shows neighbours the caller may not see

## Around it

Before: company-knowledge.find-data-asset. After: code.change-pipeline, notifications.ask-owner.

## Where this comes from

Weight 9 of 100 in Company knowledge & data catalogues: 5 of 38 counted accounts (OpenMetadata lineage from Airflow, Alation procurement lineage trial, DataHub column lineage truncation, OpenMetadata lineage permissions, OpenMetadata deployment)

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
