Search brief

Broker rejections are easier to fix before they reach the broker.

Titan helps signal operators separate rejected intent, pre-trade gate blocks, and broker-side execution problems by making the decision path inspectable.

How it works

01

Signal

Your bot, alert, or REST client creates order intent.

02

Evaluate

Titan checks the signal against configured pre-trade gates before broker submission.

03

Return

Titan returns allow or block output with a reason, trace id, and decision trail.

04

Execute

Your own execution path decides what to do next. Hosted Titan does not place orders.

Gate-level reasons

Instead of a vague failed order, Titan returns a structured reason such as symbol allowlist, market hours, bracket validity, exposure, cooldown, or sizing.

Forwarder-owned execution

Your forwarder still owns broker submission. Titan gives the forwarder an upstream allow or block answer and a traceable reason.

Receipts for review

Decision receipts make repeated rejection patterns visible so operators can tune rules, adjust bot behavior, or inspect broker compatibility assumptions.

Execution boundary

Hosted Titan evaluates and records proposed order intent. It does not generate signals, hold funds, require broker credentials for public evals, or independently place broker orders.