AgentCount
Sections
Agent

Rent-Compute

celo|id 9801|owner 0xd98e2ee165eceae767efd2f0a7952344465e1f88

Checks 1–7

Agent-native metered compute sandboxes, paid for in USDC on Celo via x402.

Keyerrorthe check could not completefaildid not passpasspassedrefusedskippeda 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
    79282391
    chain_id
    42220
    owner
    0xd98e2ee165eceae767efd2f0a7952344465e1f88
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    9801
    tx_hash
    0x2221db4151fa40e9b0f581aa3ed8be14de20156f0dae177629a29c1d92d77a43

    checked at 2026-10-05T07:21:02.137006Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    2241
    final_url
    https://compute-router-two.vercel.app/.well-known/agent.json
    http_status
    200
    request_url
    https://compute-router-two.vercel.app/.well-known/agent.json
    scheme
    https
    uri
    https://compute-router-two.vercel.app/.well-known/agent.json

    checked at 2026-10-05T07:21:02.137006Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    413
    body_sha256
    3e672901d1490e5035067fb1252ffbdaef03b7193a87bc3500bbf16e4daacaf4
    content_type
    application/json

    checked at 2026-10-05T07:21:02.137006Z

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

    checked at 2026-10-05T07:21:02.137006Z

  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-10-05T07:21:02.137006Z

  6. Answers?rung 6 · live

    unprobeable

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

    unprobeable — no declared endpoint that a probe can reach

    endpoints
    {"declared":null,"index":0,"kind":"missing","probed":false}, {"declared":null,"index":1,"kind":"missing","probed":false}
    endpoints_answered_not_live
    0
    endpoints_declared
    2
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    missing, missing
    reason
    no_probeable_endpoint

    checked at 2026-10-05T07:31:54.600744Z

  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-10-05T07:21:02.137006Z

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

celo
token id
9801
owner
0xd98e2ee165eceae767efd2f0a7952344465e1f88
block
79,282,391
observed
2026-10-05T07:21:02.140182Z
tokenURIopen →
https://compute-router-two.vercel.app/.well-known/agent.json

What the fetch saw

https
scheme
https
request url
https://compute-router-two.vercel.app/.well-known/agent.json
final url
https://compute-router-two.vercel.app/.well-known/agent.json
http status
200
content type
application/json
size
413 bytes
sha256
3e672901d1490e5035067fb1252ffbdaef03b7193a87bc3500bbf16e4daacaf4
elapsed
2,241 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
51518bd2-6305-4b27-a769-cf957aba00f4
chain
celo
pinned block
79,282,391
agents
9,878
started
2026-10-05T06:52:29.184815Z
finished
2026-10-05T07:30:46.088420Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- celo   # at block 79282391

What each check measures →