> ## Documentation Index > Fetch the complete documentation index at: https://chainpatrol.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Dead Asset Spike > Compares the count of `DETECTED_AS_DEAD` LivenessStatusEvent rows in the current window against the baseline rate from the prior `baselineDays`. Severity fires only when the current count clears `minSpikeCount` (suppresses noise when the org has near-zero baseline activity) and exceeds the configured multiplier. Useful for catching liveness-checker regressions after platform changes (captcha rollouts, anti-bot updates) which falsely mark live assets as dead. ## Overview Compares the count of assets detected as dead in the current window against the baseline rate from the prior `baselineDays`. Severity fires only when the current count clears `minSpikeCount` and exceeds the configured multiplier, which suppresses noise for organizations with near-zero baseline activity. ## When this fires A spike is useful for catching liveness-checker regressions after platform changes — captcha rollouts or anti-bot updates, for example — which can falsely mark live assets as dead. ## OpenAPI ````yaml POST /healthchecks/assets/dead-asset-spike openapi: 3.0.3 info: title: ChainPatrol External API - OpenAPI 3.0 description: ChainPatrol External API documentation version: 2.0.0 servers: - url: https://app.chainpatrol.io/api/v2 security: [] tags: - name: asset - name: report externalDocs: url: https://chainpatrol.com/docs paths: /healthchecks/assets/dead-asset-spike: post: tags: - healthchecks summary: 'Healthcheck: spike in recently dead assets' description: >- Compares the count of `DETECTED_AS_DEAD` LivenessStatusEvent rows in the current window against the baseline rate from the prior `baselineDays`. Severity fires only when the current count clears `minSpikeCount` (suppresses noise when the org has near-zero baseline activity) and exceeds the configured multiplier. Useful for catching liveness-checker regressions after platform changes (captcha rollouts, anti-bot updates) which falsely mark live assets as dead. operationId: healthchecksAssetsDeadAssetSpike requestBody: required: true content: application/json: schema: type: object properties: slug: type: string minLength: 1 windowHours: type: integer minimum: 0 exclusiveMinimum: true default: 24 baselineDays: type: integer minimum: 0 exclusiveMinimum: true default: 7 warnMultiplier: type: number minimum: 0 exclusiveMinimum: true default: 2 failMultiplier: type: number minimum: 0 exclusiveMinimum: true default: 4 minSpikeCount: type: integer minimum: 1 default: 10 required: - slug responses: '200': description: Successful response content: application/json: schema: type: object properties: id: type: string title: type: string category: type: string enum: - detection - reviewing - blocklisting - takedowns - assets - organization generatedAt: type: string scope: type: object properties: slug: type: string nullable: true required: - slug ok: type: boolean severity: type: string enum: - ok - warn - fail observed: type: object additionalProperties: nullable: true anyOf: - type: number - type: string - type: boolean threshold: type: object additionalProperties: nullable: true anyOf: - type: number - type: string - type: boolean findings: type: array items: type: object properties: kind: type: string ref: type: string nullable: true message: type: string severity: type: string enum: - warn - fail required: - kind - ref - message - severity suggestedAction: type: string nullable: true appUrl: type: string nullable: true required: - id - title - category - generatedAt - scope - ok - severity - observed - threshold - findings - suggestedAction - appUrl '400': description: Invalid input data content: application/json: schema: $ref: '#/components/schemas/error.BAD_REQUEST' '401': description: Authorization not provided content: application/json: schema: $ref: '#/components/schemas/error.UNAUTHORIZED' '403': description: Insufficient access content: application/json: schema: $ref: '#/components/schemas/error.FORBIDDEN' '500': description: Internal server error content: application/json: schema: $ref: '#/components/schemas/error.INTERNAL_SERVER_ERROR' security: - ApiKey: [] components: schemas: error.BAD_REQUEST: type: object properties: message: type: string description: The error message example: Invalid input data code: type: string description: The error code example: BAD_REQUEST issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Invalid input data error (400) description: The error information example: code: BAD_REQUEST message: Invalid input data issues: [] error.UNAUTHORIZED: type: object properties: message: type: string description: The error message example: Authorization not provided code: type: string description: The error code example: UNAUTHORIZED issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Authorization not provided error (401) description: The error information example: code: UNAUTHORIZED message: Authorization not provided issues: [] error.FORBIDDEN: type: object properties: message: type: string description: The error message example: Insufficient access code: type: string description: The error code example: FORBIDDEN issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Insufficient access error (403) description: The error information example: code: FORBIDDEN message: Insufficient access issues: [] error.INTERNAL_SERVER_ERROR: type: object properties: message: type: string description: The error message example: Internal server error code: type: string description: The error code example: INTERNAL_SERVER_ERROR issues: type: array items: type: object properties: message: type: string required: - message description: An array of issues that were responsible for the error example: [] required: - message - code title: Internal server error error (500) description: The error information example: code: INTERNAL_SERVER_ERROR message: Internal server error issues: [] securitySchemes: ApiKey: type: apiKey in: header name: X-API-KEY description: >- Your API key. This is required by most endpoints to access our API programatically. Reach out to us at [support@chainpatrol.io](mailto:support@chainpatrol.io?subject=Re:%20API%20Key%20for%20SDK&body=Company:%20%0AName:%20%0APurpose:%20) to get an API key for your use. ````