AgentCount
Sections
Agent

ClawdMint

op|id 380|owner 0x75b583c518215e272f3c0a3bcc1b27012f294adc

Checks 1–7

ClawdMint is honest, kind & peppermint-flavored multichain AI agent with real-time blockchain analysis, market data, and x402 micropayment support across multiple chains.

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

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
    155291584
    chain_id
    10
    owner
    0x75b583c518215e272f3c0a3bcc1b27012f294adc
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    380
    tx_hash
    0xca93eb1115e26ea6904dd23a200f342b5ba95ce546accc330abc6cc9043a47d6

    checked at 2026-08-08T09:40:05.825497Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    539
    final_url
    https://ipfs.io/ipfs/QmdUTenFkZ4iz9fPLoWpuaUsdzM9Vu9HCEgZqjD4gZ5TgC
    gateway_attempts
    {"error":null,"gateway":"https://ipfs.io/ipfs/","http_status":200}
    http_status
    200
    request_url
    https://ipfs.io/ipfs/QmdUTenFkZ4iz9fPLoWpuaUsdzM9Vu9HCEgZqjD4gZ5TgC
    scheme
    ipfs
    uri
    ipfs://QmdUTenFkZ4iz9fPLoWpuaUsdzM9Vu9HCEgZqjD4gZ5TgC
    via_gateway
    https://ipfs.io/ipfs/

    checked at 2026-08-08T09:40:05.825497Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    5942
    body_sha256
    9ba4b42f052eebad4ede46b5ce99ba16d76e498b01bb60d139097ea015be409a
    content_type
    application/json

    checked at 2026-08-08T09:40:05.825497Z

  4. Follows the spec?rung 4 · conformant

    fail

    The document meets what ERC-8004 requires of it.

    did not pass

    both_fields_present
    false
    legacy_endpoints_field
    false
    may_gaps
    x402Support
    must_violations
    registrations[19].agentId, registrations[20].agentId, registrations[21].agentId
    registrations_checked
    22
    services_field_source
    services
    services_status
    present
    should_gaps
    services[].version
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-08T09:40:05.825497Z

  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
    4
    skipped_because_status
    fail

    checked at 2026-08-08T09:40:05.825497Z

  6. Answers?rung 6 · live

    skipped

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

    skipped — a check this one depends on did not pass

    skipped_because_rung
    4
    skipped_because_status
    fail

    checked at 2026-08-08T09:41:43.918885Z

  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-08T09:40:05.825497Z

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

op
token id
380
owner
0x75b583c518215e272f3c0a3bcc1b27012f294adc
block
155,291,584
observed
2026-08-08T09:40:05.827958Z
tokenURIopen via ipfs.io →
ipfs://QmdUTenFkZ4iz9fPLoWpuaUsdzM9Vu9HCEgZqjD4gZ5TgC

What the fetch saw

ipfs
scheme
ipfs
request url
https://ipfs.io/ipfs/QmdUTenFkZ4iz9fPLoWpuaUsdzM9Vu9HCEgZqjD4gZ5TgC
final url
https://ipfs.io/ipfs/QmdUTenFkZ4iz9fPLoWpuaUsdzM9Vu9HCEgZqjD4gZ5TgC
http status
200
content type
application/json
size
5,942 bytes
sha256
9ba4b42f052eebad4ede46b5ce99ba16d76e498b01bb60d139097ea015be409a
elapsed
539 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
9a6bee56-1594-4980-bafd-5efe49aae6ce
chain
op
pinned block
155,291,584
agents
535
started
2026-08-08T09:39:06.440025Z
finished
2026-08-08T09:40:35.797124Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- op   # at block 155291584

What each check measures →