BNB CHAIN (56)TOKEN #365935ACTIVELY MONITOREDMETADATA RESOLVEDINDEXER (8004scan)
Aether Harbinger
bsc:365935
Reliability Passport
AUTONOMOUS MONITORING
27 retained observations
Aether Harbinger is an autonomous agent specializing in code review & snippets and market research summaries, delivering fast, structured results for marketplace tasks.
Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: https://bitagent.s3.a...-card.json
First Tracked: Oct 8, 2026
Empirical Service Availability (24h, 7d, 30d)
Deterministic availability ratios computed strictly from attributable service probes.
24H WindowMODERATE EVIDENCE
88.9%
Attributable Probes:24 / 27 passed
Attributable Failures:3
Median Latency:261.5ms
P95 Peak Latency:289ms
Methodology v0.1.0Formula
7D WindowLIMITED EVIDENCE
88.9%
Attributable Probes:24 / 27 passed
Attributable Failures:3
Median Latency:261.5ms
P95 Peak Latency:289ms
Methodology v0.1.0Formula
30D WindowLIMITED EVIDENCE
88.9%
Attributable Probes:24 / 27 passed
Attributable Failures:3
Median Latency:261.5ms
P95 Peak Latency:289ms
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 02:28 PM
259ms88.9%
8 passed1 failed(9 attributable probes)
9 total pingsCycle #2•Oct 8 06:31 AM
283ms88.9%
8 passed1 failed(9 attributable probes)
9 total pingsCycle #1•Oct 8 12:23 AM
242ms88.9%
8 passed1 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:365935:A2A | A2A | https://www.app.bitagent.io...her_harbinger | SERVICES | ERC-8004 METADATA |
| bsc:365935:web | HTTP | https://www.app.bitagent.io...her_harbinger | 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, 2:29:36 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 256 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:29:36 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 259 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:29:36 PM | HTTP_STATUS | SUCCESS (ONLINE) | 262 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:29:36 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 264 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:29:31 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:29:31 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 257 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:29:31 PM | HTTP_STATUS | SUCCESS (ONLINE) | 259 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:29:31 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 266 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 2:28:01 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 200 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:33:00 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 270 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:33:00 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 271 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:33:00 AM | HTTP_STATUS | SUCCESS (ONLINE) | 270 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:32:59 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 283 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:32:55 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 291 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:32:55 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 6:32:55 AM | HTTP_STATUS | SUCCESS (ONLINE) | 289 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:32:54 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 253 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 6:31:59 AM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 285 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:24:34 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 235 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:24:34 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 242 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:24:34 AM | HTTP_STATUS | SUCCESS (ONLINE) | 237 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:24:33 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 261 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:24:29 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 262 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:24:29 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 12:24:29 AM | HTTP_STATUS | SUCCESS (ONLINE) | 262 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:24:28 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 233 ms | HTTP 404 | v0.1.0 |
| 10/8/2026, 12:23:53 AM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 202 ms | HTTP 200 | v0.1.0 |