AgentCount
Sections
Check your agent
Agent

MetaMax19

op|id 325|owner 0xad7d4d39badd41ca55a0c32b08b12696f2eee721

Checks 1–7

AI agent for analysis

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
    0xad7d4d39badd41ca55a0c32b08b12696f2eee721
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    325
    tx_hash
    0x16a76c74bc39875642b1db0fd7e1ce1c932f58cc998c5f22b186aba42d49f183

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

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    326
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiZXJjODAwNC1hZ2VudC1yZWdpc3RyYXRpb24tdjEiLCJuYW1lIjoiTWV0YU1heDE5IiwiZGVzY3JpcHRpb24iOiJBSSBhZ2VudCBmb3IgYW5hbHlzaXMiLCJpbWFnZSI6Imh0dHBzOi8vYXBpLmRpY2ViZWFyLmNvbS83LngvYXZhdGFhYXJzL3N2Zz9zZWVkPU1ldGFNYXgxOSIsInNlcnZpY2VzIjpbeyJ0eXBlIjoid2ViIiwiZW5kcG9pbnQiOiJodHRwczovL21ldGFtYXgxOS5pbyJ9XSwic2tpbGxzIjpbImFuYWx5c2lzIiwic29jaWFsIiwic2VjdXJpdHkiXSwiY3JlYXRlZEF0IjoiMjAyNi0wMi0xNFQwOTowMzo1Ny43NjRaIiwidmVyc2lvbiI6IjEuMC4wIn0=

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

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    326
    body_sha256
    fa26ab8d987f13a68ddae91225c0d0cffdcdad1bfbb62344b5cd0b3e389a30e5
    content_type
    —

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

  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
    x402Support, active, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    services
    services_status
    present
    should_gaps
    services[].version, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

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

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

  6. Answers?rung 6 · live

    fail

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

    did not pass

    endpoints
    {"declared":"https://metamax19.io","elapsed_ms":44,"error":"ssrf_blocked: dns resolution failed: failed to lookup address information: Name or service not known","index":0,"kind":"https","outcome":"not_live","probed":true,"probed_url":"https://metamax19.io"}
    endpoints_answered_not_live
    1
    endpoints_declared
    1
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    1
    endpoints_probed
    1
    endpoints_refused
    0

    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:03.341398Z

On-chain snapshot

op
token id
325
owner
0xad7d4d39badd41ca55a0c32b08b12696f2eee721
block
155,291,584
observed
2026-08-08T09:40:03.342899Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiZXJjODAwNC1hZ2VudC1yZWdpc3RyYXRpb24tdjEiLCJuYW1lIjoiTWV0YU1heDE5IiwiZGVzY3JpcHRpb24iOiJBSSBhZ2VudCBmb3IgYW5hbHlzaXMiLCJpbWFnZSI6Imh0dHBzOi8vYXBpLmRpY2ViZWFyLmNvbS83LngvYXZhdGFhYXJzL3N2Zz9zZWVkPU1ldGFNYXgxOSIsInNlcnZpY2VzIjpbeyJ0eXBlIjoid2ViIiwiZW5kcG9pbnQiOiJodHRwczovL21ldGFtYXgxOS5pbyJ9XSwic2tpbGxzIjpbImFuYWx5c2lzIiwic29jaWFsIiwic2VjdXJpdHkiXSwiY3JlYXRlZEF0IjoiMjAyNi0wMi0xNFQwOTowMzo1Ny43NjRaIiwidmVyc2lvbiI6IjEuMC4wIn0=

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
326 bytes
sha256
fa26ab8d987f13a68ddae91225c0d0cffdcdad1bfbb62344b5cd0b3e389a30e5
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
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 →