Sharpe AI
Sharpe 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).
Sharpe AI (also: Sharpe; SAI) — an AI/Other project with the SAI token (ERC‑20; Ethereum).
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 web terminal/platform for crypto analytics and “crypto intelligence”, where some of the features are positioned as AI search/AI narratives and “insights”.
- Who it’s for: users who need a single interface for monitoring metrics (DEX/CEX/onchain data) and analytics; per the positioning — a “professional terminal”.
- Why onchain/token: in the Tier‑1 documentation, $SAI is described as the utility and governance token of the ecosystem (staking, revenue sharing, fee discounts, ecosystem currency, early access/airdrops); the documentation also describes the Sharpe Earn smart contracts for “bundling” DeFi transactions and automations.
- What you can actually touch (Tier‑1): public terminal pages (for example,
.../dexscreener) and AI search (.../search) on the official domain.
How it works (very briefly)
- The user does: opens the Sharpe terminal in a browser and selects a module (screener/search/dashboard).
- The system does: aggregates data (onchain/offchain feeds) and shows metrics/dashboards; in some modules, AI processing is claimed (natural‑language queries, narratives).
- The user gets: analytics pages/search results/summaries on assets and wallets.
- Where the blockchain is: the SAI token (ERC‑20) and its contract onchain on Ethereum; the platform itself looks like an offchain service.
- Token role: the website describes a “value accrual / buybacks” mechanism, but the specific role of the token as a necessary component of the protocol (payment/incentives/governance) requires re‑checking per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Sharpe AI |
| Also known as (aliases) | Sharpe; SAI |
| Logo (logo) | ../assets/343_sharpe-ai_logo.svg |
| Token symbol (ticker) | SAI |
| Category | AI/Other |
| 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 | 0x3567aa22cd3ab9aef23d7e18ee0d7cf16974d7e6 |
| Token model (token_type) | utility (governance) |
| Max supply | 1 000 000 000 SAI |
| Issuance | — |
| Tokenomics (tokenomics, brief) | The website describes a buyback mechanism (claim: “100% revenue allocated to buybacks”) and “supply reduction”; the explorer lists a max total supply of 1B SAI. |
| Governance | — |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI search + AI analytic summaries |
| Use‑case (use_case) | crypto analytics terminal + screeners |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 2 / token_score 2 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://sharpe.ai/ |
| Docs | https://docs.sharpe.ai/ |
| GitHub | https://github.com/Sharpelabs |
| Releases / Changelog | https://sharpeai.medium.com/ |
| Whitepaper | https://github.com/Sharpelabs/Whitepaper/blob/main/Sharpe%20Earn%20Whitepaper.pdf |
| Roadmap | — |
| Security advisories | https://github.com/Sharpelabs/Security/ |
| Explorer | https://etherscan.io/token/0x3567aa22cd3ab9aef23d7e18ee0d7cf16974d7e6 |
| App / Demo | https://sharpe.ai/dexscreener |
| X | https://twitter.com/SharpeLabs |
| Discord | https://discord.com/invite/tFAvMTw6Hx |
| Telegram | https://t.me/SharpeAI_Official |
| Medium | https://sharpeai.medium.com/ |
| Audit report(s) | https://github.com/Sharpelabs/Security |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/sharpe-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/sharpe-ai/ |
General project overview
Sharpe AI is positioned as a “crypto analytics terminal” — a web platform that aggregates market and blockchain metrics and provides monitoring tools (DEX/CEX/onchain feeds, screeners, alerts, etc.). The AI part in the Tier‑1 description looks like AI search (natural‑language queries) and the generation of “market narratives / insights” based on data streams.
Features/modules
- Sharpe Terminal (web): a set of modules/screeners and dashboards for analytics.
- Sharpe Search: AI search across entities (wallets/tokens/transactions/protocols) with natural‑language queries (claimed).
- Alerts/screeners: a set of “institutional tools” (claimed; the specific content requires re‑checking against the documentation/demo pages).
Typical scenarios
- Scenario 1: a user opens the terminal → selects a module (for example, a screener/dashboard) → gets metric visualization and filtering.
- Scenario 2: a user opens Sharpe Search → enters a query/searches for an object → gets results and related data (as claimed).
Getting started (wallet/network)
- What you need: a browser and access to the web terminal; for onchain operations with the token — an EVM wallet.
- Network/chain: the onchain part of the token — Ethereum.
- Fees: Ethereum fees apply to ERC‑20 operations; the terminal’s access/pricing terms and the token’s role in access depend on the product module and are described in the project’s documentation/terms.
Architecture/tech (non‑AI)
- Components: an offchain web platform + the SAI ERC‑20 token on Ethereum.
- Where logic runs: computations/data aggregation and the UI — offchain; the token is confirmed onchain.
Token/economics (expanded, no forecasts)
- Token: SAI (ERC‑20) on Ethereum, the contract is listed in the explorer.
- Tokenomics: the website has a description of “value accrual / buybacks” and “supply reduction” (the wording requires careful language and verification of the execution mechanics).
- Token utility (Tier‑1): the documentation lists staking, governance, fee discounts, ecosystem currency and revenue sharing (see Token Utility + SAI Staking).
Governance
- Governance format: —.
Security and incidents
- Audits: the public repository
Sharpelabs/Securityhosts PDF reports/peer reviews (see links_*). - Bug bounty: —.
- Incidents: —.
- Threat model: the risks are typical for an offchain terminal (centralization and trust in the operator), plus the risk of “AI marketing” without transparent quality metrics.
Project status and timeline
- Current status: public web pages of the terminal/search are available.
Ecosystem/integrations
- Integrations: —.
AI component of the project
- What is real AI here? AI search (natural‑language queries) and AI generation of analytics summaries/narratives (as claimed in Tier‑1).
- What is truly onchain? the SAI token (ERC‑20) on the Ethereum network; the Sharpe Earn documentation describes smart contracts/architecture for bundling DeFi transactions and automations.
- Why is a token needed? in the Tier‑1 documentation, $SAI is described as a utility and governance token: staking/benefits (including revenue sharing), fee discounts and ecosystem currency.
- Red flags (based on the information found): the product looks like an offchain service; AI claims without measurable quality metrics; the token’s role may be “financial”/marketing without protocol necessity — this needs to be re‑checked.
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | medium | 2 |
| 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): AI is described as part of a working product (AI‑powered search/insights), not only as a plan.
- Evidence: Tier‑1 — https://sharpe.ai/
- Why sufficient / why not (one line): The intent flag applies to roadmaps/plans without a working component; here, working modules are described.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Sharpe Search is claimed as AI search with natural‑language queries and AI analytics summaries.
- Evidence: Tier‑1 — https://sharpe.ai/ ; https://sharpe.ai/search
- Why sufficient / why not (one line): The Tier‑1 sources describe the AI search feature and the AI intelligence module.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There are public web pages of the terminal and AI search on the official domain.
- Evidence: Tier‑1 — https://sharpe.ai/dexscreener ; https://sharpe.ai/search
- Why sufficient / why not (one line): The available web modules/pages are sufficient as a “demo/example”.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://sharpe.ai/
- Why sufficient / why not (one line): within the check, no reproducible quality metrics of the AI part (model quality/benchmarks) were found.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): There is a marketing description of the features, but not enough technical details on the architecture/model versions.
- Evidence: Tier‑1 — https://docs.sharpe.ai/
- Why sufficient / why not (one line): The public page looks like a landing page; no detailed tech description sufficient for flag 1 is recorded.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: SAI ERC‑20: 0x3567aa22cd3ab9aef23d7e18ee0d7cf16974d7e6
- Evidence: Tier‑1 — https://etherscan.io/token/0x3567aa22cd3ab9aef23d7e18ee0d7cf16974d7e6
- Why sufficient / why not (one line): The contract and the network are confirmed by the onchain explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: the Sharpe Earn documentation describes Wallet Contract / Assembly / Automation and smart contracts for bundling and automating DeFi transactions (not only “token issuance”).
- Evidence: Tier‑1 — https://docs.sharpe.ai/introduction/meet-sharpe-ai/sharpe-earn/technical-architecture ; https://docs.sharpe.ai/introduction/meet-sharpe-ai/sharpe-earn/smart-contracts
- Why sufficient / why not (one line): There is a Tier‑1 description of the product’s onchain logic and contract architecture.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: per Tier‑1, no justification was found that the blockchain is critical for a key property of the terminal.
- Evidence: Tier‑1 — https://sharpe.ai/
- Why sufficient / why not (one line): There is no claim/mechanic of “without the blockchain the product breaks down”.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, SAI (ERC‑20), on Ethereum.
- Evidence: Tier‑1 — https://etherscan.io/token/0x3567aa22cd3ab9aef23d7e18ee0d7cf16974d7e6
- Why sufficient / why not (one line): The token contract and symbol are confirmed by the explorer.
- 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): In the Tier‑1 documentation, $SAI is described as an ecosystem currency and is linked to fee discounts when using Sharpe trading products.
- Evidence: Tier‑1 — https://docs.sharpe.ai/introduction/usdsai-tokenomics/token-utility
- Why sufficient / why not (one line): “Ecosystem currency” + fee discounts indicate a payment/functional role of the token in the ecosystem’s services.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): The Tier‑1 documentation describes staking rewards and revenue sharing for $SAI stakers.
- Evidence: Tier‑1 — https://docs.sharpe.ai/introduction/usdsai-tokenomics/token-utility ; https://docs.sharpe.ai/introduction/usdsai-tokenomics/usdsai-staking
- Why sufficient / why not (one line): Incentives for participants via staking and the distribution of a share of revenue are described.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): In the documentation, $SAI is described as a governance token allowing to propose/vote on changes to the ecosystem’s protocols.
- Evidence: Tier‑1 — https://docs.sharpe.ai/introduction/usdsai-tokenomics/token-utility
- Why sufficient / why not (one line): Token Utility directly specifies the token’s governance role.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): Per the Tier‑1 description of the utility, it is not proven that the functions (fee discounts/access/staking program) require specifically its own token and cannot be implemented with an alternative asset/subscription.
- Evidence: Tier‑1 — https://docs.sharpe.ai/introduction/usdsai-tokenomics/token-utility ; https://docs.sharpe.ai/introduction/usdsai-tokenomics/usdsai-staking
- Why sufficient / why not (one line): The utility is described as “ecosystem privileges”; irreplaceability requires separate protocol‑level argumentation.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://sharpe.ai/ | Description of the product as a crypto analytics terminal with AI modules (Sharpe Search, AI insights). |
| Tier‑1 | https://sharpe.ai/search | Public AI search page (support for AI_2=1 and AI_1). |
| Tier‑1 | https://sharpe.ai/dexscreener | Public page of the terminal/demo module (AI_2 sync: App/Demo). |
| Tier‑1 | https://docs.sharpe.ai/introduction/usdsai-tokenomics/token-utility | $SAI utility: staking, governance, fee discounts, ecosystem currency, revenue sharing. |
| Tier‑1 | https://docs.sharpe.ai/introduction/usdsai-tokenomics/usdsai-staking | Staking details: 35% APR, min 60 days, revenue sharing 50% platform revenue (as claimed), governance participation. |
| Tier‑1 | https://docs.sharpe.ai/introduction/meet-sharpe-ai/sharpe-earn/technical-architecture | Sharpe Earn onchain architecture: Wallet Contract/Assembly/Automation and bundling of DeFi transactions. |
| Tier‑1 | https://etherscan.io/token/0x3567aa22cd3ab9aef23d7e18ee0d7cf16974d7e6 | The SAI token contract (ERC‑20) and max total supply 1B. |
| Tier‑1 | https://github.com/Sharpelabs/Security | Public security materials/reports in the repository (the basis for “Audit: yes”). |
| Tier‑2 | https://www.coingecko.com/en/coins/sharpe-ai | Reference profile (secondary source). |
No comments to display
No comments to display