Run a check on a new caller-provided revision and compare it with a previous check

Static only. Idempotency-Key is required, and the credential needs checks:write and capabilities:write. Send the new snapshot, the same requirements, and previous.snapshot with its finished previous.report. The response carries the normal check report unchanged plus a separate revision_receipt. Exactlane re-evaluates the previous snapshot instead of trusting previous.report, and does not look up or depend on earlier issuance. The global previous-to-current comparison is authoritative; at most 32 changes are also evaluated in isolation, which cannot rule out interaction effects. Consumes one capability revision and one check. Request, report, runtime and quota limits are the same as for POST /v0/checks; the receipt is at most 16 KiB. There is no receipt lookup route. The caller owns CONTINUE, UPDATE_INTEGRATION, and HOLD.

post/v0/revision-checks

Request

  • Base URL: https://exactlane.dev (the document declares no server; this is the origin it was published from)
  • URL: https://exactlane.dev/v0/revision-checks
  • Auth: HTTP bearer

Headers

Idempotency-Keystring required

Required on POST /v0/agents, POST /v0/capabilities, POST /v0/checks, POST /v0/revision-checks, and POST /v0/usage-events. 8 to 128 visible ASCII characters without spaces. Same key plus same body replays; same key plus a changed body returns 409.

Request body

capability_keystring required
revision_labelstring required
source_kind'CALLER_PROVIDED' required

Response

Finished check report plus revision receipt; incomplete analysis is marked, never omitted

Changes

No recorded changes to this operation across all 1 revision of this API.