Skip to content

HoodRugCheck

Robinhood Chain Native · Utility

Token safety scanner for Robinhood Chain — 8 on-chain checks, Radar for new launches, and a pay-per-call API for AI agents.

What HEY knows

Development

Shipped this weekShipping: 12 counted ships in 30 days; latest ship yesterday. Evidence Source

Build Momentum 61How it is measured

Latest: v0.3.2

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts HoodRugCheck on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow HoodRugCheck

No account? Email me HoodRugCheck’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

More detail
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 12 counted ships in the last 30 days, the newest 2026-11-06.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.3.2Code changes this week (since Mon 2 Nov) · 9 commitsv0.3.1 (2026-11-06)+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source6 registered sources, 0 of them context only.Recordsv0.3.2Code changes this week (since Mon 2 Nov) · 9 commitsv0.3.1 (2026-11-06)+7 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Research coverage: HEY can answer 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasured

Building

  • Building activityMeasuredRead 1m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 2h ago.

Code and packages

  • Repository detailsMeasuredRead 2h ago.
  • Published packagesMeasuredRead 2h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

v0.3.2

GitHub releaseSource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

API version 1.3.1, scanner v6 and detector v6. A sell simulation that hits a transport failure now reads as unknown, not as blocked; any execution revert the node reports is still a blocked sell. scanner_version in paid responses is now 6. /radar lists Called It cards again, and… Show all

API version 1.3.1, scanner v6 and detector v6. A sell simulation that hits a transport failure now reads as unknown, not as blocked; any execution revert the node reports is still a blocked sell. scanner_version in paid responses is now 6. /radar lists Called It cards again, and scanner v5 has its own frozen record.

Record ship:8b848b7e… · HEY counts it as building; it does not judge the release’s quality.

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 11 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes this week (since Mon 2 Nov) · 9 commits

    Code activitySource-backed

    3 active days in atlasclaw67/hoodrugcheck-api.

    How HEY read this week

    This week HEY looked inside 3 of 9 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

  2. v0.3.1

    GitHub releaseSource-backed

    API version 1.3.0. Every check response has a degraded boolean, true when 3 or more of the 8 checks couldn't run because a read failed. POST /api/v1/x402/check, the Wafermap route and POST /api/snapshots answer 503 with Retry-After for a degraded scan, and nothing is charged.

  3. v0.3.1 (2026-11-06)

    API releaseSource-backed

    openapi.json copied from (API version 1.3.0): every check response has a degraded boolean, true when 3 or more of the 8 checks couldn't run because a read failed. POST /api/v1/x402/check , the Wafermap route and POST /api/snapshots answer 503 with Retry-After for a degraded… Show all

    openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.3.0): every check response has a degraded boolean, true when 3 or more of the 8 checks couldn't run because a read failed. POST /api/v1/x402/check , the Wafermap route and POST /api/snapshots answer 503 with Retry-After for a degraded scan, and nothing is charged.

  4. v0.3.2 (2026-11-06)

    API releaseSource-backed

    openapi.json copied from (API version 1.3.1). Scanner v6 and detector v6: a sell simulation that hits a transport failure (timeout, connection error, 5xx, rate limit, an RPC error that isn't an execution revert) now reads as unknown, not as blocked. Any execution revert the node… Show all

    openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.3.1). Scanner v6 and detector v6: a sell simulation that hits a transport failure (timeout, connection error, 5xx, rate limit, an RPC error that isn't an execution revert) now reads as unknown, not as blocked. Any execution revert the node reports is still a blocked sell. scanner_version in paid responses is now 6. Site: /radar lists Called It cards again, and scanner v5 has its own frozen record next to v4's.

  5. 4 releases in atlasclaw67/hoodrugcheck-api on 5 Nov

    GitHub release

    Show all 4 releases
    1. v0.3.0

      GitHub releaseSource-backed

      openapi.json from (API version 1.2.0): adds POST /api/snapshots. · README: snapshot links, frozen copies of one scan result at /s/{id}. Show all
      • openapi.json from https://hoodrugcheck.com/openapi.json (API version 1.2.0): adds POST /api/snapshots.
      • README: snapshot links, frozen copies of one scan result at /s/{id}.
    2. v0.2.2

      GitHub releaseSource-backed

      openapi.json from (API version 1.1.1): GET /api/v1/x402/check answers the same 402 as an unpaid POST, for probes. It sells nothing; pay with POST. Show all

      openapi.json from https://hoodrugcheck.com/openapi.json (API version 1.1.1): GET /api/v1/x402/check answers the same 402 as an unpaid POST, for probes. It sells nothing; pay with POST.

    3. v0.2.1

      GitHub releaseSource-backed

      Site: /radar now has a "scanner v4, frozen record" box. No API change; openapi.json is unchanged (API version 1.1.0).

    4. v0.2.0

      GitHub releaseSource-backed

      openapi.json from (API version 1.1.0): adds POST /api/v1/x402/check. · README: x402 section, pay per call at $0.02 in USDC on Base or USDG on Robinhood Chain. Show all
      • openapi.json from https://hoodrugcheck.com/openapi.json (API version 1.1.0): adds POST /api/v1/x402/check.
      • README: x402 section, pay per call at $0.02 in USDC on Base or USDG on Robinhood Chain.
  6. v0.2.0 (2026-11-05)

    API releaseSource-backed

    openapi.json copied from (API version 1.1.0): adds POST /api/v1/x402/check . README: x402 section, pay per call at $0.02 in USDC on Base or USDG on Robinhood Chain. Show all

    openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.1.0): adds POST /api/v1/x402/check . README: x402 section, pay per call at $0.02 in USDC on Base or USDG on Robinhood Chain.

  7. v0.2.2 (2026-11-05)

    API releaseSource-backed

    openapi.json copied from (API version 1.1.1): GET /api/v1/x402/check answers the same 402 as an unpaid POST, for probes. It sells nothing; pay with POST. Show all

    openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.1.1): GET /api/v1/x402/check answers the same 402 as an unpaid POST, for probes. It sells nothing; pay with POST.

  8. v0.2.1 (2026-11-05)

    API releaseSource-backed

    Site: /radar now has a "scanner v4, frozen record" box. No API change; openapi.json is unchanged (API version 1.1.0).

