Stelar Crypto Signals — regime, sentiment, price, risk
Pricing
from $20.00 / 1,000 tool calls
Stelar Crypto Signals — regime, sentiment, price, risk
Crypto market regime, sentiment, price, and volatility-risk signals for SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA — powered by the same classifier that steers Stelar Digital's live production grid-trading bot. Includes a market_brief bundle mode that merges regime+sentiment+price+risk in one call.
Pricing
from $20.00 / 1,000 tool calls
Rating
0.0
(0)
Developer
Robert Dainowski
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Share
Stelar Crypto Signals
Crypto market-signal tools for agents and pipelines, powered by the same classifier that steers Stelar Digital's live production grid-trading bot. Covers SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA.
Tools (tool input field)
| tool | what it returns |
|---|---|
market_brief (default) | bundle: regime + sentiment + price + volatility-risk in one call |
regime | market regime (chop / trend_up / trend_down / high_vol) + grid-suitability verdict |
sentiment | -1..+1 sentiment score + bullish/neutral/bearish label, from recent price action |
pricecheck | current price, 24h/7d % change, bullish/bearish/neutral signal |
token_risk | volatility / drawdown risk regime (low/med/high) vs 30-day baseline |
Input
symbol is one of: SOL, XLM, BTC, ETH, XRP, DOGE, LTC, ADA.
Output
One row is pushed to the default dataset:
Pricing
Pay-per-event: one tool-call event is charged per Actor run (the
market_brief bundle fans out to 4 origin calls internally but is still a
single charged event). Exact price is set at publish time in the Apify
Console — see README-PUBLISH.txt.
About Stelar Digital
Built and maintained by Stelar Digital — the same signal engine also powers a live production grid-trading bot, a RapidAPI listing, and an MCP server. More at https://stelardigital.com?src=apify.
Running locally
Requires a STELAR_PROXY_SECRET environment variable (Stelar Digital's
origin proxy secret — internal use only, never shared publicly):
Input is read via Actor.getInput() (Apify's local INPUT_VALUE / apify run
convention) — see README-PUBLISH.txt for the exact local test invocation used
during development.
