McCortex OI
McCortex OI
Menú

Built for Institutional Trading

  • Dedicated API Access Institutional accounts connect through a dedicated API, allowing internal systems to route orders and pull execution data without relying on the browser interface.
  • Institutional Execution Infrastructure Orders route through server-side execution infrastructure built to handle institutional order flow, maintaining consistent performance independent of any single connected device.
  • Consolidated Reporting Across Accounts Position and performance data consolidate into a single reporting view, giving institutional teams a clear record of activity across strategies and accounts.
  • Structured Onboarding Process Institutional onboarding runs through a dedicated account manager, covering verification, account structure and configuration before any capital is committed to a strategy.
  • Configurable Risk Parameters Risk limits are configured before execution begins, giving institutional desks control over exposure at the strategy level rather than adjusting positions after the fact.
  • Dedicated API Access Institutional accounts connect through a dedicated API, allowing internal systems to route orders and pull execution data without relying on the browser interface.
  • Institutional Execution Infrastructure Orders route through server-side execution infrastructure built to handle institutional order flow, maintaining consistent performance independent of any single connected device.
  • Consolidated Reporting Across Accounts Position and performance data consolidate into a single reporting view, giving institutional teams a clear record of activity across strategies and accounts.
  • Structured Onboarding Process Institutional onboarding runs through a dedicated account manager, covering verification, account structure and configuration before any capital is committed to a strategy.
  • Configurable Risk Parameters Risk limits are configured before execution begins, giving institutional desks control over exposure at the strategy level rather than adjusting positions after the fact.
  • Dedicated API Access Institutional accounts connect through a dedicated API, allowing internal systems to route orders and pull execution data without relying on the browser interface.
  • Institutional Execution Infrastructure Orders route through server-side execution infrastructure built to handle institutional order flow, maintaining consistent performance independent of any single connected device.
  • Consolidated Reporting Across Accounts Position and performance data consolidate into a single reporting view, giving institutional teams a clear record of activity across strategies and accounts.
  • Structured Onboarding Process Institutional onboarding runs through a dedicated account manager, covering verification, account structure and configuration before any capital is committed to a strategy.
  • Configurable Risk Parameters Risk limits are configured before execution begins, giving institutional desks control over exposure at the strategy level rather than adjusting positions after the fact.

For institutional traders

Who this is for and what changes at scale

McCortex OI was built as a browser-based workspace for individual traders, and the same architecture extends naturally to teams managing larger allocations across multiple strategies and accounts. What changes at scale is not the underlying technology but the way it is configured: more strategies running in parallel, more granular risk limits, and a need for reporting that a single dashboard view cannot satisfy on its own. A desk that trades size needs to see positions, exposure and strategy performance side by side, and it needs the confidence that automated execution keeps running whether or not someone is actively watching a screen.

This page describes how McCortex OI supports that kind of institutional trading without changing the core promise of the product: strategies are deployed without writing code, risk limits are applied before an order reaches the market, and execution continues server-side regardless of what is happening on the trader’s own device. Teams that outgrow a single-account setup can bring several strategies, several risk profiles and several reviewers into one workspace, structured around how a desk actually operates rather than around a retail-only interface. The goal is consistency: the same risk discipline that applies to one account applies to twenty, and the same reporting logic applies whether a strategy runs for a day or for a quarter.

Execution infrastructure and server-side strategy hosting

Every strategy on McCortex OI runs on infrastructure the platform operates, not on the trader’s own machine. Once a strategy is deployed and its risk limits are set, the logic that watches the market and places orders lives on the server side, which means it continues to operate through a dropped connection, a closed laptop or a change of location. For an institutional user, this matters less as a convenience and more as an operating principle: execution does not depend on any single person’s device staying online, and a strategy configured on Monday behaves the same way on Friday regardless of who is at their desk.

Risk limits sit ahead of execution rather than behind it. Before an order is placed, the platform checks it against the limits configured for that strategy, so exposure is capped by design rather than corrected after the fact. This applies uniformly whether a desk is running one strategy or several in parallel across spot and futures markets, long and short. McCortex OI does not publish latency figures, throughput numbers or uptime percentages, and it makes no claim to prime brokerage services, custody arrangements or segregated accounts; those are separate questions from what this workspace is designed to do, which is host and execute trading logic reliably and transparently.

API access and integration

For teams that want to connect McCortex OI to their own tooling, API access lets strategy configuration, position data and account status flow into external systems rather than staying locked inside a single interface. This is useful for a desk that already has its own risk dashboard, its own alerting stack or its own record-keeping process, and would rather pull data out of the platform than change how it works internally. The API is designed to expose the same information a user would see in the workspace itself: current positions, strategy status and configured risk parameters, so that integration does not require reverse-engineering the product.

API access is set up during onboarding alongside the rest of an institutional configuration, and it is scoped to the account requesting it rather than opened broadly by default. Because execution infrastructure runs server-side, API integration is a read and configuration layer on top of that infrastructure rather than a replacement for it, which keeps the underlying risk controls intact regardless of how a team chooses to consume the data. Specific technical limits, request volumes or supported endpoints are addressed directly during setup rather than listed here, since they depend on the configuration a given desk needs.

Reporting and oversight

Position and performance reporting lives in one place inside McCortex OI, and for institutional use the same reporting logic extends across multiple strategies and accounts rather than requiring a separate view for each one. A desk can see what is currently open, how a given strategy has behaved over a chosen period, and where risk limits have been approached or triggered, without stitching together exports from several tools. Alerts on fills and on limit breaches are configurable per strategy, so oversight can be as granular as a team needs, from a single risk officer watching everything to several reviewers each responsible for a subset of strategies.

Reporting is presented as a record of what the platform has done, not as a projection of what it will do next. Any figures shown reflect the account’s own activity, and they are not a substitute for a team’s own reconciliation processes. As with every part of the product, past results shown in reporting do not indicate what a strategy will do going forward, and the platform does not represent any figure as a guaranteed or expected outcome. Oversight here is about visibility into current and historical activity, not a forecast of future performance.

How onboarding works

Onboarding for institutional use follows the same sequence as the standard workspace, adjusted for the scale of the configuration involved. An account is created first, followed by a verification step completed with an account manager, which is where questions specific to a multi-strategy or multi-user setup are addressed directly rather than through a generic form. Once verification is complete, the account is funded and strategies are chosen, with risk limits set individually for each one before anything goes live.

For a desk bringing several strategies and API integration into the workspace at once, this verification step is also where API scope, reporting structure and any account-level permissions are worked out, so that the configuration matches how the team actually intends to operate day to day. There is no separate institutional product to purchase and no additional licensing step: the same workspace scales through configuration rather than through a different tier of software. Trading digital assets carries substantial risk, including the total loss of capital, and nothing in this onboarding process or in the reporting it produces constitutes investment advice. Availability of the platform varies by jurisdiction, and it is the trader’s responsibility to confirm local rules before funding an account.