Earlier ships (5)
  1. v0.3.0 (2026-11-05)

    API releaseSource-backed

    openapi.json copied from (API version 1.2.0): adds POST /api/snapshots . README: snapshot links, frozen copies of one scan result at /s/{id} . Show all

    openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.2.0): adds POST /api/snapshots . README: snapshot links, frozen copies of one scan result at /s/{id} .

  2. 2 releases in atlasclaw67/hoodrugcheck-api on 4 Nov

    GitHub release

    Show all 2 releases
    1. v0.1.1

      GitHub releaseSource-backed

      README: linked the Wafermap listing at · README: quick starts now use a placeholder token address. Show all
      • README: linked the Wafermap listing at https://wafermap.xyz/v1/m/hoodrugcheck.
      • README: quick starts now use a placeholder token address.
    2. v0.1.0

      GitHub releaseSource-backed

      First public release. · openapi.json copied from (API version 1.0.0, scanner v5). · README with API key instructions, quick starts and MCP setup. · examples/: curl, JavaScript and Python scripts for GET /api/v1/check/{address}. Show all
      • First public release.
      • openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.0.0, scanner v5).
      • README with API key instructions, quick starts and MCP setup.
      • examples/: curl, JavaScript and Python scripts for GET /api/v1/check/{address}.
  3. v0.1.1 (2026-11-04)

    Feature releaseSource-backed

    README: linked the Wafermap listing at . README: quick starts now use a placeholder token address. Show all

    README: linked the Wafermap listing at https://wafermap.xyz/v1/m/hoodrugcheck . README: quick starts now use a placeholder token address.

  4. v0.1.0 (2026-11-04)

    API releaseSource-backed

    First public release. openapi.json copied from (API version 1.0.0, scanner v5). README with API key instructions, quick starts and MCP setup. examples/ : curl, JavaScript and Python scripts for GET /api/v1/check/{address} . Show all

    First public release. openapi.json copied from https://hoodrugcheck.com/openapi.json (API version 1.0.0, scanner v5). README with API key instructions, quick starts and MCP setup. examples/ : curl, JavaScript and Python scripts for GET /api/v1/check/{address} .

Other changes on HEY’s record

20 changes on HEY’s record for HoodRugCheck: 16 releases · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 build pace change · 1 other change in 1 more kind.

All 20 changes for HoodRugCheck →

The full change record holds 1 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

6 places HEY reads for HoodRugCheck