Skip to main content
Openlayer connects to your Palantir Foundry AIP Chatbots to ingest execution traces for online evaluations. AIP Chatbots were formerly called AIP Agents. The integration polls a Chatbot Studio session-log streaming dataset, groups exported rows into complete executions, and writes them to the Openlayer projects linked to your chatbots.

​
How it works

Once connected, Openlayer:
  1. Discovers your chatbots — walks Compass folders for AIP Chatbot files, or lets you register a chatbot by agent RID or filesystem path.
  2. Links Openlayer projects — enabling a chatbot links it to an Openlayer project and inference pipeline. By default, Openlayer creates an LLM project named Foundry AIP Agent - <name>.
  3. Syncs executions — periodic or manual sync polls the session-log stream and ingests completed executions for enabled chatbots whose agent_rid or owning_rid matches.
  4. Builds traces — Openlayer groups rows by traceId and maps chat messages, tool calls, outputs, and errors into structured traces.
Unknown chatbots are dropped rather than registered automatically. Incomplete traces remain pending until the stream includes a final_response or execution_error.
Cron sync uses the Chatbot Studio session-log dataset rather than AIP Agents v2 listSessions. That API only returns sessions for the calling user and originating client, so it does not expose Studio traffic from other users.

​
Prerequisites

Before connecting, you need:
  • A Foundry enrollment with at least one AIP Chatbot.
  • OAuth2 client credentials for a third-party application or a bearer token. The application or token needs api:aip-agents-read and api:filesystem-read, plus api:streams-read once you configure a session-log dataset RID.
  • An Org Admin-created Chatbot Studio session-log export using the Palantir JSON schema.
  • An Openlayer workspace where you are an admin.
Your enrollment URL must use HTTPS and contain only the hostname, such as https://example.palantirfoundry.com, with no path.

​
Create the session-log export

As a Foundry Org Admin:
  1. In Control Panel, select your organization.
  2. Open Log observability settings and click Create log export.
  3. Select the projects that contain the chatbots you want to monitor.
  4. Choose the Palantir JSON schema and create the streaming dataset.
  5. Copy the dataset RID. Allow up to five minutes for rows to appear.
Markings are not inherited by the exported dataset. Prompts and user input can appear in the stream, so configure the export’s projects and access controls appropriately.
Use Palantir JSON rather than OpenTelemetry protobuf for this integration.

​
Set up the integration

​
Step 1: Connect your enrollment

  1. In Openlayer, go to Settings → Integrations.
  2. Select Palantir Foundry AIP Agents.
  3. Under Connect, enter:
    • Enrollment URL — your HTTPS Foundry enrollment hostname with no path.
    • Authentication — select OAuth2 client credentials or Bearer token.
    • For OAuth2 client credentials, enter your Client ID and Client secret.
    • For Bearer token, enter your Bearer token.
    • Session-log dataset RID (optional) — the RID from your Org Admin’s log export.
    • Stream branch — the dataset branch, which defaults to master.
  4. Click Connect.
Openlayer verifies the hostname and selected credentials before saving the connection. Palantir Foundry connect
You can connect without entering the dataset RID, but session-log sync fails with a configuration error until you add it under Settings.
After connecting, Overview shows the selected Authentication method and, for OAuth2 client credentials, the Client ID.

​
Step 2: Discover or register chatbots

Click Discover agents to walk the Compass folders visible to your credentials for AIP Chatbot files. You can also click Register agent and provide either:
  • The agent RID from the Chatbot Studio URL.
  • A Foundry filesystem path, such as /Org/Project/My Agent.
Discovery only finds Compass files with the AIP_AGENTS_AGENT type. Palantir Foundry agents

​
Step 3: Enable chatbots

Click Enable for each chatbot you want to monitor. Openlayer links a project and inference pipeline, then starts ingesting matching executions. The Agents table shows each chatbot and its number of imported sessions. Enabled AIP Chatbot projects display a Foundry mark in the configured integrations and projects tables. To stop ingesting future traces for a chatbot, open its Agent options menu and select Disable. Existing traces remain available.

​
Step 4: Configure sync

Under Settings, enter the Session-log dataset RID and Stream branch, then click Save session log. Turn on Periodic sync to poll the stream every 15 minutes, or click Sync now to queue a manual sync. Periodic sync requires a dataset RID and the api:streams-read scope. Under Connection health, click Test connection to check your stored credentials. Openlayer reports invalid credentials, missing OAuth scopes, missing resource permissions, or Foundry availability problems separately.

​
Ingest a single session

The session-log stream is the primary sync source. If you have a gateway-originated session’s three identifiers, you can ingest that session directly:
  1. Open the chatbot row’s Agent options menu and select Ingest.
  2. Enter the Session RID and Session trace ID. The agent RID is already known from the chatbot row.
  3. Click Ingest.
This action uses getSessionTrace and only works when you have the IDs from the originating client. Palantir documents that these sessions expire after approximately 24 hours.

​
Trace mapping

Openlayer maps Palantir JSON session-log events as follows: Model, token, and cost data appear only when sibling language-model usage events share the same traceId. Chatbot events do not always include these usage events. Palantir Foundry trace

​
Disconnecting

To disconnect, open Settings → Integrations → Palantir Foundry AIP Agents and click Disconnect. Disconnecting stops session-log syncing and deletes registered agent records. Existing Openlayer traces are preserved.

​
Troubleshooting

Sync fails with a missing dataset RID. Configure Session-log dataset RID under Settings. A Foundry Org Admin must create the export with the Palantir JSON schema. No chatbots appear after discovery. Discovery only finds AIP_AGENTS_AGENT Compass files. Confirm that your credentials have api:filesystem-read and can see the folders containing your chatbots. You can also register a chatbot by RID or filesystem path. Test connection reports “Foundry rejected these credentials.” For OAuth2 client credentials, confirm the Client ID and Client secret. For bearer token authentication, confirm the Bearer token. Test connection reports “Missing OAuth scope.” Add the required scope to the third-party application. The integration requires api:aip-agents-read and api:filesystem-read, plus api:streams-read once you configure a session-log dataset RID. Test connection reports “Missing resource permissions.” Confirm that the Foundry service user can access the requested chatbot, filesystem, or session-log resource. Test connection reports “Could not reach Foundry.” Confirm that the enrollment URL is an available HTTPS hostname with no path, then try again. An enabled chatbot has zero traces. Confirm that the session-log export covers the chatbot’s project, uses the Palantir JSON schema, and has started receiving rows. The chatbot must be enabled, and executions remain pending until they include a final_response or execution_error. A single-session ingest is not ready. Confirm that getSessionTrace reports a complete session and that you entered the correct session trace ID. Path A sessions expire after approximately 24 hours.