AgentCount
Sections
Check your agent
Agent

Agent #38015

mainnet|id 38015|owner 0xde152afb7db5373f34876e1499fbd893a82dd336

Checks 1–7
Keyerrorthe check could not completefaildid 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
    25923734
    chain_id
    1
    owner
    0xde152afb7db5373f34876e1499fbd893a82dd336
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    38015
    tx_hash
    0x2f2524d16aab1d6f8652ccf999161236ebc8138276df931335678b1f7ec88a9c

    checked at 2026-09-07T08:23:12.504094Z

  2. Reachable?rung 2 · resolvable

    refused

    The document URL it declared actually answers when fetched.

    refused

    elapsed_ms
    0
    reason
    robots_unavailable: connection failed fetching robots.txt: error sending request for url (https://agents.exquisite.land/robots.txt)
    request_url
    https://agents.exquisite.land/compas/1079.json
    scheme
    https
    uri
    https://agents.exquisite.land/compas/1079.json

    checked at 2026-09-07T08:23:12.504094Z

  3. Readable?rung 3 · parseable

    skipped

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

    skipped — a check this one depends on did not pass

    skipped_because_rung
    2
    skipped_because_status
    refused

    checked at 2026-09-07T08:23:12.504094Z

  4. Follows the spec?rung 4 · conformant

    skipped

    The document meets what ERC-8004 requires of it.

    skipped — a check this one depends on did not pass

    skipped_because_rung
    2
    skipped_because_status
    refused

    checked at 2026-09-07T08:23:12.504094Z

  5. Claims its identity?rung 5 · bound

    skipped

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

    skipped — a check this one depends on did not pass

    skipped_because_rung
    2
    skipped_because_status
    refused

    checked at 2026-09-07T08:23:12.504094Z

  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-09-07T08:23:12.504094Z

On-chain snapshot

mainnet
token id
38015
owner
0xde152afb7db5373f34876e1499fbd893a82dd336
block
25,923,734
observed
2026-09-07T08:23:12.507138Z
tokenURIopen →
https://agents.exquisite.land/compas/1079.json

What the fetch saw

https
scheme
https
request url
https://agents.exquisite.land/compas/1079.json
final url
—
http status
—
content type
—
size
—
sha256
—
elapsed
0 ms
error
robots_unavailable: connection failed fetching robots.txt: error sending request for url (https://agents.exquisite.land/robots.txt)

This run

reproducible
Every status above is scoped to this sweep, at this block. Rerun it and you should get these answers back.
run
faba031b-5726-4bf6-9885-8d6fcd6d1456
chain
mainnet
pinned block
25,923,734
agents
50,725
started
2026-09-07T06:38:03.089231Z
finished
2026-09-07T08:40:18.482812Z
checker
0.7.0 · 981910a8f7451ff11d8af05abef0cc7852e25953
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25923734

What each check measures →