Monitor operator judgment

Fetch one operator's JIS history, dimension breakdown, and decay projection.

Once you have scored a handful of interactions for a person, their judgment profile becomes readable. This guide shows how to pull it.

What this is

GET /v1/operator/:operator_id/profile returns the operator’s current JIS, per-dimension scores, classification band, sparkline history, and decay projection.

When to use

• Manager dashboards showing how one analyst is trending.
• Weekly one-on-one reviews.
• Triggering a maintenance recommendation when JIS drops below a threshold.

Minimum data

A valid JIS needs at least 50 scored interactions OR 10 days of monitoring, whichever comes first. Until then, the API returns the partial profile with minimum_data_met: false.

Fetch a profile

Python

profile = client.operator_profile(operator_id="analyst-42")

print(profile.jis, profile.band)
for dim, score in profile.dimensions.items():
    print(dim, score)

# JIS over time, suitable for a sparkline
for point in profile.jis_history:
    print(point.timestamp, point.jis)

TypeScript

const profile = await client.operatorProfile("analyst-42");

console.log(profile.jis, profile.band);
for (const [dim, score] of Object.entries(profile.dimensions)) {
  console.log(dim, score);
}

cURL

curl https://api.cohesionauth.com/v1/operator/analyst-42/profile \
  -H "X-API-Key: $COHESION_API_KEY"

Seven judgment dimensions

Classification bands

Errors you might see

Next step

• Aggregate across a whole team: organization oversight
• If a dimension is low, trigger intervention: maintain judgment quality
• Full endpoint: GET /v1/operator/:operator_id/profile