Skip to main content

OrbitAI

OrbitAI — 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).

OrbitAI — an AI/Agents project on Ethereum, token (symbol: ORBIT).

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 “AI agents” platform/marketplace that claims the ability to run agents with an emphasis on privacy (including running on a local server).
  • Who it’s for: users and teams that need autonomous agents for automation tasks and a private execution mode.
  • Why onchain/token: the token is claimed as the platform’s “native token” and as part of the access/deployment mechanics; the onchain confirmation in this card is limited to the existence of the token and its contract.
  • What you can actually touch (Tier‑1): the web app https://app.orbitai.org/.

How it works (very briefly)

  1. The user does: chooses an agent/scenario and runs it via the web app or following the instructions for a local host.
  2. The system does: executes tasks with agents (claimed: autonomously; collaboration of agents is possible).
  3. The user gets: the automation result (for example, monitoring/analysis/an assistant).
  4. Where the blockchain is: the token on Ethereum is confirmed; the product’s onchain logic (other than the token) requires separate verification per Tier‑1.
  5. Token role (if any): per the tokenomics, claimed as a token to “fuel agent deployment/customization” and for platform benefits.

Quick links: AI thesis fit

Project passport

Field Value
Project name OrbitAI
Also known as (aliases) $ORBIT, Orbit AI
Logo (logo) —
Token symbol (ticker) ORBIT
Category AI/Agents | 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 0x6499999951f0b5ba8b9187958884f9f5b50e45fd
Token model (token_type) utility (agent deployment + customization; platform benefits)
Max supply 10000000 (per the tokenomics)
Issuance —
Tokenomics (tokenomics, brief) claimed as a token for agent deployment/customization; total supply of 10,000,000 is specified
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) platform for autonomous AI agents
Use‑case (use_case) private AI agent launch
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

OrbitAI describes itself as a platform of autonomous AI agents with a focus on privacy: the documentation claims privacy modes and the ability to run/deploy agents on a local host (including via Docker). The project also describes an “agent marketplace” (renting/choosing ready‑made agents).

Features/modules

  • AI agents (claimed): autonomous agents for various tasks.
  • Local host deployment (claimed): running agents locally for privacy and data control.
  • Agent marketplace/catalog (claimed): a list of agents and scenarios.

Typical scenarios

  • Scenario 1: a user opens the web app → chooses an agent → runs a scenario.
  • Scenario 2: a user deploys agents on a local server via Docker → uses the local interface.
  • Scenario 3: a team uses several agents as a “team” for process automation (per the platform’s description).

Getting started (wallet/network)

  • What you need: access to https://app.orbitai.org/; for a local run — Docker and a Windows environment (per the guide page).
  • Network/chain: Ethereum (ERC‑20 token); the platform itself is described as a web product.
  • Fees: Ethereum fees on operations with the token; fees inside the platform require separate verification.

Architecture/tech (non‑AI)

  • Components: web app, documentation, local deployment via Docker, the ERC‑20 token.
  • Participant roles: platform users, the project’s operators/developers.
  • Where logic runs: AI/ML tasks and agent operations are claimed as executed locally (in local host mode) or via the platform (offchain); onchain in this card is confirmed by the token contract.
  • Dependencies: Docker (for local host), web infrastructure, Ethereum for the token.

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1, claimed): “fuel agent deployment and customization” and platform benefits.
  • Protocol necessity drivers: the tokenomics describes the token’s role in the platform; execution details require verification.
  • Who pays fees: users on onchain operations with the token (Ethereum).
  • Where fees go: network fees — to Ethereum validators; a “transaction tax” is also described as a charge directed to development/liquidity (details require verification).
  • Issuance/burn: total supply is specified as 10,000,000; other parameters — per the tokenomics page.
  • Incentive mechanisms: the tokenomics has mentions of allocation and charges, but specific protocol incentives require separate verification.
  • Distribution/vesting: shares and vesting for part of the allocation are described; details require verification.
  • Treasury: not established per Tier‑1.

Governance

  • Who makes decisions: not established per Tier‑1.
  • How protocol parameters change: not established per Tier‑1.
  • 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 and how the agents are executed in the “non‑local” mode; which data is sent to external services; the security of the token and of any contracts the platform uses.

Project status and timeline

  • Current status: active (based on the presence of the website/docs and the web app).
  • Key releases/milestones: not established per Tier‑1.
  • Roadmap: the roadmap link is in links_*.

Ecosystem/integrations

  • Integrations: local run via Docker; the agent catalog in the documentation.
  • Partners: not established per Tier‑1.
  • Where it’s actually used: examples/agents are presented in the documentation (Tier‑1), but usage metrics require separate verification.

