Triggers an on-demand recomputation of the trust score for a specific agent. The score is derived from multiple weighted factors including anomaly rate, uptime history, delegation depth, and receipt volume. Use this endpoint after a significant event (key rotation, policy violation, attestation burst) to ensure the score reflects the agent’s current posture. Trust scores range fromDocumentation Index
Fetch the complete documentation index at: https://docs.truthlocks.com/llms.txt
Use this file to discover all available pages before exploring further.
0.0 (no trust) to 1.0 (full trust) and are used by policy engines, witness selection, and delegation gates across the platform.
Authentication
RequiresX-API-Key header or Bearer JWT token. Tenant-scoped via X-Tenant-ID.
Path Parameters
The unique identifier of the machine agent whose trust score should be
recomputed. Format:
maip-agent:ULID.Request Body
When
true, the response includes the full factor history used during
computation. Useful for debugging score changes but increases response size.Response
The agent identifier that was scored.
The computed trust score as a float between
0.0 and 1.0.Breakdown of the individual factors that contributed to the score.
ISO 8601 timestamp of when the computation completed.
Score Factor Weights
| Factor | Weight | Description |
|---|---|---|
anomaly_rate | 30% | Penalizes agents with high anomaly ratios |
uptime | 25% | Rewards consistent availability |
delegation_depth | 20% | Deeper chains reduce trust proportionally |
receipt_count | 25% | More receipts indicate established history |

