Rescore a Beneficiary
Ask the Anton Engine for a fresh Payee-pillar risk evaluation of this beneficiary now, instead of waiting for the next scheduled cadence. Synchronous: on success the response carries the new and previous risk scores (0–1000 integers, higher is ALWAYS worse) and tiers.
Not the same as POST /v1/beneficiaries/{id}/rescreen, which runs
compliance screening (sanctions/PEP) rather than risk scoring.
Requires an Idempotency-Key header.
Authorizations
Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.
Headers
Unique key identifying this operation. Sending the same key twice returns the original response instead of creating a duplicate. Keys are retained for 24 hours.
255Path Parameters
^ben_[a-zA-Z0-9]+$Response
Rescore complete.
Result of a manual Payee-pillar rescore. Scores are 0–1000 integers
where higher is ALWAYS worse — the same orientation as risk_score
on the beneficiary resource. The previous_* fields are absent when
the engine had no prior evaluation on record.