# Expose Resource Lineage as a Public API

**URL:** <https://community.palantir.com/t/expose-resource-lineage-as-a-public-api/6496>\
**Category:** Product Feedback\
**Tags:** workflow-lineage, foundry-mcp\
**Created:** [April 26, 2026, 7:59pm UTC](https://community.palantir.com/t/expose-resource-lineage-as-a-public-api/6496 "2026-04-26T19:59:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ujjalb](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/ujjalb/32/6412_2.png) [@ujjalb](https://community.palantir.com/u/ujjalb)\
**Post date:** [April 26, 2026, 7:59pm UTC](https://community.palantir.com/t/expose-resource-lineage-as-a-public-api/6496/1 "2026-04-26T19:59:26Z")

</div>

Foundry’s Workflow Lineage UI shows the full dependency graph between resources (datasets, object types, transforms, applications, monitors). This data is not accessible programmatically. Please expose it as a **V2 REST API endpoint** and **MCP tool**.

Today this data is only available through the Workflow Lineage UI and AI FDE’s internal tooling. Functions, AIP Agents, and OSDK apps cannot access it.

**What We Tested**

From a TypeScript v2 Function, we tried **30+ API paths** including Compass sub-paths, decorations, V2 endpoints, and all `@osdk/foundry.*` SDK packages. **None expose lineage data.** Meanwhile, AI FDE’s internal `get_resource_lineage` tool returns exactly what we need — upstream/downstream RIDs with names, paths, and connection types.

### **The Ask**

1. **REST API** — `GET /api/v2/resources/{rid}/lineage` for Functions, OSDK apps, and scripts

2. **MCP Tool** — `get_resource_lineage` for external AI agents (Claude Desktop, etc.)

3. **AIP Agent Platform Tool** — Same capability available in AIP Agent Studio

The data already exists in the platform. It just needs a public interface.

---

<div class="post-metadata">

**Author:** ![ujjalb](https://yyz1.discourse-cdn.com/palantir/user_avatar/community.palantir.com/ujjalb/32/6412_2.png) [@ujjalb](https://community.palantir.com/u/ujjalb)\
**Post date:** [April 29, 2026, 6:40pm UTC](https://community.palantir.com/t/expose-resource-lineage-as-a-public-api/6496/2 "2026-04-29T18:40:50Z")

</div>

Any thoughts or updates on this?

---

<div class="post-metadata">

**Author:** ![helenq](https://avatars.discourse-cdn.com/v4/letter/h/a4c791/32.png) [@helenq](https://community.palantir.com/u/helenq)\
**Post date:** [June 23, 2026, 5:02pm UTC](https://community.palantir.com/t/expose-resource-lineage-as-a-public-api/6496/3 "2026-06-23T17:02:00Z")

</div>

Hey @ujjalb thanks for the details here. You’re right that currently Workflow Lineage doesn’t expose public APIs for getting the lineage of resources.

A few questions from my end:

1. What is your usecase here and what do you need it for? Wonder if it’s something we can add directly to Workflow Lineage to improve the product

2. What specific resources do you care about?

3. And confirming you are trying to get all downstream usages from a single resource rid