Parity

Measured coverage, published per release.

Evidence you can read.

Every PAL release records the upstream baseline it was built against, publishes an API Compatibility Manifest, and verifies each build against that baseline before release.

Request access

View licensing

Change caught

Current build

Compatibility gate

A response field changed on the Orchestration build endpoint upstream. The parity gate caught it and the typed client was regenerated to match before publication.

capability

orchestration

declared

supported

baseline

2026-09-18

changed

1 endpoint

Recorded in the manifest

Published with the build

Change caught

Current build

Compatibility gate

A response field changed on the Orchestration build endpoint upstream. The parity gate caught it and the typed client was regenerated to match before publication.

capability

orchestration

declared

supported

baseline

2026-09-18

changed

1 endpoint

Recorded in the manifest

Published with the build

A recorded baseline, per release.

PAL pins the exact upstream API surface each release was validated against, so you can tell precisely what changed between two versions.

Capability readiness

/ 100

Scope:

Foundry

AIP

Score breakdown

Endpoint coverage

92% of declared surface

Contract tests

all green on baseline

Schema stability

surface matched

Preview endpoints

excluded from guarantees

Capability readiness

/ 100

Scope:

Foundry

AIP

Score breakdown

Endpoint coverage

92% of declared surface

Contract tests

all green on baseline

Schema stability

surface matched

Preview endpoints

excluded from guarantees

Status, declared per capability.

Every capability carries its own state: supported, partial, preview or unsupported. Each status is recorded in the manifest and published with the release.

Most SDKs tell you what they support. PAL shows you the evidence.

Coverage · last 5 releases

Tracking

Baseline re-recorded on every release

T-4

T-3

T-2

T-1

Now

A baseline recorded per release.

Each PAL build captures the exact upstream API surface it was validated against, so any change between two versions is explicit and auditable.

Every capability given a declared status.

Supported, partial, preview or unsupported. Statuses are recorded in the manifest and published in the documentation.

Upstream changes caught before release.

Release gates compare each build against the recorded baseline, so upstream changes are caught in the pipeline and resolved before a customer deployment.

A baseline recorded per release.

Each PAL build captures the exact upstream API surface it was validated against, so any change between two versions is explicit and auditable.

Coverage · last 5 releases

Tracking

Baseline re-recorded on every release

T-4

T-3

T-2

T-1

Now

Every capability given a declared status.

Supported, partial, preview or unsupported. Statuses are recorded in the manifest and published in the documentation.

Surface comparison · Ranked by impact

Removed response field

Critical

orchestration/builds

contract change

New optional parameter

Medium

datasets/read

additive change

Documentation-only update

Low

functions/execute

contract unchanged

Upstream changes caught before release.

Release gates compare each build against the recorded baseline, so upstream changes are caught in the pipeline and resolved before a customer deployment.

Release gate · Compatibility

Active

change

contract

coverage

100%

and

the following:

baseline

mismatched

manifest

recorded

then

flag build

Pipeline

regenerate client

Manifest

record finding

A baseline recorded per release.

Each PAL build captures the exact upstream API surface it was validated against, so any change between two versions is explicit and auditable.

Coverage · last 5 releases

Tracking

Baseline re-recorded on every release

T-4

T-3

T-2

T-1

Now

Every capability given a declared status.

Supported, partial, preview or unsupported. Statuses are recorded in the manifest and published in the documentation.

Surface comparison · Ranked by impact

Removed response field

Critical

orchestration/builds

contract change

New optional parameter

Medium

datasets/read

additive change

Documentation-only update

Low

functions/execute

contract unchanged

Upstream changes caught before release.

Release gates compare each build against the recorded baseline, so upstream changes are caught in the pipeline and resolved before a customer deployment.

Release gate · Compatibility

Active

change

contract

coverage

100%

and

the following:

baseline

mismatched

manifest

recorded

then

flag build

Pipeline

regenerate client

Manifest

record finding

Connect. With intent.

Request access

Features

Company

Resources

Connect

AIC

All release gates passing

VERIFIED COVERAGE

Compatibility updates by email.

Terms and Conditions

PAL is an independent product of AIC Professional Services UK Ltd. Palantir, Foundry and AIP are trademarks of Palantir Technologies Inc. PAL is not affiliated with, endorsed by, or sponsored by Palantir Technologies Inc.

Features

Resources

Pricing

About us

Features

Resources

Pricing

About us

Measured coverage, published per release.

Evidence you can read.

A recorded baseline, per release.

Status, declared per capability.

Most SDKs tell you what they support. PAL shows you the evidence.

A baseline recorded per release.

Every capability given a declared status.

Upstream changes caught before release.

A baseline recorded per release.

Every capability given a declared status.

Upstream changes caught before release.

A baseline recorded per release.

Every capability given a declared status.

Upstream changes caught before release.

Connect. With intent.