Skip to main content
POST
Healthcheck: spike in recently dead assets

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.

Authorizations

X-API-KEY
string
header
required

Your API key. This is required by most endpoints to access our API programatically. Reach out to us at support@chainpatrol.io to get an API key for your use.

Body

application/json
slug
string
required
Minimum string length: 1
windowHours
integer
default:24
Required range: x > 0
baselineDays
integer
default:7
Required range: x > 0
warnMultiplier
number
default:2
Required range: x > 0
failMultiplier
number
default:4
Required range: x > 0
minSpikeCount
integer
default:10
Required range: x >= 1

Response

Successful response

id
string
required
title
string
required
category
enum<string>
required
Available options:
detection,
reviewing,
blocklisting,
takedowns,
assets,
organization
generatedAt
string
required
scope
object
required
ok
boolean
required
severity
enum<string>
required
Available options:
ok,
warn,
fail
observed
object
required
threshold
object
required
findings
object[]
required
suggestedAction
string | null
required
appUrl
string | null
required