Skip to content
HEY Research Lab
Menu

odaiin

AI Agents

Is this your project? Claim it →

Agent Skill, REST/OpenAPI tools, and optional MCP adapter for non-custodial route evaluation across Solana, Base, Arbitrum, and Robinhood Chain.

What HEY knows

Development

Shipping consistentlyShipping: 13 counted ships in 30 days; latest ship 7 days ago. Evidence Source

Build Momentum 73How it is measured

Latest: assetfare-mcp 1.21.6

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

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

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

View latest ship
Share
More detail
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.
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: 13 counted ships in the last 30 days, the newest 2026-10-25.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsassetfare-mcp 1.21.6Code changes, week of 2026-10-19 – 2026-10-25 · 6 commitsassetfare-mcp 1.21.3+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.
Source4 registered sources, 0 of them context only.ReadRecordsassetfare-mcp 1.21.6Code changes, week of 2026-10-19 – 2026-10-25 · 6 commitsassetfare-mcp 1.21.3+5 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 11 research questions that apply.
8 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 45m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 7d 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 4d ago.
  • Published packagesMeasuredRead 5m ago.
  • Package advisoriesMeasuredRead 4d ago.

Not applicable here: 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
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

assetfare-mcp 1.21.6

GitHub releaseSource-backed

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

Security hardening release. Pins fast-uri 3.1.9, ip-address 10.7.5, and stream-json 3.7.0 while preserving the compatible Solana web3.js 1.x API. Full test matrix passes and root production npm audit reports zero vulnerabilities. Non-custodial and no-sign/no-submit boundaries… Show all

Security hardening release. Pins fast-uri 3.1.9, ip-address 10.7.5, and stream-json 3.7.0 while preserving the compatible Solana web3.js 1.x API. Full test matrix passes and root production npm audit reports zero vulnerabilities. Non-custodial and no-sign/no-submit boundaries are unchanged.

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

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “assetfare-mcp 1.21.6” (v1.21.6).
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Independently recorded: a package version published from the same repository matches it (npm assetfare-mcp@1.21.6).
Release and deployment
Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to 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-25 16:45 UTC; HEY first knew on 2026-10-25.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts. Timing alone never links a release to a deployment.

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.

View evidence ↗ (opens in a new tab)Post this ship on X

Shared change · Development spike

odaiin: 8 meaningful ships were recorded in the latest 7 days, from 3 in the 7 days before.

Builder status: Shipping.

