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

@sibeleth · Ensoul

bsc:2387
Reliability Passport
AUTONOMOUS MONITORING
100 retained observations

The profile for @sibeleth contains minimal information, with no bio available and only mock tweets present. This makes it impossible to conduct a meaningful personality analysis at this time.

Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: data-uri (application/json)
First Tracked: Oct 8, 2026

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

Deterministic availability ratios computed strictly from attributable service probes.

Methodology & Formulas →
24H WindowSTRONG EVIDENCE
100.0%
Attributable Probes:32 / 32 passed
Attributable Failures:0
Median Latency:234.5ms
P95 Peak Latency:471ms
Methodology v0.1.0Formula
100.0%
Attributable Probes:89 / 89 passed
Attributable Failures:0
Median Latency:266ms
P95 Peak Latency:522ms
Methodology v0.1.0Formula
100.0%
Attributable Probes:89 / 89 passed
Attributable Failures:0
Median Latency:266ms
P95 Peak Latency:522ms
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 History12 cycles recorded
Total checks: 100Methodology

Each row reflects an automated probe cycle run by AgentProof. Availability is calculated solely over attributable service probes.

Cycle #12•Oct 8 08:04 PM
206ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #11•Oct 8 02:27 PM
211ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #10•Oct 8 06:31 AM
249ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #9•Oct 8 12:23 AM
236ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #8•Oct 7 08:29 PM
272ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #7•Oct 7 07:04 AM
258ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #6•Oct 7 12:57 AM
285ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #5•Oct 6 09:09 PM
298ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #4•Oct 6 04:11 PM
304ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #3•Oct 6 09:18 AM
252ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #2•Oct 6 02:26 AM
258ms100.0%
8 passed(8 attributable probes)
9 total pings
Cycle #1•Oct 5 10:23 PM
222ms100.0%
1 passed(1 attributable probes)
1 total pings
Observed Response Latency & Status89 attributable / 100 total pings
Measured Availability: 100.0%(89/89)
Median: 266ms
P95: 522ms
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:2387:webHTTPhttps://ensoul.ac/soul/sibelethSERVICESERC-8004 METADATA
bsc:2387:chatHTTPhttps://ensoul.ac/soul/sibeleth/chatSERVICESERC-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:37 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)206 msHTTP 200v0.1.0
10/8/2026, 8:04:37 PMRESPONSE_LATENCYSUCCESS (ONLINE)207 msHTTP 200v0.1.0
10/8/2026, 8:04:37 PMHTTP_STATUSSUCCESS (ONLINE)205 msHTTP 200v0.1.0
10/8/2026, 8:04:37 PMSERVICE_REACHABILITYSUCCESS (ONLINE)371 msHTTP 200v0.1.0
10/8/2026, 8:04:32 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)203 msHTTP 200v0.1.0
10/8/2026, 8:04:32 PMRESPONSE_LATENCYSUCCESS (ONLINE)201 msHTTP 200v0.1.0
10/8/2026, 8:04:32 PMHTTP_STATUSSUCCESS (ONLINE)199 msHTTP 200v0.1.0
10/8/2026, 8:04:32 PMSERVICE_REACHABILITYSUCCESS (ONLINE)376 msHTTP 200v0.1.0
10/8/2026, 8:04:11 PMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 2:28:50 PMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 2:28:01 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)207 msHTTP 200v0.1.0
10/8/2026, 2:28:01 PMRESPONSE_LATENCYSUCCESS (ONLINE)230 msHTTP 200v0.1.0
10/8/2026, 2:28:01 PMHTTP_STATUSSUCCESS (ONLINE)211 msHTTP 200v0.1.0
10/8/2026, 2:28:01 PMSERVICE_REACHABILITYSUCCESS (ONLINE)374 msHTTP 200v0.1.0
10/8/2026, 2:27:56 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)202 msHTTP 200v0.1.0
10/8/2026, 2:27:56 PMRESPONSE_LATENCYSUCCESS (ONLINE)206 msHTTP 200v0.1.0
10/8/2026, 2:27:56 PMHTTP_STATUSSUCCESS (ONLINE)207 msHTTP 200v0.1.0
10/8/2026, 2:27:56 PMSERVICE_REACHABILITYSUCCESS (ONLINE)375 msHTTP 200v0.1.0
10/8/2026, 6:32:05 AMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)243 msHTTP 200v0.1.0
10/8/2026, 6:32:05 AMRESPONSE_LATENCYSUCCESS (ONLINE)247 msHTTP 200v0.1.0
10/8/2026, 6:32:05 AMHTTP_STATUSSUCCESS (ONLINE)270 msHTTP 200v0.1.0
10/8/2026, 6:32:04 AMSERVICE_REACHABILITYSUCCESS (ONLINE)471 msHTTP 200v0.1.0
10/8/2026, 6:32:00 AMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)246 msHTTP 200v0.1.0
10/8/2026, 6:32:00 AMRESPONSE_LATENCYSUCCESS (ONLINE)249 msHTTP 200v0.1.0
10/8/2026, 6:32:00 AMHTTP_STATUSSUCCESS (ONLINE)241 msHTTP 200v0.1.0
10/8/2026, 6:31:59 AMSERVICE_REACHABILITYSUCCESS (ONLINE)508 msHTTP 200v0.1.0
10/8/2026, 6:31:49 AMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 12:23:34 AMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)233 msHTTP 200v0.1.0
10/8/2026, 12:23:34 AMRESPONSE_LATENCYSUCCESS (ONLINE)236 msHTTP 200v0.1.0
10/8/2026, 12:23:34 AMHTTP_STATUSSUCCESS (ONLINE)217 msHTTP 200v0.1.0