Skip to main content

Bird.Money

Bird.Money — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Bird.Money — an AI/Analytics \| DeFi project on Ethereum, token (symbol: BIRD).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: an oracle/interface that publishes “analytical signals” about addresses (wallet‑level analytics) for Web3 applications.
  • Who it’s for: developers and protocols that need risk signals/scoring and personalization.
  • Why onchain/token: onchain is used as the integration layer and for token ownership; the ML/analytics computations themselves are claimed to be offchain.

How it works (very briefly)

  1. The user does: a dApp/protocol requests analytics for a specific address.
  2. The system does: aggregates onchain/offchain data and runs it through ML/analytics models (per the project’s description).
  3. The user gets: analytical products/signals for UX and risk assessment (for example, in DeFi applications).
  4. Where the blockchain is: onchain — integration/execution in the Web3 application and the token on Ethereum; offchain — computations and models.
  5. Token role (if any): the BIRD token exists (ERC‑20); the necessity of the token for access/payment is not established per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Bird.Money
Also known as (aliases) Bird Money, BIRD
Logo (logo) ../assets/421_bird-money_logo.svg
Token symbol (ticker) BIRD
Category AI/Analytics | DeFi | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x70401dfd142a16dc7031c56e862fc88cb9537ce0
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance DAO (Bird DAO; token details not established)
Admins/keys —
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) ML analytics for oracle signals
Use‑case (use_case) address scoring/analytics for Web3 UX
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 1
Last verified 2026-02-11

General project overview

Bird.Money positions itself as an “off‑chain analytics oracle” that “brings machine learning to Web3” and allows developers to obtain analytical products for specific addresses via an oracle interface.

Features/modules

  • An oracle interface for accessing analytical products.
  • ML/predictive analytics based on onchain and offchain data streams (per the project’s claims).

Typical scenarios

  • Scenario 1: a DeFi protocol receives an analytical signal for an address → uses it in its risk logic/product conditions.
  • Scenario 2: a dApp receives “address‑level” analytics → personalizes the UX/offers for a specific user.
  • Scenario 3: a developer studies the documentation and integrates the oracle interface into their application.

Getting started (wallet/network)

  • What you need: access to the documentation and integration on the application/protocol side.
  • Network/chain: Ethereum (the BIRD token); the network/addresses of the oracle contracts are not established per Tier‑1 sources.
  • Fees: network fees for onchain operations; the offchain part depends on the integration.

Architecture/tech (non‑AI)

  • Components: the BIRD token (ERC‑20), the oracle interface, offchain analytics (per the project’s description).
  • Participant roles: developers/integrating protocols; dApp users (indirectly).
  • Where logic runs: offchain — analytics/ML; onchain — integration and the token.
  • Dependencies: onchain/offchain data sources (not detailed per Tier‑1 sources).

Token/economics (expanded, no forecasts)

  • Token utility: a Tier‑1 description of the necessity of the token for access/payment for the service was not found per Tier‑1 sources.
  • Protocol necessity drivers: — (not found per Tier‑1 sources).
  • Who pays fees: network users for operations with the token; integrators/users — depending on the implementation.
  • Where fees go: — (not found per Tier‑1 sources).
  • Issuance/burn: — (not found per Tier‑1 sources).
  • Security/incentive mechanisms: — (not found per Tier‑1 sources).
  • Distribution and token issuance schedule: — (not found per Tier‑1 sources).
  • Treasury: — (not found per Tier‑1 sources).

Governance

  • Who makes decisions: Bird DAO is mentioned on the official website as a “shared decision making” model.
  • How protocol parameters change: — (not found per Tier‑1 sources).
  • Where decisions are discussed/made: — (not found per Tier‑1 sources).
  • Keys/multisig: — (not found per Tier‑1 sources).

Security and incidents

Project status and timeline

  • Current status: active; the BIRD token is on Ethereum mainnet.
  • Key releases/milestones: — (not found per Tier‑1 sources).
  • Roadmap: given on the official website.

Ecosystem/integrations

  • Integrations: — (not found per Tier‑1 sources).
  • Partners: “Partners” are listed on the website (not confirmed per Tier‑1 sources as integrations).
  • Where it’s actually used: as oracle analytics for dApps/protocols (per the project’s positioning).

