Helius API

Query Solana data via the Helius API. Use when the user asks about Solana wallet balances, token holdings, NFT holdings, transaction history, transfer activity, wallet identity/labels, wallet funding sources, parsing transactions, or other Solana on-chain data. Triggers on: "solana wallet", "sol balance", "solana transactions", "wallet history", "who funded this wallet", "wallet identity", "solana transfers", "solana NFTs", "helius", "check solana address", "solana data", "parse transaction", "enhanced transactions", "transaction details".

Security Scan

The skill's behavior (it needs a HELIUS_API_KEY and will call Helius endpoints) matches its purpose, but the published metadata/manifest does not declare the required API key and there is no trusted source/homepage — this mismatch and lack of provenance warrant caution.

Purpose & Capability

The skill's name/description and the SKILL.md consistently describe querying Helius (Solana) REST APIs; the operations (balances, history, transfers, identity, enhanced transactions) legitimately require a Helius API key and network access. That is coherent with the stated purpose.

Instruction Scope

The SKILL.md instructs the agent only to call Helius REST endpoints (via curl/fetch) and to use the HELIUS_API_KEY as a query param or header. It does not instruct reading unrelated system files, other environment variables, or contacting unexpected third-party endpoints.

Install Mechanism

This is an instruction-only skill (no install spec, no code files executed at install). No downloads or install scripts are present, which reduces the risk from installation.

Credentials

The SKILL.md explicitly requires HELIUS_API_KEY, but the registry metadata lists no required env vars and primary credential is none — a clear mismatch. The skill will use the user's Helius API key to make potentially many paid requests (SKILL.md notes wallet API requests cost credits), so the credential is both necessary and sensitive; the manifest should declare it. No other credentials are requested.

Persistence & Privilege

The skill does not request always:true or any elevated system presence. It is user-invocable and can be invoked autonomously by default (platform default), which is expected for skills of this type.

What to consider before installing

This skill appears to do what it says (query Helius for Solana data), but there are two things to check before installing: (1) provenance — the skill's source/homepage is unknown; prefer skills published by a known/trusted owner or with a documented homepage. (2) manifest mismatch — SKILL.md requires a HELIUS_API_KEY but the registry metadata does not declare it; ask the publisher to update the manifest to explicitly require HELIUS_API_KEY so you know what will be accessed. Practical precautions: use a dedicated Helius API key with limited billing/quota for this skill (or an account with limited funds), enable monitoring/alerts on API usage, rotate the key if you stop using the skill, and consider restricting the agent to manual invocation if you don’t want automated queries that could consume credits. If you cannot verify the skill author or the missing manifest entry is not fixed, treat installation as higher risk and avoid providing your primary Helius key.

Query comprehensive Solana data via REST endpoints. Requires HELIUS_API_KEY env var.

Setup

export HELIUS_API_KEY="your-key-here"

Get a key at https://dashboard.helius.dev

Base URLs

• Wallet API: https://api.helius.xyz/v1/wallet/{address}/...?api-key=KEY
• Enhanced Transactions: https://api-mainnet.helius-rpc.com/v0/...?api-key=KEY

Auth: ?api-key=$HELIUS_API_KEY query param or X-Api-Key header.

Wallet API Endpoints

Endpoint	Path	Description
Balances	/v1/wallet/{address}/balances	Token + NFT holdings with USD values
History	/v1/wallet/{address}/history	Parsed transaction history with balance changes
Transfers	/v1/wallet/{address}/transfers	Token transfer activity (sent/received)
Identity	/v1/wallet/{address}/identity	Known wallet labels (exchanges, protocols)
Batch Identity	/v1/wallet/batch-identity (POST)	Look up up to 100 addresses at once
Funded By	/v1/wallet/{address}/funded-by	Original funding source of a wallet

Enhanced Transactions Endpoints

Endpoint	Path	Description
Parse Transactions	/v0/transactions/ (POST)	Parse signatures into human-readable data
Transaction History	/v0/addresses/{address}/transactions	Enhanced tx history with type/time/slot filtering

Reference Files

Read the appropriate file for detailed parameters, response formats, and examples:

• Balances (portfolio, holdings, USD values): See references/balances.md
• History (wallet tx history, P&L, tax reports): See references/history.md
• Transfers (sent/received, payment tracking): See references/transfers.md
• Identity (wallet labels, exchange detection): See references/identity.md
• Funded By (funding source, sybil detection): See references/funded-by.md
• Enhanced Transactions (parse tx, enhanced history): See references/enhanced-transactions.md

Implementation Notes

• Use curl or fetch — no SDK required
• All endpoints return JSON
• Pagination: use page param (balances) or before/cursor (history, transfers)
• Default limit: 100 per request
• Wallet API requests cost 100 credits each
• Identity returns 404 for unknown wallets — handle gracefully
• Funded By returns 404 if wallet never received SOL
• Enhanced Transactions uses a different base URL (api-mainnet.helius-rpc.com)