Skip to main content

SimsAI

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

SimsAI — an AI/Agents | SocialFi project on the Solana network, token (symbol: SIMSAI).

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/ecosystem positioned as a “social network for AI” and an API service for creating and managing AI agents.
  • Who it’s for: AI agent developers and teams that need an isolated “sandbox” setup for agent testing and interactions.
  • Why onchain/token: the token is deployed on Solana; the necessity of the token in the product logic is not established per Tier‑1 sources (requires separate verification).
  • What you can actually touch (Tier‑1): Jeeter API (documentation + Quick Start) for creating AI agent content/interactions on the platform.

How it works (very briefly)

  1. The developer does: creates/configures an AI agent and integrates with the API.
  2. The system does: provides an API for content and interactions (jeets), as well as a platform/rules for “AI‑social” interaction.
  3. The developer receives: an environment for testing/training AI agent behavior and interfaces for automated actions.
  4. Where the blockchain is: the token lives onchain on the Solana network; onchain events are observable via the explorer.
  5. Token role (if any): Tier‑1 materials describe token utility scenarios (premium subscriptions, increasing API limits via burn, DAO governance, rewards and marketplace access).

Quick links: AI thesis fit

Project passport

Field Value
Project name SimsAI
Also known as (aliases) $SIMSAI, Jeeter
Logo (logo) ../assets/833_simsai_logo.svg
Token symbol (ticker) SIMSAI
Category AI/Agents | SocialFi
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 u6VCRrFvejYX8cTnc1ptZT8UqVGbPXPmE8kvcGnpump
Token model (token_type) utility (subscriptions + API limits + governance)
Max supply 1,000,000,000 SIMSAI
Issuance fixed
Tokenomics (tokenomics, brief) TGE on Pump.fun; the documentation describes the distribution structure and utility scenarios (including community rewards and staking rewards).
Governance DAO (as claimed)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) API + interaction environment for AI agents
Use‑case (use_case) testing/training AI agents in a "social environment"
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

SimsAI describes itself on the official website as a “framework for AI agents” and a “social media ecosystem for AI”. The documentation (Jeeter API) describes the integration method: the API base URL, as well as example requests for creating content and interactions.

Tier‑1 sources show that the product surface is expressed primarily as an API and documentation for developers. At the same time, quality metrics for the AI part (benchmarks/accuracy/comparisons) were not found in the available Tier‑1 materials.

Features/modules

  • Jeeter API: creation of AI agent content and interactions on the platform.
  • Builder/Agent API (claimed): agent management and integrations (endpoints/authentication are described in the documentation).
  • Integration with ELIZA framework (claimed): a mention on the website of connecting to the ELIZA framework.

Typical scenarios

  • Scenario 1: a developer obtains keys/authentication → publishes content via the API → observes reactions/interactions.
  • Scenario 2: a developer creates and configures an agent → tests behavior on an “AI‑oriented” platform.

Getting started (wallet/network)

  • What you need: access to Jeeter API (keys/authentication per the documentation); for operations with the token — a Solana wallet.
  • Network/chain: Solana.
  • Fees: Solana network fees for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: Jeeter API (api.jeeter.social), the website and documentation; the onchain part — the token on Solana.
  • Where logic runs: API and “social” interaction functionality — offchain; the token — onchain.
  • Dependencies: not publicly established per Tier‑1 sources (other than the API/website domains).

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): the token documentation describes premium subscriptions, increasing API limits (via burn), DAO governance/voting rights, rewards, marketplace access and staking rewards.
  • Protocol necessity drivers: no rigorous explanation of “without the token the product breaks down” was found per Tier‑1.
  • Fees: Solana network fees for transfers/operations with the token.

Governance

  • Who makes decisions: the token documentation claims DAO governance/voting rights; the specific implementation of governance requires separate verification (tool/contracts).

Security and incidents

  • Audits: not found per Tier‑1 sources.
  • Bug bounty: not found per Tier‑1 sources.
  • Incidents: not established per Tier‑1 sources.

Project status and timeline

  • Current status: the product surface (website/documentation) is available.
  • Key releases/milestones: not established per Tier‑1 sources.
  • Roadmap: not found per Tier‑1 sources.

Ecosystem/integrations

  • Integrations (claimed): ELIZA framework (mention on the website).

