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

OpenOdds.Ai

bsc:49637
Reliability Passport
AUTONOMOUS MONITORING
100 retained observations

Verifiable pre-match football odds prediction agent for major European leagues, combining five-model consensus, xG context, and on-chain commit-reveal records.

Agent-provided metadata (not independently verified by AgentProof)
BNB Registry: 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
Metadata Link: ipfs://QmaynfJR...wMoyxS
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
81.3%
Attributable Probes:52 / 64 passed
Attributable Failures:12
Median Latency:268.5ms
P95 Peak Latency:914ms
Methodology v0.1.0Formula
81.1%
Attributable Probes:77 / 95 passed
Attributable Failures:18
Median Latency:285ms
P95 Peak Latency:1070ms
Methodology v0.1.0Formula
81.1%
Attributable Probes:77 / 95 passed
Attributable Failures:18
Median Latency:285ms
P95 Peak Latency:1070ms
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 History6 cycles recorded
Total checks: 100Methodology

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

Cycle #6•Oct 8 08:03 PM
264ms81.3%
13 passed3 failed(16 attributable probes)
17 total pings
Cycle #5•Oct 8 02:27 PM
265ms81.3%
13 passed3 failed(16 attributable probes)
17 total pings
Cycle #4•Oct 8 06:31 AM
330ms81.3%
13 passed3 failed(16 attributable probes)
17 total pings
Cycle #3•Oct 8 12:22 AM
261ms81.3%
13 passed3 failed(16 attributable probes)
17 total pings
Cycle #2•Oct 7 08:29 PM
296ms81.3%
13 passed3 failed(16 attributable probes)
17 total pings
Cycle #1•Oct 7 07:03 AM
286ms80.0%
12 passed3 failed(15 attributable probes)
15 total pings
Observed Response Latency & Status95 attributable / 100 total pings
Measured Availability: 81.1%(77/95)
Median: 285ms
P95: 1070ms
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 (4)

Public links, APIs, and agent-to-agent protocols advertised in this agent's ERC-8004 registry record.

Service IDProtocolEndpoint URLFormProvenance
bsc:49637:A2AUNKNOWNhttps://openodds.ai/.well-k...ent-card.jsonSERVICESERC-8004 METADATA
bsc:49637:WebHTTPhttps://openodds.ai/SERVICESERC-8004 METADATA
bsc:49637:APIUNKNOWNhttps://api.openodds.ai/SERVICESERC-8004 METADATA
bsc:49637:MCPMCPhttps://api.openodds.ai/mcpSERVICESERC-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:03:47 PMRESPONSE_LATENCYSUCCESS (ONLINE)259 msHTTP 200v0.1.0
10/8/2026, 8:03:47 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 8:03:47 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)181 msHTTP 200v0.1.0
10/8/2026, 8:03:47 PMRESPONSE_LATENCYSUCCESS (ONLINE)390 msHTTP 200v0.1.0
10/8/2026, 8:03:47 PMHTTP_STATUSSUCCESS (ONLINE)203 msHTTP 200v0.1.0
10/8/2026, 8:03:47 PMSERVICE_REACHABILITYSUCCESS (ONLINE)495 msHTTP 200v0.1.0
10/8/2026, 8:03:47 PMHTTP_STATUSSUCCESS (ONLINE)181 msHTTP 200v0.1.0
10/8/2026, 8:03:46 PMSERVICE_REACHABILITYSUCCESS (ONLINE)197 msHTTP 200v0.1.0
10/8/2026, 8:03:43 PMRESPONSE_LATENCYSUCCESS (ONLINE)264 msHTTP 404v0.1.0
10/8/2026, 8:03:43 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 8:03:43 PMRESPONSE_LATENCYSUCCESS (ONLINE)272 msHTTP 200v0.1.0
10/8/2026, 8:03:43 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 8:03:43 PMHTTP_STATUSSUCCESS (ONLINE)267 msHTTP 404v0.1.0
10/8/2026, 8:03:42 PMHTTP_STATUSSUCCESS (ONLINE)241 msHTTP 200v0.1.0
10/8/2026, 8:03:42 PMSERVICE_REACHABILITYSUCCESS (ONLINE)966 msHTTP 404v0.1.0
10/8/2026, 8:03:42 PMSERVICE_REACHABILITYSUCCESS (ONLINE)859 msHTTP 200v0.1.0
10/8/2026, 8:03:41 PMMETADATA_RESOLUTIONPOLICY BLOCKED (SSRF)——v0.1.0
10/8/2026, 2:27:11 PMPROTOCOL_RESPONSE_VALIDITYSUCCESS (ONLINE)265 msHTTP 200v0.1.0
10/8/2026, 2:27:11 PMRESPONSE_LATENCYSUCCESS (ONLINE)289 msHTTP 200v0.1.0
10/8/2026, 2:27:11 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:27:11 PMRESPONSE_LATENCYSUCCESS (ONLINE)181 msHTTP 200v0.1.0
10/8/2026, 2:27:11 PMHTTP_STATUSSUCCESS (ONLINE)261 msHTTP 200v0.1.0
10/8/2026, 2:27:11 PMHTTP_STATUSSUCCESS (ONLINE)209 msHTTP 200v0.1.0
10/8/2026, 2:27:11 PMSERVICE_REACHABILITYSUCCESS (ONLINE)299 msHTTP 200v0.1.0
10/8/2026, 2:27:11 PMSERVICE_REACHABILITYSUCCESS (ONLINE)265 msHTTP 200v0.1.0
10/8/2026, 2:27:07 PMRESPONSE_LATENCYSUCCESS (ONLINE)286 msHTTP 404v0.1.0
10/8/2026, 2:27:07 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:27:07 PMRESPONSE_LATENCYSUCCESS (ONLINE)257 msHTTP 200v0.1.0
10/8/2026, 2:27:07 PMPROTOCOL_RESPONSE_VALIDITYINVALID PROTOCOL——v0.1.0
10/8/2026, 2:27:06 PMHTTP_STATUSSUCCESS (ONLINE)260 msHTTP 200v0.1.0