Skip to main content

AI Companions

AI Companions (AIC) — 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).

AI Companions — a consumer product about AI virtual companions (personalization/communication; the description mentions VR/AR as a direction). The onchain part is confirmed in Tier‑1 sources via the AIC token on BNB Smart Chain (BEP‑20). The project repository also describes the application architecture (web/API/AI service) and declares token‑gated features.

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 application about “AI companions” (personalized communication/characters) with monetization and token gating.
  • Who it’s for: end users; developers/contributors (there is a public repository).
  • Why onchain/token: onchain is confirmed as the issuance/circulation of the AIC token; in the Tier‑1 description the token is used for access tiers/upgrades and (as an intention) future utility.
  • What you can actually touch (Tier‑1): the official project website (public storefront) and the whitepaper.

How it works (very briefly)

  1. The user does: uses the web application/companion service.
  2. The system does: web client → API → AI service (the repository designates a separate AI microservice).
  3. The user gets: responses/behavior of the “companion”, personalization, (in the future) VR/AR formats.
  4. Where the blockchain is: the AIC token and its transfers — onchain on BNB Smart Chain.
  5. Token role: token‑gated access/upgrades; possible staking (as an intention, described in general terms).

Quick links: AI thesis fit

Project passport

Field Value
Project name AI Companions
Also known as (aliases) AIC
Logo (logo) ../assets/32_ai-companions_logo.svg
Token symbol (ticker) AIC
Category AI/Agents
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0xbe6ad1eb9876cf3d3f9b85feecfb400298e80143
Token model (token_type) utility (access + upgrades)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) the Tier‑1 repository/whitepaper describe token‑gated access tiers and utility plans; numerical supply/vesting parameters require a separate extract from the tokenomics section
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI virtual companions (personalization/chat)
Use‑case (use_case) consumer AI companion app
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 0 / 3
Last verified 2026-02-11

General project overview

In the Tier‑1 whitepaper, the project describes the product as “AI virtual companions” with an emphasis on personalization and “emotionally engaging” interaction; VR/AR are mentioned as a direction for an “immersive UX”. The Tier‑1 GitHub repository additionally reveals the engineering structure: a monorepo with a web application, an API service and a separate AI microservice (FastAPI), as well as a placeholder for contracts.

Features/modules

  • Web app: the interface/marketing layer and future “dashboard/settings” (described in the repository).
  • API: a backend service (NestJS) for future CRUD/sessions/billing.
  • AI service: a separate microservice (FastAPI) with a health endpoint and scaffolding for chat/embeddings.
  • Token‑gated access: the repository describes “access tiers” and token‑gated features as a model.

Typical scenarios

  • Scenario 1: a user chats with a companion → the AI service generates a response → the result is shown in the application.
  • Scenario 2: a user gets access to extended features via a token‑gated tier/upgrade (declared in Tier‑1).

Getting started (wallet/network)

  • What you need: access to the product (website/app) and an EVM wallet for the AIC token (if token gating is needed).
  • Network/chain: BNB Smart Chain.
  • Fees: gas in BNB for operations with the AIC token.

Architecture/tech (non‑AI)

  • Components: web (Next.js) → API (NestJS) → DB (Postgres/Prisma) + AI microservice (FastAPI) + future contracts.
  • Where logic runs: the core of the AI logic — offchain; the onchain part — the token and the payments/access associated with it (if implemented).
  • Dependencies: web/API/AI infrastructure; BNB Smart Chain for the token.

Token/economics (expanded, no forecasts)

  • Token utility: the Tier‑1 repository describes $AIC as a “native utility token” for access tiers/upgrades and future utilities.
  • Replaceability: by the description this is rather a monetization/access model; in principle replaceable by a subscription/fiat/stablecoin (if no protocol necessity is shown).

Governance

No Tier‑1 artifacts on DAO/onchain governance were identified (—).

Security and incidents

  • Security advisories: GitHub Advisories are enabled for the repository.
  • Audits/bug bounty: no Tier‑1 confirmations of programs/reports were found (—).

Project status and timeline

  • Current status: the repository and whitepaper are published; the token exists on BNB Smart Chain.
  • Roadmap: published in the repository README.

Ecosystem/integrations

  • Integrations: the repository mentions future VR/AR and integrations with devices (as a direction).

