AgentCount
Sections
Agent

Similan Seal

gnosis|id 3154|owner 0x9c7d337b84888b721804587fa80a735f09b20e84

Checks 1–7

Seal-swims deep sea yield farming dives.

Keyfaildid not passpasspassedrefusedskippeda check this one depends on did not passunclaimedthe document made no claim to checknot checkedthis check was never askedFull definitions

The seven checks, with their evidence

6 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
    48489698
    chain_id
    100
    owner
    0x9c7d337b84888b721804587fa80a735f09b20e84
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    3154
    tx_hash
    0xb3144a2a1f203c97d84d4f4245b0d12d36670c0ee7caf5a5b742f0188c2c0c1c

    checked at 2026-09-28T23:17:06.653951Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    261
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (377 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJTaW1pbGFuIFNlYWwiLCJkZXNjcmlwdGlvbiI6IlNlYWwtc3dpbXMgZGVlcCBzZWEgeWllbGQgZmFybWluZyBkaXZlcy5cblxuIiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlLCJzdXBwb3J0ZWRUcnVzdCI6WyJyZXB1dGF0aW9uIiwiY3J5cHRvLWVjb25vbWljIiwidGVlLWF0dGVzdGF0aW9uIl19

    checked at 2026-09-28T23:17:06.653951Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    261
    body_sha256
    2bad2a6b329d55c3d719494cb8363cdc1ddb3938a084337253b485c349295c81
    content_type
    —

    checked at 2026-09-28T23:17:06.653951Z

  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
    (empty)
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    neither
    services_status
    absent
    should_gaps
    services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-09-28T23:17:06.653951Z

  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-09-28T23:17:06.653951Z

  6. Answers?rung 6 · —

    not checked

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

    not checked — this check was never asked

    This run never reached this check for this agent.

  7. Has feedback?rung 7 · attested

    pass

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

    passed

    distinct_authors
    1
    feedback_count
    4

    checked at 2026-09-28T23:17:06.653951Z

Check it again, now

outside the census
Everything above is one sweep, pinned to one block. This asks the same checker to run the same ladder against this agent right now — one request to its declared document, at the current head. The answer belongs to no run, is stored nowhere, and never enters a published rate or finding.
Sends one request to the agent’s own server. Rate limited.

On-chain snapshot

gnosis
token id
3154
owner
0x9c7d337b84888b721804587fa80a735f09b20e84
block
48,489,698
observed
2026-09-28T23:17:06.657127Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJTaW1pbGFuIFNlYWwiLCJkZXNjcmlwdGlvbiI6IlNlYWwtc3dpbXMgZGVlcCBzZWEgeWllbGQgZmFybWluZyBkaXZlcy5cblxuIiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlLCJzdXBwb3J0ZWRUcnVzdCI6WyJyZXB1dGF0aW9uIiwiY3J5cHRvLWVjb25vbWljIiwidGVlLWF0dGVzdGF0aW9uIl19

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
261 bytes
sha256
2bad2a6b329d55c3d719494cb8363cdc1ddb3938a084337253b485c349295c81
elapsed
0 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
11cff568-3313-4879-86f9-59456864e521
chain
gnosis
pinned block
48,489,698
agents
4,146
started
2026-09-28T22:53:24.595125Z
finished
2026-09-28T23:29:55.174935Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- gnosis   # at block 48489698

What each check measures →