The tools that change chain state are helius_send_jito_bundle and helius_execute_jupiter_swap; everything else reads and hands back what the Helius endpoint returned. Both write paths keep the sensitive part with you — one takes a signer, the other takes transactions you serialized yourself. Asset coverage runs through the Helius asset endpoints rather than raw RPC, which is what makes by-creator, by-authority and by-group queries possible at all.
A Solana RPC and digital-asset gateway over the Helius API, 38 tools deep across chain reads, asset lookups, fee estimation and transaction submission.
- Account state for any address: SOL balance, raw account info, several accounts in one call, and every account owned by a program.
- Token positions and supply — token accounts by owner or by mint, the largest holders of a mint, and the balance of a single token account.
- Chain status reads: current slot, block height, latest blockhash, epoch info and schedule, leader schedule, node version and recent performance samples.
- Digital-asset lookups by id, by owner, by creator, by authority and by group, plus a filtered asset search, NFT editions, asset proofs and real-world-asset records.
- Transaction work — signature history for an address, a transaction by signature, fee for a serialized message, priority-fee estimates and confirmation polling.
- Submission paths beyond plain RPC: helius_send_jito_bundle with helius_get_bundle_statuses, and helius_execute_jupiter_swap for a token swap.
A Helius API key in HELIUS_API_KEY. Signing stays on your side: helius_execute_jupiter_swap takes a signer, and helius_send_jito_bundle takes transactions you have already serialized.