Home / Products / PAL.NET

PAL.NET: a typed .NET access layer for Foundry and AIP.

Build applications against supported Palantir Foundry services, AIP and your customer’s Ontology using a licensed SDK with strongly typed contracts and a published compatibility approach.

05

PAL.NET SDK for Palantir Foundry and AIP - AICIsolated developer pathway from .NET application to PAL.NET to supported Palantir services with licensed SDK annotation.Illustrative developer pathwayPLATE 01010203INDEX / MODEDEVELOPER.NET applicationPAL.NETSupported Palantir servicesLicensed .NET SDKSeparate developer laneInterfaces and deployment scope requireconfirmation.

For .NET engineers and platform owners

Hand-built clients accumulate request-shape changes, inconsistent error handling and model-specific maintenance. PAL.NET is a licensed, closed-source developer SDK. It runs inside the customer’s application estate and provides typed access to supported services. It is not an analyst workspace or the operating layer for CORTEX, NERVE and GTK.

Platform services and customer Ontology

The platform surface covers supported Foundry and AIP services. The Ontology surface supports generated C# contracts when the model is known and dynamic, metadata-driven access when its shape is established at runtime. Confirm the exact service and Ontology operations required by your application against the supplied support list.

Versioning and API compatibility

AIC publishes an API Compatibility Manifest approach. Ask which service versions, operations and model-generation workflows are covered by the proposed SDK release. Plan the upgrade and regression tests before adopting the SDK. The official description targets .NET 10; confirm your target framework and release entitlement with the product team.

Application conventions

The official product description specifies async-first contracts, immutable payload records and cancellation-token support. Evaluate cancellation during a long-running call, errors from unavailable services and authentication expiry. Credential handling and transport policy follow the host platform and customer deployment decisions.

Licensing and distribution

Distribution uses authenticated private NuGet feeds or licensed offline bundles, subject to contractual entitlement. Offline package distribution does not make Foundry or AIP available without their own platform dependencies. Confirm licence checks, update access, restricted-network installation and support scope before the proof of concept.

Evaluation questions

Does the compatibility manifest cover your required operations? Can generated contracts represent the customer’s model? How are schema changes and cancellation handled? What licences and platform permissions are required? Palantir and Foundry are third-party trademarks; no partnership or endorsement is implied.