Agents

Beta

Agents are in the beta phase of development and may not be available on your enrollment. Functionality may change during active development.

With Agents, developers can build, configure, and ship pro-code agents in Foundry. An agent is custom logic written in a Foundry code repository. It uses a large language model (LLM) to reason over a prompt and call tools that read and write data in your environment.

Agents authenticate against the Ontology SDK (OSDK), Ontology MCP (OMCP), and Palantir MCP with scoped permissions out of the box. You do not need to pass a client ID and secret to call tools. After you publish an agent, you can call it from Workshop or the Ontology SDK with no additional configuration.

For common ways to use agents, such as reading and writing Ontology data, building platform resources, and migrating legacy systems, review our use cases documentation.

How agents work

An agent is defined in a code repository created from the agent template. The template includes:

  1. An OSDK client bound to your selected Ontology, used to read and write Ontology data.
  2. Ontology MCP and Palantir MCP configuration, exposing Ontology resources and platform tools to the agent's LLM.
  3. The agent's logic, where you define the prompt, the tools the agent can call, and how the agent consumes the model's response stream.

When you publish the agent, Foundry registers it with an Ontology binding and an agent API name. The published agent is exposed as an asynchronous function. We recommend triggering agents from Automate, but you can also call them from Workshop, the Ontology SDK, and Ontology actions.

Key capabilities

  • Scoped permissions out of the box: Agents authenticate against OSDK, OMCP, and Palantir MCP with scoped permissions automatically. You do not wire up client credentials manually to use tools.
  • Templates for the Claude Agent SDK, OpenAI Agents SDK, and Google ADK: Create your agent from a template for the Claude Agent SDK ↗, OpenAI Agents SDK ↗, or Google Agent Development Kit (ADK) ↗. Each template ships with simplified configuration for OMCP, Palantir MCP, and the OSDK client, with common setup moved into the library.
  • Published with an Ontology binding and agent API name: Every agent is published with an Ontology binding and an agent API name, making its function callable from both Workshop and OSDK.
  • Guided walkthrough: After you create an agent, a Build agent in Foundry landing page walks you through the next steps of building, publishing, and calling your agent.
  • Build your agent with Continue: Use Palantir MCP with Continue ↗ to manage both the SDK and the OMCP scope attached to the agent, directly from your editor.

Next steps