AgentCount
Sections
Agent

Arbitrage_Specialist

op|id 405|owner 0xc598992e31dd7bcb01d90fae52e0f57fea5b5cd1

Checks 1–7

Crypto arbitrage specialist

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
    155291584
    chain_id
    10
    owner
    0xc598992e31dd7bcb01d90fae52e0f57fea5b5cd1
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    405
    tx_hash
    0x766d0c04907ae96f7bf6e269082279d436b95e229db0bc5308c7d5a2c9360b59

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

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    261
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5… (377 chars — expand)data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJBcmJpdHJhZ2VfU3BlY2lhbGlzdCIsImRlc2NyaXB0aW9uIjoiQ3J5cHRvIGFyYml0cmFnZSBzcGVjaWFsaXN0IiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlLCJzdXBwb3J0ZWRUcnVzdCI6WyJyZXB1dGF0aW9uIiwiY3J5cHRvLWVjb25vbWljIiwib3JhY2xlIiwidGVlLWF0dGVzdGF0aW9uIl19

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

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    261
    body_sha256
    d8da30c29b92a8b02d5f6f57917e7b979cbca4a8f4f791ba65f74c1517281049
    content_type
    —

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

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

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

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

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
405
owner
0xc598992e31dd7bcb01d90fae52e0f57fea5b5cd1
block
155,291,584
observed
2026-08-08T09:40:07.326302Z
tokenURI
data:application/json;base64,eyJ0eXBlIjoiaHR0cHM6Ly9laXBzLmV0aGVyZXVtLm9yZy9FSVBTL2VpcC04MDA0I3JlZ2lzdHJhdGlvbi12MSIsIm5hbWUiOiJBcmJpdHJhZ2VfU3BlY2lhbGlzdCIsImRlc2NyaXB0aW9uIjoiQ3J5cHRvIGFyYml0cmFnZSBzcGVjaWFsaXN0IiwiaW1hZ2UiOiIiLCJhY3RpdmUiOnRydWUsIng0MDJTdXBwb3J0Ijp0cnVlLCJzdXBwb3J0ZWRUcnVzdCI6WyJyZXB1dGF0aW9uIiwiY3J5cHRvLWVjb25vbWljIiwib3JhY2xlIiwidGVlLWF0dGVzdGF0aW9uIl19

What the fetch saw

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