Skip to main content

StrikeBit

StrikeBit (STRIKE) — 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).

StrikeBit — an AI/Agents / Infra project: a platform and documentation for creating/running/monetizing AI agents (Multi‑Agent architecture, “Modular Agent Protocol”) and the “Radiant AI Agents” showcase. Onchain SSOT: the STRIKE token (BEP‑20) on the BNB Smart Chain network (per BscScan).

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: a platform where you can get access to “AI agents” and use them, and also (as claimed) launch your own agents/tokens.
  • Who it’s for: users/traders (agents “for trading/analytics”), developers (modular agents), the community.
  • Why onchain/token: the STRIKE token on BSC is confirmed; the docs also describe onchain ownership for “Agent NFTs”, but contract addresses (other than the token) are not confirmed in this card.
  • What you can actually touch (Tier‑1): radiant.strikebit.io (the agent package showcase) and the official documentation docs.strikebit.io.

How it works (very briefly)

  1. The user does: buys/selects an AI agent in Radiant and uses it (per the website).
  2. The system does: provides agent functions (analytics/signals/automation — per the description of the tiers) and describes the “Multi‑Agent” architecture in the docs.
  3. The user gets: results/insights from the agent and (as claimed) can “earn Strike tokens”.
  4. Where the blockchain is: the STRIKE token is onchain on BSC; the other onchain modules require addresses/contracts.
  5. Token role: rewards/ecosystem economy (per the website); governance is described as a future module (per the roadmap).

Quick links: AI thesis fit

Project passport

Field Value
Project name StrikeBit
Also known as (aliases) StrikeBit AI; Radiant AI
Logo (logo) ../assets/239_strikebit-ai_logo.svg
Token symbol (ticker) STRIKE
Category AI/Agents | Infra
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) 2024 (copyright on the website)
Project status (status) active (website/docs available)
Token (standard) BEP-20
Token contract 0x2aa89a0113bcbbcdc5812c6df794e2d9650fc1af
Token model (token_type) utility (rewards; governance in roadmap)
Max supply 2,000,000,000 STRIKE (BscScan Max Total Supply)
Issuance capped (max total supply on BscScan)
Tokenomics (tokenomics, brief) rewards for usage/participation are claimed; tokenomics details — in the docs tokenomics
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) modular AI agents + multi-agent architecture
Use‑case (use_case) AI agents for analytics/trading + ownership models
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 1 / 0 / 3
Last verified 2026-02-11

General project overview

StrikeBit positions itself as a platform that “makes AI Agents accessible to millions”: users can buy ready‑made “Radiant AI Agents” (Core/Prime/Elite tiers), while developers can create modular and customizable agents (MAP, Multi‑Agent architecture) and monetize them.

The GitBook documentation describes the concepts of ownership/packaging of agents as tokenized objects (ERC404‑based Agent NFTs — per the docs) and a roadmap where governance for $STRIKE is listed as a future module. In this card, the onchain SSOT is confirmed for the STRIKE token on BNB Smart Chain; the addresses of the other protocol contracts are not provided.

Features/modules

  • Radiant AI Agents: showcase/purchase of agent packages and tiers (website).
  • Modular Agent Protocol / Multi‑Agent architecture: documentation on modularity and “subagents” (docs).
  • AgentHub / Agent migration (claimed): migration/ownership concepts for agents (docs).

Typical scenarios

  • Scenario 1 (user): selects a Radiant agent → uses it for analytics/signals → receives insights/alerts (website).
  • Scenario 2 (dev): uses the MAP approach → assembles a multi‑agent system → publishes/monetizes it (docs).

Getting started (wallet/network)

  • What you need: access to radiant.strikebit.io and/or the documentation docs.strikebit.io.
  • Network/chain: BNB Smart Chain (STRIKE token).
  • Fees: BSC fees for onchain operations with the STRIKE token.

Architecture/tech (non‑AI)

  • Components: web showcases (Radiant/Launch Portal), docs (GitBook), the STRIKE token (BEP‑20), offchain AI agents.
  • Participant roles: users, agent developers, the platform team/operator.
  • Where logic runs: agent logic — offchain; the token — onchain on BSC.
  • Dependencies: web infrastructure; BSC RPC for onchain operations.

Token/economics (expanded, no forecasts)

  • Token utility: rewards/incentives (website) and a separate tokenomics section in the docs.
  • Protocol necessity drivers: the token’s role in must‑have flows (payment/access) is not confirmed in the extracted Tier‑1 sources.
  • Who pays fees: BSC users for onchain operations with STRIKE.
  • Where fees go: to BSC validators.
  • Issuance/burn: max total supply 2,000,000,000 STRIKE (BscScan).
  • Security/incentive mechanisms: there is a rewards context; staking/slashing parameters are not confirmed in the extracted Tier‑1.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: Discord/Telegram/X (links_*).
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: per the current materials, the AI part is not accompanied by verifiable metrics and technical details; there also remain risks of centralized control over the agent infrastructure and token/contract risks (no audits provided).

Project status and timeline

  • Current status: active (website + docs available).
  • Key releases/milestones: —.
  • Roadmap: in the docs roadmap overview.

