Post by mujahid-dev about Helius Staked SOL ($hSOL)

$hSOL Note: The only Helius page on TokenGems is for $hSOL, so I'm reviewing Helius the company's developer infrastructure (RPC + DAS API) here. My feedback is about their RPC product, not the staking token itself.

$HELIUS — tried the RPC + DAS API as a developer, with PowerShell and a free key (Oct 12, 2026). Three things stood out:

1. Error response format is inconsistent between protocol and auth failures.

A malformed JSON-RPC request returned proper structured JSON:

{"error":{"code":-32700,"message":"Parse error"},"id":null,"jsonrpc":"2.0"}

But an invalid API key returned HTTP 401 with a plain-text body — literally just "Unauthorized", 12 bytes, no JSON, no error code, no docs link. Client SDKs handling auth failures have to string-match instead of reading a status code. A structured {"error":{"code":401,"message":"Invalid API key","docs":"..."}} on the auth path would make error handling consistent across the API.

2. DAS getAsset works on the free tier — but the docs don't say so clearly.

I tested getAsset for USDC (EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v) and got the full asset response: interface=FungibleToken, last_indexed_slot, full token metadata. It worked. But when signing up, I couldn't tell whether DAS was available on Free or gated behind a paid plan — the pricing page says "Enhanced APIs" without a per-method breakdown. A one-line note ("getAsset, getAssetsByOwner, and X other DAS methods are available on Free") would save devs from guessing.

3. The free tier is more permissive than the docs imply.

I ran 30 sequential getAsset calls and then 20 concurrent getAsset calls on the free plan. All 50 returned 200. No 429, no Retry-After, no throttling. Either the limit is higher than expected or it's enforced differently than the docs suggest. Publishing the actual RPS ceiling per plan on the Usage page would let devs build confidently instead of guessing whether a burst will fail.

Question for the Helius team: Is the free tier's DAS rate limit enforced per-second, per-minute, or only on credit consumption? And can the auth error path be upgraded to return structured JSON like the rest of the RPC?

Scope: public RPC via PowerShell Invoke-RestMethod + free-tier dashboard + docs, Oct 12, 2026. Free plan API key used, no paid upgrade. No affiliation with Helius.

Tagging $hSOL since this is its token page — the review itself is about Helius's developer products, not the staking token's mechanics.