VC

Restricted provider review

Enter the conformance room.

Each account opens only its provider's sanitized review room. It contains no provider credentials, raw protocol payloads, production accounts, or order controls.

VCVaultCoreOSProvider Conformance Room
API under test: R | Protocol API 0.89.0.0Environment: Rithmic Test

Authentic credentialed evidence · Read-only integration

Rithmic conformance,
without theater.

A transparent view of what VaultCoreOS actually executed, what Rithmic returned, what remains permission-limited, and what is still awaiting provider approval.

Loading evidenceVerifying capture time

Credentialed testOrder and PnL plants

0

Orders submittedRouting remains disabled

Secrets displayedRuntime-only resolution

Provider approvalNot submitted

Accessible test accountsIdentifiers intentionally removed
Trade routes observedRead-only route discovery
Exchange permissionsEntitlement records returned
Generated schemasSupplied RProtocol 0.89.0.0

Working product walkthrough

From VaultCore access to account monitoring.

This guided reviewer mode uses the authentic sanitized capture below. It demonstrates the actual product flow without exposing the Rithmic credential or pretending the recorded session is currently live.

Captured evidence replay

Step 1 · Application access

VaultCoreOS reviewer session

The reviewer has entered the isolated conformance room. This is VaultCore authentication—not a Rithmic credential form. Provider credentials remain server-side and unavailable to the browser.

Session roleProvider reviewer · read onlyApplicationVaultCoreOS

Step 2 · Provider connection

Choose the approved environment

Only the environment issued for conformance is enabled. Production deployments and gateways remain unavailable.

Credentialed capture verifiedOrder Plant and PnL Plant login succeeded · this screen is a sanitized replay

Step 3 · Account selection

Select an entitled test account

The authenticated account-list request returned one accessible account. Its provider identifier is intentionally replaced in reviewer mode.

Step 4 · Read-only monitoring

Rithmic Test Account 01

Last credentialed capture shown below. No live-state claim is made.

Snapshot received
Account statusAccessibleAccount List response passed
RMS statusReceived1 account RMS record
P&L snapshotReceived1 account update · 0 instrument updates
Trade routes20Discovery only · no order submission
Order entry unavailableNew, modify, cancel, and flatten controls are not present in this conformance scope.

Protocol execution

What actually ran

Loading

Loading sanitized request outcomes…

Ticker Plant evidence

Bounded market-data smoke passed.

A separate credentialed Rithmic Test session used the VaultCoreOS application identity for one instrument. This is sanitized captured evidence, not a currently live quote display.

Loading evidence
EnvironmentLoadingTicker Plant
InstrumentLoadingSingle-instrument scope
Updates requestedLoadingEntitlement-limited test
Session cleanupLoadingCapture time unavailable
Read-only boundary preserved0 orders · 0 historical requests
13

Transparent permission boundary

Get User Info was valid—and denied.

Template 3510 was sent with the authenticated login name and the FCM/IB context returned by Rithmic. An empty target produced 6: bad input; the correctly populated request produced 13: permission denied. VaultCore records this as permission-limited, never as passed.

Trading Platform by RithmicPowered by OMNE