Skip to main content

Top Hat

Top Hat (HAT) — 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).

Top Hat — an AI/Agents | Infra project on Solana: described in the documentation as an infrastructure platform for creating multi‑purpose AI agents that can perform onchain and offchain tasks (per the official docs). The HAT token is an SPL token on Solana (the CA is listed in the docs).

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 platform/infrastructure for creating task‑specific AI agents in the Solana ecosystem.
  • Who it’s for: users and builders who want to assemble and launch agents (including with integrations/APIs).
  • Why onchain/token: the HAT token is described as the platform token; the docs claim credits/paid features and a deflationary buy&burn mechanic.

How it works (very briefly)

  1. The user does: creates/configures an AI agent via the platform interface (per the description in the docs).
  2. The system does: the agent performs tasks, including working with “live‑data” and “knowledge retrieval”, and can also initiate onchain actions.
  3. The user gets: task automation/information synthesis/workflow execution.
  4. Where the blockchain is: the Solana network and the HAT SPL token; specific onchain contracts of the platform are not singled out in Tier‑1 sources.
  5. Token role (if any): the docs claim utilities around credits and premium features, as well as buy&burn from credit operations.

Quick links: AI thesis fit

Project passport

Field Value
Project name Top Hat
Also known as (aliases) HAT; TopHat
Logo (logo) —
Token symbol (ticker) HAT
Category AI/Agents | Infra
Primary chain (chain) Solana
Type non-EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) 2024-10-31 (fair launch, per the docs)
Project status (status) active
Token (standard) SPL
Token contract AxGAbdFtdbj2oNXa4dKqFvwHzgFtW9mFHWmd7vQfpump
Token model (token_type) utility (payments)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) credits + buy&burn; premium features gated by HAT (per the docs)
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI agents (live-data + knowledge retrieval)
Use‑case (use_case) AI agent creation + launch
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary 1 / 1 / 2 / 0
Last verified 2026-02-11

General project overview

In the official documentation, Top Hat is described as an infrastructure platform for creating multi‑purpose AI agents in the Solana ecosystem, with the goal of building an “agent‑driven ecosystem” where user agents interact with people and other agents and can perform onchain/offchain tasks. The docs emphasize the use of live‑data tracking and knowledge retrieval.

Features/modules

  • Creation and configuration of AI agents (platform/infrastructure).
  • A credits system to keep agents running.
  • HAT token utilities (credits pricing / premium gating / fee distribution / buy&burn).

Typical scenarios

  • Scenario 1: a user creates an agent for information synthesis and action automation → the agent performs tasks taking data/knowledge into account.
  • Scenario 2: a builder publishes APIs/integrations → receives a reward in HAT (per the “API store payouts” description).

Getting started (wallet/network)

  • What you need: a Solana wallet for interacting with the SPL token and possible onchain operations; access to the documentation.
  • Network/chain: Solana.
  • Fees: Solana network fees for onchain actions.

Architecture/tech (non‑AI)

  • Components: user interface/platform, credits system, SPL token.
  • Where logic runs: the AI logic and integrations are probably mostly offchain; onchain, at least the HAT token is confirmed (address in the docs).

Token/economics (expanded, no forecasts)

  • Token utility: credits and paid features; the docs state that credit packages will/may be priced in HAT (V2) and that part of the top‑up is used for HAT buy&burn.
  • Incentive mechanisms: payouts to API store builders and distribution of part of the fees from the launchpad (per the docs).

Governance

Not established per Tier‑1 sources (on the tokenomics page in the docs, governance is not singled out as a separate function).

Security and incidents

  • Audits / bug bounty / advisories: no confirmation found in Tier‑1 sources.

Project status and timeline

  • Roadmap: described in the docs (HAT V2 upgrade).

AI component of the project

  • What is real AI here? In the Tier‑1 documentation, the product is explicitly positioned as a platform for creating AI agents; the agents’ tasks are described (knowledge retrieval, live‑data tracking, execution of onchain/offchain tasks).
  • What is truly onchain? The HAT SPL token on Solana; onchain tasks for agents are also claimed, but specific contracts/addresses of the platform are not singled out as verifiable artifacts in Tier‑1 sources.
  • Why is a token needed? The docs describe the economic role of HAT around credits and utilities (premium gating, payouts, buy&burn).
  • Red flags (based on the information found): onchain‑washing — if onchain boils down to the token without product contracts; what to double‑check — which specific operations and contracts of the platform are executed onchain and where their addresses/docs are.

DecAI Fit component summary

  • DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis
Component Level Score
AI reality low 1
Onchain necessity low 1
Token necessity medium 2
Evidence Tier‑1 present 0
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI is claimed not only as intent but as the core of the product (a platform for AI agents).
  • Evidence: Tier‑1 — https://docs.tophat.one/
  • Why sufficient / why not (one line): by definition, AI_0 is used for intent without evidence, whereas here there is a Tier‑1 description of the product; therefore we do not use AI_0 and evaluate via AI_1..AI_4.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI agents perform tasks (information synthesis / workflows) with live‑data tracking and knowledge retrieval.
  • Evidence: Tier‑1 — https://docs.tophat.one/
  • Why sufficient / why not (one line): the docs explicitly describe the purpose and functions of the AI agents.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a Tier‑1 “what you can touch” artifact (app/demo/quickstart with a reproducible scenario) was not found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without a specific Tier‑1 link to a demo/guide we do not raise AI_2.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): quality metrics of the AI agents are not published in Tier‑1 sources.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): the technical architecture/model versions/pipelines of the agent are not laid out as a verifiable Tier‑1 artifact.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the available docs pages contain no structured tech description of the AI architecture.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Solana
  • Addresses/identifiers: token HAT: AxGAbdFtdbj2oNXa4dKqFvwHzgFtW9mFHWmd7vQfpump
  • Evidence: Tier‑1 — https://docs.tophat.one/docs/Readme/usdhat-tokenomics
  • Why sufficient / why not (one line): the tokenomics lists the token CA.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): no Tier‑1 source with addresses/a description of the platform’s onchain contracts was found.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not proven; the Tier‑1 texts do not show that a key property of the product breaks down without the blockchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no explicit 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 platform has a token, HAT, on Solana.
  • Evidence: Tier‑1 — https://docs.tophat.one/docs/Readme/usdhat-tokenomics
  • Why sufficient / why not (one line): the token is described in the official documentation.
  • 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): credit packages are claimed as priced in HAT (V2) and tied to the operation of agents.
  • Evidence: Tier‑1 — https://docs.tophat.one/docs/Readme/usdhat-tokenomics
  • Why sufficient / why not (one line): the tokenomics directly links HAT to credits.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): payouts to builders and distribution of part of the fees, buy&burn — elements of incentives/economics around HAT.
  • Evidence: Tier‑1 — https://docs.tophat.one/docs/Readme/usdhat-tokenomics
  • Why sufficient / why not (one line): the tokenomics lists the V2 utilities (payouts/fee distribution/buy&burn).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the governance role of the token is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the tokenomics does not describe voting/governance via HAT.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): no conclusion about the replaceability of the token has been drawn (there is no Tier‑1 comparison “with the token/without the token”).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without an explicit Tier‑1 justification we do not raise TK_4.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.tophat.one/ Top Hat is positioned as a platform for creating AI agents on Solana
Tier‑1 https://docs.tophat.one/docs/Readme/usdhat-tokenomics role of the HAT token (credits, buy&burn, premium gating, payouts), token CA
Tier‑1 — No Tier‑1 source for claim “there are onchain contracts of the platform (other than the token) with addresses” was found.