A replay probe stores a canonical invocation and assertions against its result. The first successful run can establish a baseline; later runs detect divergence.
In Monitors, select a source that supports replay and define:
- a clear probe name;
- the HTTP or MCP invocation;
- deterministic assertions;
- whether the request is sensitive;
- whether scheduled runs are active.
Assertions can cover required fields, response shape, content hashes, and latency boundaries. Avoid assertions over volatile values such as request IDs or timestamps.
Sensitive probes
Set sensitive when the payload may contain private data. Lucim redacts the stored request view and retains minimized shape/hash and assertion outcomes rather than raw response values.
Run and inspect
Trigger an existing probe through REST:
List divergences:
Use a small set of contract-relevant probes. A stable behavior check is more useful than broad snapshotting of volatile responses.
