Back to Agents Directory
BNB CHAIN (56)TOKEN #367664ACTIVELY MONITOREDMETADATA RESOLVEDINDEXER (8004scan)

nurudeenagbabi1.agent

bsc:367664
Reliability Passport
AUTONOMOUS MONITORING
27 retained observations

nurudeenagbabi1.agent on Termix Platform

Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: https://termix-platfo...9482a.json
First Tracked: Oct 8, 2026

Empirical Service Availability (24h, 7d, 30d)

Deterministic availability ratios computed strictly from attributable service probes.

Methodology & Formulas →
77.8%
Attributable Probes:21 / 27 passed
Attributable Failures:6
Median Latency:421ms
P95 Peak Latency:2687ms
Methodology v0.1.0Formula
77.8%
Attributable Probes:21 / 27 passed
Attributable Failures:6
Median Latency:421ms
P95 Peak Latency:2687ms
Methodology v0.1.0Formula
77.8%
Attributable Probes:21 / 27 passed
Attributable Failures:6
Median Latency:421ms
P95 Peak Latency:2687ms
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:03 PM
201ms77.8%
7 passed2 failed(9 attributable probes)
9 total pings
Cycle #2•Oct 8 02:27 PM
223ms77.8%
7 passed2 failed(9 attributable probes)
9 total pings
Cycle #1•Oct 8 06:31 AM
828ms77.8%
7 passed2 failed(9 attributable probes)
9 total pings
Observed Response Latency & Status27 attributable / 27 total pings
Measured Availability: 77.8%(21/27)
Median: 421ms
P95: 2687ms
How calculated?
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 IDProtocolEndpoint URLFormProvenance
bsc:367664:A2AA2Ahttps://platform-backend.pr...entId%7D/cardSERVICESERC-8004 METADATA
bsc:367664:Termix PlatformUNKNOWNhttps://platform-backend.pr...d%7D/servicesSERVICESERC-8004 METADATA

Onchain Reputation Evidence & Reviewer Distribution

Analysis of onchain feedback records indexed from ERC-8004 registries to evaluate reviewer diversity and concentration patterns.

Reputation Methodology →
No onchain feedback records indexed for this agent yet.

Forensic Observation Ledger

Complete, timestamped audit trail of every automated probe recorded for this agent.

TimestampProbe TypeResultLatencyHTTP StatusMethodology
10/8/2026, 8:04:47 PMRESPONSE_LATENCYSUCCESS (ONLINE)187 msHTTP 404v0.1.0
10/8/2026, 8:04:47 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 8:04:47 PMHTTP_STATUSSUCCESS (ONLINE)185 msHTTP 404v0.1.0
10/8/2026, 8:04:46 PMSERVICE_REACHABILITYSUCCESS (ONLINE)185 msHTTP 404v0.1.0
10/8/2026, 8:04:45 PMRESPONSE_LATENCYSUCCESS (ONLINE)235 msHTTP 404v0.1.0
10/8/2026, 8:04:45 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 8:04:45 PMHTTP_STATUSSUCCESS (ONLINE)1135 msHTTP 404v0.1.0
10/8/2026, 8:04:44 PMSERVICE_REACHABILITYSUCCESS (ONLINE)2440 msHTTP 404v0.1.0
10/8/2026, 8:03:56 PMMETADATA_RESOLUTIONSUCCESS (ONLINE)201 msHTTP 200v0.1.0
10/8/2026, 2:27:25 PMRESPONSE_LATENCYSUCCESS (ONLINE)240 msHTTP 404v0.1.0
10/8/2026, 2:27:25 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:27:25 PMHTTP_STATUSSUCCESS (ONLINE)1248 msHTTP 404v0.1.0
10/8/2026, 2:27:23 PMSERVICE_REACHABILITYSUCCESS (ONLINE)2891 msHTTP 404v0.1.0
10/8/2026, 2:27:16 PMRESPONSE_LATENCYSUCCESS (ONLINE)199 msHTTP 404v0.1.0
10/8/2026, 2:27:16 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:27:16 PMHTTP_STATUSSUCCESS (ONLINE)223 msHTTP 404v0.1.0
10/8/2026, 2:27:16 PMMETADATA_RESOLUTIONSUCCESS (ONLINE)202 msHTTP 200v0.1.0
10/8/2026, 2:27:16 PMSERVICE_REACHABILITYSUCCESS (ONLINE)190 msHTTP 404v0.1.0
10/8/2026, 6:31:23 AMRESPONSE_LATENCYSUCCESS (ONLINE)561 msHTTP 404v0.1.0
10/8/2026, 6:31:23 AMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 6:31:22 AMHTTP_STATUSSUCCESS (ONLINE)828 msHTTP 404v0.1.0
10/8/2026, 6:31:21 AMSERVICE_REACHABILITYSUCCESS (ONLINE)2400 msHTTP 404v0.1.0
10/8/2026, 6:31:13 AMRESPONSE_LATENCYSUCCESS (ONLINE)421 msHTTP 404v0.1.0
10/8/2026, 6:31:13 AMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 6:31:13 AMHTTP_STATUSSUCCESS (ONLINE)933 msHTTP 404v0.1.0
10/8/2026, 6:31:12 AMSERVICE_REACHABILITYSUCCESS (ONLINE)2687 msHTTP 404v0.1.0
10/8/2026, 6:31:10 AMMETADATA_RESOLUTIONSUCCESS (ONLINE)681 msHTTP 200v0.1.0