INT>OS
INT>OS — 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).
INT>OS — an AI/Agents | Infra project on the Base network, token (symbol: —).
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: no comprehensive description of the product/service was found per Tier‑1; the official website has an “Agents” section (shows “0 agents available”).
- Who it’s for: — (not established per Tier‑1).
- Why onchain/token: only the fact of the token’s existence on the Base network is confirmed; the token utility is not established per Tier‑1.
How it works (very briefly)
- The user does: — (not established per Tier‑1).
- The system does: — (not established per Tier‑1).
- The user gets: — (not established per Tier‑1).
- Where the blockchain is: the project’s token exists on the Base network (see links_* → Explorer).
- Token role (if any): not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | INT>OS |
| Also known as (aliases) | IntOS |
| Logo (logo) | — |
| Token symbol (ticker) | — |
| Category | AI/Agents | Infra |
| Primary chain (chain) | Base |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Base; Ethereum L2) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x42e07fA3d31190731368Ca2F88D12D80139DCa42 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | — |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://intos.ai/ |
| Docs | — |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | — |
| Explorer | https://basescan.org/token/0x42e07fA3d31190731368Ca2F88D12D80139DCa42 |
| X | https://twitter.com/IntOSLabs |
| Discord | — |
| Telegram | https://t.me/intosann/ |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/int-os |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/int-os/ |
General project overview
No detailed description of the product was found per Tier‑1. The official website has an “Agents” section (showed “0 agents available” at the time of the check) and “Stake” / “Manifesto” navigation links, but with no details available in this overview. The onchain fact of the token’s existence on the Base network is recorded.
Features/modules
- — (not established per Tier‑1).
Typical scenarios
- — (not established per Tier‑1).
Getting started (wallet/network)
- What you need: — (not established per Tier‑1).
- Network/chain: Base.
- Fees: Base fees for operations with the token (if performed).
Architecture/tech (non‑AI)
- Components: the ERC‑20 token on the Base network.
- Participant roles: — (not established).
- Where logic runs: — (not established).
- Dependencies: — (not established).
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1.
- Token parameters: see the passport for the contract address; confirmed by the explorer link.
Governance
- — (not established per Tier‑1).
Security and incidents
- Audits: — (not established per Tier‑1).
- Bug bounty: — (not established per Tier‑1).
- Incidents: — (not established per Tier‑1).
Project status and timeline
- Current status: — (not established per Tier‑1).
- Roadmap: — (not established per Tier‑1).
Ecosystem/integrations
- Integrations: — (not established per Tier‑1).
- Partners: — (not established per Tier‑1).
- Where it’s actually used: — (not established per Tier‑1).
AI component of the project
- What is real AI here? no description of an AI component was found per Tier‑1.
- What is truly onchain? the token contract on the Base network is confirmed.
- Why is a token needed? not established per Tier‑1 (other than the fact of the token’s existence).
- Red flags (based on the information found): no Tier‑1 proof of an AI component/product; Tier‑1 (docs/repo/releases/demo) is required to confirm the claims.
DecAI Fit component summary
- DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
| Component | Level | Score |
|---|---|---|
| AI reality | low | 0 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 partial | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): No Tier‑1 source with explicit AI intentions was found.
- Evidence: Tier‑1 — https://intos.ai/
- Why sufficient / why not (one line): The website has “Agents”, but without explicit AI wording; conservatively 0.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): What exactly the AI does is not established (no Tier‑1 found).
- Evidence: Tier‑1 — https://intos.ai/
- Why sufficient / why not (one line): There is no Tier‑1 description of AI functionality.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): Demos/examples of operation were not found per Tier‑1.
- Evidence: Tier‑1 — https://intos.ai/
- Why sufficient / why not (one line): There is no Tier‑1 link to an app/demo confirming operation.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found.
- Context (version/date/how measured): —.
- Evidence: Tier‑1 — https://intos.ai/
- Why sufficient / why not (one line): No Tier‑1 metrics/benchmarks were found.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): A technical description/architecture was not found per Tier‑1.
- Evidence: Tier‑1 — https://intos.ai/
- Why sufficient / why not (one line): There are no Tier‑1 docs/repo/specification to set 1.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Base
- Addresses/identifiers: token: 0x42e07fA3d31190731368Ca2F88D12D80139DCa42
- Evidence: Tier‑1 — https://basescan.org/token/0x42e07fA3d31190731368Ca2F88D12D80139DCa42
- Why sufficient / why not (one line): The onchain fact of the token contract is 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: not established (other than the token).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): No Tier‑1 description of onchain logic “other than the token” was found.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established (conservatively 0).
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token (contract on the Base network).
- Evidence: Tier‑1 — https://basescan.org/token/0x42e07fA3d31190731368Ca2F88D12D80139DCa42
- Why sufficient / why not (one line): The Explorer confirms the existence of the token.
- Conflict note (if any): —
TK_1..TK_4 (1/0)
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): Utility as “payment for the service” is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of what the token is used to pay for.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Mechanics of incentives/collateral/penalties are not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of incentives/collateral/penalties.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): The use of the token for governance is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of governance.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 argumentation “replaceable/irreplaceable”; we conservatively set 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://intos.ai/ | The presence of the project/website and the “Agents” section (without details). |
| Tier‑1 | https://basescan.org/token/0x42e07fA3d31190731368Ca2F88D12D80139DCa42 | The existence of the token and the contract address on the Base network. |
| Tier‑1 | — | No Tier‑1 source for claim “what the project’s AI/product does” was found. |
No comments to display
No comments to display