> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trdrs.co/llms.txt
> Use this file to discover all available pages before exploring further.

# FXCubic

> Connect a dedicated FXCubic test pricing service; execution still requires vendor conformance.

FXCubic is a bridge to a venue's contracted liquidity services. The current TRDRS-maintained
integration implements FXCubic FIX API v1.2.2 and exposes the TRDRS public provider contract.
Its **test pricing only** candidate is available as an owning-organization sandbox preview.
Public listing review is pending; other organizations cannot install that preview.

## What is available

The current release supports authenticated readiness, its manifest, and live bid/ask market data
through a dedicated provisioned connection. The journal preserves quote sequence numbers across
service restarts. It does not claim account discovery, order execution, execution history,
account provisioning or production qualification. Listing does not enable those capabilities.

## Connect your venue

1. Once its public listing is approved, open **Providers → Browse providers** in
   [sandbox Back Office](https://sandbox.trdrs.co/developer) and select **FXCubic**.
   Its maintainer can already see the sandbox preview. Read its release, contact and requirements.
2. Contact [TRDRS](mailto:info@trdrs.co) to arrange a dedicated deployment with your vendor-provided
   host, quote/trade credentials, account and connection requirements. The current service accepts
   one provisioned connection. A public listing does not share another venue's private session.
3. Add the pinned release to your venue, then create your private **Connection** with the endpoint
   and credentials supplied for that deployment.
4. Run manifest validation. Successful manifest validation proves the declared contract; it does
   not grant trading permission. Market-data validation and order conformance are different checks.

FXCubic/vendor commercial access and liquidity arrangements remain yours to obtain. Before order
execution is enabled, an authorized operator must complete the vendor's coordinated conformance
on its dedicated test account. Mainnet execution remains disabled until that evidence is accepted.

See [provider publishing](/providers/publishing) for ownership and maintenance handoff, and
[provider self-check](/providers/provider-self-check) for the separate data and execution suites.

## Current verification

On September 30, 2026, the sandbox service passed authenticated readiness and the engine's
manifest-validation request. A bounded EURUSD quote stream produced live bid/ask prices; after a
service restart, the journal continued its durable sequence from 4 to 5/6 under a new generation.
The provider journal contained zero commands and executions. These were read-only recovery
checks. They are not a claim that vendor order conformance or every live execution self-check ran.

The data-only self-check rules are also tested in hermetic CI with a disposable provider fixture.
A maintainer supplies its own test evidence for publication review. The submitted candidate
continues to declare execution and account discovery false.