AGI‑Alpha‑Agent
AGI Alpha / AGI‑Alpha‑Agent (AGIALPHA) — 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).
AGI‑Alpha‑Agent — an AI/Agents project/codebase (research prototype) about “meta‑agentic” orchestration of agents + demonstrations (for example, the Insight demo via GitHub Pages). A utility token, AGIALPHA, is claimed around the project (per Tier‑1 GitHub — an ERC‑20 address is recorded in the repository; this card also lists a separate SPL token on Solana — see the conflict note).
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 open‑source prototype of an “agent factory”: code and demos in which the system creates/orchestrates other agents.
- Who it’s for: developers and researchers who want to look at agentic orchestration and demos.
- Why onchain/token: per the project’s claims — for the utility/economy of the marketplace/jobs and governance; the practical necessity of the onchain part in its current form is not proven.
- What you can actually touch (Tier‑1): https://montrealai.github.io/AGI-Alpha-Agent-v0/README/
How it works (very briefly)
- The user does: opens the demo in the browser (GitHub Pages) or runs the code locally.
- The system does: executes an agentic cycle (orchestrator → sub‑agents → collection of the result) within the repository’s demonstrations.
- The user gets: an interactive example of agentic orchestration and a set of sources/docs.
- Where the blockchain is: the codebase contains references/configuration of the token and onchain components; the fact confirmed in Tier‑1 is a fixed ERC‑20 token address in the repository. Deployment/use of an onchain marketplace in production is not confirmed.
- Token role: claimed as the system’s utility token ($AGIALPHA), but the current verifiability of the utility is limited.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AGI‑Alpha‑Agent |
| Also known as (aliases) | AGI Alpha, α‑AGI, Alpha‑Factory (in the repository), AGIALPHA |
| Logo (logo) | ../assets/216_agi-alpha-agent_logo.jpg |
| Token symbol (ticker) | AGIALPHA |
| Category | AI/Agents |
| Primary chain (chain) | Ethereum |
| Type | non-EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum), PoS/PoH (Solana) |
| Launch date (launch_date) | 2024-05-01 (Git tag v0.1.0-alpha in the changelog; 2025 appears on the roadmap page — conflict) |
| Project status (status) | active (the repository and demo are being updated) |
| Token (standard) | ERC-20 |
| Token contract | 0xa61a3b3a130a9c20768eebf97e21515a6046a1fa (ERC‑20, per GitHub); tWKHzXd5PRmxTF5cMfJkm2Ua3TcjwNNoSRUqx6Apump (SPL, per links_*) |
| Token model (token_type) | utility (marketplace + governance) |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | the roadmap/whitepaper describe marketplace/jobs and burn/fees ideas; this does not confirm the actual economy on mainnet |
| Governance | DAO (claimed on the website; the actual mechanism not verified) |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | MontrealAI / Vincent Boucher (per the website/repository) |
| Funding (investors/funding) | — |
| AI component (ai_component) | meta-agentic orchestration, demos |
| Use‑case (use_case) | agentic system demos + prototypes |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 3 / 1 / 0 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://agialpha.com/ |
| Docs | https://montrealai.github.io/AGI-Alpha-Agent-v0/README/ |
| App / Demo | https://montrealai.github.io/AGI-Alpha-Agent-v0/README/ |
| GitHub | https://github.com/MontrealAI |
| Releases / Changelog | https://github.com/MontrealAI/AGI-Alpha-Agent-v0/blob/main/CHANGELOG.md |
| Whitepaper | https://agialpha.com/whitepaper |
| Roadmap | https://agialpha.com/roadmap |
| Security advisories | — |
| Explorer | https://solscan.io/token/tWKHzXd5PRmxTF5cMfJkm2Ua3TcjwNNoSRUqx6Apump |
| X | https://twitter.com/agialphaagent |
| Discord | — |
| Telegram | https://t.me/agialpha |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/agi-alpha-agent |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/agi-alpha-agent/ |
General project overview
AGI‑Alpha‑Agent is a public MontrealAI repository described as a conceptual research prototype and a set of demonstrations of “meta‑agentic” AGI: an orchestrator system that creates/configures/manages other agents and collects the result in an end‑to‑end cycle.
Important: the Tier‑1 README itself contains a disclaimer that “AGI/superintelligence” is an aspirational wording and does not mean the existence of a real AGI.
Features/modules
- GitHub repository with code and demo: documentation, scripts, Docker builds, tests.
- Insight demo (GitHub Pages): a browser demo that can be opened without installation.
- Whitepaper.md and roadmap: describe the conceptual architecture and the planned components (Nova‑Seeds, marketplace/jobs, etc.).
Typical scenarios
- Scenario 1 (trying the demo): a user opens the Insight demo in the browser → looks at the interface and the logic of the agentic cycle.
- Scenario 2 (running locally): a developer clones the repository and runs the quickstart/Docker → gets a local testbed for experiments.
- Scenario 3 (analysis of onchain ideas): reads
WHITEPAPER.md/the roadmap → understands which onchain components the authors plan, but does not take this as a fact of implementation.
Getting started (wallet/network)
- What you need: for the demo — a browser; for a local run — Python/Node/Docker (see the repository README).
- Network/chain: if considering the token — Ethereum (per the GitHub token config); links_* also lists an SPL token on Solana (conflict).
- Fees: network fees for onchain operations; actual onchain operations are not required within the demo.
Architecture/tech (non‑AI)
- Components: the codebase (demos, scripts, containerization), a set of smart‑contract folders in the repository (as part of the concept).
- Participant roles: demo users; developers; (in the whitepaper/roadmap) — agents and validators, but this is a conceptual model.
- Where logic runs: most of it — offchain (demo/local run). The onchain part is confirmed as the token configuration and the presence of contracts in the repository.
- Dependencies: GitHub Pages for the demo; Python/Node tools; optionally RPC/keys if the onchain modules are enabled (not required for the basic demo).
Token/economics (expanded, no forecasts)
- Token utility: the website and the whitepaper/roadmap describe $AGIALPHA as a utility token for the marketplace/jobs and ecosystem operations.
- Protocol necessity drivers: in the currently verifiable form (repository + demo) the token is not mandatory, so the necessity remains at the level of claims.
- Who pays fees: — (depends on future onchain modules; not confirmed as a working mechanism).
- Where fees go: —.
- Issuance/burn: burn/fees ideas appear in the whitepaper/roadmap, but the issuance/supply parameters are not confirmed by a Tier‑1 onchain source.
- Security/incentive mechanisms: the roadmap describes staking/validators as a concept; parameters/contracts on mainnet are not confirmed.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: the MontrealAI team/community; DAO governance is claimed on the website.
- How protocol parameters change: via repository updates; onchain governance is not confirmed.
- Where decisions are discussed/made: the GitHub repository (issues/PRs) and the project’s social media.
- Keys/multisig: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
- Threat model: the key risk is the mixing of “concept/marketing” and “working product”; also the conflict of token networks/addresses (see below).
Project status and timeline
- Current status: an actively maintained open‑source repository + a public demo.
- Key releases/milestones: initial release
v0.1.0-alpha(perCHANGELOG.md). - Roadmap: published on the website (link in
links_*).
Ecosystem/integrations
- Integrations: GitHub Pages demo; local run via Docker/scripts.
- Partners: —.
- Where it’s actually used: as a demo/prototype; production integrations are not confirmed.
AI component of the project
- What is real AI here? The demos/code of agentic orchestration are real (including the browser demo). At the same time, the repository itself emphasizes that this is a conceptual prototype and “AGI” is an aspirational wording.
- What is truly onchain? A Tier‑1 fact is confirmed: the repository records the address of the $AGIALPHA ERC‑20 token; this card also lists an SPL token on Solana — without a Tier‑1 link between them.
- Why is a token needed? The whitepaper/roadmap describe utility for the marketplace/jobs, but for the current demo the mandatory nature of the token is not confirmed; this requires a separate check.
- Red flags (based on the information found): token‑washing (the token is not required for the demo), onchain‑washing (many onchain concepts without proof of deployment), a conflict of token addresses/networks between sources.
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 3 |
| 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): 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 = 3.
- Conflict note (if any): none.
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): the repository describes and implements an agentic approach: an orchestrator and demonstrations (including the Insight demo), as well as a local/offline mode.
- Evidence: Tier‑1 — https://github.com/MontrealAI/AGI-Alpha-Agent-v0 ; https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/WHITEPAPER.md
- Why sufficient / why not (one line): the presence of code and descriptions confirms the AI component as an agentic demo, but does not confirm an “AGI” level.
- Conflict note (if any): none.
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): the repository README contains a link to a public browser demo (α‑AGI Insight) “to see it in action”.
- Evidence: Tier‑1 — https://github.com/MontrealAI/AGI-Alpha-Agent-v0
- Why sufficient / why not (one line): the Tier‑1 repository points to a reproducible demo artifact that can be opened without installation.
- Conflict note (if any): none.
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — https://github.com/MontrealAI/AGI-Alpha-Agent-v0
- Why sufficient / why not (one line): public measurable quality metrics of the model/agents as a “product” could not be verified (many descriptions, but few KPIs).
- Conflict note (if any): none.
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): the repository has detailed documents/instructions on running, CI and the structure of the demos, as well as a whitepaper description of the architecture.
- Evidence: Tier‑1 — https://github.com/MontrealAI/AGI-Alpha-Agent-v0 ; https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/CHANGELOG.md
- Why sufficient / why not (one line): the documentation is sufficient for a reproducible run of the demo/prototype.
- Conflict note (if any): none.
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum (ERC‑20 per the Tier‑1 GitHub config)
- Addresses/identifiers: 0xa61a3b3a130a9c20768eebf97e21515a6046a1fa (ERC‑20 address, 18 decimals — in the repository)
- Evidence: Tier‑1 — https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/token.config.js
- Why sufficient / why not (one line): the repository directly records the address and decimals of the token used in the CI/configuration.
- Conflict note (if any):
links_*lists a different token/network (Solana), which creates an identification conflict.
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: a working onchain marketplace/Jobs available as a production service is not confirmed.
- Evidence: Tier‑1 — https://agialpha.com/roadmap ; https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/WHITEPAPER.md
- Why sufficient / why not (one line): the sources describe the onchain components as a roadmap/concept, but not as a verifiable deployed product.
- Conflict note (if any): none.
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: the demo and most of the prototype work without a blockchain; without onchain, only the claimed economy/accounting/escrow breaks down (which is not confirmed as mandatory for the demo).
- Evidence: Tier‑1 — https://github.com/MontrealAI/AGI-Alpha-Agent-v0
- Why sufficient / why not (one line): the Tier‑1 README emphasizes the demo orientation and offline modes, which reduces the necessity of onchain.
- Conflict note (if any): none.
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): the project has a claimed token, $AGIALPHA.
- Evidence: Tier‑1 — https://agialpha.com/ ; https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/token.config.js
- Why sufficient / why not (one line): the token is mentioned on the website and recorded in the repository.
- Conflict note (if any): there is a conflict of token networks/addresses between sources.
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): no verifiable Tier‑1 confirmation that “the token is actually paid for service X today” was found (the descriptions are conceptual).
- Evidence: Tier‑1 — https://agialpha.com/roadmap
- Why sufficient / why not (one line): the roadmap describes planned mechanics, but is not proof of a working payment layer.
- Conflict note (if any): none.
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): staking/slashing and validator mechanics are described in the roadmap/whitepaper, but the parameters/deployment are not confirmed.
- Evidence: Tier‑1 — https://agialpha.com/roadmap ; https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/WHITEPAPER.md
- Why sufficient / why not (one line): without deployed contracts and parameters, this cannot be considered a proven mechanism.
- Conflict note (if any): none.
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): the website claims DAO governance and the role of the $AGIALPHA utility token in the ecosystem.
- Evidence: Tier‑1 — https://agialpha.com/
- Why sufficient / why not (one line): this is a Tier‑1 claim, but the governance mechanism/contracts are not presented as a verifiable implementation.
- Conflict note (if any): none.
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 1
- Claim (one line): in the current demo the token is functionally replaceable (the demo/code run without onchain payments), and the role of the token is predominantly economic/marketing.
- Evidence: Tier‑1 — https://github.com/MontrealAI/AGI-Alpha-Agent-v0
- Why sufficient / why not (one line): the README describes the demo and offline modes; this reduces the necessity of the token for the core functions.
- Conflict note (if any): none.
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://github.com/MontrealAI/AGI-Alpha-Agent-v0 | Existence of the code and an explicit “conceptual research prototype” disclaimer; a link to the browser demo. |
| Tier‑1 | https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/token.config.js | The recorded address of the $AGIALPHA ERC‑20 token and decimals=18 in the repository. |
| Tier‑1 | https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/CHANGELOG.md | Existence of the release tag v0.1.0-alpha (dated 2024-05-01) and notes about the token. |
| Tier‑1 | https://raw.githubusercontent.com/MontrealAI/AGI-Alpha-Agent-v0/main/WHITEPAPER.md | Conceptual description of the architecture and the claimed token utility (as a whitepaper draft). |
| Tier‑1 | https://agialpha.com/roadmap | Roadmap with a description of the stages and onchain components (as a plan/intent). |
| Tier‑1 | https://agialpha.com/ | Marketing claims about “meta-agentic AGI”, DAO governance and the $AGIALPHA utility token. |
No comments to display
No comments to display