RX5 Marketplace: Demos and Licences
Preview the proposed marketplace for RX5 bots, indicators and tools. Demo, purchase and activation flows are not yet available; publisher and refund terms await approval.
Bots, Indicators and Publisher Standards
The proposed RX5 Marketplace brings product evaluation, eligible licences and versioned publisher records into one workflow. A preview listing is not a purchasable product, tested result or promise of returns.
Proposed Marketplace Categories
Review the proposed product and policy scope. No live catalog count, purchase availability or launch date is established here.
RX5 Trading Bots
Planned strategy listings must identify the compatible runtime, permissions and broker account scope.
- Authorized order actions
- Named runtime version
- Original validation fixtures
RX5 Indicators
Planned indicator listings must separate chart calculations from permission to submit trades.
- Declared data requirements
- Documented calculations
- Supported client versions
Demo Evaluation
Demo rules must be published before access, including duration and trading or data restrictions.
- Eligibility and expiry
- Runtime and data limits
- Permission boundaries
Licences and Activation
Purchase and activation are planned. An approved flow must validate entitlement and account eligibility.
- Account and instance limits
- Renewal and update terms
- Approved refund process
Publisher Standards
Publishers need verified distribution rights, versioned artifacts and a defined support process.
- Rights and dependencies
- Evidence-based claims
- Updates and support
What a Listing Must Disclose
These are publication requirements for the planned marketplace, not verified claims about an available product catalog.
Version and Compatibility
Each listing must name its SDK/runtime version, supported clients, instrument scope and dependencies.
Results and Assumptions
Label simulated, backtested and live results separately, with data rights, period, costs and limitations.
Permissions and Limits
Disclose data, account, trading and network permissions, resource limits and stop behavior before activation.
Updates and Support
State the supported versions, update process, contact and renewal/refund terms after those policies are approved.
Technical Listing Requirements
Runtime support and test evidence must accompany every product claim before a marketplace launch.
Chart Output
An indicator listing should document its output, input series and compatible chart client.
Original Examples
Publish original, authorized examples and reproducible fixtures. No verified indicator count is supplied.
Approved Runtime
A bot requires desktop validation and broker approval before any hosted order-execution workflow.
Execution Boundaries
Supported order controls depend on the runtime and broker. Stops and position sizing cannot eliminate trading loss.
RX5 Marketplace — Preview
The proposed RX5 Marketplace would distribute bots, indicators and supporting tools. Its demo, purchase, entitlement and activation flows are not yet implemented.
Swipe horizontally to view all columns.
| Choice | What a listing should explain | Availability |
|---|---|---|
| Demo | What can be evaluated, eligible accounts, duration, data/runtime restrictions and whether order execution is enabled. | Demo access rules and functioning demo flow: not yet published. |
| Paid licence | Product version, supported runtime, account/device/instance allowance, term, renewal and included updates. | Purchase and entitlement service: not yet implemented. |
| Activation | Eligible broker/account, permissions, compatible runtime and how an entitlement is attached to an instance. | Activation and entitlement checks: not yet implemented. |
- 01
Review the product scope
Check whether the product is a bot or indicator, its compatible runtime, data needs, permissions and documented limitations. Example performance must identify how it was measured.
- 02
Evaluate within demo limits
A proposed demo should state its expiry and restrictions before access is granted. The ability to display a chart does not imply permission to execute trades.
- 03
Confirm entitlement and activate
An implemented purchase flow would need to create the correct licence, validate broker/account eligibility and report activation success or failure.
- 04
Manage the licensed version
The owner should be able to review expiry, supported updates, allowed instances and the process for support, renewal or a refund request.
Swipe horizontally to view all columns.
| Policy area | Details to publish |
|---|---|
| Publisher rights | Identity, ownership or distribution rights, authorized dependencies and responsibility for the listed product. |
| Submission and review | Versioned artifact, compatibility record, declared permissions, original test fixtures, documentation and support contact. |
| Updates | How changes are reviewed, whether upgrades require approval, licence compatibility and access to prior supported versions. |
| Renewal and refunds | Licence term, renewal consent, cancellation process, eligibility, request window, decision owner and processing status. Approved terms: not yet published. |
| Product claims | Distinguish simulated, backtested and live results; identify data/build/period and limitations. A listing is not a promise of profitability. |
Review a version through its full lifecycle
The proposed marketplace needs clear rules for demo access, paid entitlements, updates and incident handling before products can be activated.
- 01
Review publisher and package
Verify publisher identity, distribution rights, declared dependencies, supported runtime, requested permissions and original test evidence. Product claims need dated support.
- 02
Define the entitlement
Show the demo/live boundary, eligible broker/account, licence period, allowed instances, hosting charge and renewal terms before acceptance. A software licence does not fund a trading account.
- 03
Manage updates and restoration
Keep the active version visible, define version pinning and approval for permission changes, and reconcile eligible restoration, refunds and revocation events.
- 04
Respond to a report
Provide abuse reporting, review, takedown and appeal paths. Security revocation needs trader notification and defined behavior for running bots, pending orders and open positions.
Standards Before Launch
Marketplace access depends on implemented transaction flows, tested runtime support and approved customer and publisher policies.
Measured Execution
Publish timings only with a named build, workload, environment and reproducible measurement method.
Scoped Compatibility
Eligible instruments and brokers belong in a tested compatibility record; universal access is not assumed.
Security Review
Review artifact identity, permissions and entitlement checks. No security certification or capital guarantee is established by this preview.
Clear Licence Terms
Show price, term, eligible instances, updates and approved refund conditions before an implemented purchase flow.
Evaluate Scope Before Activation
Review original test evidence and licence restrictions before choosing a bot or indicator. No listing, backtest or demonstration guarantees profitability.
Marketplace and Trading Risk
Using a bot or indicator can result in trading losses. Review permissions, dependencies, costs and execution assumptions. The marketplace remains a preview and does not currently offer purchases or an approved refund policy.
Ask About the RX5 Marketplace
Request the proposed demo, licence and publisher scope. Access and launch timing depend on approved policies and implemented workflows.