Skip to content
Menu

Blue Agent

$BLUEAGENT

AI Agents

Token unverified: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Token market

Contract 0x765eecec6b7bee0474d00faf76e61fca8ed027b3

HEY holds 68 other Robinhood Chain tokens that use $BLUEAGENT. This page is only the contract above. See them

Is this your project? Claim and verify →

What HEY knows

Building
Shipping consistentlyShipping: 4 meaningful events in 30 days; latest ship 4 days ago. Evidence Source

Build Momentum 44How it is measured

Latest ship
Code changes, week of 2026-10-12 – 2026-10-18 · 31 commits · · Code activity

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

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not a release or a deployment: code is not 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 to the week of 2026-10-16; HEY first knew on 2026-10-13.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

Evidence: ship 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 Blue Agent 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 Blue Agent’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.

Attention
Building and market attention rank about level among comparable projects: 97.3 of 100 for building, 72.9 of 100 for market attention (a gap of 24.5). What the Discovery Gap is

It compares building with market attention; it is not a prediction and not a reason to trade.

Product usage
Fact1 of 1 watched contract active · 1 call to the contracts' own functions in 7 days; the other 128 of 129 calls were ERC-20 token transfers and approvals, which trading alone produces.

Counted from the chain. Usage says the contracts are used, not that anyone is building.

Contracts
Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context
Active market$49K fully diluted valuationToken unverified
Not yet known
Unknown5 gaps: Published packages (not enough yet), Official docs (not tied to the project yet), API description (not tied to the project yet), Official site changes (not tied to the project yet), Contract activity (not enough yet). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 14 of the 19 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
Shipping.
“Shipping” by the activity rule: 4 meaningful events in the last 30 days, the newest 2026-10-16.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 31 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 17 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 133 commits+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 verified building evidence from the project's own sources.
Source3 registered sources, 1 of them context only.ReadRecordsCode changes, week of 2026-10-12 – 2026-10-18 · 31 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 17 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 133 commits+4 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.
Token unverified.
Token unverified: HEY found the token through a launch record or a market listing, and nothing the project published names it.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedToken unverified: HEY knows it from a launchpad record, and the site that record named does not name it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.
Active market: the pool holds liquidity and the token traded in the last day.
Source8 readings from HEY's own market tables.ReadWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.
Market figures are context only and never change activity status. Methodology
LinksWebsite (context only)GitHubXdefined.fiRHToolsSources

Latest ship

Checked

Code changes, week of 2026-10-12 – 2026-10-18 · 31 commits

Code activitySource linked

What changed, in the repository’s own words:

3 active days in madebyshun/blue-agent.

This week HEY looked inside 3 of 31 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

View evidence ↗

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 Blue Agent — as of 2026-10-20

Is Blue Agent still being built?
DerivedShipping: 4 meaningful events in 30 days; latest ship 4 days ago. Evidence
What did Blue Agent ship last?
FactCode changes, week of 2026-10-12 – 2026-10-18 · 31 commits — Code activity, 4 days ago. Evidence
Is 0x765eecec6B7BEe0474D00FAf76e61fCA8ed027b3 Blue Agent’s own contract?
UnknownToken unverified: HEY found this token through a launchpad record. The site that record named does not name the contract, so HEY does not treat it as confirmed by the project. Token discovery alone never establishes ownership. Details
What does HEY not know about Blue Agent?
Unknown5 gaps: Published packages (not enough yet), Official docs (not tied to the project yet), API description (not tied to the project yet), +2 more. Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in madebyshun/blue-agent.

    This week HEY looked inside 2 of 17 commits to see what changed: 1 changed code, 1 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-10-05 – 2026-10-11 · 17 commits (opens in a new tab)

  2. Code changes, week of 2026-09-28 – 2026-10-04 · 133 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    6 active days in madebyshun/blue-agent.

    This week HEY looked inside 3 of 133 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 133 commits (opens in a new tab)

  3. Code changes, week of 2026-09-21 – 2026-09-27 · at least 91 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    at least 2 active days in madebyshun/blue-agent since 2026-09-26; the count stops at the newest 100 commits listed.

    This week HEY looked inside 3 of 91 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · at least 91 commits (opens in a new tab)

  4. Code changes, week of 2026-09-14 – 2026-09-20 · at least 22 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    4 active days in madebyshun/blue-agent.

    This week HEY looked inside 1 of 22 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 22 commits (opens in a new tab)

  5. Code changes, week of 2026-09-07 – 2026-09-13 · at least 41 commits

    Code activitySource linked

    What changed, in the repository’s own words:

    8 active days in madebyshun/blue-agent.

    This week HEY looked inside 3 of 41 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 41 commits (opens in a new tab)

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

    Code activitySource linked

    What changed, in the repository’s own words:

    10 active days in madebyshun/blue-agent.

    This week HEY looked inside 3 of 70 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 70 commits (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 Blue Agent? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

13 changes on HEY’s record for Blue Agent: 6 market moves · 7 weeks of code pushed.

All 13 changes for Blue Agent →

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 14 of the 19 research questions that apply.

14 of 19 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 38m ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNot tied to the project yetHEY found a docs link on its website and holds it until the website is tied to the project.
  • API descriptionNot tied to the project yetIts website is not yet confirmed as the project’s own.
  • Official site changesNot tied to the project yetIts website is not yet confirmed as the project’s own.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Contracts

  • Contract creationMeasuredRead 20h ago.
  • Contract activityNot enough yetCalls were read, but the days’ events could not be decoded.
  • Verified sourceMeasuredRead 6d ago.
  • Contract interfaceMeasuredRead 6d ago.

Market

  • Current marketMeasuredRead 2h ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead yesterday.
  • LocksMeasuredRead 3h ago.
  • Market checksMeasured

Not applicable here: Package advisories, 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

  • Website
    https://blueagent.dev/Context onlyContext only because HEY reached this site through a launch record or a listing and nothing yet ties it to this token; it counts once the site names the token’s contract, a GitHub claim names one of the project’s repositories, or a moderator confirms one of them.
  • Repository
    https://github.com/madebyshun/blue-agentOfficial
  • X
    https://x.com/blueagent_@blueagent_ links back to blueagent.dev — checked 2026-10-20.From a launch or market listing
Contract
0x765e…27b30x765eecec6b7bee0474d00faf76e61fca8ed027b3