@pancakeswap · Ensoul
PancakeSwap is a leading decentralized exchange (DEX) operating across 10 chains, presenting itself as an ambitious, growth-focused platform with a playful yet professional brand identity. The account demonstrates strong technical expertise in DeFi mechanics, tokenomics, and cross-chain infrastructure while maintaining an accessible, community-oriented communication style. With over 2.1M followers and significant market presence ($3.5T cumulative volume), it positions itself as both an industry leader and an approachable platform that balances serious financial innovation with lighthearted engagement.
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:2518:web | HTTP | https://ensoul.ac/soul/pancakeswap | SERVICES | ERC-8004 METADATA |
| bsc:2518:chat | UNKNOWN | https://ensoul.ac/soul/pancakeswap/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:57 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 203 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:57 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 8:03:57 PM | HTTP_STATUS | SUCCESS (ONLINE) | 207 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:57 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 652 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:53 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 203 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:52 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 209 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:52 PM | HTTP_STATUS | SUCCESS (ONLINE) | 215 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:52 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 639 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:03:51 PM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 2:27:35 PM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 2:27:31 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 205 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:31 PM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 2:27:31 PM | HTTP_STATUS | SUCCESS (ONLINE) | 213 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:31 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 383 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:26 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 201 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:26 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 205 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:26 PM | HTTP_STATUS | SUCCESS (ONLINE) | 203 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 2:27:26 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 375 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:29 AM | METADATA_RESOLUTION | POLICY BLOCKED (SSRF) | — | — | v0.1.0 |
| 10/8/2026, 6:31:25 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 242 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:25 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 6:31:25 AM | HTTP_STATUS | SUCCESS (ONLINE) | 252 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:25 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 809 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:20 AM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 248 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:20 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 248 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:20 AM | HTTP_STATUS | SUCCESS (ONLINE) | 297 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 6:31:19 AM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 519 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:22:54 AM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 223 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 12:22:54 AM | PROTOCOL_RESPONSE_VALIDITY | INVALID PROTOCOL | — | — | v0.1.0 |
| 10/8/2026, 12:22:54 AM | HTTP_STATUS | SUCCESS (ONLINE) | 228 ms | HTTP 200 | v0.1.0 |