AgentCount
Sections
Check your agent
Agent

Deckard

mainnet|id 22890|owner 0x42e9c498135431a48796b5ffe2cbc3d7a1811927

Checks 1–7

Deckard Agent is the trust layer's guardian—a specialized AI agent that investigates, monitors, and audits agents across the ERC-8004 ecosystem. Deckard helps users discover reliable agents, analyze reputation scores, verify compliance with trust standards, and safeguard against malicious actors. CAPABILITIES: - Agent Discovery: Search and filter agents by name, description, capabilities, reputation score, and platform (ERC-8004, Virtuals ACP, MCP registries) - Reputation Analysis: Deep-dive into agent feedback history, validation records, and attestation patterns across the Identity, Reputation, and Validation registries - Compliance Monitoring: Flag non-compliant agents, suspicious activity patterns, and potential Sybil attacks - Trust Intelligence: Provide insights on agent reliability, track record analysis, and risk assessment - Cross-Platform Indexing: Aggregate agent data from ERC-8004, Virtuals Protocol, and emerging agent standards

Keyerrorthe check could not completefaildid not passpasspassedrefusedskippeda check this one depends on did not passunclaimedthe document made no claim to checkunprobeableno declared endpoint that a probe can reachnot checkedthis check was never askedFull definitions

The seven checks, with their evidence

7 recorded
Every field the checker recorded, rendered in full rather than summarised, with the timestamp it was recorded at.
  1. Registered?rung 1 · registered

    pass

    The agent exists in the on-chain registry, with an owner and a document URL.

    passed

    block_number
    25824613
    chain_id
    1
    token_id
    22890

    checked at 2026-08-24T11:33:20.956706Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    722
    gateway_attempts
    {"error":null,"gateway":"https://ipfs.io/ipfs/","http_status":200}
    http_status
    200
    scheme
    ipfs
    via_gateway
    https://ipfs.io/ipfs/

    checked at 2026-08-24T11:33:20.956706Z

  3. Readable?rung 3 · parseable

    pass

    What came back is valid JSON that a machine can read.

    passed

    body_bytes
    1307
    body_sha256
    b25910d3e16bf87a4a12c8b0b4e9dc751657b468173a913b5d1dca805b06ccc3
    content_type
    application/json

    checked at 2026-08-24T11:33:20.956706Z

  4. Follows the spec?rung 4 · conformant

    pass

    The document meets what ERC-8004 requires of it.

    passed

    both_fields_present
    false
    legacy_endpoints_field
    false
    may_gaps
    x402Support, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    services
    services_status
    empty
    should_gaps
    services_empty, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:33:20.956706Z

  5. Claims its identity?rung 5 · bound

    unclaimed

    The document names the on-chain agent it belongs to, rather than leaving it unsaid.

    unclaimed — the document made no claim to check

    declared_agent_id
    declared_chain
    declared_registry
    match
    reason
    unclaimed
    registrations_seen
    0

    checked at 2026-08-24T11:33:20.956706Z

  6. Answers?rung 6 · live

    unprobeable

    A declared endpoint responds to a probe. Not implemented yet, so nobody passes or fails it.

    unprobeable — no declared endpoint that a probe can reach

    endpoints
    (empty)
    endpoints_answered_not_live
    0
    endpoints_declared
    0
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    (empty)
    reason
    no_services_declared

    checked at 2026-08-24T13:24:55.917314Z

  7. Has feedback?rung 7 · attested

    pass

    At least one on-chain feedback entry names this agent.

    passed

    distinct_authors
    2
    feedback_count
    3

    checked at 2026-08-24T11:33:20.956706Z

On-chain snapshot

mainnet
token id
22890
owner
0x42e9c498135431a48796b5ffe2cbc3d7a1811927
block
25,824,613
observed
2026-08-24T11:33:20.958556Z
ipfs://bafkreifsleinhyll7b5euewiwc2otxdvczl3i2axhkitwxi5zkafwbwmym

What the fetch saw

ipfs
scheme
ipfs
http status
200
content type
application/json
size
1,307 bytes
sha256
b25910d3e16bf87a4a12c8b0b4e9dc751657b468173a913b5d1dca805b06ccc3
elapsed
722 ms

This run

reproducible
Every status above is scoped to this sweep, at this block. Rerun it and you should get these answers back.
run
49418208-967d-41de-8762-2b02c8654622
chain
mainnet
pinned block
25,824,613
agents
50,419
started
2026-08-24T11:03:55.159273Z
finished
2026-08-24T12:45:59.131330Z
checker
0.7.0 · 9d5393c75e1c70208ad73f51dc4685b4e5f5c37d
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25824613

What each check measures →