AI component of the project

  • What is real AI here? AI agents as the product: autonomous agents and scenarios described in the official documentation.
  • What is truly onchain? the ERC‑20 token is confirmed via the explorer; the product’s other onchain logic (other than the token) requires separate verification.
  • Why is a token needed? the tokenomics describes $ORBIT as a token that “fuel agent deployment/customization” and provides platform benefits.
  • Red flags (what to double‑check): the conflict between “the token contract exists” vs the wording “token launching soon” in the tokenomics; the absence of Tier‑1 information about audits; which functions actually require onchain.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): the AI component is described as part of the product, so AI_0 is not used as “intent only”.
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai
  • Why sufficient / why not (one line): there is a description of the AI agents and how‑to materials.
  • Conflict note: —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the product describes autonomous AI agents that perform tasks and can operate in a private mode.
  • Evidence: Tier‑1 — https://orbitai.org/ ; https://orbitai.gitbook.io/orbitai
  • Why sufficient / why not (one line): the Tier‑1 materials describe the purpose of the AI agents and the principles of private execution.
  • Conflict note: —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the web app is available as the platform’s entry point/demo.
  • Evidence: Tier‑1 — https://app.orbitai.org/
  • Why sufficient / why not (one line): there is a public app endpoint.
  • Conflict note: —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai
  • Why sufficient / why not (one line): AI quality metrics/benchmarks were not found in Tier‑1.
  • Conflict note: —

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

  • AI_4 (decision): 1
  • Claim (one line): there is a guide for running agents locally on Windows via Docker.
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai/local-host/setting-up-a-local-host-server-and-run-orbitai-agents-with-docker
  • Why sufficient / why not (one line): this is a Tier‑1 tech guide for deployment and operation.
  • Conflict note: —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 0x6499999951f0b5ba8b9187958884f9f5b50e45fd
  • Evidence: Tier‑1 — https://etherscan.io/token/0x6499999951f0b5ba8b9187958884f9f5b50e45fd
  • Why sufficient / why not (one line): onchain fact: the token contract in the network explorer.
  • Conflict note: —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: no Tier‑1 description of specific onchain logic of the product (other than the token) was found.
  • Evidence: Tier‑1 — https://orbitai.org/ ; https://orbitai.gitbook.io/orbitai
  • Why sufficient / why not (one line): there is general Web3 wording, but without addresses/contracts of the product logic.
  • Conflict note: —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality (in terms of trustless properties) for the platform’s operation was found.
  • Evidence: Tier‑1 — https://orbitai.org/
  • Why sufficient / why not (one line): the focus of the Tier‑1 materials is privacy/local execution, not trustless onchain properties.
  • Conflict note: —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a claimed token, $ORBIT (ERC‑20).
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai/tokenomics ; https://etherscan.io/token/0x6499999951f0b5ba8b9187958884f9f5b50e45fd
  • Why sufficient / why not (one line): the Tier‑1 tokenomics describes the token, and the explorer provides an onchain artifact at the address.
  • Conflict note: —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the tokenomics claims $ORBIT as a token that “fuel” the deployment and customization of agents.
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai/tokenomics
  • Why sufficient / why not (one line): this is a Tier‑1 description of the token’s utility in the platform.
  • Conflict note: —

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

  • TK_2 (decision): 0
  • Claim (one line): no Tier‑1 description of collateral/penalties/mandatory protocol incentives was found.
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai/tokenomics
  • Why sufficient / why not (one line): the tokenomics describes allocation/charges, but does not disclose protocol collateral/penalties.
  • Conflict note: —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): an explicit model of governance via the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai/tokenomics
  • Why sufficient / why not (one line): the tokenomics page does not record a specific voting/governance process.
  • Conflict note: —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://orbitai.gitbook.io/orbitai/tokenomics
  • Why sufficient / why not (one line): a specification of the access/payment mechanics is required for a strict conclusion.
  • Conflict note: —

Evidence (table)

Tier Source What it proves
Tier‑1 https://orbitai.org/ Tier‑1 description of the product (AI agents + focus on privacy/local host)
Tier‑1 https://app.orbitai.org/ public web app (demo/entry point)
Tier‑1 https://orbitai.gitbook.io/orbitai Tier‑1 documentation on the product and the agents
Tier‑1 https://orbitai.gitbook.io/orbitai/local-host/setting-up-a-local-host-server-and-run-orbitai-agents-with-docker Tier‑1 tech guide for a local run (Docker)
Tier‑1 https://orbitai.gitbook.io/orbitai/tokenomics Tier‑1 description of the tokenomics (supply/utility/charges)
Tier‑1 https://etherscan.io/token/0x6499999951f0b5ba8b9187958884f9f5b50e45fd onchain fact: the token contract
Tier‑2 https://www.coingecko.com/en/coins/orbitai reference token card (aggregator; not proof of technology)
Tier‑2 https://coinmarketcap.com/currencies/orbitai/ reference token card (aggregator; not proof of technology)

No comments to display

Back to top