HYPERIONX DEVELOPER CENTER

Build trading tools in C#

Create indicators, automated strategies, custom bar builders, research modules, and platform add-ons in the same desktop environment where you chart, test, and trade.

Build your first strategyBuild your first indicator

Release-safe path: HyperionX 1.1.10 HyperionX.Custom · Release-candidate surfaces are labeled Preview · API status

Choose what you want to build

CHART ANALYSIS · CURRENTIndicatorsCalculate values, expose parameters, plot series, color bars, and render custom overlays.AUTOMATION · CURRENTStrategiesBuild a managed strategy with entries, stops, targets, exits, order callbacks, and simulation checks.MARKET DATA · PREVIEWCustom bar typesTransform base bars or trade ticks into reusable chart and research series.PLATFORM · CURRENTAdd-onsRun extension logic when the custom assembly loads and release it cleanly on unload.RESEARCH · PREVIEWOptimizers and fitnessControl parameter search and define how HyperionX ranks strategy results.COST AND SIZE · PREVIEWMoney management and commissionsModel quantity, starting capital, fees, and trading costs independently from signal logic.

Preview contracts are runtime-enabled but can still change. Review API status and compatibility before distributing an extension.

Pick the right developer surface

Surface	Use it for	Runs where	Start here
Code Lab	In-process indicators, strategies, bar types, research modules, and add-ons	HyperionX desktop custom assembly	Code Lab overview
Local desktop API	Reading context and invoking permissioned desktop actions from external tools	Local HTTP boundary	Platform APIs
Agent Builder	Creating governed AI agents with selected tools, prompts, and workspace access	HyperionX agent runtime	Agent Builder

These surfaces solve different problems. A Code Lab script is loaded into the desktop process; an external integration should use a documented API boundary instead of reaching into desktop internals.

The shortest path to a working extension

1. Open Tools → Code Lab.
2. Choose an extension type and a built-in template.
3. Save and select Build. Code Lab compiles every custom C# source file into one HyperionX.Custom.dll.
4. Complete desktop runtime activation with Compile Project, the intended selector, or a restart.
5. Create a fresh instance and verify it in a chart or the relevant research window before simulation, playback, or live routing.

Start with Build your first strategy for trading automation or Build your first indicator for chart analysis. Then use Build, test, and debug when you are ready to work across multiple files.

Trading code can place real orders

Strategy examples are development patterns, not trading advice. Validate with historical data, then playback or simulation using an explicitly selected LocalPaper account. Playback does not select that account automatically; the current release-candidate build rejects external-account mutations while Playback is active. Review account, quantity, stop, target, and provider behavior before enabling live execution.

Reference map

• API status and compatibility — current, preview, internal, unreleased, and roadmap boundaries.
• Extension type catalog — all eight Code Lab categories, namespaces, base types, and discovery.
• Build your first strategy — complete source, managed entries, stops, targets, compilation, chart loading, and an AI prompt.
• Script lifecycle and calculation — initialization, update callbacks, multi-series scheduling, and cleanup.
• Parameters and generated helpers — editable properties, helper signatures, and cache identity.
• HyperionXScript context — chart, market data, drawing, orders, account, position, logging, and runtime facades.
• Indicator patterns and strategy patterns — production-oriented implementation guidance.
• Common ScriptBase reference — inherited series, chart, and logging members.
• Strategy and order reference — managed orders, direct submission, and order callbacks.
• Drawing API and chart rendering — plots, drawings, and custom render passes.
• Examples library — small patterns to adapt after completing the quick start.
• Script troubleshooting — compile, runtime, multi-series, drawing, and order problems.
• Share and deploy extensions — source bundles, installation, updates, removal, and current packaging limits.