Orenix — checking crypto trade setups before entering a position

[Orenix]

Hi everyone,

I work on Orenix, a tool for reviewing crypto trade setups before opening a position, and would appreciate feedback on the workflow.

You can paste a Telegram signal or enter a setup manually. Orenix structures the entry, stop-loss and take-profit levels, then shows a risk/reward assessment and market context. It also includes a screener, a Market Mood view and demo/paper trading without connecting a live exchange.

For example, when reviewing a signal, the questions we want to make easier to answer are: Are the entry, stop and targets clearly specified? What does the planned risk/reward look like? How does the setup fit the broader market?

There is a 14-day full demo/paper trial, followed by a free basic mode covering BTC, ETH, SOL and BNB. Paid access is also available. The assessment does not guarantee a profitable trade.

What would you want to see first in a tool like this: the original signal beside the parsed parameters, a clearer explanation of the risk assessment, or the demo result? Specific feedback on unclear or missing information would be useful.

 

[Orenix]

I work on Orenix. We have added two public, step-by-step examples showing the inputs, the actual service response and its limitations.

BTC/USDT: entry 73,577.10, stop 72,841.33 and target 75,048.64 USDT gave approximately 2:1 price-distance risk/reward. The service returned Score 67 and WAIT, with DIRECTION_NOT_CONFIRMED. A larger target distance did not confirm market direction.

ETH/USDT: entry 2,045.52, stop 2,004.61 and target 2,065.98 USDT gave approximately 0.50 R/R. It returned Score 62 and WAIT, with WEAK_RISK_REWARD and DIRECTION_NOT_CONFIRMED.

These were educational inputs authored by our team around public quotes on 12 November 2026. The API responses are real; no orders or paper trades were executed. Score is not a win percentage, and these examples do not establish profitability. Fees and execution were not evaluated.

The full inputs, calculations and response tables are published in the public Orenix Radar case studies. Both examples can be read without login.

For anyone designing a similar review interface: would you explain the exact warning before showing the overall Score? That is the distinction these examples are intended to make inspectable.