Dated 2026-10-12 by the sourceSource: HEY Signal

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: 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-19 – 2026-10-25 · 6 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in assetfare/assetfare-mcp.

    How HEY read this week

    This week HEY looked inside 2 of 6 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. 1 automated commit (bot accounts or a repeating scripted message) not counted.

    View evidence: Code changes, week of 2026-10-19 – 2026-10-25 · 6 commits (opens in a new tab)

  2. 2 releases in assetfare/assetfare-mcp on 25 Oct

    GitHub release

    Show all 2 releases

    1. assetfare-mcp v1.21.5

      GitHub releaseSource-backed

      Supersedes v1.21.4 for npm publication. Preserves the 65-route whole-product policy update while upgrading Express/body-parser and Zod, using the audited Zod v3 compatibility entrypoint. Full tests and the high-severity npm audit gate pass.

      View evidence: assetfare-mcp v1.21.5 (opens in a new tab)

    2. assetfare-mcp v1.21.4

      GitHub releaseSource-backed

      Aligns npm, hosted MCP, A2A, skills, and integration metadata with the 65-route whole-product policy: 3 core, 50 conditional, 12 strategic/scarce, with 35 researched routes not offered. Adds fail-closed support for economic guidance v5 and caller-owned execution v3.

      View evidence: assetfare-mcp v1.21.4 (opens in a new tab)

  3. 4 releases in assetfare/assetfare-mcp on 12 Oct

    GitHub release

    Show all 4 releases

    1. assetfare-mcp 1.21.3

      GitHub releaseSource-backed

      Caps every route-recommendation profile at an absolute 60 seconds. Fast remains 30 seconds; balanced and explicit economy are 60 seconds. Slower routes remain reference-only. AssetFare still never signs or submits.

      View evidence: assetfare-mcp 1.21.3 (opens in a new tab)

    2. assetfare-mcp v1.21.2

      GitHub releaseSource-backed

      Proof-carrying caller execution handoff for the six route-intelligence pilots, with restored fail-closed live evidence verification. AssetFare candidates require deterministic caller-local recomputation and fresh wallet simulation before a compact verified_for_signing verdict… Show all

      Proof-carrying caller execution handoff for the six route-intelligence pilots, with restored fail-closed live evidence verification. AssetFare candidates require deterministic caller-local recomputation and fresh wallet simulation before a compact verified_for_signing verdict; external provider candidates remain explicit provider handoffs. Public evidence and RPC quorum verification now handles provider-specific archive capabilities transparently without weakening chain-ID, runtime-code, or deployment-receipt quorum. AssetFare never receives private keys, signs, or submits.

      View evidence: assetfare-mcp v1.21.2 (opens in a new tab)

    3. assetfare-mcp v1.21.1

      GitHub releaseSource-backed

      Proof-carrying caller execution handoff for the six route-intelligence pilots. AssetFare candidates now require deterministic caller-local recomputation and fresh wallet simulation before a compact verified_for_signing verdict; external provider candidates remain explicit… Show all

      Proof-carrying caller execution handoff for the six route-intelligence pilots. AssetFare candidates now require deterministic caller-local recomputation and fresh wallet simulation before a compact verified_for_signing verdict; external provider candidates remain explicit provider handoffs. AssetFare never receives private keys, signs, or submits.

      View evidence: assetfare-mcp v1.21.1 (opens in a new tab)

    4. assetfare-mcp v1.21.0

      GitHub releaseSource-backed

      Adds proof-carrying execution handoffs for the six route-intelligence pilots. AssetFare candidates now require caller-local deterministic re-verification and fresh wallet simulation before a compact verified_for_signing verdict. External-provider selections remain explicit… Show all

      Adds proof-carrying execution handoffs for the six route-intelligence pilots. AssetFare candidates now require caller-local deterministic re-verification and fresh wallet simulation before a compact verified_for_signing verdict. External-provider selections remain explicit provider handoffs and do not inherit AssetFare transaction-verification claims. AssetFare remains non-custodial and never receives private keys, signs, or submits.

      View evidence: assetfare-mcp v1.21.0 (opens in a new tab)

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

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in assetfare/assetfare-mcp.

    How HEY read this week

    This week HEY looked inside 1 of 4 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-10-12 – 2026-10-18 · 4 commits (opens in a new tab)

  5. 4 releases in assetfare/assetfare-mcp on 11 Oct

    GitHub release

    Show all 4 releases

    1. assetfare-mcp v1.20.3

      GitHub releaseSource-backed

      Adds always-on current AssetFare amount guidance to six-pilot route selection. Requests now quote the recent top two plus the best AssetFare direct graph at the caller exact amount. Static crossover hints are removed; observed higher-amount ranges require two supporting buckets… Show all

      Adds always-on current AssetFare amount guidance to six-pilot route selection. Requests now quote the recent top two plus the best AssetFare direct graph at the caller exact amount. Static crossover hints are removed; observed higher-amount ranges require two supporting buckets, remain advisory, and are suppressed by a conflicting exact quote. The non-custodial no-sign/no-submit boundary is unchanged.

      View evidence: assetfare-mcp v1.20.3 (opens in a new tab)

    2. assetfare-mcp 1.20.2

      GitHub releaseSource-backed

      Expands the 30-minute complete-graph route-intelligence pilot from four Solana-to-Base routes to six Solana-origin Base/Arbitrum routes. Preserves exact request-amount top-three requoting, fresh top-two recommendations, caller-owned signing, and server signing/submission… Show all

      Expands the 30-minute complete-graph route-intelligence pilot from four Solana-to-Base routes to six Solana-origin Base/Arbitrum routes. Preserves exact request-amount top-three requoting, fresh top-two recommendations, caller-owned signing, and server signing/submission disabled.

      View evidence: assetfare-mcp 1.20.2 (opens in a new tab)

    3. assetfare-mcp v1.20.1

      GitHub releaseSource-backed

      Four-pilot Solana-to-Base route intelligence: 30-minute multi-amount exploration across the complete USDC/SOL to USDC/ETH matrix, with exact request-time top-three quoting and fresh top-two recommendations. AssetFare remains non-custodial and never signs or submits.

      View evidence: assetfare-mcp v1.20.1 (opens in a new tab)

    4. assetfare-mcp v1.20.0 (unpublished)

      GitHub releaseSource-backed

      Unpublished superseded release. Provenance CI stopped before artifact creation or npm publication because a documentation self-test still expected the retired nine-tool count. No package was published from this tag; v1.20.1 contains the corrected self-test.

      View evidence: assetfare-mcp v1.20.0 (unpublished) (opens in a new tab)

  6. Code changes, week of 2026-10-05 – 2026-10-11 · 15 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    5 active days in assetfare/assetfare-mcp.

    How HEY read this week

    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.

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 15 commits (opens in a new tab)

  7. 3 releases in assetfare/assetfare-mcp on 10 Oct

    GitHub release

    Show all 3 releases

    1. assetfare-mcp v1.19.1

      GitHub releaseSource-backed

      Full Changelog: https://github.com/assetfare/assetfare-mcp/compare/v1.19.0...v1.19.1

      View evidence: assetfare-mcp v1.19.1 (opens in a new tab)

    2. assetfare-mcp v1.19.0

      GitHub releaseSource-backed

      Full Changelog: https://github.com/assetfare/assetfare-mcp/compare/v1.18.0...v1.19.0

      View evidence: assetfare-mcp v1.19.0 (opens in a new tab)

    3. AssetFare MCP v1.18.0

      GitHub releaseSource-backed

      Adds precomputed, time-aware top-two route selection and exact selected-candidate requoting. AssetFare candidates retain strict continuation_v3 binding; external candidates return normalized fresh quote facts and a provider handoff without executable payloads. AssetFare never… Show all

      Adds precomputed, time-aware top-two route selection and exact selected-candidate requoting. AssetFare candidates retain strict continuation_v3 binding; external candidates return normalized fresh quote facts and a provider handoff without executable payloads. AssetFare never receives private keys, signs, or submits.

      View evidence: AssetFare MCP v1.18.0 (opens in a new tab)

  8. 7 releases in assetfare/assetfare-mcp on 9 Oct

    GitHub release

    Show all 7 releases

    1. assetfare-mcp v1.17.1

      GitHub releaseSource-backed

      Patch release for the 100-route v2 adapter. Accepts only the three exact boolean noncustodial policy fields returned by Core (private_keys_accepted=false, private_key_stays_client_side=true, and assetfare_accepts_private_key=false) while continuing to fail closed on private-key… Show all

      Patch release for the 100-route v2 adapter. Accepts only the three exact boolean noncustodial policy fields returned by Core (private_keys_accepted=false, private_key_stays_client_side=true, and assetfare_accepts_private_key=false) while continuing to fail closed on private-key, secret, signed-transaction, and unsafe action material. Adds hostile regression coverage and keeps server signing/submission disabled.

      View evidence: assetfare-mcp v1.17.1 (opens in a new tab)

    2. assetfare-solana-agent-kit-plugin 1.3.0

      GitHub releaseSource-backed

      Adds AssetFare 100-route, Unichain/Ink, and economic guidance v4 compatibility.

      View evidence: assetfare-solana-agent-kit-plugin 1.3.0 (opens in a new tab)

    3. @assetfare/goat-plugin 1.3.0

      GitHub releaseSource-backed

      Adds AssetFare 100-route, Unichain/Ink, and economic guidance v4 compatibility.

      View evidence: @assetfare/goat-plugin 1.3.0 (opens in a new tab)

    4. assetfare-elizaos-route-plugin 1.3.0

      GitHub releaseSource-backed

      Adds AssetFare 100-route, Unichain/Ink, and economic guidance v4 compatibility.

      View evidence: assetfare-elizaos-route-plugin 1.3.0 (opens in a new tab)

    5. assetfare-agentkit-action-provider 1.3.0

      GitHub releaseSource-backed

      Adds AssetFare 100-route, Unichain/Ink, and economic guidance v4 compatibility.

      View evidence: assetfare-agentkit-action-provider 1.3.0 (opens in a new tab)

    6. @assetfare/agenti-route-tools 1.3.0

      GitHub releaseSource-backed

      Adds AssetFare 100-route, Unichain/Ink, and economic guidance v4 compatibility.

      View evidence: @assetfare/agenti-route-tools 1.3.0 (opens in a new tab)

    7. assetfare-mcp 1.17.0

      GitHub releaseSource-backed

      Adds the 100-route AssetFare contract, Core 98/100 compatibility, Unichain and Ink source routes, economic guidance v4, and updated agent integration contracts.

      View evidence: assetfare-mcp 1.17.0 (opens in a new tab)
