Skip to main content

Unmarshal

Unmarshal (MARSH) — 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).

Unmarshal — an AI/Other / Infra project: an API/indexing platform that gives developers access to decoded onchain data (balances, transactions, NFTs, etc.) for dApps. The project’s Tier‑1 materials contain claims about “AI‑powered / AI integration”, but no detailed description of a specific AI component (models/metrics/architecture) was found per Tier‑1 sources — therefore the AI part is assessed conservatively as intent.

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: API/indexing infrastructure that helps applications obtain structured data from different blockchains.
  • Who it’s for: developers and dApp/DeFi/NFT teams who need data (balances, transactions, history, metadata).
  • Why onchain/token: the MARSH token is described as a currency/staking for participants of the indexer network and as a means of payment for/access to some functions.

How it works (very briefly)

  1. The user does: calls the API/integrates the SDK or uses the self‑serve portal.
  2. The system does: indexes blockchains and returns “rich” responses (decoded and normalized data).
  3. The user gets: data for the application (balances, NFT assets, transactions, history, etc.) with a unified interface.
  4. Where the blockchain is: the data is taken from blockchains, but processing/indexing operates as offchain infrastructure.
  5. Token role (if any): MARSH is used for staking/participation in the network and, per the description, for payments/access to some services.

Quick links: AI thesis fit

Project passport

Field Value
Project name Unmarshal
Also known as (aliases) MARSH
Logo (logo) ../assets/412_unmarshal_logo.svg
Token symbol (ticker) MARSH
Category AI/Other | 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 0x5a666c7d92e5fa7edcb6390e4efd6d0cdd69cf37
Token model (token_type) utility (payments + staking)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) staking for network roles; payments/access to services
Governance company / —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) positioning only (AI toolkit)
Use‑case (use_case) on-chain data API for apps
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 2 / 2 / 3
Last verified 2026-02-11

General project overview

Unmarshal describes itself as a provider of data infrastructure for Web3: indexers and APIs allow applications to obtain data on addresses/tokens/NFTs/transactions and to build user scenarios on top of it. The documentation (API reference) provides a description of the API set (balances/transaction history/NFT, etc.) and states goals of low response latency and fast reflection of changes in the blockchain.

Features/modules

  • DeFi/NFT API suite (balances, transactions, NFT assets, history).
  • Indexing and “decoding” of data (enriched responses/metadata).
  • Notifications (webhooks) and additional products (per the links on the website/docs).
  • Self‑serve portal/console for access to the products (console.unmarshal.io).

Typical scenarios

  • Scenario 1: a developer connects the API → obtains balances/transactions/NFTs → uses them in a dApp/analytics.
  • Scenario 2: a team connects webhooks/notifications → receives events → builds alerts for users.

Getting started (wallet/network)

  • What you need: an account in the Unmarshal self‑serve console for access to the API/keys; for onchain operations with MARSH — an EVM wallet.
  • Network/chain: data is indexed across many networks; the MARSH token is an ERC‑20 on Ethereum.
  • Fees: payment/service pricing (if applicable) + network fees for onchain operations with MARSH.

Architecture/tech (non‑AI)

  • Components: indexers/decoders, API gateways, console/portal, documentation/API reference.
  • Participant roles: data consumers (API clients), (claimed) node runners/indexers/validators in the decentralized network model.
  • Where logic runs: indexing/decoding — offchain infrastructure; onchain — the token and the (claimed) staking mechanics of the network.
  • Dependencies: RPC/node infrastructure of the supported networks; external metadata sources (not detailed per Tier‑1 sources).

Token/economics (expanded, no forecasts)

  • Token utility: staking for network roles (indexers/validators/delegators) and, per the description, payment for/access to infrastructure services and some functions (for example, premium features).
  • Protocol necessity drivers: the token is used to motivate participants and is described as the currency of the ecosystem/payments.
  • Who pays fees: data consumers/infrastructure clients (per the description) + network participants for onchain operations.
  • Where fees go: revenue distribution among network participants is claimed; the details of the mechanics and the contracts are not established per Tier‑1 sources.
  • Issuance/burn: the official materials mention a burn mechanic as part of revenue operations (without parameters per Tier‑1 sources).
  • Security/incentive mechanisms: MARSH staking for network roles; slashing conditions are not established per Tier‑1 sources.
  • Distribution and token issuance schedule: the tokenomics publication describes lock/vesting decisions (for example, holding part of the tokens in a vesting contract until the specified date).
  • Treasury: — (not established per Tier‑1 sources).

Governance

  • Who makes decisions: the Unmarshal team/company (decentralized governance is not confirmed by Tier‑1 sources).
  • How protocol parameters change: via updates of products/documentation and infrastructure (per public announcements/posts).
  • Where decisions are discussed/made: official channels (Website/Docs/Blog/X/Discord/Telegram).
  • Keys/multisig: — (not established per Tier‑1 sources).

Security and incidents

  • Audits: — (not established per Tier‑1 sources).
  • Bug bounty: — (not established).
  • Incidents: — (not established).
  • Threat model: risks to the quality/correctness of indexed data, centralization of infrastructure, compromise of API keys/accounts and service outages; for the token part — smart contract/staking risks (if/when the mechanics are fully onchain).

Project status and timeline

  • Current status: active (based on the presence of docs/console).
  • Key releases/milestones: — (not established per Tier‑1 sources; see the project blog).
  • Roadmap: — (in links_*).

