Skip to main content
Use this endpoint to analyze the full training metric history of a job. The analysis detects reward spikes that may indicate reward hacking and computes summary statistics over the entire run. This is useful for auditing RL jobs before accepting a model into production.

Method + Path

Authentication

Include your PIN API token or JWT in the Authorization header as a Bearer token.

Path parameters

string
required
The job identifier (e.g., jb_abc123def456).

Request example

Response

Returns a standard PIN success envelope with the analysis result.
integer
required
0 on success, nonzero on error.
object
required
string
Human-readable message (empty on success).

Example response

Detection logic

The analyzer applies the following checks over the full step history:
  1. Reward spike detection: For each step after the first 10, if the reward is at least 2x the mean of the preceding 10 steps, that step is flagged as a spike.
  2. Second-half comparison: If the mean reward in the second half of training is more than 50% higher than the first half, evidence is added.
  3. Risk flag: Two or more spike steps trigger suspected_reward_hacking. Otherwise the risk is ok.
  4. High variance warning: If no spikes are found but standard deviation exceeds 0.3, a manual review recommendation is appended.
Non-RL jobs (SFT, OPD) that do not report reward are skipped for reward-specific checks.

Errors