Free access / Consumer evidence
Free crypto signals and separate automation costs
Keep a crypto message, marketplace publisher, bot subscription and exchange execution in different evidence and cost records.
The message is not the whole system
A crypto alert may be read on a public page while execution uses a separate automation product and exchange account. The publisher, software and venue need not be the same organisation. Record what the original message specifies: asset, pair, venue if named, direction, validity and updates. A ticker without a quote currency or venue can be ambiguous. Do not silently fill those gaps from whichever chart later looks favourable. A research explanation or educational token discussion remains different from an executable instruction even when both mention a price.
Separate software and marketplace entitlements
A platform's free account or trial does not establish that every marketplace signal subscription or automation feature is included. Name the selected publisher and software tier with their own dated terms. Cryptohopper's marketplace provides a place to inspect signal offers; it does not supply one universal entitlement for all combinations. This desk has not connected an exchange account, purchased a marketplace listing or measured delivery. The profile links official material and keeps those operational questions visible rather than asserting a tested no-charge trading stack.
Credentials do not belong in a review worksheet
A consumer access record should describe permissions without storing API secrets or account credentials. If an automation workflow is being considered, inspect the official permission model and revocation route separately. Do not grant permissions merely to complete an editorial checklist, and do not infer their scope from a marketing screenshot. No broker or exchange connection exists in this publication's tools. Exported examples are local decision records, not commands that can create orders, move funds or validate the safety of a third-party account integration.
A matched cost and observation window
For a cost comparison, use one declared period and currency for subscriptions, software, data and observed execution charges. Include actual account expenses only when documented; otherwise label inputs hypothetical. A deposit, unrealised loss and software bill are different quantities. Define usable messages before dividing by their count, and retain duplicates and incomplete calls outside that denominator without deleting them from the record. Neither a low per-item cost nor a visually active round-the-clock channel certifies profitable execution, complete history or suitability for the reader.
Completed fictional consumer case
Fictional case: Ren reads twelve invented crypto posts. Eight meet her predeclared monitoring definition; four lack a complete pair identifier. Her hypothetical monthly stack has zero message subscription, $20 software and $12 execution costs, so $32 divided by eight is $4 per usable monitoring item. These are not current tariffs, observed bills or vendor results. She retains all twelve records and labels the output a cost scenario. There are no account permissions, actual fills or strategy profits in the example, and the cheap message access does not resolve those missing pieces.
| Record | Evidence object | Bounded finding |
|---|---|---|
| Message population | 12 invented posts | All retained |
| Usable monitoring items | 8 | Predefined identifier rule |
| Scenario expense | Invented $32 / 8 | Cost only: $4 per item |

Primary references and their limits
Public documents reviewed 13 October 2026. A link supports its stated mechanism or access description, not a completed account trial or this desk's invented case.