AI Pin
AI Pin — 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 Pin — a consumer project with a set of AI tools/bots and claimed “autonomous agents” (Tier‑1: website and whitepaper), token: AI (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 set of AI tools (chatbots/content generation/agents) available via the project’s web products (Tier‑1: website/whitepaper).
- Who it’s for: users and teams that need AI tools for content/automation (claimed in Tier‑1 sources).
- Why onchain/token: the AI token is claimed as a utility token for access/subscriptions and rewards in the ecosystem (Tier‑1: whitepaper).
- What you can actually touch (Tier‑1): https://chat.ai-pin.io (the project’s web application)
How it works (very briefly)
- The user does: selects an AI tool/bot in the project’s web interface.
- The system does: performs the AI task (generation/chat/assistance), as described in Tier‑1 sources.
- The user gets: generated text/a response/content or the result of the tool’s work.
- Where the blockchain is: the AI ERC‑20 token (Ethereum).
- Token role (if any): described in the whitepaper as a token for access/subscriptions/purchases and rewards.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | AI Pin |
| Also known as (aliases) | AI‑PIN; AI |
| Logo (logo) | ../assets/538_ai-pin_logo.png |
| Token symbol (ticker) | AI |
| Category | AI/Agents | Consumer |
| 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 | 0xbc544207ff1c5b2bc47a35f745010b603b97e99e |
| Token model (token_type) | utility (payments) |
| Max supply | 100,000,000 |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | Max total supply: 100,000,000 AI |
| Governance | — |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agents + generative tools |
| Use‑case (use_case) | chatbots + content generation |
| DecAI Fit — AI thesis fit | 4/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 2 / 1 / 2 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://ai-pin.io |
| App / Demo | https://chat.ai-pin.io |
| Docs | https://ai-pin.gitbook.io/whitepaper/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://ai-pin.gitbook.io/whitepaper |
| Roadmap | https://ai-pin.gitbook.io/whitepaper/ |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0xbc544207ff1c5b2bc47a35f745010b603b97e99e |
| X | https://twitter.com/aipin_io |
| Discord | — |
| Telegram | https://t.me/aipinio |
| Medium | http://aipin.medium.com/ |
| Audit report(s) | https://ai-pin.gitbook.io/whitepaper/legalities/safu-and-audit-report |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/ai-pin |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ai-pin/ |
General project overview
AI Pin is a set of web AI tools that the website describes as “AI agents / autonomous bots / generative AI tools” for various scenarios (content, chatbots, automation). The onchain part in the available Tier‑1 sources is represented by the AI token (ERC‑20).
Features/modules
- A set of AI templates/tools (content generation, chatbots, etc.) (Tier‑1: website).
- White‑label chatbot solutions (Tier‑1: website).
- Token utility for access/subscriptions/rewards (Tier‑1: whitepaper).
Typical scenarios
- Scenario 1: a user opens the web application → launches an AI tool → receives generated text/content.
- Scenario 2: a user uses the chatbot interface for their own tasks → receives answers/assistance (as described on the website).
Getting started (wallet/network)
- What you need: access to the project’s web application.
- Network/chain: Ethereum (if interacting with the token).
- Fees: Ethereum network fees for onchain operations with the token.
Architecture/tech (non‑AI)
- Components: web products/bots (offchain) + the token contract (onchain).
- Participant roles: users of the AI tools; token holders.
- Where logic runs: onchain — the token; the AI logic — offchain (per the meaning of Tier‑1 sources; technical details not extracted).
- Dependencies: the Ethereum infrastructure (for the token).
Token/economics (expanded, no forecasts)
- Token utility: in the Tier‑1 whitepaper, the $AI token is described as a means of access to subscriptions/premium services and purchases of AI products, as well as for community rewards and developer grants.
- Protocol necessity drivers: per the whitepaper, the token is used as payment/access and as part of the ecosystem’s reward mechanics.
- Who pays fees: users performing onchain operations with the token.
- Where fees go: Ethereum network fees.
- Issuance/burn: fixed supply (per the explorer/whitepaper: max supply).
- Security/incentive mechanisms: community rewards and grants (Tier‑1).
- Distribution and token issuance schedule: there is a Tokenomics section in the whitepaper (details not extracted).
- Treasury: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
- Where decisions are discussed/made: —.
- Keys/multisig: —.
Security and incidents
- Audits: the whitepaper publishes a “SAFU & Audit Report” page (Tier‑1).
- Bug bounty: —.
- Incidents: —.
- Threat model: separate verification of the token smart contract and the security terms (audit/report) is required.
Project status and timeline
- Current status: active (web products available; token on mainnet).
- Key releases/milestones: —.
- Roadmap: given in the whitepaper (see links_*).
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: inside the project’s web AI tools (claimed).
AI component of the project
- What is real AI here? Tier‑1 sources describe a set of AI tools/bots and “autonomous agents”. Metrics/benchmarks and the technical architecture of the model/versions are not established per Tier‑1 sources.
- What is truly onchain? The AI ERC‑20 token (Ethereum).
- Why is a token needed? In the Tier‑1 whitepaper, the token is described as a means of access/subscriptions/purchases and for rewards/grants inside the ecosystem.
- Red flags (based on the information found): most of the product is offchain; insufficient technical details/metrics on AI; the quality/scope of the audit and its applicability need to be double‑checked per Tier‑1.
DecAI Fit component summary
- DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 2 |
| Onchain necessity | low | 1 |
| 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 the product, so the intent flag does not apply.
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper
- Why sufficient / why not (one line): There is a Tier‑1 description of the AI tools, so AI_1/AI_2 are considered directly.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The project provides AI tools/bots (chatbots, content generation, etc.), as well as “autonomous agents” (claimed).
- Evidence: Tier‑1 — https://ai-pin.io ; https://ai-pin.gitbook.io/whitepaper
- Why sufficient / why not (one line): Tier‑1 sources explicitly describe the purpose of the AI component.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a web application (chat.ai-pin.io) where AI tools/a chatbot can be launched.
- Evidence: Tier‑1 — https://ai-pin.io (the “Experience it Free!” link) ; https://chat.ai-pin.io
- Why sufficient / why not (one line): There is an accessible product entry point that allows one to “touch” the features.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found per Tier‑1
- Context (version/date/how measured): not found per Tier‑1
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper
- Why sufficient / why not (one line): No quantitative metrics/benchmarks were found in the available Tier‑1 materials.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A tech description of the AI architecture/model versions sufficient for AI_4=1 was not found per Tier‑1.
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper
- Why sufficient / why not (one line): There is a high‑level description, but without a specific architecture/versions.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: 0xbc544207ff1c5b2bc47a35f745010b603b97e99e
- Evidence: Tier‑1 — https://etherscan.io/token/0xbc544207ff1c5b2bc47a35f745010b603b97e99e
- Why sufficient / why not (one line): The token contract and its parameters are available in the explorer.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: per Tier‑1 sources, no confirmation of onchain logic other than the token was found
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper ; https://etherscan.io/token/0xbc544207ff1c5b2bc47a35f745010b603b97e99e
- Why sufficient / why not (one line): The sources describe the product and the token utility, but not an onchain protocol.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that without the blockchain the product loses a key property (per Tier‑1)
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper
- Why sufficient / why not (one line): Onchain necessity is not substantiated in the available materials.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, AI (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0xbc544207ff1c5b2bc47a35f745010b603b97e99e
- Why sufficient / why not (one line): The token contract is 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): Whitepaper: $AI is used for subscriptions/purchases of premium AI services and products.
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper/ai-pin-utilities/token-utility
- Why sufficient / why not (one line): The Tier‑1 source explicitly describes the payment/access scenario.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Whitepaper: community rewards and developer grants are distributed/supported with the $AI token.
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper/ai-pin-utilities/token-utility
- Why sufficient / why not (one line): The Tier‑1 source describes rewards/grants as part of the token utility.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): A governance function of the token is not established per Tier‑1.
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper/ai-pin-utilities/token-utility
- Why sufficient / why not (one line): Governance is not described in the available token utility section.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): No Tier‑1 justification of the replaceability of the token without loss of the claimed functions was found.
- Evidence: Tier‑1 — https://ai-pin.gitbook.io/whitepaper/ai-pin-utilities/token-utility
- Why sufficient / why not (one line): In the docs, the token is described as the key to access/rewards, so we conservatively set 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://ai-pin.io | Description of the set of AI tools/bots and a link to the web app. |
| Tier‑1 | https://chat.ai-pin.io | Demo/product entry point (AI_2). |
| Tier‑1 | https://ai-pin.gitbook.io/whitepaper | Whitepaper: positioning and description of features. |
| Tier‑1 | https://etherscan.io/token/0xbc544207ff1c5b2bc47a35f745010b603b97e99e | Onchain fact: the AI token (ERC‑20), contract and max supply. |
| Tier‑1 | https://ai-pin.gitbook.io/whitepaper/ai-pin-utilities/token-utility | Token utility: subscriptions/purchases, rewards, grants. |
| Tier‑1 | https://ai-pin.gitbook.io/whitepaper/legalities/safu-and-audit-report | Publication of the audit/SAFU link (as claimed in the whitepaper). |
No comments to display
No comments to display