Sensay

Sensay (SNSY) — 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).

Sensay — an AI/Agents / AI/Knowledge project: a B2B “better offboarding” platform where an AI interviewer collects and structures the knowledge of departing employees, and the team can later ask questions and generate documents “on demand”. In parallel, Sensay promotes the idea of “lifelike digital replicas / AI Wisdom Engine”. The $SNSY token is an ERC‑20 on Ethereum; in the litepaper the token is described as a means of paying for subscriptions/the replica marketplace/staking and governance.

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 SaaS platform for preserving “tacit knowledge” during departures through automated interviews and Q&A.
Who it’s for: companies (HR/teams) that want to reduce “brain drain”.
Why onchain/token: the SNSY token is a separate economic layer (subscriptions/marketplace/rewards — per the litepaper); onchain does not look critical for the core offboarding product.

How it works (very briefly)

The company does: sets up an organization and invites “leavers” to interviews.
The system does: the AI interviewer (Sophia) conducts the interview and “captures role nuances and tacit knowledge”; the knowledge is then available for search/chat questions and document generation.
The company receives: a knowledge base that can be queried after the employee leaves, and faster onboarding of replacements.
Where the blockchain is: the SNSY token exists as an ERC‑20 (Ethereum); the product’s onchain logic (other than the token) is not confirmed.
Token role: the litepaper claims subscriptions/a marketplace for replicas and data, staking rewards and governance; a working “must‑have” payment layer on the token in offboarding is not confirmed.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Sensay
Also known as (aliases)	SNSY, $SNSY, Sensay.io
Logo (logo)	../assets/228_sensay_logo.webp
Token symbol (ticker)	SNSY
Category	AI/Agents \| AI/Knowledge
Primary chain (chain)	Ethereum
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Ethereum)
Launch date (launch_date)	2024 (launch Q1 2024 in the litepaper)
Project status (status)	active
Token (standard)	ERC-20
Token contract	0x82a605d6d9114f4ad6d5ee461027477eeed31e34
Token model (token_type)	utility (governance)
Max supply	Etherscan Max Total Supply ~9.394B
Issuance	fixed supply (as claimed in the litepaper) + possible burn activities (as claimed)
Tokenomics (tokenomics, brief)	use‑cases: subscriptions, marketplace, staking, governance; the litepaper includes distribution/vesting (at the level of claims)
Governance	token governance via the staking platform (as claimed)
Admins/keys	—
Audit	Hashlock + Hacken (as claimed on the docs security page; the Hashlock PDF is available via the link in `links_*`)
Bug bounty	yes (bug bounty program on the website)
Team (team)	Dan Thomson (CEO) is listed on the website
Funding (investors/funding)	—
AI component (ai_component)	AI interviewer + knowledge Q&A replicas
Use‑case (use_case)	knowledge retention during offboarding
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

Links (links_*)

Type	Link
Website	https://www.snsy.ai/
Docs	https://docs.snsy.ai
GitHub	https://www.github.com/sensay-io
Releases / Changelog	https://blog.sensay.io/
Whitepaper	https://docs.snsy.ai/docs/litepaper
Roadmap	https://docs.snsy.ai/docs/roadmap
Security advisories	https://docs.snsy.ai/docs/security
Explorer	https://etherscan.io/token/0x82a605d6d9114f4ad6d5ee461027477eeed31e34
X	https://twitter.com/asksensay
Discord	https://discord.com/invite/sensay
Telegram	https://t.me/asksensay
Medium	https://asksensay.medium.com
Audit report(s)	https://hashlock.com/wp-content/uploads/2024/10/Sensay.io-Smart-Contract-Audit-Report-Final-Report.pdf
Bug bounty	https://sensay.io/security-bounty-program
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/sensay
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/sensay/

General project overview

Sensay promotes “AI‑powered knowledge transfer”: a product for companies where knowledge “does not leave with the people”. The website describes the flow: quick creation of an organization → inviting departing employees → an interview with the AI interviewer Sophia → access to knowledge via chat/integrations and document generation.

As a separate track, in the litepaper and on CoinMarketCap Sensay describes an “AI Wisdom Engine” and “lifelike digital replicas” (including digital immortality/personality replication scenarios, dementia care cases, etc.). This extends the positioning beyond HR offboarding, but part of this consists of marketing/roadmap claims.

Features/modules

AI offboarding interviews: Sophia conducts interviews and extracts “tacit knowledge” (website).
Knowledge access / Q&A: the team can “query this knowledge anytime” and generate documents (website).
API: the Sensay API for “AI-driven chatbots (replicas)” and integrations (API docs).
Token layer: $SNSY as payment/marketplace/staking/governance (litepaper).

Typical scenarios

