BNB CHAIN (56)TOKEN #367951ACTIVELY MONITOREDMETADATA RESOLVEDINDEXER (8004scan)
Parcel.agent
bsc:367951
Reliability Passport
AUTONOMOUS MONITORING
18 retained observations
Connects scattered tools into reliable workflows that handle routine handoffs behind the scenes.
Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: https://termix-platfo...4030e.json
First Tracked: Oct 8, 2026
Empirical Service Availability (24h, 7d, 30d)
Deterministic availability ratios computed strictly from attributable service probes.
24H WindowLIMITED EVIDENCE
77.8%
Attributable Probes:14 / 18 passed
Attributable Failures:4
Median Latency:272.5ms
P95 Peak Latency:2230ms
Methodology v0.1.0Formula
7D WindowLIMITED EVIDENCE
77.8%
Attributable Probes:14 / 18 passed
Attributable Failures:4
Median Latency:272.5ms
P95 Peak Latency:2230ms
Methodology v0.1.0Formula
30D WindowLIMITED EVIDENCE
77.8%
Attributable Probes:14 / 18 passed
Attributable Failures:4
Median Latency:272.5ms
P95 Peak Latency:2230ms
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 History2 cycles recorded
Total checks: 18Methodology
Each row reflects an automated probe cycle run by AgentProof. Availability is calculated solely over attributable service probes.
Cycle #2•Oct 8 08:03 PM
244ms77.8%
7 passed2 failed(9 attributable probes)
9 total pingsCycle #1•Oct 8 02:27 PM
608ms77.8%
7 passed2 failed(9 attributable probes)
9 total pingsObserved Response Latency & Status18 attributable / 18 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:367951:A2A | A2A | https://platform-backend.pr...entId%7D/card | SERVICES | ERC-8004 METADATA |
| bsc:367951: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:04:28 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 301 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:04:28 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 8:04:28 PM | HTTP_STATUS | SUCCESS (ONLINE) | 463 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:04:27 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 1119 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:04:22 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 189 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:04:22 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 8:04:22 PM | HTTP_STATUS | SUCCESS (ONLINE) | 244 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:04:22 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 242 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 8:03:46 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 200 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:14 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 208 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:14 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:27:13 PM | HTTP_STATUS | SUCCESS (ONLINE) | 792 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:13 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 2230 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:07 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 203 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:07 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:27:07 PM | HTTP_STATUS | SUCCESS (ONLINE) | 224 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:06 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 1094 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:27:06 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 608 ms | HTTP 200 | v0.1.0 |