Syntor
Syntor — 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).
Syntor — an AI/Agents | Infra project on the Ethereum network, token (symbol: TOR).
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 platform/protocol where “decentralized AI agents” and an interface for their creation/browsing are claimed.
- Who it’s for: users who need AI agents and an interface for their creation/use.
- Why onchain/token: the onchain part is confirmed by an ERC‑20 token and a contract; the Tier‑1 website has $TOR staking and a description of the rewards mechanics (including TOR buyback).
- What you can actually touch (Tier‑1): the “Create agent” and “Explorer” pages on the official website.
How it works (very briefly)
- The user does: goes to the website → creates an agent via the interface or selects an agent in “Explore”.
- The system does: provides an interface for managing agents and their “listing” (per the project’s description).
- The user gets: an agent/agent page and basic management actions.
- Where the blockchain is: the token issuance and the existence of the contract are confirmed onchain (Etherscan).
- Token role (if any): the website mentions the token, but a Tier‑1 description of what exactly “breaks down” without the token requires clarification.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Syntor |
| Also known as (aliases) | $TOR, TOR |
| Logo (logo) | ../assets/664_syntor-ai_logo.png |
| Token symbol (ticker) | TOR |
| 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 | 0x21e133E07b6CB3FF846B5a32Fa9869a1E5040da1 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | The Tier‑1 website describes $TOR staking and rewards mechanics (including TOR buyback); supply/issuance parameters are not established per Tier‑1. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI agent creation + management platform |
| Use‑case (use_case) | AI agent creation + launch |
| 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.syntor.ai/ |
| Docs | https://docs.syntor.ai/ |
| GitHub | — |
| Releases / Changelog | — |
| Whitepaper | https://docs.syntor.ai/ |
| Roadmap | https://docs.syntor.ai/roadmap-and-next-steps |
| Security advisories | — |
| Explorer | https://etherscan.io/token/0x21e133E07b6CB3FF846B5a32Fa9869a1E5040da1 |
| App / Demo | https://www.syntor.ai/create-agent |
| X | https://twitter.com/syntorai |
| Discord | — |
| Telegram | https://t.me/SyntorAI |
| Medium | — |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/syntor-ai |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/syntor-ai/ |
General project overview
Syntor is positioned as a platform/protocol for “decentralized AI agents” and provides a web interface for their creation and browsing. In the documentation (Tier‑1), the project describes its goals as infrastructure for Web3 applications, including those with AI functionality, and lists directions (compute, storage, AI automation integrations).
Features/modules
- Explore / Explorer: pages with “agents” and their cards (per the website data).
- Create agent: an agent creation interface (no‑code).
- Docs: a description of the goals and components of the protocol (compute/storage/AI‑integration at the level of a description).
Typical scenarios
- Scenario 1: a user creates an agent via the web interface → gets an agent page and the ability to manage parameters.
- Scenario 2: a user selects an agent in “Explore” → interacts with the agent/its page (details of specific integrations are not established per Tier‑1).
Getting started (wallet/network)
- What you need: an account/access to the web interface; for onchain operations — an EVM wallet.
- Network/chain: Ethereum (per the token contract).
- Fees: Ethereum network fees for onchain operations.
Architecture/tech (non‑AI)
- Components: a web application (UI) + a token contract (ERC‑20) on the Ethereum network.
- Participant roles: users/agent creators, agent users.
- Where logic runs: UI/management — offchain; the onchain part (at minimum) — the token.
- Dependencies: Ethereum infrastructure (wallets/explorer), external platforms (social networks).
Token/economics (expanded, no forecasts)
- Token utility: the Tier‑1 website describes $TOR staking (Stake & Earn) and rewards mechanics (including TOR buyback as part of the distribution of fees).
- Protocol necessity drivers: Tier‑1 describes $TOR staking and the use of TOR buyback in the rewards mechanics; at the same time, a Tier‑1 description of mandatory payments in TOR for using agents is not established.
- Issuance/distribution: not established per Tier‑1.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
Security and incidents
- Audits: —.
- Bug bounty: —.
- Incidents: —.
Project status and timeline
- Current status: the web product is available; the token contract is available on the Ethereum network.
- Roadmap: claimed in the documentation (see
links_*).
Ecosystem/integrations
- Integrations: web UI (Explore/Create), Ethereum (token contract), X/Telegram channels (see
links_*). - Partners: —.
- Where it’s actually used: not established per Tier‑1 (other than the public UI of the product).
AI component of the project
- What is real AI here? Tier‑1 materials describe the product as a platform of AI agents with an interface for creating/browsing agents.
- What is truly onchain? The ERC‑20 token and its contract (Ethereum); other onchain logic of the project is not confirmed by Tier‑1.
- Why is a token needed? Tier‑1 describes $TOR staking and rewards mechanics (including TOR buyback).
- Red flags (based on the information found): onchain‑washing (if onchain boils down to the token); token‑washing (if the role of the token is not confirmed by the product’s mechanisms).
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 partial | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): Tier‑1 sources describe an existing product of AI agents, not only an “intent”.
- Evidence: Tier‑1 — https://www.syntor.ai/ ; https://docs.syntor.ai/
- Why sufficient / why not (one line): AI_0 applies in the absence of a product; here there is a UI and a description of the product.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): The project describes the product as “AI agents” and a platform for their creation/use.
- Evidence: Tier‑1 — https://www.syntor.ai/ ; https://docs.syntor.ai/
- Why sufficient / why not (one line): Tier‑1 materials explicitly state the function: AI agents + management tools.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): The “Explore” and “Create agent” pages are available on the official website (product surface).
- Evidence: Tier‑1 — https://www.syntor.ai/explorer ; https://www.syntor.ai/create-agent
- Why sufficient / why not (one line): This makes it possible to “touch” the product via the official UI.
- 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.syntor.ai/
- Why sufficient / why not (one line): No Tier‑1 benchmark/quality metrics of AI agents/models were found.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 1
- Claim (one line): The Tier‑1 documentation describes the goals and components (compute/storage/AI integration) at the level of an architectural description.
- Evidence: Tier‑1 — https://docs.syntor.ai/
- Why sufficient / why not (one line): There is a tech description at the level of components/tasks; details of models/versions are not recorded, however.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: 0x21e133E07b6CB3FF846B5a32Fa9869a1E5040da1
- Evidence: Tier‑1 — https://etherscan.io/token/0x21e133E07b6CB3FF846B5a32Fa9869a1E5040da1
- Why sufficient / why not (one line): The existence of the token contract in the official explorer confirms the onchain component.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: Not established per Tier‑1 (other than the token).
- Evidence: Tier‑1 — https://www.syntor.ai/ ; https://docs.syntor.ai/
- Why sufficient / why not (one line): OC_2 requires confirmed onchain mechanics (access/accounting/rules), not only a token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.syntor.ai/
- Why sufficient / why not (one line): There is no Tier‑1 justification that a key property of the product breaks down without the blockchain.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, TOR (contract on Ethereum).
- Evidence: Tier‑1 — https://etherscan.io/token/0x21e133E07b6CB3FF846B5a32Fa9869a1E5040da1 ; https://www.syntor.ai/
- Why sufficient / why not (one line): The token contract is observable in the explorer; there are mentions on the official website.
- 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): No Tier‑1 description of a mandatory payment with the TOR token for a specific service was found.
- Evidence: Tier‑1 — https://docs.syntor.ai/ ; https://www.syntor.ai/
- Why sufficient / why not (one line): TK_1 requires an explicit payment/access mechanism in the protocol.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): The Tier‑1 website describes $TOR staking and rewards mechanics, where platform fees are used for TOR buyback.
- Evidence: Tier‑1 — https://www.syntor.ai/stake ; https://www.syntor.ai/rewards
- Why sufficient / why not (one line): Tier‑1 explicitly describes staking/rewards as an incentive mechanism (although details of protocol penalties/slashing are not disclosed).
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): A governance role of the TOR token is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.syntor.ai/
- Why sufficient / why not (one line): TK_3 requires a Tier‑1 record of the governance process and the role of the token.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the TOR token is not established per Tier‑1.
- Evidence: Tier‑1 — https://docs.syntor.ai/
- Why sufficient / why not (one line): An analysis of the token’s functions and alternatives is required; Tier‑1 data is insufficient.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://www.syntor.ai/ | Official website: positioning as a platform of AI agents; presence of the Explore/Create UI. |
| Tier‑1 | https://docs.syntor.ai/ | Official documentation: description of the goals and components (compute/storage/AI integration). |
| Tier‑1 | https://www.syntor.ai/create-agent | Demo surface: the agent creation UI. |
| Tier‑1 | https://www.syntor.ai/explorer | Demo surface: the agent browsing UI. |
| Tier‑1 | https://www.syntor.ai/stake | Staking: description of $TOR staking (Stake & Earn) as the token utility. |
| Tier‑1 | https://www.syntor.ai/rewards | Rewards: description of the revenue‑sharing mechanics and TOR buyback. |
| Tier‑1 | https://etherscan.io/token/0x21e133E07b6CB3FF846B5a32Fa9869a1E5040da1 | Onchain fact: the TOR token contract on the Ethereum network. |
| Tier‑2 | https://coinmarketcap.com/currencies/syntor-ai/ | Reference token profile (metadata; not proof of protocol utility). |
| Tier‑2 | https://www.coingecko.com/en/coins/syntor-ai | Reference token profile (metadata; not proof of protocol utility). |
No comments to display
No comments to display