Scenario 1 (offboarding): HR marks an employee as a “leaver” → Sophia conducts the interview → the knowledge remains accessible after departure.
Scenario 2 (knowledge search): a new employee asks questions about projects/processes → receives answers based on the saved interviews/materials.
Scenario 3 (integrations/chatbots): the team integrates “replicas” and conversations via the API into its own applications/workflows.

Getting started (wallet/network)

What you need: an account/access to Sensay (B2B, “Book a demo”); for the API — an API key request.
Network/chain: Ethereum (the SNSY token).
Fees: Ethereum fees for operations with the ERC‑20 token; inside the SaaS product, fees are not necessarily onchain.

Architecture/tech (non‑AI)

Components: the SaaS platform for interviews/knowledge access; API (OpenAPI); the SNSY token (ERC‑20).
Participant roles: companies/admins; “leavers”; reader users; integration developers via the API.
Where logic runs: interviews/Q&A/replicas — offchain; the token — onchain (Ethereum).
Dependencies: Ethereum RPC for the token; external AI models/infrastructure (not disclosed publicly).

Token/economics (expanded, no forecasts)

Token utility: the litepaper lists subscriptions, a marketplace for replicas/data, staking rewards, governance, participation/rewards.
Protocol necessity drivers: the core product (offboarding) can work without the token; the token adds a “Web3‑native” economic layer (per the CMC/litepaper description).
Who pays fees: Ethereum users for onchain operations with SNSY.
Where fees go: —.
Issuance/burn: a fixed supply of 10B is claimed in the litepaper; burn is possible “from time to time” (claimed). There is a conflict with the “Max Total Supply” on Etherscan.
Security/incentive mechanisms: staking (litepaper), early withdrawal with a fee and redistribution to the rewards pool (litepaper).
Distribution and token issuance schedule: distribution and vesting are described in the litepaper (Public sale 20%, etc.).
Treasury: the litepaper mentions a “Sensay Treasury” in the context of LP.

Governance

Who makes decisions: token holders (via the staking platform — claimed).
How protocol parameters change: via votes/proposals within the platform (details not disclosed).
Where decisions are discussed/made: public channels (X/Discord/Telegram) and docs.
Keys/multisig: —.

Security and incidents

Audits: docs security claims Hashlock and Hacken audits of the token; the Hashlock PDF is available via a direct link.
Bug bounty: a public bug bounty program page on the Sensay website.
Incidents: —.
Threat model: data privacy risks (offboarding knowledge), risks of AI hallucinations in Q&A, as well as the need to separately verify whether SNSY is a mandatory element of the core product; additionally, the token’s smart contract risks remain.

Project status and timeline

Current status: an active B2B product + API docs; the SNSY token on Ethereum.
Key releases/milestones: Q1 2024 — launch (per the litepaper); API docs version 2025‑03‑25 (updated Dec 11, 2025).
Roadmap: https://docs.snsy.ai/docs/roadmap

Ecosystem/integrations

Integrations: Slack/Teams (mentioned on the website); API integrations (docs.sensay.io); Telegram/Discord (per CMC and the GitHub org).
Partners: the website has a list of logos/mentions, but the “client/partner” terms are not verified.
Where it’s actually used: an offboarding platform for companies (positioning), without public KPIs.

AI component of the project

What is real AI here? the AI interviewer and “replicas”/chat Q&A are the core of the product; the litepaper claims “cutting-edge AI and machine learning algorithms”, but quality metrics/models are not disclosed.
What is truly onchain? the SNSY ERC‑20 token on Ethereum; other onchain contracts/marketplace addresses are not confirmed in open sources.
Why is a token needed? In the litepaper it is described as a means of paying for subscriptions/the marketplace, staking rewards and governance, but the core SaaS can work without the token.
Red flags (based on the information found): token‑washing (the mandatory nature of SNSY is unclear), AI‑washing (no model metrics), privacy/security of offboarding data.

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‑medium	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): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
Conflict note (if any): none.

AI_1 — what the AI does (1/0)

AI_1 (decision): 1
Claim (one line): the AI interviewer conducts offboarding interviews and forms a knowledge base; the API is intended for “AI-driven chatbots (replicas)”.
Evidence: Tier‑1 — https://sensay.io/ ; https://docs.sensay.io/
Why sufficient / why not (one line): the Tier‑1 pages describe the product functionality and the API.
Conflict note (if any): none.

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): there is no verifiable public demo that allows checking the quality of the interviewer/replica (there are product pages and an API spec).
Evidence: Tier‑1 — https://sensay.io/ ; https://docs.sensay.io/
Why sufficient / why not (one line): the website provides a description, but without verifiable AI examples/metrics.
Conflict note (if any): none.

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: — (marketing KPIs on the website are not model quality metrics).
Context (version/date/how measured): —.
Evidence: Tier‑1 — https://sensay.io/
Why sufficient / why not (one line): quality metrics of the models/replicas are not published.
Conflict note (if any): none.

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

