# Circuit breaker and webhook timing APIs

## Circuit Breaker Transition Audit API

Check a supplied circuit breaker trace for disconnected states, invalid edges and early probes. Use whole milliseconds on one clock and supply transitions in recorded order. The model allows closed to open, open to half-open, and half-open to closed or open. A half-open probe meets the minimum when elapsed time since a connected opening is at least the supplied value. If that opening cannot be established, the elapsed result is null and the report flags the missing evidence. The reported final state is the last recorded destination. This check evaluates the supplied trace without operating a live circuit breaker. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

[Request example](circuit-breaker-transition-audit.request.example.json) · [Input schema](circuit-breaker-transition-audit.input.schema.json) · [Result schema](circuit-breaker-transition-audit.result.schema.json)

## Webhook Timestamp Window Audit API

Compare recorded webhook timestamps with a caller-defined receipt-time window. Supply Unix epoch milliseconds, a maximum age, an allowed future skew and up to 120 deliveries with unique opaque labels. Use null for a missing timestamp. Signed age is receipt time minus the supplied timestamp. A negative age means the timestamp is ahead of receipt. Values equal to either tolerance are within the window. Provide normalized timestamps only, without headers, signatures or secrets. This evaluates timing evidence without authenticating messages or checking replay state. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.

[Request example](webhook-timestamp-window-audit.request.example.json) · [Input schema](webhook-timestamp-window-audit.input.schema.json) · [Result schema](webhook-timestamp-window-audit.result.schema.json)

Per job, USD 9.00 once. Save your private JSON result within its 30-day access period.
Requests accept at most 36,000 UTF-8 input bytes. Send only authorized, non-sensitive records.

Use the existing [agent checkout guide](https://gatewayinformationgroup.com/developers) to prepare a quote, pay and retrieve the private result.