AI component of the project

  • What is real AI here? The official website claims that the project uses machine learning and predictive analytics, providing analytical products via an oracle.
  • What is truly onchain? The Tier‑1‑confirmed onchain artifact is the BIRD token contract on Ethereum; onchain addresses of the oracle contracts/modules were not found per Tier‑1 sources.
  • Why is a token needed? The existence of the token is established, but a Tier‑1 explanation of the necessity of the token in the product was not found per Tier‑1 sources.
  • Red flags (based on the information found): the absence of metrics/benchmarks of the ML models; the absence of confirmed addresses of the onchain oracle modules; the risk of “token‑first” without confirmation of the necessity of the token for access/payment.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 1
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There is AI intent, but there is also a direct description of the AI feature (AI_1) and of the concept (AI_4).
  • Evidence: Tier‑1 — https://bird.money/
  • Why sufficient / why not (one line): AI_0 applies when there is only intent without a description of the AI feature; here the description exists.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The project claims ML/predictive analytics that produce analytical products for addresses via an oracle interface.
  • Evidence: Tier‑1 — https://bird.money/ , https://docs.bird.money/
  • Why sufficient / why not (one line): The Tier‑1 sources explicitly state “machine learning” and the purpose of the analytical products.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A public app/demo/guide that allows one to reproducibly “touch” the ML analytics (in product form) was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.bird.money/
  • Why sufficient / why not (one line): The documentation contains descriptions, but there is no explicit “app/demo” artifact for verifying the result.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://bird.money/ , https://docs.bird.money/
  • Why sufficient / why not (one line): No quantitative quality metrics/benchmarks of the models were found per Tier‑1 sources.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): The concept is described: onchain/offchain data streams → ML models → an oracle interface for dApps.
  • Evidence: Tier‑1 — https://bird.money/
  • Why sufficient / why not (one line): There is a Tier‑1 description of the architectural scheme at the component level (without details of specific models).
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the BIRD token: 0x70401dfd142a16dc7031c56e862fc88cb9537ce0
  • Evidence: Tier‑1 — https://etherscan.io/token/0x70401dfd142a16dc7031c56e862fc88cb9537ce0
  • Why sufficient / why not (one line): There is a public onchain artifact (the token contract) in the explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: No Tier‑1 addresses/description of onchain oracle modules (other than the token) were found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.bird.money/
  • Why sufficient / why not (one line): The documentation describes the oracle interface, but without confirmed addresses/contracts.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: A Tier‑1 justification of “without the blockchain the product breaks down” was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://bird.money/
  • Why sufficient / why not (one line): The positioning speaks of a Web3 oracle interface, but the criticality of the onchain layer is not proven.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, BIRD (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x70401dfd142a16dc7031c56e862fc88cb9537ce0
  • Why sufficient / why not (one line): The token contract is confirmed in the explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): A Tier‑1 description of payment for the service with the BIRD token was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.bird.money/
  • Why sufficient / why not (one line): The documentation has no explicit description of a paywall/tariff via the token.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): A Tier‑1 description of incentives/collateral/penalties tied to the BIRD token was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.bird.money/
  • Why sufficient / why not (one line): No description of TK_2 mechanics was found per Tier‑1 sources.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Bird DAO is mentioned, but a Tier‑1 link of governance specifically to the BIRD token is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://bird.money/
  • Why sufficient / why not (one line): A mention of a DAO does not equal proof of token governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): No Tier‑1 proof of an irreplaceable function of the BIRD token in the protocol was found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.bird.money/
  • Why sufficient / why not (one line): There is no described onchain mechanic that requires specifically BIRD as a mandatory element.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://bird.money/ Tier‑1: the project claims an “off‑chain analytics oracle” and “machine learning to Web3”, as well as an oracle interface for analytical products.
Tier‑1 https://docs.bird.money/ Tier‑1: the project documentation (context and a description of “what the product does”).
Tier‑1 https://etherscan.io/token/0x70401dfd142a16dc7031c56e862fc88cb9537ce0 Tier‑1 onchain fact: the BIRD token contract on Ethereum.
Tier‑1 https://github.com/bird-money/bird-smart-contract-erc20/blob/master/CHANGELOG.md Tier‑1: an artifact of releases/changes of the token contract.
Tier‑1 https://github.com/bird-money/bird-smart-contract-erc20/tree/master/audit Tier‑1: a section with audit materials is published (per the repository).
Tier‑1 — No Tier‑1 source for claim “there is an app/demo/guide for reproducible verification of the ML analytics” was found per Tier‑1 sources.
Tier‑1 — No Tier‑1 source for claim “the BIRD token is mandatory for payment/access to the product” was found per Tier‑1 sources.
Tier‑2 https://www.coingecko.com/en/coins/bird-money Tier‑2 token profile/metadata and links (context).
Tier‑2 https://coinmarketcap.com/currencies/bird-money/ Tier‑2 token profile/metadata and links (context).

No comments to display

Back to top