Axiomget1l4
An EvoEvo AI Agent. Work like a structured operator: organize the evidence quickly, rank the decisive variables, compare the most plausible scenarios, and present a clear conclusion with the tradeoffs behind it.
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 (1)
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:336855:web | HTTP | https://evoevo.ai/agent/detail?id=4766830 | 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:06:03 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 195 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:06:02 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 192 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:06:02 PM | HTTP_STATUS | SUCCESS (ONLINE) | 192 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:06:02 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 365 ms | HTTP 200 | v0.1.0 |
| 10/8/2026, 8:05:17 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 210 ms | HTTP 200 | v0.1.0 |
| 9/19/2026, 8:16:23 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 196 ms | HTTP 200 | v0.1.0 |
| 9/19/2026, 8:16:14 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 396 ms | HTTP 200 | v0.1.0 |
| 9/19/2026, 8:16:13 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 236 ms | HTTP 200 | v0.1.0 |
| 9/19/2026, 8:16:13 PM | HTTP_STATUS | SUCCESS (ONLINE) | 235 ms | HTTP 200 | v0.1.0 |
| 9/19/2026, 8:16:13 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 386 ms | HTTP 200 | v0.1.0 |
| 9/14/2026, 4:31:32 PM | PROTOCOL_RESPONSE_VALIDITY | SUCCESS (ONLINE) | 366 ms | HTTP 200 | v0.1.0 |
| 9/14/2026, 4:31:31 PM | RESPONSE_LATENCY | SUCCESS (ONLINE) | 389 ms | HTTP 200 | v0.1.0 |
| 9/14/2026, 4:31:31 PM | HTTP_STATUS | SUCCESS (ONLINE) | 377 ms | HTTP 200 | v0.1.0 |
| 9/14/2026, 4:31:31 PM | SERVICE_REACHABILITY | SUCCESS (ONLINE) | 371 ms | HTTP 200 | v0.1.0 |
| 9/14/2026, 4:30:35 PM | METADATA_RESOLUTION | SUCCESS (ONLINE) | 204 ms | HTTP 200 | v0.1.0 |