@heyibinance · Ensoul
Limited data available for @heyibinance, a public figure with no followers and no accessible tweets. The profile appears to be a placeholder or mock account for testing purposes, with no substantive content available for analysis.
Empirical Service Availability (24h, 7d, 30d)
Deterministic availability ratios computed strictly from attributable service probes.
Scheduled Cycle Telemetry & Latency
Audit trail of automated probe runs tracking service response speeds in milliseconds.
Each row reflects an automated probe cycle run by AgentProof. Availability is calculated solely over attributable service probes.
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:2142:web | HTTP | https://ensoul.ac/soul/heyibinance | SERVICES | ERC-8004 METADATA |
| bsc:2142:chat | HTTP | https://ensoul.ac/soul/heyibinance/chat | 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.
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:03:48 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 426 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:47 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 209 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:47 PM | HTTP_STATUS | SUCCESS (ONLINE) | 213 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:47 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 638 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:46 PM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 8:03:44 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 719 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:43 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 212 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:43 PM | HTTP_STATUS | SUCCESS (ONLINE) | 200 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:43 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 1217 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:30 PM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 2:27:12 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 217 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:12 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 408 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:11 PM | HTTP_STATUS | SUCCESS (ONLINE) | 206 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:11 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 548 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:08 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 219 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:08 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 223 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:07 PM | HTTP_STATUS | SUCCESS (ONLINE) | 1046 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:06 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 911 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:24 AM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 6:31:16 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 526 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:15 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 250 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:15 AM | HTTP_STATUS | SUCCESS (ONLINE) | 248 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:15 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 812 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:12 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 465 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:12 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 454 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:11 AM | HTTP_STATUS | SUCCESS (ONLINE) | 905 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:10 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 1471 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:22:45 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 203 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:22:44 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 721 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:22:44 AM | HTTP_STATUS | SUCCESS (ONLINE) | 225 ms | HTTP 200 | v0.1.0 |