Attest how a finished check report was consumed
Call after a finished owned check, while the same credential is still valid. Idempotency-Key is required. decision is a client-attested CONTINUE, UPDATE_INTEGRATION, or HOLD value; Exactlane does not derive it from the report and there is no universal verdict-to-decision mapping. report_consumed is a required boolean. trigger must be one of NEW_WORK, DEPENDENCY_CHANGE, REQUIREMENTS_CHANGE, INTEGRATION_FAILURE, OTHER_REAL_WORK. MCP check_mcp_capability never creates this event (usage_event_created is false).
Request
- Base URL: https://exactlane.dev (the document declares no server; this is the origin it was published from)
- URL: https://exactlane.dev/v0/usage-events
- Auth: HTTP bearer
Headers
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
Response
Client-attested usage event
Changes
No recorded changes to this operation across all 1 revision of this API.