AI_4 (decision): 1
Claim (one line): there is a formal API description of the replicas/conversations functions and integrations.
Evidence: Tier‑1 — https://docs.sensay.io/
Why sufficient / why not (one line): sufficient to understand the interfaces and integrations, but not the internal models.
Conflict note (if any): none.

Onchain necessity

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

OC_1 (decision): 1
Chain: Ethereum mainnet
Addresses/identifiers: ERC‑20 SNSY: 0x82a605d6d9114f4ad6d5ee461027477eeed31e34
Evidence: Tier‑1 — https://etherscan.io/token/0x82a605d6d9114f4ad6d5ee461027477eeed31e34
Why sufficient / why not (one line): Etherscan confirms the contract and decimals=18.
Conflict note (if any): the max total supply on Etherscan conflicts with the “fixed supply 10B” in the litepaper/CMC.

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

OC_2 (decision): 0
What useful logic is onchain: apart from the SNSY token, onchain marketplace/replica‑rights (NFT) contracts are not confirmed by addresses.
Evidence: Tier‑1 — https://docs.snsy.ai/docs/litepaper
Why sufficient / why not (one line): the litepaper describes the future marketplace conceptually, but without onchain SSOT addresses.
Conflict note (if any): none.

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: the core product (interviews/knowledge Q&A) can be implemented in a centralized way; onchain is rather about the token and future economic scenarios.
Evidence: Tier‑1 — https://sensay.io/ ; https://docs.snsy.ai/docs/litepaper
Why sufficient / why not (one line): onchain criticality for the core SaaS is not proven.
Conflict note (if any): none.

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a token, $SNSY (ERC‑20).
Evidence: Tier‑1 — https://etherscan.io/token/0x82a605d6d9114f4ad6d5ee461027477eeed31e34
Why sufficient / why not (one line): the contract is confirmed by the explorer.
Conflict note (if any): none.

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

TK_1 (decision): 0
Claim (one line): the litepaper describes paying for subscriptions with the token and discounts, but there is no verifiable mandatory payment layer in the token for the core product.
Evidence: Tier‑1 — https://docs.snsy.ai/docs/litepaper
Why sufficient / why not (one line): described as a plan/model, without “SNSY is currently paid for X” parameters in open sources.
Conflict note (if any): none.

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

TK_2 (decision): 1
Claim (one line): a staking/points‑based system and a rewards pool are described in the litepaper.
Evidence: Tier‑1 — https://docs.snsy.ai/docs/litepaper
Why sufficient / why not (one line): the mechanism is described in text, but without onchain contracts and execution parameters.
Conflict note (if any): none.

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): governance is described as “token holders vote via staking platform”, but no specific governance mechanism/contract is provided.
Evidence: Tier‑1 — https://docs.snsy.ai/docs/litepaper
Why sufficient / why not (one line): this is an intent/design, not a proven working onchain governance.
Conflict note (if any): none.

TK_4 — token is replaceable (1/0)

TK_4 (decision): 1
Claim (one line): since the core SaaS does not require onchain and the mandatory utility of SNSY is not proven, the token looks partially replaceable (fiat/subscription/stablecoin).
Evidence: Tier‑1 — https://sensay.io/ ; https://docs.snsy.ai/docs/litepaper
Why sufficient / why not (one line): the described utility is mainly economic/marketing and is not a “must‑have” for offboarding.
Conflict note (if any): none.

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://sensay.io/	Description of the core product (AI offboarding interviews, knowledge access) and positioning.
Tier‑1	https://docs.sensay.io/	Sensay API specification (replicas/conversations/analytics/users/knowledge base).
Tier‑1	https://docs.snsy.ai/docs/litepaper	Litepaper: use‑cases, the token’s role, a fixed supply of 10B (claimed), distribution and staking mechanics.
Tier‑1	https://docs.snsy.ai/docs/security	Claims about security and audits (Hashlock/Hacken); a mention of enterprise nodes with FHE (roadmap).
Tier‑1	https://etherscan.io/token/0x82a605d6d9114f4ad6d5ee461027477eeed31e34	The SNSY ERC‑20 contract and max total supply (there is a conflict with the litepaper/CMC).
Tier‑1	https://sensay.io/security-bounty-program	Public bug bounty program (payouts in SNSY).
Tier‑1	https://hashlock.com/wp-content/uploads/2024/10/Sensay.io-Smart-Contract-Audit-Report-Final-Report.pdf	PDF audit of the Sensay token (Hashlock; the report is publicly available).
Tier‑1	https://github.com/sensay-io	Integration repositories (telegram/whatsapp/widget examples, etc.) as confirmation of the dev ecosystem.