Operations

Service status

The live check below reports whether Warden answered this browser now. Build, benchmark, and marketplace facts are dated separately.

Current API reachability

UNKNOWN · health check not completed

API reachabilityUnknown until checked
Checked at
API versionUnknown until checked
Corpus entriesUnknown until checked
Analyzers loadedUnknown until checked
Historical uptimeNot measured

Historical uptime is not measured by this page. A successful check establishes only that the API answered this browser at the displayed instant.

Readiness objective and measurement

99.5% application-readiness objective

Every five minutes, the scheduled monitor checks application readiness and requests an unsigned /scan payment challenge. The 99.5% objective applies to Warden's application readiness. Challenge generation is reported separately and does not establish payment settlement or facilitator uptime.

UNKNOWN · readiness evidence not loaded

Monitor stateEvidence not loaded
Evidence windowEvidence not loaded
Application availabilityNot measured until evidence qualifies
Unsigned x402 challenge-generation readinessEvidence not loaded
Latest two-signal probeEvidence not loaded
Latest application probeEvidence not loaded
Latest unsigned challenge probeEvidence not loaded
Build, benchmark, marketplace, and payment evidence

Source ledger

Live and dated evidence stay separate

UNKNOWN · dated build metadata not loaded

Live API source
GET /health · checked at the exact time above
Build metadata verified
Dated metadata not loaded
Marketplace listing verified
Dated metadata not loaded
Repository tests verified
Dated metadata not loaded

Dated marketplace snapshot

Listing and service state

These values were verified from the public OKX.AI listing and committed as static metadata. They are not polled from OKX on each page load.

UNKNOWN · marketplace snapshot not loaded

Provider agentDated metadata not loaded
Listing statusDated metadata not loaded
Service IDsDated metadata not loaded
Repository tests passedDated metadata not loaded

Repository verification note is unavailable until dated metadata loads.

Deterministic corpus version

Byte-level build identity

The fingerprint is SHA-256 over the attack corpus bytes followed by the benign corpus bytes. It identifies the exact two corpus files represented by this build.

UNKNOWN · corpus fingerprint not loaded

Fingerprint
Dated fingerprint not loaded
Reason-code contract
Open the current reference
Decision states
ALLOW / SANITIZE / BLOCK

Measured security · dated benchmark

Held-out recall, with the misses left visible.

Attack success requires a non-ALLOW decision with the expected threat class. Any non-ALLOW decision on the held-out benign set is a false positive. These authored cases are excluded from the scanner's training corpus and similarity examples.

UNKNOWN · evaluation snapshot not loaded

Attack recallEvaluation snapshot not loaded
Attacks detectedEvaluation snapshot not loaded
Benign false positivesEvaluation snapshot not loaded
False-positive rateEvaluation snapshot not loaded
Measured atEvaluation snapshot not loaded
Evaluation modeEvaluation snapshot not loaded

Payment evidence boundary

Address activity is not an order receipt.

The address explorer link does not contain transaction-specific proof that a payment bought a Warden service.

UNKNOWN · payment evidence metadata not loaded