Skip to main content

Sphere AI

Sphere AI — 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).

Sphere AI — an AI/Inference project on the Solana network, token (symbol: SPHERE).

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 users can run ML models via a web interface (Tier‑1 docs).
  • Who it’s for: users who want to run ready‑made models without their own ML infrastructure (per the product description).
  • Why onchain/token: per Tier‑1, “hold‑to‑use” access to the models via holding the SPHERE token is described; the existence of the token on the Solana network is also confirmed.
  • What you can actually touch (Tier‑1): running models via the web interface (described in the official documentation).

How it works (very briefly)

  1. The user does: opens the platform and selects a model.
  2. The system does: provides a web form and runs the model (per the description in the docs).
  3. The user gets: the output of the selected model.
  4. Where the blockchain is: Tier‑1 describes the token as an access key (“hold‑to‑use”); other onchain artifacts are not established per Tier‑1.
  5. Token role (if any): holding the token is used as a condition of access to using the models (Tier‑1).

Quick links: AI thesis fit

Project passport

Field Value
Project name Sphere AI
Also known as (aliases) SPHERE, Sphere
Logo (logo) —
Token symbol (ticker) SPHERE
Category AI/Inference | 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 NuSvbWzz2QaqepZSyj8MhyvVv1E4W9AxnSge7G8pump
Token model (token_type) utility (access)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Tier‑1: access to the models is described as “hold‑to‑use” (a token holding requirement).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) running ML models via web interface
Use‑case (use_case) run models in the browser
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

In the Tier‑1 documentation, Sphere AI describes a platform where users can run open‑source ML models via a web interface. The documentation also describes a “hold‑to‑use” access model (as a temporary solution before the introduction of pay‑per‑use), where a token holding requirement is used as a condition of access to using the models.

Features/modules

  • Web interface for running models: a parameter input form and launch from the browser (Tier‑1).
  • Hold‑to‑use access model: access to features via holding the token (Tier‑1).
  • Public product materials: “About” + “Guide for users” in the official documentation (Tier‑1).

Typical scenarios

  • Scenario 1: a user enters the web interface, selects a model and enters parameters → runs the model and gets the result.
  • Scenario 2: a user checks the token holding requirements for access to the models → uses the product once the requirements are met.

Getting started (wallet/network)

  • What you need: access to the platform’s web interface; if necessary — a Solana wallet for holding the token.
  • Network/chain: Solana (token).
  • Fees: Solana network fees arise for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: the platform’s web interface + the token on the Solana network.
  • Participant roles: users, the team/product operators.
  • Where logic runs: model execution — offchain (as a service); onchain — the token and the holding check (as a condition of access, per the description).
  • Dependencies: Solana for the token; the platform’s web infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: Tier‑1: “hold‑to‑use” (holding the token as an access key to using the models).
  • Protocol necessity drivers: per Tier‑1, the product ties access to the token; at the same time, the criticality of onchain for the operation of the service is not justified as OC_3.
  • Who pays fees: users for operations on Solana.
  • Where fees go: to Solana validators (per the network rules).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of model quality/security; risks of access via the web interface; risks of the token as a separate onchain asset.

Project status and timeline

  • Current status: active (there is public documentation and a “guide for users”).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: the web interface for running models is described in the Tier‑1 documentation.

AI component of the project

  • What is real AI here? Tier‑1 describes the ability to run ML models via the platform (web interface).
  • What is truly onchain? The SPL token on the Solana network.
  • Why is a token needed? Tier‑1 describes the token as a condition of access to using the models (“hold‑to‑use”).
  • Red flags (based on the information found): access to the AI service is tied to “holding requirements”; insufficient Tier‑1 technical details on architecture/versions/quality metrics; the necessity of the blockchain for model execution is not obvious.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
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): AI is described as a working layer of the product (a platform for running models), not only a roadmap intent.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/
  • Why sufficient / why not (one line): Tier‑1 “About” describes the platform and its purpose.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The platform allows running ML models (as an AI service) via a web interface.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/ ; https://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): Tier‑1 describes the ability to “run machine learning models in the browser”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The docs describe running models via the web interface (instructions and screenshots).
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): This is a reproducible “demo surface”: one can follow the instructions and run models.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): The documentation describes usage but does not provide quality metrics for the models/service.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The architecture/versions of the models and the platform are not described sufficiently for AI_4 per Tier‑1.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/
  • Why sufficient / why not (one line): There is a description of “what it is”, but not a tech description of the architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: SPL mint NuSvbWzz2QaqepZSyj8MhyvVv1E4W9AxnSge7G8pump
  • Evidence: Tier‑1 — https://solscan.io/token/NuSvbWzz2QaqepZSyj8MhyvVv1E4W9AxnSge7G8pump
  • Why sufficient / why not (one line): There is a verifiable onchain artifact (the token on Solana).
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 (other than the token and holding‑based access rules).
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): There are no contracts/addresses or description of onchain logic other than the fact of the token and the access conditions.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification was found that the model execution service breaks down without the blockchain.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/
  • Why sufficient / why not (one line): Tier‑1 contains claims about blockchain/transparency, but there is no criticality test.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, SPHERE, on the Solana network.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/ ; https://solscan.io/token/NuSvbWzz2QaqepZSyj8MhyvVv1E4W9AxnSge7G8pump
  • Why sufficient / why not (one line): The Tier‑1 docs describe the token as an access key; the onchain page confirms the mint.
  • 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): Access to using the models is described as “hold‑to‑use” (a requirement to hold the SPHERE token).
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): This is a direct description of the utility: the token is used as a condition of access to the service.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Staking/slashing/penalties on the token are not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): The documentation focuses on hold‑to‑use access; incentives/penalties are not described as a mechanic.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — https://docs.sphere-ai.pro/
  • Why sufficient / why not (one line): No Tier‑1 description of DAO/voting was found.
  • Conflict note (if any): —

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://docs.sphere-ai.pro/guide-for-users
  • Why sufficient / why not (one line): Access is tied to holding, but there is no formal “replace the blockchain/token” test.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.sphere-ai.pro/ Official description of the platform: running ML models + the role of the token as an “access key” (general wording).
Tier‑1 https://docs.sphere-ai.pro/guide-for-users Tier‑1: the “hold‑to‑use” model and a description of running models in the browser (demo surface).
Tier‑1 https://solscan.io/token/NuSvbWzz2QaqepZSyj8MhyvVv1E4W9AxnSge7G8pump The existence of the token on the Solana network (SPL mint).

No comments to display

Back to top