Ecosystem/integrations

  • Integrations: Telegram mini app (described in the docs), the Radiant/Launch web showcases, BSC token.
  • Partners: —.
  • Where it’s actually used: as an agent showcase and documentation for creating modular agents (Tier‑1).

AI component of the project

  • What is real AI here? Tier‑1 contains a description of the “AI Agents” product and a modular multi‑agent architecture (MAP), but without public quality metrics.
  • What is truly onchain? The STRIKE token contract (BEP‑20) on BNB Smart Chain.
  • Why is a token needed? The website says that users can “earn Strike tokens”; the governance module is listed in the roadmap as future.
  • Red flags (based on the information found): AI‑washing (no KPIs/metrics), onchain‑washing (only the token is confirmed in this card), absence of public audits.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): the AI agents are described as a product, not only as a roadmap.
  • Evidence: Tier‑1 — https://www.strikebit.io/ ; https://docs.strikebit.io/
  • Why sufficient / why not (one line): there is a description of the functions and the architecture, so AI_0 is not needed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the platform provides AI agents and a modular multi‑agent approach (MAP).
  • Evidence: Tier‑1 — https://docs.strikebit.io/ ; https://www.strikebit.io/
  • Why sufficient / why not (one line): Tier‑1 describes what is being built and how it is used.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the Radiant AI Agents showcase (purchase/tiers) and public docs are available.
  • Evidence: Tier‑1 — https://radiant.strikebit.io/ ; https://docs.strikebit.io/
  • Why sufficient / why not (one line): the product showcase and the documentation can be checked.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.strikebit.io/
  • Why sufficient / why not (one line): the docs contain no verifiable KPIs/benchmarks of agent quality.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the multi‑agent architecture and MAP as a modular framework are described.
  • Evidence: Tier‑1 — https://docs.strikebit.io/introduction/multi-agent-architecture-and-map
  • Why sufficient / why not (one line): there is a high‑level technical description.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: BEP‑20 STRIKE: 0x2aa89a0113bcbbcdc5812c6df794e2d9650fc1af
  • Evidence: Tier‑1 — https://bscscan.com/token/0x2aa89a0113bcbbcdc5812c6df794e2d9650fc1af
  • Why sufficient / why not (one line): BscScan confirms the token contract and the Max Total Supply.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: apart from the token, the protocol’s onchain addresses/contracts (Agent NFTs/marketplace) are not confirmed in this card.
  • Evidence: Tier‑1 — https://docs.strikebit.io/
  • Why sufficient / why not (one line): there are onchain concepts, but no onchain SSOT addresses.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the AI agents and the showcase can work in a centralized way; the blockchain’s criticality for the core functions is not proven.
  • Evidence: Tier‑1 — https://www.strikebit.io/ ; https://docs.strikebit.io/
  • Why sufficient / why not (one line): there is no strict proof of “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 project has a token, STRIKE (BEP‑20).
  • Evidence: Tier‑1 — https://bscscan.com/token/0x2aa89a0113bcbbcdc5812c6df794e2d9650fc1af
  • Why sufficient / why not (one line): the token is confirmed onchain.
  • 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): the available Tier‑1 sources contain no strict statement of “payment for services in STRIKE”.
  • Evidence: Tier‑1 — https://docs.strikebit.io/
  • Why sufficient / why not (one line): the docs describe the product and the token, but do not record a payment layer in the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): “Users can earn Strike tokens” (reward context).
  • Evidence: Tier‑1 — https://www.strikebit.io/
  • Why sufficient / why not (one line): the reward statement is published on the official website.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the governance module for $STRIKE is described as a future phase (roadmap).
  • Evidence: Tier‑1 — https://docs.strikebit.io/roadmap/overview
  • Why sufficient / why not (one line): this is an intent/roadmap, not proof of working governance.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the reward model and access to the agents could potentially be implemented without its own token.
  • Evidence: Tier‑1 — https://www.strikebit.io/ ; https://docs.strikebit.io/
  • Why sufficient / why not (one line): there is no Tier‑1 proof of the irreplaceability of STRIKE.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.strikebit.io/ Product positioning, Radiant tiers, the “earn Strike tokens” reward context, roadmap on the website.
Tier‑1 https://docs.strikebit.io/ Official documentation: MAP/multi‑agent concepts and product sections.
Tier‑1 https://docs.strikebit.io/introduction/multi-agent-architecture-and-map Technical description of the multi‑agent architecture.
Tier‑1 https://docs.strikebit.io/roadmap/overview Roadmap: development phases and the “$STRIKE governance module” as a future phase.
Tier‑1 https://bscscan.com/token/0x2aa89a0113bcbbcdc5812c6df794e2d9650fc1af Onchain SSOT: the STRIKE token, decimals=18, Max Total Supply 2B.
Tier‑2 https://coinmarketcap.com/currencies/strikebit-ai/ Aggregator: reference profile and links (not Tier‑1).
Tier‑2 https://www.coingecko.com/en/coins/strikebit-ai Aggregator: reference profile and links (not Tier‑1).

No comments to display

Back to top