AgentCount
Sections
Check your agent
Agent

Oya Deterministic DCA Agent

mainnet|id 28283|owner 0x2967c076182f0303037072670e744e26ed4a830f

Checks 1–7

Deterministic single-active-campaign DCA reimbursement agent: reconstructs campaign state from chain history, executes 4 tranches over 9h (immediate + every 3h), applies an implied 0.5% service fee, and halts on user withdrawal cancellation.

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
    25824613
    chain_id
    1
    owner
    0x2967c076182f0303037072670e744e26ed4a830f
    registry
    0x8004a169fb4a3325136eb29fa0ceb6d2e539a432
    token_id
    28283
    tx_hash
    0xc2781f607b15c26acb48bd2747b1a1dbe2237fd1051e1c6a2766f57e54bd99c1

    checked at 2026-08-24T11:37:39.764839Z

  2. Reachable?rung 2 · resolvable

    pass

    The document URL it declared actually answers when fetched.

    passed

    elapsed_ms
    310
    final_url
    https://raw.githubusercontent.com/oyaprotocol/oya-commitments/main/agent-library/agents/deterministic-dca-agent/agent.json
    http_status
    200
    request_url
    https://raw.githubusercontent.com/oyaprotocol/oya-commitments/main/agent-library/agents/deterministic-dca-agent/agent.json
    scheme
    https
    uri
    https://raw.githubusercontent.com/oyaprotocol/oya-commitments/main/agent-library/agents/deterministic-dca-agent/agent.json

    checked at 2026-08-24T11:37:39.764839Z

  3. Readable?rung 3 · parseable

    pass

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

    passed

    body_bytes
    696
    body_sha256
    24e7418da1e9016f3a7c7601faee998ed41f880b27328db7917eabb51a622b97
    content_type
    text/plain; charset=utf-8

    checked at 2026-08-24T11:37:39.764839Z

  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
    present
    should_gaps
    services[].version, registrations
    spec_commit
    68fc6765761a10fb26f0692df21c8a6f9d12b1be

    checked at 2026-08-24T11:37:39.764839Z

  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-24T11:37:39.764839Z

  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":"eip155:11155111:0x0000000000000000000000000000000000000000","index":0,"kind":"caip10","name":"agentWallet","probed":false}
    endpoints_answered_not_live
    0
    endpoints_declared
    1
    endpoints_live
    0
    endpoints_our_error
    0
    endpoints_payment_gated
    0
    endpoints_probeable
    0
    endpoints_probed
    0
    endpoints_refused
    0
    kinds
    caip10
    reason
    no_probeable_endpoint

    checked at 2026-08-24T13:24:55.917314Z

  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-24T11:37:39.764839Z

On-chain snapshot

mainnet
token id
28283
owner
0x2967c076182f0303037072670e744e26ed4a830f
block
25,824,613
observed
2026-08-24T11:37:39.765997Z
tokenURIopen →
https://raw.githubusercontent.com/oyaprotocol/oya-commitments/main/agent-library/agents/deterministic-dca-agent/agent.json

What the fetch saw

https
scheme
https
request url
https://raw.githubusercontent.com/oyaprotocol/oya-commitments/main/agent-library/agents/deterministic-dca-agent/agent.json
final url
https://raw.githubusercontent.com/oyaprotocol/oya-commitments/main/agent-library/agents/deterministic-dca-agent/agent.json
http status
200
content type
text/plain; charset=utf-8
size
696 bytes
sha256
24e7418da1e9016f3a7c7601faee998ed41f880b27328db7917eabb51a622b97
elapsed
310 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
49418208-967d-41de-8762-2b02c8654622
chain
mainnet
pinned block
25,824,613
agents
50,419
started
2026-08-24T11:03:55.159273Z
finished
2026-08-24T12:45:59.131330Z
checker
0.7.0 · 9d5393c75e1c70208ad73f51dc4685b4e5f5c37d
spec commit
68fc6765761a10fb26f0692df21c8a6f9d12b1be
Reproduce
cargo run -p sweeper -- mainnet   # at block 25824613

What each check measures →