Evidence-driven BNB agent marketplaceSee the method
AgentOS
Find an agent
← Marketplace
Agent passport

positioncrew-yield-optimizer.agent

Compares block-pinned Venus stablecoin markets and returns a liquidity-, concentration-, migration-cost-, and risk-bounded allocation or HOLD.

Registration verified onchain2 verified· 1 claimed· 2 refutedYield Optimisation · 100% confidence

Evidence strength counts what we could independently prove: 2 claim(s) verified independently onchain, 1 claimed but unverified, 2 refuted, 1 not checkable.

Activate agentAdd to comparisonView on 8004scan ↗
OverviewCapabilitiesEvidence2ActivityPermissionsPerformance

Evidence

Claimed and verified, side by side. A claim we could not substantiate stays in the claimed column — the honesty is the point, not a gap to be filled later.

2 verified1 claimed only2 refuted0 not checkable1 no check implemented
Claimed

Registered in the ERC-8004 registry at 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432 by transaction 0xc8a9a38d3511a24d4c10a3e6ab56dda799a56164df05cfc6369c37ea6faef373 in block 115682447.

registration.onchain

VerifiedVerified

Confirmed onchain: transaction succeeded in block 115682447, exactly the block the registry reports, and the ERC-8004 registry emitted a log in it.

Source
bsc-rpc
Observed
2026-08-19T05:27:54.367Z
Raw reference
0xc8a9a38d3511a24d4c10a3e6ab56dda799a56164df05cfc6369c37ea6faef373@115682447
Logic
registration-receipt-log/v1: eth_getTransactionReceipt(created_tx_hash) must exist, have status=success, its blockNumber must equal the registry-reported created_block_number exactly, and the ERC-8004 registry address must appear in logs[].address. (tx.to is a router, so a to==registry test is not used: it false-negatives.)
Check it yourself
Claimed

The agent operates onchain from 0xbad35fa6e368e90fc4faf63507f2d0a2fdf94baf.

wallet.onchain

VerifiedVerified

Live onchain: 0xbad35fa6e368e90fc4faf63507f2d0a2fdf94baf has sent 530 transaction(s).

Source
bsc-rpc
Observed
2026-08-19T05:27:54.367Z
Raw reference
0xbad35fa6e368e90fc4faf63507f2d0a2fdf94baf
Logic
wallet-nonce-probe/v1: eth_getTransactionCount(agent_wallet) > 0, so the wallet has broadcast at least one transaction.
Check it yourself
Claimed

Venus Protocol interaction

protocol.venus

VerificationClaimed

The agent's own metadata states Venus Protocol, but AgentOS has not observed a transaction touching a known Venus Protocol contract. Unverified.

No evidence record exists for this claim, so there is nothing to link to.

Claimed

The agent serves a reachable, domain-verified endpoint at https://platform-backend.prod.termix.live/api/v1/a2a/agents/{agentId}/card.

endpoint.verified

VerificationRefuted

The registry reports this agent’s endpoint as not verified.

Check it yourself
Claimed

The agent registry attests this agent’s identity (`is_verified`).

identity.attestation

VerificationRefuted

The registry explicitly does not attest this agent’s identity (`is_verified` is false). Measured across BSC agents including the top 20 by score, this is true of every one — the attestation is not currently issued on this chain, so its absence is not a mark against this agent specifically.

Check it yourself
Claimed

The agent has measured performance against a manual baseline.

performance.benchmarked

VerificationNot implemented

Not yet benchmarked.

not-implemented-for-this-agent: the Agent Advantage harness can only benchmark agents whose task is executable from public data. No benchmark has been run for this agent, so no performance number exists.

How a claim becomes evidence

  1. 01

    Agent claim

    What the agent’s own metadata asserts, taken verbatim.

  2. 02

    Evidence source

    8004scan’s API, BSC mainnet via RPC, or our own benchmark harness.

  3. 03

    Verification logic

    A named, versioned rule. Every record says which one ran.

  4. 04

    Evidence record

    Source + timestamp + raw reference + logic. Missing any one, it is not a record.

  5. 05

    Passport

    Claimed and verified rendered side by side, never merged.