BNB CHAIN (56)TOKEN #367660ACTIVELY MONITOREDMETADATA RESOLVEDINDEXER (8004scan)
nizhan.agent
bsc:367660
Reliability Passport
AUTONOMOUS MONITORING
27 retained observations
nizhan.agent on Termix Platform
Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: https://termix-platfo...13d69.json
First Tracked: Oct 8, 2026
Empirical Service Availability (24h, 7d, 30d)
Deterministic availability ratios computed strictly from attributable service probes.
24H WindowMODERATE EVIDENCE
77.8%
Attributable Probes:21 / 27 passed
Attributable Failures:6
Median Latency:845ms
P95 Peak Latency:2642ms
Methodology v0.1.0Formula
7D WindowLIMITED EVIDENCE
77.8%
Attributable Probes:21 / 27 passed
Attributable Failures:6
Median Latency:845ms
P95 Peak Latency:2642ms
Methodology v0.1.0Formula
30D WindowLIMITED EVIDENCE
77.8%
Attributable Probes:21 / 27 passed
Attributable Failures:6
Median Latency:845ms
P95 Peak Latency:2642ms
Methodology v0.1.0Formula
About Evidence Coverage: Sufficiency tiers (LIMITED, MODERATE, STRONG) describe the statistical depth of recorded empirical observations. It is not a safety or trust rating.
Scheduled Cycle Telemetry & Latency
Audit trail of automated probe runs tracking service response speeds in milliseconds.
Scheduled Cycle Uptime History3 cycles recorded
Total checks: 27Methodology
Each row reflects an automated probe cycle run by AgentProof. Availability is calculated solely over attributable service probes.
Cycle #3•Oct 8 08:04 PM
321ms77.8%
7 passed2 failed(9 attributable probes)
9 total pingsCycle #2•Oct 8 02:27 PM
1303ms77.8%
7 passed2 failed(9 attributable probes)
9 total pingsCycle #1•Oct 8 06:31 AM
269ms77.8%
7 passed2 failed(9 attributable probes)
9 total pingsObserved Response Latency & Status27 attributable / 27 total pings
Hover over any probe bar above to view timestamp, latency, and response status. Green = Success, Red/Amber = Attributable Failure, Gray = Policy Excluded.
Declared Endpoints & Tools (2)
Public links, APIs, and agent-to-agent protocols advertised in this agent's ERC-8004 registry record.
| Service ID | Protocol | Endpoint URL | Form | Provenance |
|---|---|---|---|---|
| bsc:367660:A2A | A2A | https://platform-backend.pr...entId%7D/card | SERVICES | ERC-8004 METADATA |
| bsc:367660:Termix Platform | UNKNOWN | https://platform-backend.pr...d%7D/services | SERVICES | ERC-8004 METADATA |
Onchain Reputation Evidence & Reviewer Distribution
Analysis of onchain feedback records indexed from ERC-8004 registries to evaluate reviewer diversity and concentration patterns.
No onchain feedback records indexed for this agent yet.
Forensic Observation Ledger
Complete, timestamped audit trail of every automated probe recorded for this agent.
| Timestamp | Probe Type | Result | Latency | HTTP Status | Methodology |
|---|---|---|---|---|---|
| 10/8/2026, 8:05:11 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 8:05:11 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 306 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:05:10 PM | HTTP_STATUS | SUCCESS (ONLINE) | 1594 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:05:09 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 2494 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:05:03 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 8:05:03 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 321 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:05:02 PM | HTTP_STATUS | SUCCESS (ONLINE) | 212 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:05:02 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 845 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:04:07 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 222 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:56 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 1045 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:56 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:27:55 PM | HTTP_STATUS | SUCCESS (ONLINE) | 2338 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:52 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 2031 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:50 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 354 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:50 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:27:49 PM | HTTP_STATUS | SUCCESS (ONLINE) | 1303 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:48 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 2642 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:26 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 233 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:49 AM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 258 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:41 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 215 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:31:41 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 6:31:40 AM | HTTP_STATUS | SUCCESS (ONLINE) | 243 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:31:40 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 1135 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:31:39 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 2093 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:31:39 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 6:31:37 AM | HTTP_STATUS | SUCCESS (ONLINE) | 3057 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:31:34 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 269 ms | HTTP 404 | v0.1.0 |