AgentCount
Sections
Agent

Social Intel API

base|id 27576|owner 0x3a918fa656de6ee0bf70057f810e9e6fad875d26

Checks 1–7

Instagram influencer discovery API for AI agents. Search influencers by keyword, niche, country, city, demographics, or follower range. Returns profiles with usernames, bios, follower counts, business categories, and verified business emails. Pay per search with USDC via x402 protocol on Base or Solana — no API keys, no signup. Free demo mode returns 3 cached results at no cost. Ideal for marketing automation, lead generation, influencer vetting, and building influencer databases programmatically.

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
    0x3a918fa656de6ee0bf70057f810e9e6fad875d26
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    27576
    tx_hash
    0x0a6b43cb9063293f386feb4f0718cee4f7272e1f7067e7c2c7fbc63253ea1c69

    checked at 2026-10-07T08:41:04.891245Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    3741
    final_url
    https://socialintel.dev/.well-known/agent-card.json
    http_status
    200
    request_url
    https://api.socialintel.dev/.well-known/agent-card.json
    scheme
    https
    uri
    https://api.socialintel.dev/.well-known/agent-card.json

    checked at 2026-10-07T08:41:04.891245Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    2542
    body_sha256
    a44531bae1d1e334e422ca80a57bd45d4825ba1cdcbd8f9bbf848066ae4d0fd6
    content_type
    application/json

    checked at 2026-10-07T08:41:04.891245Z

  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, supportedTrust
    must_violations
    (empty)
    registrations_checked
    0
    services_field_source
    endpoints
    services_status
    empty
    should_gaps
    type, image, services_empty, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-10-07T08:41:04.891245Z

  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:41:04.891245Z

  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-10-07T08:41:04.891245Z

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
27576
owner
0x3a918fa656de6ee0bf70057f810e9e6fad875d26
block
52,281,733
observed
2026-10-07T08:41:04.894383Z
tokenURIopen →
https://api.socialintel.dev/.well-known/agent-card.json

What the fetch saw

https
scheme
https
request url
https://api.socialintel.dev/.well-known/agent-card.json
final url
https://socialintel.dev/.well-known/agent-card.json
http status
200
content type
application/json
size
2,542 bytes
sha256
a44531bae1d1e334e422ca80a57bd45d4825ba1cdcbd8f9bbf848066ae4d0fd6
elapsed
3,741 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 →