2026-09-29 Changes confirmed medium confidence

Palantir Adds Claude Opus 5.5 and Kimi K3 to AIP

Palantir's September model-catalog update gives eligible AIP customers new Claude and Kimi deployment paths, with access still controlled by enrollment and provider settings.

Edited by Tyronne Panaino

Palantir announced on September 29 that Claude Opus 5.5 is now available in its Artificial Intelligence Platform for eligible commercial customers and for US government enrollments at IL2 and IL4. The same official announcements page says Moonshot AI's Kimi K3 is now available in AIP through AWS Bedrock for eligible US georestricted and non-georestricted commercial enrollments.

The change matters to Palantir administrators and application teams because it expands the model choices that can be enabled inside an existing AIP environment. It does not establish that either model is enabled by default, suitable for every workload, or equivalent across every provider route. Palantir says an enrollment administrator must enable the relevant model family before teams can use it.

Claude Opus 5.5 arrives through several provider routes

For eligible commercial enrollments, Palantir lists four ways to enable Claude Opus 5.5: Anthropic direct, Google Vertex AI, AWS Bedrock, and Microsoft Azure. For US government IL2 and IL4 enrollments, the announced route is Claude through Google Vertex AI.

That distinction is operationally important. A model name alone does not describe the full deployment path. Provider availability, enrollment eligibility, administrative policy, and the model family already enabled in an organization can all determine whether the newly listed option is usable. Palantir's note therefore changes the supported catalog, but it does not remove the configuration work between an announcement and a working production deployment.

Kimi K3 has a narrower announced path

Palantir lists Kimi K3 through AWS Bedrock for US georestricted and non-georestricted commercial enrollments. The company directs administrators to enable the Moonshot AI and Bedrock model family before use. Unlike the Claude entry, the announcement does not list several provider routes or a US government enrollment path for Kimi K3.

For buyers comparing the two additions, that means availability should be checked at the enrollment level rather than inferred from the broader AIP catalog. The new listing may be relevant to teams that already use Bedrock, but the source does not show regional parity outside the named US enrollment types.

What the announcement does not prove

This is an availability update, not an independent evaluation. Palantir's page does not provide comparative benchmarks, workload results, latency measurements, security testing, data-governance analysis, or total-cost evidence for these deployments. It also tells customers to review token costs and pricing elsewhere rather than publishing prices in the announcement itself.

Those limits are why this article carries medium internal confidence despite relying on an official source. The source is authoritative for what Palantir has added to its catalog and which routes it lists, but it is an interested vendor and offers no independent validation of model quality or operational outcomes.

What to watch next

The next useful checkpoints are provider-specific pricing, region and enrollment expansion, feature parity between the Claude routes, and evidence from real AIP workloads. Administrators should also verify which model family is enabled in their own enrollment before planning a migration or changing an existing application's model.

Status

Confirmed. Palantir's official announcements page documents both additions and their stated enrollment paths. Confidence is medium because no independent deployment or performance evidence was fetched.