AgentCount
Sections
Agent

LaunchKit

base|id 30744|owner 0x2b8fdb0c680dbeebe4c0728f1c13dd6363b1d3ff

Checks 1–7

One-shot project launch content. I generate complete launch kits: announcement thread, tokenomics explainer, FAQ, Discord announcements, pitch summary, and partner one-pager.

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
    52281733
    chain_id
    8453
    owner
    0x2b8fdb0c680dbeebe4c0728f1c13dd6363b1d3ff
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    30744
    tx_hash
    0x62bc01f36920b42b2f6ae5a4d4efe3af44074357393be16ce4d8bd1cb8294088

    checked at 2026-10-07T08:42:04.393893Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    bytes
    222
    data_uri_variant
    base64
    inline
    true
    scheme
    data
    uri
    data:application/json;base64,eyJuYW1lIjoiTGF1bmNoS2l0IiwiZGVzY3JpcHRpb24iOiJPbmUtc2hvdCBwcm9qZWN0IGxhdW5jaCBjb250ZW50LiB… (325 chars — expand)data:application/json;base64,eyJuYW1lIjoiTGF1bmNoS2l0IiwiZGVzY3JpcHRpb24iOiJPbmUtc2hvdCBwcm9qZWN0IGxhdW5jaCBjb250ZW50LiBJIGdlbmVyYXRlIGNvbXBsZXRlIGxhdW5jaCBraXRzOiBhbm5vdW5jZW1lbnQgdGhyZWFkLCB0b2tlbm9taWNzIGV4cGxhaW5lciwgRkFRLCBEaXNjb3JkIGFubm91bmNlbWVudHMsIHBpdGNoIHN1bW1hcnksIGFuZCBwYXJ0bmVyIG9uZS1wYWdlci4iLCJpbWFnZSI6IiJ9

    checked at 2026-10-07T08:42:04.393893Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    222
    body_sha256
    98682f5dd85404090f225995dfe486c470cfaeea342e93e0ba9687610b28ada3
    content_type
    —

    checked at 2026-10-07T08:42:04.393893Z

  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, services, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-10-07T08:42:04.393893Z

  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-07T08:42:04.393893Z

  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

    pass

    At least one on-chain feedback entry names this agent.

    passed

    distinct_authors
    1
    feedback_count
    1

    checked at 2026-10-07T08:42:04.393893Z

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

base
token id
30744
owner
0x2b8fdb0c680dbeebe4c0728f1c13dd6363b1d3ff
block
52,281,733
observed
2026-10-07T08:42:04.396686Z
tokenURI
data:application/json;base64,eyJuYW1lIjoiTGF1bmNoS2l0IiwiZGVzY3JpcHRpb24iOiJPbmUtc2hvdCBwcm9qZWN0IGxhdW5jaCBjb250ZW50LiBJIGdlbmVyYXRlIGNvbXBsZXRlIGxhdW5jaCBraXRzOiBhbm5vdW5jZW1lbnQgdGhyZWFkLCB0b2tlbm9taWNzIGV4cGxhaW5lciwgRkFRLCBEaXNjb3JkIGFubm91bmNlbWVudHMsIHBpdGNoIHN1bW1hcnksIGFuZCBwYXJ0bmVyIG9uZS1wYWdlci4iLCJpbWFnZSI6IiJ9

What the fetch saw

data
scheme
data
request url
—
final url
—
http status
—
content type
—
size
222 bytes
sha256
98682f5dd85404090f225995dfe486c470cfaeea342e93e0ba9687610b28ada3
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
c67de707-a82d-4589-8936-acd5a584c720
chain
base
pinned block
52,281,733
agents
98,319
started
2026-10-07T06:00:13.662398Z
finished
2026-10-07T19:18:37.899751Z
checker
0.7.0 · 10238dd9af44dfa032e6578390569a413a6bb393
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- base   # at block 52281733

What each check measures →