AI component of the project

  • What is real AI here? the project is positioned as a platform for AI agents and for training/testing agent behavior through artificial interactions.
  • What is truly onchain? the existence of the token on the Solana network is confirmed per Tier‑1 (mint + explorer).
  • Why is a token needed? the Tier‑1 token documentation describes utility scenarios: premium subscriptions, API limits (burn), DAO governance, rewards and marketplace access.
  • Red flags (based on the information found): there are no Tier‑1 quality metrics for the AI part; part of the token utility looks replaceable with a subscription/payments (see TK_4).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity medium 2
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 part is described as an already working product surface (website + API docs), not only as “intent”.
  • Evidence: Tier‑1 — https://www.simsai.io/ ; https://www.simsai.io/docs/
  • Why sufficient / why not (one line): AI_0 is used as “intent” in the absence of a product; here there is a described product surface and API.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): A platform/framework for creating and training AI agents through interactions and content managed via the API.
  • Evidence: Tier‑1 — https://www.simsai.io/ ; https://www.simsai.io/docs/
  • Why sufficient / why not (one line): Tier‑1 sources describe the product’s purpose as a platform for AI agents and outline the interface/integration.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): Jeeter API docs contain a Quick Start with an example request to create a “jeet”.
  • Evidence: Tier‑1 — https://www.simsai.io/docs/
  • Why sufficient / why not (one line): There is a reproducible example of API use (an example request/response) as a “product surface”.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.simsai.io/ ; https://www.simsai.io/docs/
  • Why sufficient / why not (one line): No benchmarks/quality metrics for the AI component were found per Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The documentation describes the API: the base URL, authentication and a set of endpoints for working with agents/content.
  • Evidence: Tier‑1 — https://www.simsai.io/docs/
  • Why sufficient / why not (one line): This is a tech description of integration interfaces (API), sufficient for “there is a technical description”.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: u6VCRrFvejYX8cTnc1ptZT8UqVGbPXPmE8kvcGnpump (mint)
  • Evidence: Tier‑1 — https://solscan.io/token/u6VCRrFvejYX8cTnc1ptZT8UqVGbPXPmE8kvcGnpump
  • Why sufficient / why not (one line): Explorer confirms the existence of the token on the Solana network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: no confirmation of mandatory onchain logic of the product, other than the token, was found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.simsai.io/ ; https://www.simsai.io/docs/
  • Why sufficient / why not (one line): Contracts/addresses and a description of the product’s onchain functions are required; this is not established in the available Tier‑1 materials.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established per Tier‑1 that without the blockchain a key property of the product breaks down (API/platform).
  • Evidence: Tier‑1 — https://www.simsai.io/ ; https://www.simsai.io/docs/
  • Why sufficient / why not (one line): OC_3=1 requires an explicit justification of onchain criticality; not found per the available Tier‑1 sources.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, SIMSAI, on the Solana network.
  • Evidence: Tier‑1 — https://www.simsai.io/docs/ ; https://solscan.io/token/u6VCRrFvejYX8cTnc1ptZT8UqVGbPXPmE8kvcGnpump
  • Why sufficient / why not (one line): The documentation provides the CA, and the explorer confirms the mint/token.
  • 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): The Tier‑1 token documentation describes the use of SIMSAI for premium subscriptions and platform access (including via burn).
  • Evidence: Tier‑1 — https://www.simsai.io/token
  • Why sufficient / why not (one line): Tier‑1 directly describes the scenarios “use tokens to upgrade to premium / burn for API limits”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The Tier‑1 token documentation claims rewards for contributions to the ecosystem and staking rewards (staked SIMSAI → rewards).
  • Evidence: Tier‑1 — https://www.simsai.io/token
  • Why sufficient / why not (one line): Tier‑1 lists rewards/staking scenarios (including “Staking Rewards” and benefits).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): The Tier‑1 token documentation claims DAO governance and voting rights for holders.
  • Evidence: Tier‑1 — https://www.simsai.io/token
  • Why sufficient / why not (one line): Tier‑1 explicitly lists “DAO Governance” and “Voting Rights”.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): A significant part of the token utility looks replaceable with a subscription/payments (premium upgrades / API limits).
  • Evidence: Tier‑1 — https://www.simsai.io/token
  • Why sufficient / why not (one line): Tier‑1 describes “burn/use tokens to upgrade premium / increase API limits”, which is typically replaceable with a subscription without the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.simsai.io/ Tier‑1 description: a platform/framework for AI agents and an “AI social network” (positioning and purpose).
Tier‑1 https://www.simsai.io/docs/ Jeeter API docs: API base URL + Quick Start (a reproducible example request).
Tier‑1 https://www.simsai.io/token Token utility + tokenomics: premium subscriptions, API limits (burn), DAO governance/voting rights, rewards/staking.
Tier‑1 https://github.com/simsaidev/DankAI/ The project’s public repository (code artifact).
Tier‑1 https://solscan.io/token/u6VCRrFvejYX8cTnc1ptZT8UqVGbPXPmE8kvcGnpump Onchain fact: the token/mint on the Solana network.

No comments to display

Back to top