Pre-broker decision diagnostics for automated trading · Public beta

Gate every signal. Explain every verdict. Trace every decision.

Send Titan a proposed order before it reaches your broker. Titan evaluates configured checks, returns an allow or block verdict with a reason and trace ID, and records the decision path. Your forwarder remains in control of execution.

Try a simulated signal View the 5-minute quickstart

Verify a decision receipt

No generated signals No broker credentials No order submission

02 · See it work

Try an ALLOW / BLOCK decision.

Enter a proposed order and run the same ordered gate names used by Titan's pre-trade pipeline. The demo stops at the first failed check and prints a simulated reason and trace. It runs only in this browser: nothing is sent, stored, forwarded, or submitted.

TITAN DIAGNOSTICS · PRE-TRADE SLIPSIMULATED

Awaiting signal

Fill in the order and run the check.

Client-side demo · nothing submitted, nothing stored.

cleared stopped here not reached or not applicable

03 · How it fits

One decision boundary before your broker.

Titan sits between proposed order intent and a user-controlled forwarder. Its evaluation is one stage in a longer lifecycle; an ALLOW verdict is not evidence that any later broker-side stage occurred.

01 · IntentYour strategy creates a proposed order.

02 · EvaluationTitan returns ALLOW or BLOCK, a reason, and a trace ID. A receipt accompanies the verdict.

03 · ForwardingYour forwarder remains in control of whether an allowed intent moves on.

04 · Broker acceptanceThe broker independently accepts or rejects the submitted order.

05 · ExecutionExecution is a broker-side event, not a Titan verdict.

06 · FillA fill is separate evidence with price, quantity, and time.

07 · OutcomeP&L and strategy quality are later results, outside the receipt claim.

request / full evaluation

curl -X POST https://www.titandiagnostics.io/api/public/v1/eval?eval_mode=full \
  -H "X-Titan-Agent-Key: tak_..." \
  -H "Content-Type: application/json" \
  -d '{
    "symbol": "NVDA",
    "side": "BUY",
    "close": 495.00,
    "atr": 6.10,
    "stop": 496.50,
    "target": 502.00
  }'

response / BLOCK

{
  "ok": true,
  "allow": false,
  "reason_label": "Bracket validity: stop must be below entry",
  "trace_id": "..."
}

Full headers, schemas, and receipt retrieval: view the 5-minute quickstart.

04 · What the evidence proves

Authenticate the record. Keep the claim bounded.

A decision receipt accompanies an ALLOW or BLOCK verdict. Signature and anchor evidence can authenticate specific recorded bytes and their commitment path; neither turns the receipt into proof that the input was right or that a broker-side event happened.

Titan signature

A Titan signature authenticates the versioned payload Titan signed and its declared signing domain. It does not establish that supplied inputs are truthful, correct, or complete.

Anchor commitment

An anchor can establish that a commitment existed by a time and remained unchanged relative to the verified path. It does not establish broker acceptance, execution, fill, outcome, or profitability.

Fig. 1 — anchored sandbox exampledecision receipt

intentBUY NVDA · fourth buy proposal of the day · 2026-06-10

evaluationPASS input and side checks · BLOCK Max Daily Trades · forwarding not reached

verdictBLOCK — daily cap of 3 already used

reasonDaily trade limit reached before broker submission

trace5699daa4-7e1b-49dd-a3e6-b29f8f230dae

proof boundaryThe displayed path matches Titan's committed record for this example. It does not establish input truth, broker acceptance, execution, fill, outcome, or profitability.

anchorCommitment confirmed in Bitcoin block 953175.

Verify a decision receipt → Detailed decision rows follow retention policy; retained commitments are not complete copies of those rows.

05 · Start using it

Free during public beta

Run full evaluations, inspect decision receipts, and review trace history while beta access is open.

Try a simulated signal

Already have trade history? Open the CSV diagnostic.