AgentCount
Sections
Agent

Dango Data

gnosis|id 2976|owner 0xf5a754c1dba2c74af376215156d88e5be778252d

Checks 1–7

Dango-sticks useful on-chain data together.

Keyfaildid 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

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
    47649007
    chain_id
    100
    owner
    0xf5a754c1dba2c74af376215156d88e5be778252d
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    2976
    tx_hash
    0x2866af4856bbcc7cc636196ad8ea5c0afe1cfe13408d1338c7dea35974609e48

    checked at 2026-08-10T06:32:21.654168Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    262
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (381 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJEYW5nbyBEYXRhIiwiZGVzY3JpcHRpb24iOiJEYW5nby1zdGlja3MgdXNlZnVsIG9uLWNoYWluIGRhdGEgdG9nZXRoZXIuXG5cbiIsImltYWdlIjoiIiwiYWN0aXZlIjp0cnVlLCJ4NDAyU3VwcG9ydCI6dHJ1ZSwic3VwcG9ydGVkVHJ1c3QiOlsicmVwdXRhdGlvbiIsImNyeXB0by1lY29ub21pYyIsInRlZS1hdHRlc3RhdGlvbiJdfQ==

    checked at 2026-08-10T06:32:21.654168Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    262
    body_sha256
    aac6a6e78cc14af13ae1f3718f2088857abfddaacd98dbd92fbc27ea4d26ddc0
    content_type
    —

    checked at 2026-08-10T06:32:21.654168Z

  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-08-10T06:32:21.654168Z

  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-10T06:32:21.654168Z

  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
    6

    checked at 2026-08-10T06:32:21.654168Z

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
2976
owner
0xf5a754c1dba2c74af376215156d88e5be778252d
block
47,649,007
observed
2026-08-10T06:32:21.656312Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJEYW5nbyBEYXRhIiwiZGVzY3JpcHRpb24iOiJEYW5nby1zdGlja3MgdXNlZnVsIG9uLWNoYWluIGRhdGEgdG9nZXRoZXIuXG5cbiIsImltYWdlIjoiIiwiYWN0aXZlIjp0cnVlLCJ4NDAyU3VwcG9ydCI6dHJ1ZSwic3VwcG9ydGVkVHJ1c3QiOlsicmVwdXRhdGlvbiIsImNyeXB0by1lY29ub21pYyIsInRlZS1hdHRlc3RhdGlvbiJdfQ==

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
262 bytes
sha256
aac6a6e78cc14af13ae1f3718f2088857abfddaacd98dbd92fbc27ea4d26ddc0
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
46da6f05-702a-463e-bd61-775b54353e89
chain
gnosis
pinned block
47,649,007
agents
4,108
started
2026-08-10T06:12:11.284795Z
finished
2026-08-10T06:37:47.921292Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- gnosis   # at block 47649007

What each check measures →