Quantisentry

Quantisentry

See the fleet. Don’t touch the trade.

Telemetry from your MT5 experts lands in Sentinel Cloud, gets validated against a strict contract, and is served back read-only. Every route that could change trading state answers 403.

Read the contract API status
Quantisentry telemetry pipeline An MT5 expert advisor posts telemetry over TLS with a header key. A validator checks six required rules, then the latest value per expert is stored and served through read-only GET routes. A separate branch shows operational and trading routes stopped by a fail-closed wall that returns HTTP 403. MT5 expert SentinelTelemetryV1 TLS + header key POST /api/ea-telemetry/v1 X-Sentinel-Telemetry-Key Contract validator 29 fields · 5 families multiplier 0–5 · lots 4 dp Latest per expert ea_telemetry_latest.json GET /latest · /summary read paths are never blocked POST /api/tactical/apply overrides · config · apply 403 COMMERCIAL_OBSERVATION_ONLY 48 mutating routes stopped here app refuses to boot without it
ingest → validate → store → read · everything else stops at the wall

The system, in numbers

Nothing here is a placeholder.

Each figure below is a constant in the running product, not a marketing rounding.

29

telemetry fields accepted per payload

31 stored, incl. server-side identityKey

48

mutating routes blocked in observation mode

overrides, apply, config, registry repair

5 min

freshness window before an expert reads stale

measured server-side from last ingest

0

routes that can place, size, or close a trade

observation-only enforced at startup

Fail-closed

It doesn’t decline to trade. It can’t.

Observation is not a setting an operator can flip in production. If the platform is configured with observation mode off, startup validation throws and the process does not come up. There is no running state in which Quantisentry holds trading authority.

  • ObservationOnly = true
  • startup validation
  • no apply path
POST /api/tactical/apply 403 Forbidden 
{
  "ok": false,
  "code": "COMMERCIAL_OBSERVATION_ONLY",
  "mode": "observation",
  "applied": false,
  "message": "Sentinel Cloud V1 does not execute
              operational or trading actions."
}

What you actually get

Three things, done properly.

  • A strict wire contract

    Six hard-required fields, five permitted strategy families, a bounded risk multiplier and lot rounding to four decimals. Malformed telemetry is rejected at the door with a reason, not silently absorbed. See the contract →

  • Obedience evidence

    The lot audit compares the size Sentinel expected against the size your broker actually filled, within a 5% tolerance. You get OK, MISMATCH or MISSING_DATA — proof, not assumption.

  • Advisory intelligence, boxed in

    Health scoring is a transparent 100-point deduction model where every penalty carries a written reason. Advisory output is contractually stripped of anything actionable. How that works →

What we don’t claim. There is no rate limiting in the product today, no telemetry history — the store keeps the latest value per expert and overwrites the rest — and no trained model shipped inside Quantisentry.

On the roadmap, not in the box. Payload signing exists as a schema (payloadHash, signature) but nothing signs or verifies it yet. Today’s transport is TLS with header-key authentication, and we describe it that way.

Why say so. Operators running live capital check claims. A site that survives the check is worth more than one that doesn’t.

Next step

Ready when your fleet is.

Read the telemetry contract, then request access. There is no self-serve deploy from this site.

Request access View pricing