Enable AIP features

Palantir AIP (Artificial Intelligence Platform) is enabled by default in new enrollments. Enrollments that began prior to 2024 may need to manually turn on access to AIP features in Control Panel. Your AIP configuration can be managed in Control Panel > AIP settings if you are an enrollment administrator.

Note that enabling AIP may incur additional compute usage.

Review the list of supported models.

AIP and capabilities for custom workflows

AIP's AI functionality can be divided into three categories:

• AIP Assist: An LLM-powered support tool designed to help users navigate, understand, and generate value with the Palantir platform. Users can ask AIP Assist questions in natural language and receive real-time help with their queries.
• AIP assistant features in platform applications: Native LLM-backed features designed to help end users perform regular workflows in the Palantir platform. These are highly-specific features that leverage knowledge of the platform to accelerate a user's day-to-day operations.
• AIP capabilities for custom workflows: A set of capabilities that allow developers to build their own LLM-backed workflows or applications. These are open-ended functionalities built for developers or data scientists.

AIP permissions

AIP usage on the Palantir platform is governed by two levels of permissions:

• AIP and core assistant features: Turns on AIP, AIP Assist, and associated assistant features in Code Repositories, Pipeline Builder, and Workshop.

  

• AIP capabilities for custom workflows: With AIP enabled, platform administrators can enable an additional layer of capabilities to empower developers and application builders to create custom AIP workflows and grant users the necessary permissions to use these custom AIP workflows. The capabilities that are unlocked when permission is granted are as follows:

  • Capabilities with LLM support in point-and-click interfaces
    • AIP Logic: Use LLM Board
    • Pipeline Builder: Use LLM node and Text-to-embeddings
    • AIP Automate
    • AIP Model Catalog
    • AIP Agent Studio
    • AIP Workshop widgets: AIP Interactive, AIP Generated Content
    • AIP Workshop translations
    • Quiver
    • AIP Threads
  • Capabilities for development with code-based tools
    • Transforms using LLMs
    • Functions using LLMs
    • Jupyter® in Code Workspaces with LLMs

Restrict AIP usage

Platform administrators can restrict AIP usage on two different levels; user groups and Organizations.

User groups

To restrict AIP usage on user groups, platform administrators can select Everyone, given User Groups, or restrict usage by selecting Nobody.

Note that certain applications, such as AIP Logic, may need to first be enabled in Control Panel > Application access before they can be used.

Organizations

To restrict AIP on Organizations, platform administrators can enable the Restrict AIP To Organizations option and select the desired Organizations from the dropdown. Keep in mind that this setting restricts AIP to the selected Organizations. As a result, AIP will be disabled for any Organizations that are not selected. Additionally, if AIP is not enabled for an enrollment, no Organizations will have access to AIP.

Enable LLMs

Enabling specific LLMs is performed separately after general AIP enablement and can be managed by enrollment administrators under the Model enablement tab within the AIP settings extension of Control Panel.

Enrollment administrators may view and manage the available models for use within AIP, which may differ across enrollments.

View a list of all supported models. Models are grouped according to their legal requirements and terms of use, and groups can be individually enabled. Disabling a model group will break workflows that rely on a model in that specific group.

Model groups may be currently disallowed if the legal requirements for use have not been satisfied. In this case, an enrollment administrator may need to first accept the relevant terms and conditions for the specific model. Note that certain LLM groups may require manual configuration by your Palantir representative to use.

Learn how to bring your own model to run on the Palantir platform.

Enrollment administrators can enable or disable model families at the organization level, allowing certain organizations within the same enrollment to access specific model families while restricting others.

In the example below, only the Test1 organization in this enrollment has access to AWS Bedrock Claude models.

Experimental models

Usage of experimental models can be enabled and disabled by enrollment administrators. For an experimental model to be visible for use in workflows, the Enable experimental models toggle must be enabled as well as the model family to which the experimental model belongs.

Learn more

• Available LLMs
• LLM availability prerequisites
• LLM capacity management
• Georestriction of model availability

---

Note: AIP feature availability is subject to change and may differ between customers.

The "OpenAI" name and the “GPT” brands are property of OpenAI.

Jupyter®, JupyterLab®, and the Jupyter® logos are trademarks or registered trademarks of NumFOCUS.

All third-party trademarks (including logos and icons) referenced remain the property of their respective owners. No affiliation or endorsement is implied.