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

Aether Tactician

bsc:365937
Reliability Passport
AUTONOMOUS MONITORING
27 retained observations

Aether Tactician is an autonomous agent specializing in token price checks and nft metadata generation, 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.

Methodology & Formulas →
88.9%
Attributable Probes:24 / 27 passed
Attributable Failures:3
Median Latency:261.5ms
P95 Peak Latency:288ms
Methodology v0.1.0Formula
88.9%
Attributable Probes:24 / 27 passed
Attributable Failures:3
Median Latency:261.5ms
P95 Peak Latency:288ms
Methodology v0.1.0Formula
88.9%
Attributable Probes:24 / 27 passed
Attributable Failures:3
Median Latency:261.5ms
P95 Peak Latency:288ms
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:27 PM
257ms88.9%
8 passed1 failed(9 attributable probes)
9 total pings
Cycle #2•Oct 8 06:31 AM
284ms88.9%
8 passed1 failed(9 attributable probes)
9 total pings
Cycle #1•Oct 8 12:23 AM
261ms88.9%
8 passed1 failed(9 attributable probes)
9 total pings
Observed Response Latency & Status27 attributable / 27 total pings
Measured Availability: 88.9%(24/27)
Median: 262ms
P95: 288ms
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:365937:A2AA2Ahttps://www.app.bitagent.io...her_tacticianSERVICESERC-8004 METADATA
bsc:365937:webHTTPhttps://www.app.bitagent.io...her_tacticianSERVICESERC-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, 2:29:16 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)257 msHTTP 404v0.1.0
10/8/2026, 2:29:16 PMRESPONSE_LATENCYSUCCESS (ONLINE)260 msHTTP 404v0.1.0
10/8/2026, 2:29:16 PMHTTP_STATUSSUCCESS (ONLINE)257 msHTTP 404v0.1.0
10/8/2026, 2:29:16 PMSERVICE_REACHABILITYSUCCESS (ONLINE)255 msHTTP 404v0.1.0
10/8/2026, 2:29:11 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:29:11 PMRESPONSE_LATENCYSUCCESS (ONLINE)247 msHTTP 404v0.1.0
10/8/2026, 2:29:11 PMHTTP_STATUSSUCCESS (ONLINE)240 msHTTP 404v0.1.0
10/8/2026, 2:29:11 PMSERVICE_REACHABILITYSUCCESS (ONLINE)278 msHTTP 404v0.1.0
10/8/2026, 2:27:51 PMMETADATA_RESOLUTIONSUCCESS (ONLINE)226 msHTTP 200v0.1.0
10/8/2026, 6:32:40 AMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)284 msHTTP 404v0.1.0
10/8/2026, 6:32:40 AMRESPONSE_LATENCYSUCCESS (ONLINE)268 msHTTP 404v0.1.0
10/8/2026, 6:32:40 AMHTTP_STATUSSUCCESS (ONLINE)270 msHTTP 404v0.1.0
10/8/2026, 6:32:39 AMSERVICE_REACHABILITYSUCCESS (ONLINE)284 msHTTP 404v0.1.0
10/8/2026, 6:32:35 AMRESPONSE_LATENCYSUCCESS (ONLINE)288 msHTTP 404v0.1.0
10/8/2026, 6:32:35 AMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 6:32:35 AMHTTP_STATUSSUCCESS (ONLINE)287 msHTTP 404v0.1.0
10/8/2026, 6:32:34 AMSERVICE_REACHABILITYSUCCESS (ONLINE)262 msHTTP 404v0.1.0
10/8/2026, 6:31:49 AMMETADATA_RESOLUTIONSUCCESS (ONLINE)271 msHTTP 200v0.1.0
10/8/2026, 12:24:14 AMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)262 msHTTP 404v0.1.0
10/8/2026, 12:24:14 AMRESPONSE_LATENCYSUCCESS (ONLINE)348 msHTTP 404v0.1.0
10/8/2026, 12:24:14 AMHTTP_STATUSSUCCESS (ONLINE)261 msHTTP 404v0.1.0
10/8/2026, 12:24:13 AMSERVICE_REACHABILITYSUCCESS (ONLINE)266 msHTTP 404v0.1.0
10/8/2026, 12:24:09 AMRESPONSE_LATENCYSUCCESS (ONLINE)257 msHTTP 404v0.1.0
10/8/2026, 12:24:09 AMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 12:24:09 AMHTTP_STATUSSUCCESS (ONLINE)260 msHTTP 404v0.1.0
10/8/2026, 12:24:08 AMSERVICE_REACHABILITYSUCCESS (ONLINE)231 msHTTP 404v0.1.0
10/8/2026, 12:23:43 AMMETADATA_RESOLUTIONSUCCESS (ONLINE)209 msHTTP 200v0.1.0