Agents are in the beta phase of development and may not be available on your enrollment. Functionality may change during active development.
Agents combine a large language model with the Ontology SDK (OSDK), Ontology MCP (OMCP), and Palantir MCP to read data, reason about it, and act across the platform. The patterns and examples below describe common ways to use agents.
A change in the Ontology triggers the agent, which then reads the relevant objects through OSDK or OMCP. The agent reasons about the data with the model and writes results back to the Ontology. This pattern works well when triggered from Automate when objects change.
A claim is declined, which triggers the agent. The agent reads the claim and its decline reason through the Ontology. It uses the model to explain the decline and how the customer can remediate it, then writes the explanation and recommended next steps back to the claim object. This helps customers understand and resolve declines faster, saving time and cost.
A platform event triggers these agents, which use Palantir MCP to inspect and modify resources such as code repositories and transforms. The agent reasons about what to change with the model, then applies the change on the platform.
A build failure event triggers the agent. The agent finds the transform repository that owns the failing build and uses Palantir MCP to read the build logs. It uses the model to determine the cause of failure, writes a fix in the repository, and tests it. The agent finishes by submitting a pull request for the developer to review.
Migration agents combine the Ontology data agents and platform resource agents patterns to migrate a legacy system into Foundry. Legacy source code is first ingested into the Ontology. The agent uses OSDK and OMCP to understand the existing functionality, then uses Palantir MCP to build the Foundry resources that replicate the legacy logic in a modern system.
Source code from a legacy system is ingested as Ontology objects. The agent reads and reasons about the existing logic through OSDK and OMCP. It then uses Palantir MCP to generate the transforms, functions, and ontology resources that reproduce that logic in Foundry.