AI component of the project

  • What is real AI here? AI personalization and the behavior of “virtual companions” (whitepaper) + a dedicated AI service in the repository.
  • What is truly onchain? the AIC token on BNB Smart Chain; no other onchain components are confirmed by addresses in Tier‑1.
  • Why is a token needed? described as a utility for access/upgrades; protocol necessity is not proven (rather product/economic).
  • Red flags (based on the information found): onchain‑washing (apart from the token, there are no onchain artifacts); AI‑quality (no metrics of model quality/safety); token‑washing (check where exactly the token is mandatory and where it is replaceable).

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 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): AI is described as a current component of the product, not only as intent.
  • Evidence: Tier‑1 — https://aivcompanions.com/AIC_Whitepaper.pdf
  • Why sufficient / why not (one line): the whitepaper describes AI‑driven personalization/companions as the core value.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI‑driven personalization / virtual companions.
  • Evidence: Tier‑1 — https://aivcompanions.com/AIC_Whitepaper.pdf
  • Why sufficient / why not (one line): the wording in the whitepaper describes the AI function of the product.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a public repository of the application with an AI microservice (FastAPI) and an interface.
  • Evidence: Tier‑1 — https://github.com/AICompanions/AI-Companions
  • Why sufficient / why not (one line): the presence of code and a described architecture is sufficient for 1/0 at the level of “there is something to look at”.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context: —
  • Evidence: Tier‑1 — https://aivcompanions.com/AIC_Whitepaper.pdf
  • Why sufficient / why not (one line): quantitative metrics of model/personalization quality are not presented.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is an application architecture, but no Tier‑1 description of the specific AI model/versions/pipeline.
  • Evidence: Tier‑1 — https://github.com/AICompanions/AI-Companions
  • Why sufficient / why not (one line): the repo describes the services but does not record the model/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: AIC token: 0xbe6ad1eb9876cf3d3f9b85feecfb400298e80143
  • Evidence: Tier‑1 — https://bscscan.com/token/0xbe6ad1eb9876cf3d3f9b85feecfb400298e80143
  • Why sufficient / why not (one line): the onchain address of the token is verifiable via the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: no Tier‑1 confirmation of separate onchain modules (staking/access) by contract addresses was found, apart from the token.
  • Evidence: Tier‑1 — https://github.com/AICompanions/AI-Companions
  • Why sufficient / why not (one line): the repo mentions a “contracts placeholder”, but this is not Tier‑1 proof of working onchain logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core value of the AI service is preserved without a blockchain; onchain is not shown as critical here.
  • Evidence: Tier‑1 — https://aivcompanions.com/AIC_Whitepaper.pdf
  • Why sufficient / why not (one line): the product is described as an application/AI service, and the token — as an access layer.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the AIC token exists on BNB Smart Chain.
  • Evidence: Tier‑1 — https://bscscan.com/token/0xbe6ad1eb9876cf3d3f9b85feecfb400298e80143
  • Why sufficient / why not (one line): the token is visible in the explorer.
  • Conflict note (if any): —

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): token‑gated access tiers/upgrades are described as the utility.
  • Evidence: Tier‑1 — https://github.com/AICompanions/AI-Companions
  • Why sufficient / why not (one line): the README describes “token-gated features / access tiers”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives/slashing/rewards as a protocol necessity are not confirmed by Tier‑1 artifacts.
  • Evidence: Tier‑1 — https://aivcompanions.com/AIC_Whitepaper.pdf
  • Why sufficient / why not (one line): a description of the token as an access utility was found, but not as a mandatory network incentive.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): onchain governance is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — https://aivcompanions.com/AIC_Whitepaper.pdf
  • Why sufficient / why not (one line): there is no described governance mechanism/artifacts.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the “access/upgrades” function is usually replaceable by a subscription/stablecoin without loss of meaning for the AI product.
  • Evidence: Tier‑1 — https://github.com/AICompanions/AI-Companions
  • Why sufficient / why not (one line): Tier‑1 does not show a unique protocol necessity for the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://aivcompanions.com/AIC_Whitepaper.pdf AI virtual companions and the positioning of AI personalization
Tier‑1 https://github.com/AICompanions/AI-Companions architecture of the web/API/AI service and token‑gated features
Tier‑1 https://bscscan.com/token/0xbe6ad1eb9876cf3d3f9b85feecfb400298e80143 onchain fact of the AIC token and its address

No comments to display

Back to top