SCIM 2.0

How it was measured

Two gradings per operation. `normative_force` is what RFC 7644 says, quoted. `tier` is what the industry declares, measured the same way as every other profile here. The gap between them is the point.

The core tier

What a provider has to implement before a compatibility claim means anything. Every placement is measured, and the evidence for each sits in the tier profile.

GET /UsersPOST /UsersGET /Users/{id}PUT /Users/{id}DELETE /Users/{id}

Adopters

Every entry in the registry carries the URL it was read from and the date it was read. A claim is never promoted to a verdict.

Providers that reach a tier

32 of the 320 recorded adopters demonstrably reach the core tier or better. The 24 below link to their catalog pages; the registry and matrix carry the rest.

ActivTrakAmerican Express Global Business TravelAmplitudeAPIs.io Engineering PlatformAuthenticxBeyond IdentityCventCvent Event CloudCvent RegistrationCyberArk IdentityDataStaxEnvianceFactsetGitHubHugging Face TransformersInductive AutomationKiteworksLightdashMaltOpenMetadataReclaim.aiRingCentralRiotSAP BI Tools

Artifacts

Everything this standard publishes. All of it is generated from the profile, so a re-measurement moves every artifact together.

Source