Public service surfaces
The root, plans, two checkout forms, signals archive, dashboard, API guide, Telegram archive and Cryptohopper profile returned public content.
Independent provider evidence file | researched 2026-07-11
Crypto Quality Signals Review: Pricing, Proof and Service Status Audit
The current public footprint is active enough to inspect: prices, checkout forms, a 30-day signal archive, a subscriber dashboard and an API guide are reachable. That footprint does not yet identify the responsible legal operator or prove subscriber-account profitability.
Current CSR position: Under review - not CSR verified.
Read the dated findings
The public footprint is substantial enough to research, but not sufficient for verified status or a profitability conclusion.
No account, checkout, payment, support message, exchange connection or trade was used.
- Evidence facts
- 15
- Public sources
- 11
- Displayed plans
- 2
- Fixed feed sample
- 20
Decision first
What this Crypto Quality Signals review can decide now
Confirmed
The reviewed public domain, plans, checkout forms, free-signal archive, subscriber dashboard, API documentation, alternate public API route, Telegram announcement channel and Cryptohopper seller profile were reachable on the research date.
Still missing
The reviewed public pages did not identify a legal operator, named analyst, registration, jurisdiction or street address, and they did not provide a CSR-reviewed, loss-inclusive account return record.
Safest next action
Use the public feed or paper trading first. Before payment or any exchange connection, save the exact plan, refund process and official support route, then ask for the legal operator and a complete result export that includes losses, fees, slippage, sizing and drawdown.
- 1
Save the exact offer
Capture the plan name, billing period, price, included channels, bot access and any coupon before payment. Gold and Silver are not interchangeable.
- 2
Identify the contracting party
Ask for the legal operator, registration, jurisdiction, support owner and governing terms. A brand handle and support email do not answer who owes fulfillment or a refund.
- 3
Normalize the evidence
Deduplicate exchange-level rows into provider ideas, preserve the first timestamp, include every closure and loss, and reconcile fills, fees, slippage, leverage, sizing and drawdown.
- 4
Test without live-account risk
Use the free public route or a paper account first. Do not grant withdrawal permission, and do not assume a bot integration protects you from stale routes, duplicate records or execution differences.
Evidence map
Nine current observations do not erase six claim, gap or route limits
The evidence map counts the fifteen fixed findings in this dataset. A confirmed route or displayed price is useful, but it answers a narrower question than operator identity, contractual recourse or account-level performance.
Price is visible; contract is not
Two plan families and checkout methods are displayed. The reviewed checkout HTML did not expose governing terms, privacy, operator, jurisdiction or a refund-process acknowledgement.
Records are not returns
The archive exposes rows that can be logged, but exchange replication means record volume cannot be read as independent trade ideas, wins or realized fills.
Brand continuity is not operator identity
Cross-linked routes support attribution to the CQS brand footprint. They do not name the analyst, legal merchant or entity responsible for fulfillment and recourse.
Current displayed pricing
Gold and Silver have different delivery scope and five billing periods
The provider labels the catalog as live billing data in staging. Gold is described as full Telegram access with premium channels and support. Silver is described as signal delivery through external platforms and a Telegram bot. A lower price therefore does not mean the same product at a discount.
| Plan | Monthly | Every 2 months | Every 3 months | Every 6 months | Yearly |
|---|---|---|---|---|---|
| CQS Premium Gold | US$50 | US$90 | US$120 | US$210 | US$300 |
| CQS Premium Silver | US$15 | US$27 | US$36 | US$63 | US$90 |
CQS Premium Gold
The provider describes Gold as full Telegram service with a premium chat room, exclusive content channels, support and connections to named third-party trading tools.
Sources: cqs-plans, cqs-checkout-gold
CQS Premium Silver
The provider describes Silver as premium signals on supported external bots and platforms, with Telegram delivery through one of its bots rather than the full Gold channel set.
Sources: cqs-plans, cqs-checkout-silver
The checkout boundary
Both checkout pages offered PayPal and cryptocurrency payment buttons, but CSR stopped before submission. A reachable checkout confirms a purchase route, not successful delivery, recurring-billing behavior, cancellation timing or refund fulfillment. Save the plan and demand the governing terms before using the form.
Original public-feed audit
The displayed 32,316 records are exchange-level rows, not 32,316 independent calls
At the observation time, the provider archive displayed 32,316 records across 1,616 pages for the prior 30 days. CSR froze the first twenty visible rows without filtering. The sample exists to identify the archive's counting unit, not to estimate performance.
17 XRP/USDT rows at one displayed timestamp3 DOGE/USDT rows at a second displayed timestamp
Every displayed exchange row had its own ID.
Seventeen rows shared one XRP timestamp; three sampled rows shared one DOGE timestamp.
The sample's row multiplication was caused by venue coverage, not twenty separate ideas.
All twenty sampled records were open, long, scalping rows when captured.
What can and cannot be inferred
The visible archive counts exchange-level records. In the fixed sample, one pair and timestamp produced 17 separate rows across exchanges. The 32,316 displayed records therefore cannot be treated as 32,316 independent trade ideas, completed trades, wins or subscriber fills.
All sampled rows were still open. This sample describes publication structure only and cannot estimate win rate, realized return, fees, slippage, drawdown or subscriber results.
Automation route check
The alternate public API route responded; the documented primary path did not
Documented primary path
/getSignal/?api_key=FREE&interval=20The public request returned a plain 404 response from the research location.
Documented alternate path
/api/v1/getSignal?api_key=FREE&interval=20The public request returned a valid empty JSON response with error code zero.
The public documentation described both paths as the same handler. On the research date, the documented primary path returned 404 while the alternate path returned a valid empty response. This is a route-parity observation, not evidence that premium delivery fails.
What the guide exposes
The May 2026 guide documents entry zones, targets, stops, exchange identifiers, signal types, risk fields and a literal FREE key. That structure can support paper-trade capture and deduplication.
What the guide cannot prove
Documentation cannot prove private feed uptime, message latency, downstream bot behavior, fill quality, revocation, subscription fulfillment or realized account results. Test the exact response contract before writing automation.
Performance-proof boundary
Price-path statistics are not the same as subscriber-account returns
The provider's About page says daily reports demonstrate profitability under an immediate-entry and target-exit assumption, while also saying profit is not guaranteed. Cryptohopper describes displayed results using highest and lowest movement after a signal. In the reviewed platform stats rows, real-buy and real-sell columns were zero.
1
Original alert
Preserve publication time, entry range, stop, targets, direction, leverage and every edit.
2
Executable fill
Match the alert to venue availability, latency, partial fills, fees, funding and slippage.
3
Complete closure
Include losses, expiries, manual closes, open risk and targets that were touched but not realistically filled.
4
Account return
Apply position sizing and leverage, then report equity curve and maximum drawdown, not summed percentages.
No CSR win rate is published for Crypto Quality Signals
The fixed sample had no closed outcome, and the reviewed public surfaces did not supply the complete execution-ready population needed to calculate one. Visible volume, selected results and platform price excursions are useful inputs, but none independently answers what a subscriber account earned after costs and sizing.
Identity and recourse
The public refund promise is specific in one way and incomplete in several others
What the provider states
The About page describes an unconditional first-month money-back promise for services bought on the website, limited to one use per customer. It also publishes an email, Telegram support handle and Discord route.
What the reviewed pages do not state
No named legal operator, registration, jurisdiction, street address, refund submission procedure, response deadline, processing deadline or dispute forum appeared on the reviewed About and checkout pages.
This is an evidence gap, not an accusation. The operator or terms may exist elsewhere or appear after authentication. Until they are attributable, a buyer cannot know from the reviewed public checkout who owes the service, which law governs the transaction or how the provider's promise would be enforced.
Proof still needed before verified status
- Named legal operator and contracting party
- Company registration, jurisdiction and service address
- Named analyst or accountable trading team
- Checkout-linked governing terms and privacy notice
- Refund request method, response deadline, processing deadline and escalation route
- Plan-specific fulfillment proof for Gold and Silver
- Complete loss-inclusive signal population with edit and deletion history
- Timestamp-to-fill reconciliation with fees, funding, slippage and latency
- Position sizing, leverage and account-return methodology
- Maximum drawdown and open-risk accounting
- Independent subscriber-account evidence
- Private API uptime and downstream bot execution evidence
Fifteen attributable findings
Open the evidence state, decision use and limit for each finding
Every finding keeps the source and the limit together. Positive evidence is not hidden, and missing evidence is not upgraded into a misconduct claim.
service statusThe root page returned HTTP 200, labelled itself Staging v2 and said the platform rebuild was in progress. It also said base infrastructure was operational while signals and subscriptions were under development.Confirmed current
Decision use: Treat the current site as a live rebuild surface, not as a finished-product assurance.
Limit: A staging label does not by itself prove that checkout, delivery or support is unavailable.
Sources: cqs-home
service statusEvery reviewed provider-site page included a noindex, nofollow robots meta directive.Confirmed current
Decision use: Use direct attributable routes rather than assuming search visibility proves which provider page is official.
Limit: The directive is an indexing choice on the provider site, not a safety or legitimacy finding.
Sources: cqs-home, cqs-plans, cqs-about, cqs-signals, cqs-api-docs, cqs-checkout-silver, cqs-checkout-gold
pricingThe public plan catalog displayed Gold from US$50 monthly and Silver from US$15 monthly, with five billing periods for each plan.Confirmed current
Decision use: Save the exact plan and period because the access scope differs between Gold and Silver.
Limit: Displayed prices can change and do not prove billing, delivery or total third-party bot costs.
Sources: cqs-plans
checkoutBoth public checkout routes returned HTTP 200 and displayed email, billing-period and optional coupon fields plus PayPal and BTCPay submission buttons.Confirmed current
Decision use: A reachable form confirms a purchase path exists, but the buyer still needs a written fulfillment and cancellation record.
Limit: No checkout form was submitted and no payment, account creation or fulfillment test was performed.
Sources: cqs-checkout-silver, cqs-checkout-gold
commercial termsThe reviewed checkout HTML did not expose a visible terms, privacy, refund, cancellation, legal-operator, jurisdiction or address link or acknowledgement.Not found on reviewed pages
Decision use: Ask for the governing terms and operator before payment instead of inferring them from the buttons.
Limit: Terms may appear after an authenticated step or through support; that was not tested.
Sources: cqs-checkout-silver, cqs-checkout-gold
refundThe About page states a first-month money-back promise for website purchases, limited to one use per customer.Provider claim
Decision use: Capture this wording before purchase and ask how to submit, time and prove a refund request.
Limit: The reviewed page did not state a response deadline, processing deadline, governing entity or dispute forum. CSR did not test a refund.
Sources: cqs-about
identityThe reviewed About and checkout pages named the brand and support routes but no individual analyst, legal entity, company registration, jurisdiction or street address.Not found on reviewed pages
Decision use: Request the contracting party and jurisdiction before sending money or granting account access.
Limit: Absence on the reviewed pages is not proof that no entity exists elsewhere.
Sources: cqs-about, cqs-checkout-silver, cqs-checkout-gold
identityThe public Telegram announcement channel, provider domain, premium routes and Cryptohopper seller profile use the Crypto Quality Signals or CQS identity and cross-reference compatible support routes.Confirmed current
Decision use: These links support route continuity for the brand footprint.
Limit: Cross-linking does not establish the legal operator, analyst credentials, ownership continuity or profitability.
Sources: cqs-telegram, cqs-home, cryptohopper-cqs-free
signal recordsThe public archive displayed 32,316 exchange-level records for the prior 30 days across 1,616 pages at the observation time.Confirmed current
Decision use: The archive creates a reviewable starting point, but its counting unit must be normalized before any accuracy calculation.
Limit: The count is volatile and is not a count of independent ideas, completed trades, wins or subscriber fills.
Sources: cqs-signals
signal recordsSeventeen of the first 20 rows were the same XRP/USDT timestamp replicated across 17 exchanges; the other three sampled rows were DOGE/USDT records.Confirmed current
Decision use: Deduplicate by provider idea, timestamp and instrument before calculating coverage or outcomes.
Limit: The sample is deterministic but small and was selected to describe page structure, not performance.
Sources: cqs-signals
performanceAll 20 fixed-sample rows were open, long, scalping records, so the sample had no closed outcome to score.Not verified
Decision use: Do not derive a win rate from open records or from selected result posts.
Limit: Later page states may close or revise records; CSR did not monitor this sample forward.
Sources: cqs-signals
performanceThe About page says daily reports demonstrate profitability when a user buys immediately after issuance and sells at recommended targets, while also saying profit is not guaranteed.Provider claim
Decision use: Treat the statement as conditional provider marketing until an execution-ready, loss-inclusive account record is reconciled.
Limit: The reviewed statement does not itself establish fills, fees, slippage, position sizing, leverage, losing trades, drawdown or account return.
Sources: cqs-about
performanceCryptohopper describes its displayed performance in terms of highest and lowest price movement after a signal, and the reviewed stats rows showed zero real buys and zero real sells.Confirmed current
Decision use: Keep price-path metrics separate from realized subscriber account results.
Limit: Marketplace values are volatile, platform-defined and not a CSR audit of every signal or subscriber.
Sources: cryptohopper-cqs-free
automationThe May 2026 API guide documents a FREE key, premium subscription IDs, open-signal retrieval, entry zones, targets, stops, exchange fields and risk levels.Confirmed current
Decision use: A structured feed can support paper-trade logging and reproducible record capture before any exchange automation.
Limit: Documentation does not prove every field is current, every route is available or every downstream bot executes as intended.
Sources: cqs-api-docs
automationThe documented primary public API path returned 404 while the documented alternate path returned HTTP 200 with a valid empty response.Route conflict
Decision use: Test the exact route and response contract before building automation around the documentation.
Limit: One empty public request cannot assess premium delivery, uptime or historical reliability.
Sources: cqs-api-docs, cqs-api-primary-test, cqs-api-alternate-test
Dated source wall
Eleven public snapshots with response hashes
Hashes identify the exact response bodies reviewed at the observation time without republishing those pages. Provider-owned statements remain attributed as claims; linked-platform data remains subject to that platform's method and later changes.
- Crypto Quality Signals root pagecqs-home | HTTP 200 | 10,729 bytes
Staging-v2 rebuild label, noindex directive, base-infrastructure status and links to plans, signals, dashboard, About and API documentation.
Boundary: Provider-owned current surface; statements are not independently verified.
sha256:d944759ef38f8809ed3d98a67174c7ff7ec584fbabe1fd2b8e6458927476efab - Crypto Quality Signals subscription planscqs-plans | HTTP 200 | 11,315 bytes
Gold and Silver descriptions, five displayed billing periods each and direct checkout links.
Boundary: Displayed catalog only; no purchase or fulfillment test.
sha256:57f1f565fa4482cfcc68cc17f6ef1783f098e88cb569798fb68bce461004d845 - Crypto Quality Signals About and refund pagecqs-about | HTTP 200 | 11,469 bytes
History, product claims, support routes, money-back wording, payment-method statement and results-channel link.
Boundary: Provider-authored statements; no named operator or independent result sheet found on the reviewed page.
sha256:d25363f477fa0dc0858de645f2945f8727d0fe6a58e95ef25182829ff5f7711d - Crypto Quality Signals public 30-day signal archivecqs-signals | HTTP 200 | 32,504 bytes
Displayed 32,316 records over 1,616 pages; first 20 rows captured as a deterministic structure sample.
Boundary: Volatile provider-owned archive; sample cannot establish outcomes or completeness.
sha256:7450c0e5ca23d1b4de0b19f8c34dd42846b90cefb977be03c6b217b0df983b1a - Crypto Quality Signals public API guidecqs-api-docs | HTTP 200 | 38,822 bytes
Public and premium authentication model, response fields, route aliases, futures fields, polling guidance and May 2026 update label.
Boundary: Documentation can differ from runtime and does not test private service.
sha256:527270f216dbd6574d15295b903b5d82d0b004840a41f5212c29e9b436081909 - Crypto Quality Signals Silver checkoutcqs-checkout-silver | HTTP 200 | 12,750 bytes
Silver billing choices, email and coupon fields, PayPal and BTCPay buttons.
Boundary: GET-only observation; no form submission, account creation, payment or fulfillment test.
sha256:6492b4129828aad4d6f8329c3c12f062804fc294866f074c1b60456cc5f8a653 - Crypto Quality Signals Gold checkoutcqs-checkout-gold | HTTP 200 | 12,751 bytes
Gold billing choices, email and coupon fields, PayPal and BTCPay buttons.
Boundary: GET-only observation; no form submission, account creation, payment or fulfillment test.
sha256:11dc259d0df4be6d51119b5e73adf7c8af207618b4fd8e0d7da473fd06878a10 - Documented CQS public API route runtime testcqs-api-primary-test | HTTP 404 | 19 bytes
The documented primary path returned a plain 404 response.
Boundary: Single unauthenticated public request from the research location.
sha256:b16e15764b8bc06c5c3f9f19bc8b99fa48e7894aa5a6ccdad65da49bbf564793 - Alternate CQS public API route runtime testcqs-api-alternate-test | HTTP 200 | 71 bytes
The alternate documented path returned a valid empty JSON response with error code zero.
Boundary: Single unauthenticated public request; no private key or premium feed used.
sha256:ccba441b66c554daaf7cb73ebb2bd7645495027a2a7c02b07c3bd40da0957140 - Crypto Quality Signals public announcement channelcqs-telegram | HTTP 200 | 109,423 bytes
Public announcement archive cross-linking the domain, premium portal and service routes.
Boundary: Provider-owned announcement channel; not a complete or independently reconciled result archive.
sha256:acb73f7bd081e4374bc140590512e03fd296142720dedb65c1aab2a895f432b3 - Cryptohopper CQS FREE seller and signal profilecryptohopper-cqs-free | HTTP 200 | 2,757,925 bytes
Seller identity, free signal product, supported exchanges, platform performance methodology and real-trade columns.
Boundary: Third-party marketplace values are volatile and platform-defined; not an independent account audit.
sha256:1b62aee8e9292fad191a5f1504d47fe6d555e4b8c56254d9128c56a72f071c1f
Method and machine-readable evidence
One original canonical, not a page for every query variation
Source policy
Prefer current provider-owned pages and directly linked platform records. Attribute every provider statement, separate observed behavior from marketing claims, and keep missing proof visible.
Sample policy
The public-feed sample is the first 20 visible rows on page 1 at the observation time. It is used only to identify the archive counting unit and cannot score performance.
Excluded actions
account creation, login, checkout submission, payment, refund request, support message, private API access, exchange connection, order placement, trade execution.
Change policy
Prices, records, routes and platform metrics are dated observations. Recheck them before making a decision.
Review summary JSONDecision boundary, metrics, facts, sources and current observationsEvidence facts CSVOne row per finding with source IDs and limitsImmutable source datasetGitHub Gist version 29ec4b7a2ee1f99b87a63baf4ae357af8bd0bff6 | 25,429 bytes | SHA-256 739da251af14be2d067e5e3334ee51eee7fbea1a9dd077b7710b4ff55eed3a27
Reuse boundary: You may cite the dated facts with attribution to CryptoSignalsReview and the named source. Do not convert under-review status into endorsement, or a public record count into a win-rate or profitability claim.