AgentCount
Sections
Agent

Aegis

celo|id 9300|owner 0x24a46a27047a5614334d117c785a7e0d5901b810

Checks 1–7

Multi-chain agent orchestration framework — identity registry, policy enforcement, x402 micropayments, verifiable run receipts. Live on Celo mainnet and Stellar testnet.

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

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
    74443315
    chain_id
    42220
    owner
    0x24a46a27047a5614334d117c785a7e0d5901b810
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    9300
    tx_hash
    0xa6077314bb7869391349108a69e3166a23a46bac975914e102004f7f10297578

    checked at 2026-08-10T07:05:03.600654Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    446
    data_uri_variant
    plain
    inline
    true
    scheme
    data
    uri
    data:application/json,{"name":"Aegis","domain":"aegis.calebux.com","role":"orchestrator","capabilities":["agent-orchestr… (466 chars — expand)data:application/json,{"name":"Aegis","domain":"aegis.calebux.com","role":"orchestrator","capabilities":["agent-orchestration","on-chain-identity","on-chain-reputation","spend-governance","x402-payments","verifiable-receipts","agent-discovery","celo","stellar"],"version":"0.2.1","description":"Multi-chain agent orchestration framework — identity registry, policy enforcement, x402 micropayments, verifiable run receipts. Live on Celo mainnet and Stellar testnet."}

    checked at 2026-08-10T07:05:03.600654Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    446
    body_sha256
    28bb3b3eecc103d7369252c98304a397a2bce067bf767edffa5714a1164deafe
    content_type
    —

    checked at 2026-08-10T07:05:03.600654Z

  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
    neither
    services_status
    absent
    should_gaps
    type, image, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-10T07:05:03.600654Z

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

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

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
9300
owner
0x24a46a27047a5614334d117c785a7e0d5901b810
block
74,443,315
observed
2026-08-10T07:05:03.603498Z
tokenURI
data:application/json,{"name":"Aegis","domain":"aegis.calebux.com","role":"orchestrator","capabilities":["agent-orchestration","on-chain-identity","on-chain-reputation","spend-governance","x402-payments","verifiable-receipts","agent-discovery","celo","stellar"],"version":"0.2.1","description":"Multi-chain agent orchestration framework — identity registry, policy enforcement, x402 micropayments, verifiable run receipts. Live on Celo mainnet and Stellar testnet."}

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
446 bytes
sha256
28bb3b3eecc103d7369252c98304a397a2bce067bf767edffa5714a1164deafe
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
4131a5a1-0461-46ce-b393-bcd825d2113b
chain
celo
pinned block
74,443,315
agents
9,765
started
2026-08-10T06:41:13.909696Z
finished
2026-08-10T07:06:42.747601Z
checker
0.7.0 · 55deaa9ce71c025a9199311a53cdc2de236eae53
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- celo   # at block 74443315

What each check measures →