AlphaKEK.AI (Alphakek)
AlphaKEK.AI (Alphakek) — 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).
Alphakek — an AI/Agents | Infra project (crypto‑aware AI infrastructure and API) with the AIKEK token (primary contract — 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 set of AI tools and APIs for crypto/DeFi research and visual generation; the documentation describes “universal agents” and a knowledge engine (Fractal).
- Who it’s for: developers/builders who need a crypto‑native AI layer (analytics/meme generation) and users of B2C tools (claimed).
- Why onchain/token: onchain records the existence of the token and its parameters; in the Tier‑1 documentation the AIKEK token is described as “hold‑to‑access/hold‑to‑build/hold‑to‑govern” for access to features and participation in the DAO.
- What you can actually touch (Tier‑1): https://api.alphakek.ai/skill.md (API instructions/endpoints).
How it works (very briefly)
- The user does: uses the website/documentation or the API (e.g., knowledge queries / image generation).
- The system does: processes requests through the AI layer (universal agents/knowledge engine) and returns answers/artifacts (claimed).
- The user gets: research results (an answer + source links) and/or generated images.
- Where the blockchain is: the main onchain artifact is the AIKEK ERC‑20 token on Ethereum (the documentation also claims a multichain version).
- Token role (if any): access to premium features/the Developer API and participation in the Alphakek DAO (Tier‑1).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AlphaKEK.AI (Alphakek) |
| Also known as (aliases) | Alphakek |
| Logo (logo) | — |
| Token symbol (ticker) | AIKEK |
| Category | AI/Agents | Infra |
| 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 | 0x8dce83eca4af45dbe618da1779f9aaca43201084 |
| Token model (token_type) | utility (access + governance) |
| Max supply | 256 000 000 AIKEK |
| Issuance | deflationary (as claimed: fee/buyback/burn) |
| Tokenomics (tokenomics, brief) | Max supply 256M; a multichain version (ETH/Base/Solana) and “hold‑to‑access/build/govern” utility are claimed. |
| Governance | Alphakek DAO (as claimed) |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | crypto-aware AI agents + knowledge engine (Fractal) + API |
| Use‑case (use_case) | crypto/DeFi research + image generation + agent orchestration |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 3 / onchain_score 1 / token_score 1 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.alphakek.ai/ |
| Docs | https://docs.alphakek.ai/ |
| GitHub | https://github.com/alphakek-ai/alphakek-py |
| Releases / Changelog | https://blog.alphakek.ai/ |
| Whitepaper | — |
| Roadmap | https://docs.alphakek.ai/roadmap |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x8dce83eca4af45dbe618da1779f9aaca43201084 |
| App / Demo | https://api.alphakek.ai/skill.md |
| X | https://x.com/alphakek_ai |
| Discord | https://discord.gg/ZY3g6xUuuS |
| Telegram | https://t.me/alphakek_chat |
| Medium | — |
| Audit report(s) | https://docs.alphakek.ai/token-audit |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/alphakek-ai/ |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/alphakek-ai/ |
General project overview
Per the Tier‑1 documentation, Alphakek is positioned as crypto‑aware AI infrastructure, where “universal agents” and the Fractal knowledge engine are used for analytics/research and the generation of visual content. In addition, API documentation (skill.md) and an official Python client that calls the Alphakek REST API have been published.
Features/modules
- Universal Agents: AIKEK Wizard (analytics layer) and AIKEK Memelord (meme generation) (Tier‑1, claimed).
- Knowledge engine (Fractal): a “knowledge engine” with integration of on/off‑chain and external data (Tier‑1, claimed).
- API: endpoints for knowledge queries and image generation + a credits system (Tier‑1, claimed).
Typical scenarios
- Scenario 1: a developer integrates the API/“universal agents” into their application/agent.
- Scenario 2: a user makes a request to the knowledge API and receives an answer with a list of sources.
- Scenario 3: a user generates an image via the Visuals API.
Getting started (wallet/network)
- What you need: access to the documentation/tools; for the API — registration/authorization per the instructions in
skill.md. - Network/chain: the token contract is on Ethereum; the documentation claims a multichain version (ETH/Base/Solana).
- Fees: onchain fees depend on the chosen network/actions; the API uses credits (Tier‑1, claimed).
Architecture/tech (non‑AI)
- Components: universal agents (Wizard/Memelord), the Fractal knowledge engine, the API layer, client libraries (Python).
- Participant roles: users of B2C tools; developers/integrators; token holders (per the utility description).
- Where logic runs: AI logic and data processing — offchain; onchain — the token (and the claimed multichain representation).
- Dependencies: external data sources, API infrastructure, EVM networks for the token.
Token/economics (expanded, no forecasts)
- Token utility (Tier‑1, claimed): hold‑to‑access (premium research and the Meme Generator), hold‑to‑build (access to Universal Agents via the Developer API), hold‑to‑govern (Alphakek DAO).
- Protocol necessity drivers: in the Tier‑1 description, the utility is “access/gov” (it is not proven that the product technically breaks without the token).
- Who pays fees: the API uses credits (Tier‑1); onchain fees — network users when making transactions.
- Where fees / buyback/burn go: the tokenomics describe fee/buyback/LP and burn as elements of the deflationary design (Tier‑1, claimed).
- Issuance/burn: max supply 256M; burn is mentioned in the tokenomics (Tier‑1, claimed).
- Security/incentive mechanisms: not established per Tier‑1 (apart from the description of fee/buyback/burn).
- Distribution and token issuance schedule: not established per Tier‑1 within this card.
- Treasury: not established per Tier‑1 within this card.
Governance
- Who makes decisions: the tokenomics claim participation of token holders in “key business decisions” via the Alphakek DAO.
- How protocol parameters change: not established per Tier‑1 (procedures/threshold rules are not described in the extracted sources).
- Where decisions are discussed/made: not established per Tier‑1.
- Keys/multisig: not established per Tier‑1.
Security and incidents
- Audits:
links_*lists a “Token Audit” as a product/tool for token analysis; an external smart contract audit is not confirmed in Tier‑1. - Bug bounty: not established per Tier‑1.
- Incidents: not established per Tier‑1.
- Threat model: not established per Tier‑1.
Project status and timeline
- Current status: the website/documentation and the API client repository are publicly available.
- Key releases/milestones: not established per Tier‑1 within this card.
- Roadmap: published in the docs (see
links_*).
Ecosystem/integrations
- Integrations: —
- Partners: —
- Where it’s actually used: —
AI component of the project
- What is real AI here? Tier‑1 sources describe an AI layer (universal agents) and a knowledge engine (Fractal) + an API for research/visuals.
- What is truly onchain? the confirmable artifact is the AIKEK ERC‑20 token on Ethereum; the rest of the logic/accounting is not confirmed as onchain per Tier‑1.
- Why is a token needed? in the tokenomics it is described as “hold‑to‑access/build/govern” (Tier‑1, claimed).
- Red flags (based on the information found): most of the claims about “infrastructure/knowledge engine/1M+ datapoints” are descriptive (claimed) without independent quality metrics (AI_3=0); the onchain part is confirmed only at the token level (OC_2=0).
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | high | 3 |
| Onchain necessity | low | 1 |
| Token necessity | low | 1 |
| 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 working part of the product/infrastructure, not only an intent/roadmap.
- Evidence: Tier‑1 — https://docs.alphakek.ai/launch/universal-agents
- Why sufficient / why not (one line): Per SSOT, AI_0=1 is set only when AI_1..AI_4 = 0; here there is a description of working AI components.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): “Universal Agents” (Wizard/Memelord) perform crypto analysis and meme content generation (claimed in Tier‑1).
- Evidence: Tier‑1 — https://docs.alphakek.ai/launch/universal-agents
- Why sufficient / why not (one line): The Tier‑1 document describes the functions (analytics/meme generation) as part of the product.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a verifiable usage “surface” via the API (described in
skill.md) and a public Python client. - Evidence: Tier‑1 — https://api.alphakek.ai/skill.md ; https://github.com/alphakek-ai/alphakek-py
- Why sufficient / why not (one line): There is an instructional Tier‑1 artifact (skill) and the client’s source code with call examples.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://docs.alphakek.ai/
- Why sufficient / why not (one line): —
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): The Tier‑1 documentation describes Fractal (knowledge engine) and the structure of the “universal agents”.
- Evidence: Tier‑1 — https://docs.alphakek.ai/fractal ; https://docs.alphakek.ai/launch/universal-agents
- Why sufficient / why not (one line): A Tier‑1 technical description of the components and their roles is available.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: AIKEK token (ERC‑20): 0x8dce83eca4af45dbe618da1779f9aaca43201084
- Evidence: Tier‑1 — https://etherscan.io/token/0x8dce83eca4af45dbe618da1779f9aaca43201084
- Why sufficient / why not (one line): The explorer records the network/address and the main parameters of the token.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: —
- Evidence: Tier‑1 — https://docs.alphakek.ai/
- Why sufficient / why not (one line): —
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: what breaks without onchain: —
- Evidence: Tier‑1 — https://docs.alphakek.ai/
- Why sufficient / why not (one line): —
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, AIKEK.
- Evidence: Tier‑1 — https://etherscan.io/token/0x8dce83eca4af45dbe618da1779f9aaca43201084 ; https://docs.alphakek.ai/tokenomics
- Why sufficient / why not (one line): Tier‑1 confirms the existence of the token and its parameters/utility.
- 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 tokenomics describe “hold‑to‑access” as a condition for access to premium features.
- Evidence: Tier‑1 — https://docs.alphakek.ai/tokenomics ; https://docs.alphakek.ai/guides/user-tiers
- Why sufficient / why not (one line): Tier‑1 describes token‑gating of functionality (access model).
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): —
- Evidence: Tier‑1 — https://docs.alphakek.ai/tokenomics
- Why sufficient / why not (one line): —
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): The tokenomics describe “hold‑to‑govern” (participation in key decisions via the Alphakek DAO).
- Evidence: Tier‑1 — https://docs.alphakek.ai/tokenomics
- Why sufficient / why not (one line): Tier‑1 records the governance role of the token (at the level of a claim).
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): The token’s utility is described as access/tiers and governance, i.e. the role looks replaceable by alternatives (subscription/account tier) without an onchain necessity.
- Evidence: Tier‑1 — https://docs.alphakek.ai/tokenomics ; https://docs.alphakek.ai/guides/user-tiers
- Why sufficient / why not (one line): Based on the Tier‑1 utility description, there is no proof that the token is technically irreplaceable.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.alphakek.ai/ | Product positioning and the existence of a public website. |
| Tier‑1 | https://docs.alphakek.ai/ | Tier‑1 documentation: overview of the stack, products and token utility (context). |
| Tier‑1 | https://docs.alphakek.ai/launch/universal-agents | Description of the “universal agents” functions (Wizard/Memelord) and their roles. |
| Tier‑1 | https://docs.alphakek.ai/fractal | Description of Fractal as a knowledge engine (architectural context). |
| Tier‑1 | https://api.alphakek.ai/skill.md | API documentation (knowledge/visuals), the credits system and call examples. |
| Tier‑1 | https://github.com/alphakek-ai/alphakek-py | Official Python client for the Alphakek REST API (code + examples). |
| Tier‑1 | https://docs.alphakek.ai/tokenomics | Token utility (hold‑to‑access/build/govern), max supply and multichain contracts (claimed). |
| Tier‑1 | https://docs.alphakek.ai/guides/user-tiers | Token‑gated access model (User Tiers) (claimed). |
| Tier‑1 | https://etherscan.io/token/0x8dce83eca4af45dbe618da1779f9aaca43201084 | Onchain fact: the AIKEK token on Ethereum (address, decimals, max supply). |
| Tier‑2 | https://www.coingecko.com/en/coins/alphakek-ai/ | Aggregator (context). |
| Tier‑2 | https://coinmarketcap.com/currencies/alphakek-ai/ | Aggregator (context). |
No comments to display
No comments to display