Skip to content
Menu

bagbot

AI Agents

Is this your project? Claim and verify →

🪐 The first self-funding, self-healing AI daemon for agents on Orbio — claim, watch, top-up, and rotate OpenRouter keys automatically. Chinese notifications built in.

What HEY knows

Building
Quiet for 44 daysQuiet: 0 meaningful events in 30 days; latest ship 44 days ago. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · 25 commits · · Code activity

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

Latest change
Derived13 days ago: 0 meaningful ships this month, 4 the month before. Evidence

HEY’s own reading

What this change is
What it names
HEY’s own reading names no capability.
Stage
HEY’s own reading of the record, not something the project shipped.
Reported by
HEY’s reading of the record. HEY’s own reading of the record: nothing to corroborate.
Release and deployment
Not a release or a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-10-09; HEY first knew on 2026-10-09.
Not known
  • No source HEY holds names what this change does.

Evidence: signal record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

FollowCreate alertTerminal previewView latest ship
Share

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

No account? Email me bagbot’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.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.

HEY can answer 7 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Quiet.
“Quiet” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-09-08.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · 25 commitsv0.1.3 — 🔒 Dashboard auth + portable testsCode changes, week of 2026-08-31 – 2026-09-06 · at least 10 commits+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Quiet”.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 verified building evidence from the project's own sources.
Source2 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · 25 commitsv0.1.3 — 🔒 Dashboard auth + portable testsCode changes, week of 2026-08-31 – 2026-09-06 · at least 10 commits+2 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.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-09-07 – 2026-09-13 · 25 commits

Code activitySource linked

What changed, in the repository’s own words:

2 active days in keyneszeng/bagbot.

This week HEY looked inside 5 of 25 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

Record ship:9b0702c8… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Shared change · Release

bagbot shipped v0.1.3 — 🔒 Dashboard auth + portable tests.

Builder status: Quiet.

Dated 2026-09-07 by the sourceSource: GitHub

View evidence ↗Evidence receipt

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: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about bagbot — as of 2026-10-22

Is bagbot still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship 44 days ago. Evidence
What did bagbot ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · 25 commits — Code activity, 44 days ago. Evidence
What does HEY not know about bagbot?
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs. Details

Build timeline

  1. v0.1.3 — 🔒 Dashboard auth + portable tests

    GitHub releaseSource verified

    v0.1.3 — 2026-09-07 · 🔒 Security patch What's in this release Security: dashboard mutation endpoints (/api/claim, /api/rotate, /api/topup) now require DASHBOARD_TOKEN. Without it, mutations return 403 (read-only dashboard). With it, the token is sent via Authorization: Bearer… Show all
    • v0.1.3 — 2026-09-07 · 🔒 Security patch What's in this release Security: dashboard mutation endpoints (/api/claim, /api/rotate, /api/topup) now require DASHBOARD_TOKEN. Without it, mutations return 403 (read-only dashboard). With it, the token is sent via Authorization: Bearer or X-Dashboard-Token. Portability: CLI error tests no longer hard-code /Users/mac/.... Quality: 13 new mutation-resistant auth tests — dashboard.py mutation score is now 100%. Stats
    • 97 tests passing (was 84)
    • dashboard.py: 100% mutation score
    • ruff + mypy + shellcheck: all…
    View evidence: v0.1.3 — 🔒 Dashboard auth + portable tests (opens in a new tab)

  2. Code changes, week of 2026-08-31 – 2026-09-06 · at least 10 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in keyneszeng/bagbot.

    This week HEY looked inside 3 of 10 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.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 10 commits (opens in a new tab)

  3. v0.1.2 — CLI error handling + installable package

    GitHub releaseSource verified

    v0.1.2 — 2026-09-06 What's in this release · Bug fix: CLI no longer dumps full Python tracebacks for common errors (missing token, bad token, network errors). Prints a clean one-line error + hint instead. · Installable as a package via pip install -e . — no more cd src/ needed… Show all
    • v0.1.2 — 2026-09-06 What's in this release
    • Bug fix: CLI no longer dumps full Python tracebacks for common errors (missing token, bad token, network errors). Prints a clean one-line error + hint instead.
    • Installable as a package via pip install -e . — no more cd src/ needed to use python -m bagbot.cli.
    • MyPy strict type checking added to CI.
    • Ruff linting (bugbear + security + pyupgrade) added to CI.
    • CI matrix expanded to Python 3.10, 3.11, and 3.12.
    • Nightly mutation testing GitHub Action.
    • 3 new tests for CLI error paths. Test…
    View evidence: v0.1.2 — CLI error handling + installable package (opens in a new tab)

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about bagbot? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

5 changes on HEY’s record for bagbot: 2 releases · 1 build pace change · 2 weeks of code pushed.

bagbot on What changed →

The full change record holds 2 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 7 of the 10 research questions that apply.

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 9h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

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

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, 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.

Sources