Ecosystem/integrations

  • Integrations: support for many networks via the API; a self‑serve console for clients.
  • Partners: — (not established per Tier‑1 sources).
  • Where it’s actually used: dApps/DeFi/NFT applications that need balances/transactions/NFT data via the API (per the docs description).

AI component of the project

  • What is real AI here? The Tier‑1 materials contain “AI‑powered / AI integration” positioning, but a detailed description of a specific AI component (what it does and how it is verified) is not established per Tier‑1 sources.
  • What is truly onchain? the MARSH token as an ERC‑20 (address in the explorer); the official publications describe staking roles for a decentralized network of indexers.
  • Why is a token needed? the token is described as a stake for network participants and as a currency/means of payment for/access to some functions of the ecosystem.
  • Red flags (based on the information found): AI‑washing — “AI‑powered” without a tech description/metrics; what to double‑check — the presence of a public specification of the AI modules and of onchain staking/role contracts.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): the official website claims “Powered by AI” and “Blockchain and AI integration”.
  • Evidence: Tier‑1 — https://unmarshal.io/
  • Why sufficient / why not (one line): this is a Tier‑1 declaration of intent, but without proof of a specific AI component/metrics.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): what exactly the AI does in the product is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://unmarshal.io/ ; Tier‑1 — https://docs.unmarshal.io/
  • Why sufficient / why not (one line): there is AI positioning, but no coherent description of an AI feature as a separate component of the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a demo of the AI component specifically is not established; there is a self‑serve console for the API.
  • Evidence: Tier‑1 — https://unmarshal.io/
  • Why sufficient / why not (one line): the console/portal confirms the product, but does not prove an AI demo as a verifiable AI artifact.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://unmarshal.io/
  • Why sufficient / why not (one line): the website has general “stats”, but no AI quality metrics/benchmarks.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a tech description of the AI component/versions is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.unmarshal.io/
  • Why sufficient / why not (one line): the documentation describes the API/products, but does not disclose the AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x5a666c7d92e5fa7edcb6390e4efd6d0cdd69cf37 (MARSH ERC‑20)
  • Evidence: Tier‑1 — https://etherscan.io/token/0x5a666c7d92E5fA7Edcb6390E4efD6d0CDd69cF37
  • Why sufficient / why not (one line): there is a verifiable onchain fact of the token (the contract) via the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: staking/role mechanics for participants of the indexer network (per the description “network contributors stake MARSH”).
  • Evidence: Tier‑1 — https://blog.unmarshal.io/marsh-in-unmarshal-ecosystem-a-complete-guide-c07127408ea9
  • Why sufficient / why not (one line): the official publication describes staking roles and economic interactions that go beyond “just a token”.
  • Conflict note (if any): staking addresses/contracts are not specified in the Tier‑1 sources used.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: indexing and data delivery can exist as a centralized service; onchain criticality as a trustless property is not proven by Tier‑1.
  • Evidence: Tier‑1 — https://docs.unmarshal.io/
  • Why sufficient / why not (one line): the docs describe the API infrastructure, but do not prove that the product “breaks down” without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the MARSH token exists (ERC‑20 contract).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x5a666c7d92E5fA7Edcb6390E4efD6d0CDd69cF37
  • Why sufficient / why not (one line): there is an onchain token contract.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): in the ecosystem description, MARSH is specified as the currency/payment for using the infrastructure (payments).
  • Evidence: Tier‑1 — https://blog.unmarshal.io/marsh-in-unmarshal-ecosystem-a-complete-guide-c07127408ea9
  • Why sufficient / why not (one line): the official article lists the use cases: payment/stake/premium features.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): MARSH staking is used for network roles (indexers/validators/delegators) and for the distribution of revenue/rewards.
  • Evidence: Tier‑1 — https://blog.unmarshal.io/marsh-in-unmarshal-ecosystem-a-complete-guide-c07127408ea9
  • Why sufficient / why not (one line): the article describes the roles and the need for a stake for participation/network security.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of MARSH for governance is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.unmarshal.io/ ; https://unmarshal.io/
  • Why sufficient / why not (one line): in the available Tier‑1 sources the emphasis is on staking/payment, not on governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): no statement was found in Tier‑1 that the token can be fully replaced without loss of network functions.
  • Evidence: Tier‑1 — https://blog.unmarshal.io/marsh-in-unmarshal-ecosystem-a-complete-guide-c07127408ea9
  • Why sufficient / why not (one line): replaceability requires separate proof/a model; the current materials do not substantiate it.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.unmarshal.io/ the product: API/indexing of onchain data (description of the API set and purpose)
Tier‑1 https://unmarshal.io/ Tier‑1 positioning “Powered by AI / AI integration” + links to the console/products
Tier‑1 https://etherscan.io/token/0x5a666c7d92E5fA7Edcb6390E4efD6d0CDd69cF37 the MARSH token contract (a verifiable onchain fact)
Tier‑1 https://blog.unmarshal.io/marsh-in-unmarshal-ecosystem-a-complete-guide-c07127408ea9 the token’s role: staking/payment/premium features; the network role model
Tier‑1 https://blog.unmarshal.io/marsh-tokenomics-explained-36dead3ff2b1 tokenomics: lock/vesting decisions (distribution context)
Tier‑2 https://www.coingecko.com/en/coins/unmarshal aggregator (context/for reference)
Tier‑2 https://coinmarketcap.com/currencies/unmarshal/ aggregator (context/for reference)

No comments to display

Back to top