Skip to content

Anyroute

AI · Utility

Not confirmed by the project: The project’s own site named this contract when HEY read it, but the site has not answered HEY’s reads since. HEY keeps that reading as context and does not treat the token as confirmed until the site answers again. Token market

Contract 0xa4ddf89a40a35264e9d7f896a1ef01c59b1e977a

HEY holds 25 other Robinhood Chain tokens with the ticker $ANYR. This page is only the contract above. See them

Is this your project? Claim it →

Anyroute is building an open inference routing layer for AI applications on Robinhood Chain. Developers use one OpenRouter-compatible API to access models and providers, set routing preferences around cost, latency, privacy, and availability, and manage usage through a unified USDG balance. Each generation is designed to produce a signed receipt with the model, provider, tokens, route, and cost, making AI inference more programmable, accountable, and easier to integrate into agent workflows.

Read more

What HEY knows

Development

Last shipped 26 days agoActive: 2 counted ships in 30 days; latest ship 26 days ago. Evidence Source

Build Momentum 29How it is measured

Latest: Code changes, week of 2026-10-19 – 2026-10-25 · 15 commits

Token market · context

Active marketThe tracked token's FDV (fully diluted) $7.1K, not the project's valuation: the project does not name this token and another published project’s token carries the same ticker, so HEY cannot tell it from a lookalike

Same name, different contract: 1 other published project uses the name Anyroute and the ticker $ANYR. This page: its site anyroute.tech named 0xa4dd…977a and no longer answers. Anyroute: its site anyroute.site named 0xde7f…03b9 and no longer answers. HEY does not say which is the real one — only what each project’s own sources name.

Token check

Not confirmed by the project
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Anyroute 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 Anyroute

No account? Email me Anyroute’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
Discovery Gap not measured — the token is not tied to the project. What the Discovery Gap is
More detail
Product usage
Fact1 of 1 watched contract active · 849 calls in 7 days — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches.

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 published source code; no implementation or interface change recorded.
Not yet known
Unknown2 gaps: API description (source unavailable), Official site changes (source unavailable). Its website did not answer.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-10-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 15 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 44 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 123 commits+1 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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, 1 of them context only.ReadRecordsCode changes, week of 2026-10-19 – 2026-10-25 · 15 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 44 commitsCode changes, week of 2026-10-05 – 2026-10-11 · 123 commits+6 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.
Not confirmed by the project.
Not confirmed by the project: HEY has not confirmed that the project stands behind this contract — the project’s site named it, and has not answered HEY’s reads since.
SourceThe project's own published sources and HEY's check of the contract.What HEY derivedNot confirmed by the project: the project’s site named it, and has not answered HEY’s reads since.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.
Source7 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.
Discovery Gap: Not measured — the token is not tied to the project.
Not measured — the token is not tied to the project: the project does not name the tracked token and another published project's token carries the same ticker, so HEY cannot tell it from a lookalike and does not measure its market as the project's.
SourceThe score row: the Build Momentum percentile and the market-attention percentile, both taken over the projects with a market reading.ReadWhat HEY derivedNot measured — the token is not tied to the project.Not concludedIt compares building with market attention; it is not a prediction and not a reason to trade.
Research coverage: HEY can answer 17 of the 19 research questions that apply.
17 of 19 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 46d ago.

Building

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

Official site

  • Official docsMeasuredRead 19d ago.
  • API descriptionSource unavailableIts website did not answer.
  • Official site changesSource unavailableIts website did not answer.

Code and packages

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

Contracts

  • Contract creationMeasuredRead 12h ago.
  • Contract activityMeasuredRead yesterday.
  • Published source codeMeasuredRead 3d ago.
  • Contract interfaceMeasuredRead 3d ago.

Market

  • Current marketMeasuredRead 1m ago.
  • Market historyMeasuredRead today.
  • Supply distributionMeasuredRead 2d ago.
  • 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.

Market figures are context only and never change activity status. Methodology
LinksWebsite anyroute.tech has not answered HEY since 2026-10-26: the page is not found.GitHub (opens in a new tab)X (opens in a new tab)DEX Screener (opens in a new tab)RHTools (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-19 – 2026-10-25 · 15 commits

Code activitySource-backed

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

1 active day in anyrouterh/anyroute.

This week HEY looked inside 1 of 15 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 3 automated commits (bot accounts or a repeating scripted message) not counted.

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit 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-19; HEY first knew on 2026-10-19.
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.

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.

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, week of 2026-10-12 – 2026-10-18 · 44 commits

    Code activitySource-backed

    4 active days in anyrouterh/anyroute.

    How HEY read this week

    This week HEY looked inside 3 of 42 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. 8 automated commits (bot accounts or a repeating scripted message) not counted.

  2. Code changes, week of 2026-10-05 – 2026-10-11 · 123 commits

    Code activitySource-backed

    6 active days in anyrouterh/anyroute.

    How HEY read this week

    This week HEY looked inside 3 of 115 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. 8 automated commits (bot accounts or a repeating scripted message) not counted.

  3. Code changes, week of 2026-09-28 – 2026-10-04 · at least 458 commits

    Code activitySource-backed

    at least 6 active days in anyrouterh/anyroute since 2026-09-29; the count stops at the newest 100 commits listed.

    How HEY read this week

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

Other changes on HEY’s record

25 changes on HEY’s record for Anyroute: 1 new Verified Builder or owner proof · 2 token check changes · 3 market checks · 1 official source change · 18 other changes in 3 more kinds.

All 25 changes for Anyroute →

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

The token’s market, checks, locks and stamps below are context only: none of it changes activity status or Build Momentum.

Contract 0xa4dDF89A40A35264E9D7F896a1ef01C59b1e977a on Robinhood Chain

0xa4dd…977a0xa4ddf89a40a35264e9d7f896a1ef01c59b1e977a

Not confirmed by the project.

Market context

Active market · the tracked token's FDV (fully diluted) $7.1K, not the project's valuation: the project does not name this token and another published project’s token carries the same ticker, so HEY cannot tell it from a lookalike.

Token

Launch stage
Trading in a DEX pool
Pair age
38d ago

Market

Liquidity
$6.9K
24h volume
$2.5K
Trades 24h
6 buys · 46 sells
Price 24h
down 41.3 percent over 24 hours

The tracked token has liquidity, and trading volume was read for it within a day of its newest market reading — in that reading, or in HEY’s record of on-chain trades.

Read from DEX Screener, 1m ago.

Market history, trading and checks →

Market integrity

Liquidity is 94% below the level it held two days running ($122.1K, 2026-10-04).

Market
Active market
Under a tenth since
2026-11-09
Last day with trading
2026-11-13

Liquidity is under 10% of the level it held, on two consecutive daily readings to 2026-11-14.

No verified replacement pool for the same token was found.

Signal conflict

  • HEY observed recent builder activity while the tracked token market had already lost most of its liquidity.

This describes the token market, not whether development has stopped.

  1. seen 2026-10-15Trading fell from 3,755 trades a day (the seven days to 2026-10-07) to 30 a day in the seven days to 2026-11-10, in HEY's decoded on-chain trades.
  2. seen 2026-11-10HEY observed recent builder activity while the tracked token market had already lost most of its liquidity. Token market status: liquidity removed. This describes the token market, not whether development has stopped.
  3. Every event, with its figures, on the market page →

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-11-14 12:58 UTC · How HEY checks this

Sources

6 places HEY reads for Anyroute