Botify.cloud
Botify.cloud — 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).
Botify.cloud — an AI/Agents project on Solana, token (symbol: BOTIFY).
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 no‑code platform and marketplace of automations (bots/agents) for crypto tasks.
- Who it’s for: users who want to quickly switch on automation; agent creators who want to publish/sell their agents.
- Why onchain/token: onchain is used as the settlement/payment layer; the token is claimed as a means of payment, access to features and participation in incentive/governance mechanics.
- What you can actually touch (Tier‑1): the web app
https://app.botify.cloud/.
How it works (very briefly)
- The user does: picks an agent in the marketplace or builds their own via the no‑code builder.
- The system does: configures the agent’s behavior (template/parameters), connects the wallet and payment methods.
- The user gets: an agent for the chosen scenario (for example, trading/social/utility automation).
- Where the blockchain is: payments/purchases/activations (and related platform transactions) go through onchain (claimed: the Solana network).
- Token role (if any): payment/activation of agents and access to premium features; staking/rewards and governance are additionally claimed.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Botify.cloud |
| Also known as (aliases) | Botify, $BOTIFY |
| Logo (logo) | — |
| Token symbol (ticker) | BOTIFY |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Solana |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Solana) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | SPL |
| Token contract | BYZ9CcZGKAXmN2uDsKcQMM9UnZacija4vWcns9Th69xb |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | payment/activation of agents; access to premium features; staking/rewards and governance are claimed |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | no-code AI agent marketplace |
| Use‑case (use_case) | crypto task automation |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 2 / token_score 3 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://botify.cloud/ |
| App / Demo | https://app.botify.cloud/ |
| Docs | https://botify-cloud.gitbook.io/docs |
| GitHub | — |
| Releases / Changelog | https://www.botify.cloud/updates |
| Whitepaper | https://botify-cloud.gitbook.io/whitepaper |
| Roadmap | https://botify-cloud.gitbook.io/whitepaper/roadmap |
| Security advisories | — |
| Explorer | https://solscan.io/token/BYZ9CcZGKAXmN2uDsKcQMM9UnZacija4vWcns9Th69xb |
| X | https://twitter.com/botifydotcloud |
| Discord | https://discord.com/invite/botify |
| Telegram | https://t.me/botifycloud |
| Medium | https://www.botify.cloud/updates |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/botify |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/botify/ |
General project overview
Botify.cloud is positioned as a no‑code platform for creating and using AI agents (bots) and as a marketplace where such agents can be found and launched. According to the project’s description, the product is oriented toward automating tasks in the crypto environment, and part of the operations (in particular payments/activations) is carried out onchain on the Solana network.
Features/modules
- Agent marketplace: a catalog of agents by categories and scenarios.
- Agent Builder (no‑code): assembling and configuring an agent without code (choice of category, inputs, LLM and behavior).
- Token utility (Tier‑1, claimed): payment/access to features, staking/rewards and participation in governance.
Typical scenarios
- Scenario 1: a user picks a ready‑made agent → connects a wallet → activates/purchases access → launches the automation.
- Scenario 2: a creator assembles an agent in the builder → configures the parameters → publishes it in the marketplace.
- Scenario 3: a user tests several agents → saves favorites → reuses them in similar tasks.
Getting started (wallet/network)
- What you need: web access to
https://app.botify.cloud/, a Solana wallet, a small SOL balance for fees (if there are onchain actions). - Network/chain: Solana.
- Fees: Solana network fees on transactions (payments/purchases/activations).
Architecture/tech (non‑AI)
- Components: web application, marketplace/builder, onchain transactions (at minimum payments/activations).
- Participant roles: users (buyers), agent creators, the platform operator.
- Where logic runs: agent execution is most likely offchain; onchain is used for transactions and accounting of operations.
- Dependencies: the Solana network and providers of access to it (RPC); external AI/LLM components — depending on the specific agent.
Token/economics (expanded, no forecasts)
- Token utility (Tier‑1): purchase/activation of agents, access to premium features, participation in governance, staking/rewards.
- Protocol necessity drivers: the token is described as a built‑in mechanism for transactions/access/incentives inside the platform.
- Who pays fees: users on onchain operations.
- Where fees go: network fees — to Solana validators; the distribution of platform charges requires separate verification per Tier‑1.
- Issuance/burn: not established per Tier‑1.
- Incentive mechanisms: Tier‑1 claims staking and rewards; implementation details require verification.
- Distribution/vesting: not established per Tier‑1.
- Treasury: not established per Tier‑1.
Governance
- Who makes decisions: not established; Tier‑1 describes “governance participation”, but the specific governance model requires verification.
- How product parameters change: platform updates (offchain); for the onchain parts it depends on the smart contracts/rules (not established).
- Where decisions are discussed/made: not established per Tier‑1.
- Keys/multisig: not established per Tier‑1.
Security and incidents
- Audits: no confirmation of public audits was found per Tier‑1.
- Bug bounty: not found per Tier‑1.
- Incidents: no public postmortems were found per Tier‑1.
- Threat model (what to double‑check): where the agents’ logic is executed (offchain centralization), which onchain contracts are used other than the token, which token mechanics are implemented by smart contracts now.
Project status and timeline
- Current status: the product and documentation are available; specific versions/releases require separate verification.
- Key releases/milestones: not established per Tier‑1.
- Roadmap (Tier‑1): https://botify-cloud.gitbook.io/whitepaper/roadmap
Ecosystem/integrations
- Integrations (claimed): Solana wallet integrations (in the roadmap), agent categories for different tasks.
- Partners: not established per Tier‑1.
- Where it is used: agent scenarios and categories are described in the official materials (website/docs); usage metrics require separate verification.
AI component of the project
- What is real AI here? Tier‑1 describes the AI/ML capabilities of the agents (for example, adaptive learning and predictive analytics) and a marketplace of AI agents.
- What is truly onchain? Tier‑1 describes the integration with Solana; onchain is used at minimum for transactions (payments/activations).
- Why is a token needed? Tier‑1 describes the utility of $BOTIFY: payments for agents, access to features, staking/rewards and governance.
- Red flags (what to double‑check): which actions are actually executed onchain and by which contracts; which AI features are implemented with the project’s own code vs external LLMs; whether there are public audits and security disclosure.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | medium | 2 |
| Token necessity | high | 3 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI intent is present, but it is accounted for via AI_1/AI_2 (and not as “intent only”).
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper
- Why sufficient / why not (one line): AI_0 is used when there is only a roadmap/intent without a working described component; here there is a product description and a demo.
- Conflict note: —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Tier‑1 describes the AI/ML capabilities of the agents (adaptive learning, predictive analytics) for automation.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/technology-architecture/ai-and-machine-learning ; https://botify-cloud.gitbook.io/docs
- Why sufficient / why not (one line): there is a Tier‑1 description of which AI capabilities are claimed for the agents.
- Conflict note: —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): a web application is available as a demo/entry point to the platform.
- Evidence: Tier‑1 — https://app.botify.cloud/
- Why sufficient / why not (one line): there is a public app endpoint with onboarding (“Get Started”).
- Conflict note: —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/technology-architecture/ai-and-machine-learning
- Why sufficient / why not (one line): Tier‑1 lists capabilities, but there are no quantitative metrics/benchmarks with context (version/date/data).
- Conflict note: —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): there is a high‑level description of the AI/ML capabilities, but without a specific architecture/model versions.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/technology-architecture/ai-and-machine-learning
- Why sufficient / why not (one line): no Tier‑1 tech description with the architecture and versioning of the AI component was found.
- Conflict note: —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Solana
- Addresses/identifiers: SPL mint
BYZ9CcZGKAXmN2uDsKcQMM9UnZacija4vWcns9Th69xb - Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/technology-architecture/blockchain-integration ; https://solscan.io/token/BYZ9CcZGKAXmN2uDsKcQMM9UnZacija4vWcns9Th69xb
- Why sufficient / why not (one line): Tier‑1 records the Solana network, and the explorer provides a verifiable token identifier.
- Conflict note: —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: payments/purchases/activations of agents and part of the accounting of platform operations (at minimum settlement).
- Evidence: Tier‑1 — https://botify.cloud/ ; https://botify-cloud.gitbook.io/whitepaper/technology-architecture/blockchain-integration
- Why sufficient / why not (one line): Tier‑1 describes onchain transactions as part of the marketplace’s operation (payment/activation).
- Conflict note: —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: no Tier‑1 justification was found that a key property of the product breaks down when the blockchain is replaced with centralized settlement.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/technology-architecture/blockchain-integration
- Why sufficient / why not (one line): the advantages of the network (speed/fees) are listed, but the criticality of onchain for trustless properties is not proven.
- Conflict note: —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a claimed token, $BOTIFY.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/tokenomics/token-utility
- Why sufficient / why not (one line): Tier‑1 describes the token’s utility and its role in the ecosystem.
- Conflict note: —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 1
- Claim (one line): the token is claimed as the means of purchasing/activating agents in the marketplace.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/tokenomics/token-utility
- Why sufficient / why not (one line): Tier‑1 directly lists “Purchasing Agents”.
- Conflict note: —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Tier‑1 claims staking and rewards for holders/participants.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/tokenomics/token-utility
- Why sufficient / why not (one line): Tier‑1 lists “Staking and Rewards”.
- Conflict note: —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): Tier‑1 claims voting by token holders on platform proposals/changes.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/tokenomics/token-utility
- Why sufficient / why not (one line): Tier‑1 lists “Governance Participation”.
- Conflict note: —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): the replaceability of the token is not established: some functions (governance/staking) are tied to the token, but the implementation is not verified.
- Evidence: Tier‑1 — https://botify-cloud.gitbook.io/whitepaper/tokenomics/token-utility
- Why sufficient / why not (one line): without implementation details, “replaceable/irreplaceable” cannot be strictly proven for the key functions.
- Conflict note: —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://botify-cloud.gitbook.io/docs | positioning of the product as an AI‑agent marketplace + description of its purpose |
| Tier‑1 | https://app.botify.cloud/ | public entry into the web application (demo/starting point) |
| Tier‑1 | https://botify-cloud.gitbook.io/whitepaper/technology-architecture/ai-and-machine-learning | the claimed AI/ML capabilities of the agents (adaptive learning, predictive analytics) |
| Tier‑1 | https://botify-cloud.gitbook.io/whitepaper/technology-architecture/blockchain-integration | Tier‑1 statement that the platform is built on Solana |
| Tier‑1 | https://solscan.io/token/BYZ9CcZGKAXmN2uDsKcQMM9UnZacija4vWcns9Th69xb | verifiable token identifier (SPL mint) |
| Tier‑1 | https://botify-cloud.gitbook.io/whitepaper/tokenomics/token-utility | Tier‑1 description of the token’s utility (payments/access/staking/governance) |
| Tier‑2 | https://www.coingecko.com/en/coins/botify | reference token card (aggregator; not proof of technology) |
| Tier‑2 | https://coinmarketcap.com/currencies/botify/ | reference token card (aggregator; not proof of technology) |
No comments to display
No comments to display