Earlier ships (1)

  1. AssetFare MCP 1.16.0

    GitHub releaseSource-backed

    Expose all 98 technically ready routes through the same non-custodial quote, unsigned prepare, and session flow. Price guidance remains advisory: 44 routes are price-recommended at published thresholds and 54 have no current price recommendation. No economic acknowledgement… Show all

    Expose all 98 technically ready routes through the same non-custodial quote, unsigned prepare, and session flow. Price guidance remains advisory: 44 routes are price-recommended at published thresholds and 54 have no current price recommendation. No economic acknowledgement field is required. AssetFare never receives private keys, signs, or submits transactions.

    View evidence: AssetFare MCP 1.16.0 (opens in a new tab)

Other changes on HEY’s record

143 changes on HEY’s record for odaiin: 129 releases · 1 new Verified Builder or owner proof · 3 build pace changes · 10 weeks of code pushed.

All 143 changes for odaiin →

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

Questions HEY can answer about odaiin — as of 1 Nov

Show the answers
Is odaiin still being built?
DerivedShipping: 13 counted ships in 30 days; latest ship 7 days ago. Evidence
What did odaiin ship last?
Factassetfare-mcp 1.21.6 — GitHub release, 7 days ago. Evidence
What does HEY not know about odaiin?
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.

Sources

4 places HEY reads for odaiin