Skip to content
Menu

agex

AI Agents

Is this your project? Claim and verify →

Autonomous Agent Exchange Terminal — AI agents trade trending tokens with real ETH on Robinhood Chain

What HEY knows

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

Build Momentum 18How it is measured

Latest ship
Code changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit · · Code activity

Why it matters: First week of code changes after 15 quiet days.

Latest change
DerivedYesterday: HEY reclassified the project — activity status moved from Active to Quiet. Evidence
FollowCreate alertTerminal previewView latest ship
Share

Follow puts agex 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 agex’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
Unknown1 gap: API description (no source). Its website links no API description.

HEY can answer 9 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-16.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commitCode changes, week of 2026-08-31 – 2026-09-06 · at least 3 commitsWhat 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.
Source24 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commitCode changes, week of 2026-08-31 – 2026-09-06 · at least 3 commitssource:ac6cfc74-fc74-4fd4-a12a-fde2110ddd66+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.
Market figures are context only and never change activity status. Methodology
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit

Code activitySource linked

What changed, in the repository’s own words:

4 active days in Manyachandra/agex.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:f2a0a4b5… · 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: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

Questions HEY can answer about agex — as of 2026-10-18

Is agex still being built?
DerivedQuiet: 0 meaningful events in 30 days; latest ship 32 days ago. Evidence
What did agex ship last?
FactCode changes, week of 2026-09-14 – 2026-09-20 · at least 1 commit — Code activity, 32 days ago. Evidence
What does HEY not know about agex?
Unknown1 gap: API description (no source). Its website links no API description. Details

Build timeline

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

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in Manyachandra/agex.

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

    View evidence

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 agex? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

2 changes on HEY’s record for agex: 2 weeks of code pushed.

agex on What changed →

The full change record holds 26 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 9 of the 10 research questions that apply.

9 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 17h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 9h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 6d ago.

Code and packages

  • Repository detailsMeasuredRead 3h ago.
  • Published packagesMeasuredRead 3h 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

20 more sources (docs)