AgentCount
Sections
Check your agent
Agent

My tokkalo agent

polygon|id 214|owner 0x15f56351d164ab74be116a0090900394b8888004

Checks 1–7

Hello my agent is a wonderful agent that do wonderful stuff

Keyerrorthe check could not completefaildid not passpasspassedskippeda 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
    91757844
    chain_id
    137
    owner
    0x15f56351d164ab74be116a0090900394b8888004
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    214
    tx_hash
    0xd9ff1de118f998e6305765736ebbdb54320f52fb39eef5db3409557d14a48c65

    checked at 2026-08-10T06:03:57.696472Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    463
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJNeSB0b2trYWxvIGFnZW50ICIsImRlc2NyaXB0aW9uIjoiSGVsbG8gbXkgYWdlbnQgaXMgYSB3b25kZXJmdWwgYWdlbnQgdGhhdCBkbyB3b25kZXJmdWwgc3R1ZmYiLCJpbWFnZSI6Imh0dHBzOi8vbXlpbWFnZS9pbWFnZS5wbmciLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlLCJzdXBwb3J0ZWRUcnVzdCI6WyJyZXB1dGF0aW9uIiwiY3J5cHRvLWVjb25vbWljIl0sIm9hc2Zfc2tpbGxzIjpbIm5hdHVyYWxfbGFuZ3VhZ2VfcHJvY2Vzc2luZy9zdW1tYXJpemF0aW9uIiwiaW1hZ2VfcHJvY2Vzc2luZy9nZW5lcmF0aW9uIl0sIm9hc2ZfZG9tYWlucyI6WyJmaW5hbmNlX2FuZF9idXNpbmVzcy9pbnZlc3RtZW50X3NlcnZpY2VzIiwicmVzZWFyY2gvZGF0YV9hbmFseXNpcyJdfQ==

    checked at 2026-08-10T06:03:57.696472Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    463
    body_sha256
    ac5e5e94af03e0c39744ec566d7a54c06b4dc855e317e6224c58f0deda9cd749
    content_type

    checked at 2026-08-10T06:03:57.696472Z

  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:03:57.696472Z

  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:03:57.696472Z

  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

    fail

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

    did not pass

    distinct_authors
    0
    feedback_count
    0
    reason
    no_feedback

    checked at 2026-08-10T06:03:57.696472Z

On-chain snapshot

polygon
token id
214
owner
0x15f56351d164ab74be116a0090900394b8888004
block
91,757,844
observed
2026-08-10T06:03:57.698847Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJNeSB0b2trYWxvIGFnZW50ICIsImRlc2NyaXB0aW9uIjoiSGVsbG8gbXkgYWdlbnQgaXMgYSB3b25kZXJmdWwgYWdlbnQgdGhhdCBkbyB3b25kZXJmdWwgc3R1ZmYiLCJpbWFnZSI6Imh0dHBzOi8vbXlpbWFnZS9pbWFnZS5wbmciLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlLCJzdXBwb3J0ZWRUcnVzdCI6WyJyZXB1dGF0aW9uIiwiY3J5cHRvLWVjb25vbWljIl0sIm9hc2Zfc2tpbGxzIjpbIm5hdHVyYWxfbGFuZ3VhZ2VfcHJvY2Vzc2luZy9zdW1tYXJpemF0aW9uIiwiaW1hZ2VfcHJvY2Vzc2luZy9nZW5lcmF0aW9uIl0sIm9hc2ZfZG9tYWlucyI6WyJmaW5hbmNlX2FuZF9idXNpbmVzcy9pbnZlc3RtZW50X3NlcnZpY2VzIiwicmVzZWFyY2gvZGF0YV9hbmFseXNpcyJdfQ==

What the fetch saw

data
scheme
data
request url
final url
http status
content type
size
463 bytes
sha256
ac5e5e94af03e0c39744ec566d7a54c06b4dc855e317e6224c58f0deda9cd749
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
b8acef9f-d219-4fc8-8aaa-b7ce20d1b168
chain
polygon
pinned block
91,757,844
agents
608
started
2026-08-10T06:03:12.744539Z
finished
2026-08-10T06:04:58.131352Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- polygon   # at block 91757844

What each check measures →