Skip to main content
AVOID.NET
← Platform Data

The Agents

The machine behind this site, working in the open: every agent and worker, what it does, and how its recent runs went.

What the agents did

WorkLast 7 daysLast 30 days
findings judged945945
findings written440457
reviewed225225
escalated212212
suggestions87161
investigations written83103
pages published7292
evidence submitted3774
skipped3458
duplicate requests closed3741
queued1223
Telegram posts read020
pages backfilled1516
accepted1111
errors57
pages fact-checked55
rejected22
rerouted11

Counted from what each run reports it produced. Only agents that record their output are counted.

Research agents

Scheduled AI agents that find, write and fact-check the pages on this site.

  • Scout

    Working

    Searches the web for new scams, hacks, rug pulls and enforcement actions, and queues the ones worth investigating.

    Runs
    three times a day (03:00, 11:00 and 19:00 UTC)
    Last success
    2h ago
  • Queue drain

    Working

    Works through the investigation queue: researches each requested entity and writes its page.

    Runs
    six times a day (00:00, 04:00, 08:00, 12:00, 16:00 and 20:00 UTC)
    Last success
    1h ago
  • Nightly fact-check

    Working

    Fact-checks published pages against the evidence they cite, concentrating on the pages people read or asked for.

    Runs
    four times a day, hourly from 05:07 to 08:07 UTC
    Last success
    16h ago
  • Telegram analyst

    Working

    Reads the posts collected from crypto investigators' Telegram channels and turns the notable ones into public queue entries or evidence for review.

    Runs
    six times a day (02:30, 06:30, 10:30, 14:30, 18:30 and 22:30 UTC)
    Last success
    2h ago

Background workers

Small programs that keep the evidence, the on-chain audit trail and the notifications moving. None of them uses AI.

  • Watchlist alerts

    Working

    Sends an alert to people who follow an entity when something about it changes.

    Runs
    every 7 minutes
    Last success
    2m ago
  • Request fulfilment

    Working

    Tells people who requested an investigation when their page is published.

    Runs
    every hour
    Last success
    2m ago
  • Wallet guardian

    Working

    Warns wallet owners when they deal with a counterparty flagged as risky.

    Runs
    every minute
    Last success
    58s ago
  • Push dispatcher

    Working

    Delivers the app notifications the other workers queue up.

    Runs
    every 1m
    Last success
    1m ago
  • Telegram answer bot

    Not switched on yet

    Built, but not switched on yet, so it is not doing this today. Once on: Answers /check lookups in Telegram.

    Planned
    every 30 seconds
  • Merkle roots

    Not switched on yet

    Built, but not switched on yet, so it is not doing this today. Once on: Publishes an hourly fingerprint of the page history on the Solana blockchain, so anyone can prove a page was not quietly edited.

    Planned
    every hour
  • Signals detectors

    Not switched on yet

    Built, but not switched on yet, so it is not doing this today. Once on: Watches for stablecoin peg breaks and price-oracle disagreements. Readings go to the operator first, never straight to the public.

    Planned
    every 10 minutes
  • Solana anchoring

    Working

    Writes each editorial decision to the Solana blockchain, so the audit history can be checked without trusting this site.

    Runs
    every 30 seconds
    Last success
    5s ago
  • Corrections propagator

    Working

    Carries accepted corrections and updates through to the pages they correct.

    Runs
    every minute
    Last success
    59s ago
  • Structured sources

    Not switched on yet

    Built, but not switched on yet, so it is not doing this today. Once on: Pulls official and community datasets once a day: US sanctions (OFAC), SEC and CFTC actions, DeFiLlama, Web3 Is Going Great and CryptoScamDB.

    Planned
    once a day
  • Helius address sync

    Failing

    Keeps the set of wallets watched on-chain in step with the wallets our pages track.

    Runs
    every 6 hours
    Last success
    5d ago
    Last problem
    reported an error
  • Source URL archive

    Not running

    Saves a copy of every cited source to the Internet Archive, so the evidence survives if the original link disappears.

    Runs
    every minute
    Last success
    38m ago
    Last problem
    never finished
  • Submission archive

    Working

    Saves a copy of the links in community submissions to the Internet Archive.

    Runs
    every minute
    Last success
    30s ago
  • On-chain heartbeat

    Not switched on yet

    Built, but not switched on yet, so it is not doing this today. Once on: Posts a daily signed heartbeat on-chain, showing the publishing key is still alive (see /about/keys).

    Planned
    once a day
  • Telegram collector

    Working

    Collects new posts from the crypto investigators' Telegram channels we follow, for the Telegram analyst to read.

    Runs
    every 10 minutes
    Last success
    4m ago
  • Fleet watchdog

    Not switched on yet

    Built, but not switched on yet, so it is not doing this today. Once on: Watches every other worker on this page and alerts the operator when one goes quiet.

    Planned
    every hour
  • succeeded
  • nothing to do
  • partly done
  • failed
  • never finished
  • in progress

Each strip is a worker's last 30 runs, oldest on the left. A worker is working when it has run and succeeded within three of its own cycles, and not running when it has not started a run in that time. 6 of the 20 workers are built but not switched on yet. They are shown in grey, with no run history, and are not counted as working. Not running is also grey, not red, on purpose: it means a worker that is switched on has stopped starting runs.

Problems are described in plain words only. This page never shows costs, raw error messages or internal identifiers. Ages are measured from 21:24 UTC; the page refreshes every five minutes. The operator's view of the same fleet is on internal metrics, and the on-chain record is in the audit trail.

Data refreshes every 5 minutes · All metrics derived from Supabase