Credits
userInternal compute units: action costs, purchase tiers, and the rules.
What credits are
Credits are non-transferable internal compute units. They meter AI and analytics work — nothing else. They are not money, not a token, not a balance you can trade or withdraw, and never anything investment-like. Every plan refills a monthly allowance; heavier users can buy top-ups.
Action costs
Rendered live from HISS_CREDIT_COSTS in @hiss/core:
| Action | Key | Credits |
|---|---|---|
| Generate a basket from a whisper | generateBasket | 1 |
| Deep HISS Score with full risk report | deepScore | 5 |
| Simulated paper backtest | backtest | 10 |
| Oracle health report | oracleHealthReport | 3 |
| Rebalance suggestion (never executed) | rebalanceSuggestion | 5 |
| MCP plan export | mcpPlan | 10 |
| Premium (watermark-free) share card | shareCardPremium | 2 |
| Social thread draft | ctThread | 5 |
| Creator fork/engagement analytics | creatorAnalytics | 10 |
| Basket Wars advanced ranking breakdown | basketWarsAdvancedRank | 5 |
Purchase tiers
| Price | Credits | Credits per $ |
|---|---|---|
| $5 | 50 | 10 |
| $10 | 120 | 12 |
| $25 | 350 | 14 |
| $100 | 1,600 | 16 |
The rules
- Credits never expire mid-cycle games: monthly allowances reset, purchased credits carry.
- Credits are bound to one account — no transfers, gifts, or secondary markets.
- Credits buy compute, never outcomes: a deep score costs the same whether the news is good or bad.
- The x402 endpoints publish a
creditsEquivalentper request so agent spend and in-app spend stay comparable.