Skip to main content

Live Verified Beta

This page is the current external-facing verification snapshot for professional integrations. It is written for market makers, liquidity providers, and HFT-style teams that need to know what is live, what was tested, and what still requires account-level conformance before production use.

Verification scope

The credentialed 30-minute BSL HTTP canary below was run on July 7, 2026 and remains historical evidence; it was not silently re-dated. HTTP across all five markets, BSL Direct TCP, FIX 4.4, FIXP/SBE, DNS/TLS, and production-route reachability were credential-tested again on July 25, 2026. Current placement availability must still be read from GET /api/v1/readiness.

API Health
Operational
ledger ok, engine truth lag 0
BSL Submit
Accepted
institutional_agent only
FIX Logon
Accepted
institutional_agent HMAC
Guardrail
api_agent rejected
BSL/FIX permission boundary enforced

In-datacentre measurements — 2026-09-21​

Measured from a host in the venue's own facility, so the network term is close to zero and what remains is the venue plus the wire. Clock offset between the two machines was 0.6 ms, taken from NTP on both and applied to every absolute figure.

Measurementp50p99
TCP connection establishment, FIX 4.40.44 ms0.60 ms
TCP connection establishment, FIXP/SBE0.47 ms0.69 ms
TCP connection establishment, BSL Direct TCP0.48 ms0.73 ms
TCP connection establishment, direct market data0.51 ms2.52 ms
TCP connection establishment, CDN-fronted api.21.67 ms34.44 ms
Market-data frame delivery, direct route1.80 ms4.56 ms
Market-data frame delivery, via CDN8.55 ms14.99 ms

| FIX 4.4 NewOrderSingle → ExecutionReport (PendingNew), 50 rounds | 6.22 ms | 183.78 ms | | FIX 4.4 OrderCancelRequest → ExecutionReport, 50 rounds | 47.97 ms | 126.74 ms |

The FIX rows were measured with resting orders far below the market that could not trade, one open at a time, while the venue's own market-making fleet was quoting on the same market. Method, clock discipline and the limits of the market-data figures are in the Colocation Latency Benchmark, which also explains why the frame timestamp does not measure the path from a trade occurring to a client seeing it.

External market-maker measurements — 2026-09-13​

An external market maker measured every order-entry lane on production from a client in Vienna with a 29.5 ms network round trip to the venue. These are one client's single-order measurements on one day, not capacity claims or an SLA.

LaneClient round tripConfirmation
FIX 4.4 order → ExecutionReport29.9 msIn the ack
FIX 4.4 cancel → ExecutionReport29.7 msIn the ack
FIXP/SBE order → ack35–40 msExecutionReport New 10–22 ms and Canceled 90–130 ms after send; mass-status median 38 ms
BSL Direct TCP (Ed25519 session key, AuthSidecarV2)CoreAck p50 30–38 msApplied; wallet-signed AuthSidecarV1 frames are still 202 accepted-not-applied
BSL HTTPS /api/v1/bsl/orders/compactp50 ~74 msIngress-WAL ack with seqs[]

The same client verified session-key registration, the Dead Man Switch (order cancelled within the timeout after heartbeats stopped) and private WebSocket resume. Two things a client must still design around: an accepted BSL response can arrive without order ids (derive child ids locally from the signed payload), and a batch with one inadmissible leg is dropped whole.

What Is Verified​

Production lane canaries — July 25, 2026​

These are credentialed production tests with funded internal-beta accounts. FIX and FIXP order timings are single-order conformance samples (n=1), not percentiles or capacity claims.

LaneScopeResult
HTTP signed actionsBinary market 1 and spot markets 2–5; depth, matches, Post-only, IOC, FOK, Reduce-only, Split/Merge, PnL, algo orders, and cleanupPassed
BSL Direct TCP10/10 matched trades, alternate maker/taker roles0 rejects; maker ACK p50 42.627 ms / p99 55.875 ms; taker ACK p50 42.461 ms / p99 47.639 ms; trade visibility p99 63.624 ms
BSL compact HMAC, spotCKT/USDC SpotQuoteReplace; stale machine nonce recovered from the server-provided floor and re-signedHTTP 200; 1/1 accepted; local and server-derived order id matched
BSL restart recoveryIdle-core-restart Unix regression suite 8/8; gateway v165 deployed; then 4/4 matched BSL/TCP trades0 rejects; cleanup passed; gateway healthy with zero restarts
FIX 4.4 binaryMarket 1, D/H/G/F/q/AFPassed; New 294 ms, Status 36 ms, Replace 338 ms, Cancel 449 ms
FIX 4.4 spotMarket 4 CKT/USDC, D/H/G/F/q/AFPassed; New 268 ms, Status 66 ms, Replace 374 ms, Cancel 581 ms
FIXP/SBE8/8 golden vectors, Negotiate/Establish, binary market 1 and spot market 5Passed; market 1 New/Cancel 288/441 ms; market 5 New/Cancel 400/656 ms

These canaries prove the tested account and lifecycle. Every unattended market maker still needs account-policy, rate-limit, COD, drop-copy, and recovery conformance for its own credential set.

60-minute multi-lane production soak — July 25, 2026​

Three funded internal-beta wallets rotated through maker, counterparty, and taker roles. Every market sweep exercised the binary market plus all four spot markets and ended with no open orders or locked balances for either participant.

MetricResult
Runtime60.332 minutes
Full market sweeps36
Signed action submissions5,904, including intentional boundary rejects
Algo / BSL Direct TCP / FIX / FIXP canaries6 / 6 / 6 / 6
Child runs63 passed, 0 failed
Readiness gates36 / 36 passed
Durable batch progress during sampled gates71,780 → 75,981
Maximum checkpoint-persist / engine-truth lag0 / 0 batches
Transient recoveries0
Maximum signed-submit total / read-model visibility1,429 / 1,493 ms
BSL Direct TCP48 submissions, 24 matched cycles, 0 rejects; client RTT p50 43.997 ms / p95 78.720 ms / p99 167.967 ms
Final cleanupAC, AB, and BC all passed

The BSL RTT values in this soak are from the public client path and are not co-location or engine-only latency claims. During the same production review, checkpoint 644 finalized with four accepted validator results, zero failed, and a required quorum of three.

Historical 30-minute BSL HTTP canary — July 7, 2026​

The latest funded market-maker canary used the BSL HTTP order-entry path with private receipt/execution reconciliation. It did not use BSL Direct TCP.

MetricResult
Runtime30 minutes
Cycles90 / 90 successful
New trades90
Applied receipts180
Non-applied receipts0
Maker submit p50150.5 ms
Taker submit p50126.4 ms

Three maker submits retried after stale local nonce-window state from older account activity; the server returned the nonce floor and the client recovered. For unattended market making, clients should periodically refresh nonceFloor from bootstrap or snap to the server-provided floor on any nonce reject.

Direct TCP is live-tested, but remains account-level conformance work after the BSL HTTP quote, reconciliation, and nonce-recovery path are green.

AreaResultClient impact
Public status200, operationalClients can health-check the venue before connecting.
BSL metadataGET /api/v1/bsl/limits, /executions, /sessions, quote obligations return expected beta contractsMarket makers can discover the live BSL envelope before submitting flow.
Protected BSL readsPrivate execution replay without auth returns 401Private account data is not exposed by metadata routes.
api_agent creationWallet-authorized api_agent with HMAC credential succeedsStandard trading bots can use normal HTTP/private read flows.
institutional_agent creationWallet-authorized institutional_agent with HMAC credential succeedsMarket makers can self-create the credential family used for BSL/FIX beta access.
BSL submit with api_agentRejected with 403Standard bot credentials cannot accidentally enter institutional order-entry.
BSL submit with institutional_agent200, one signed action accepted, derived order id returnedProfessional compact order-entry is live on the canonical BSL route.
BSL cleanup cancel200 in the institutional conformance runA resting test order can be cleaned up through the same BSL path.
FIX Logon with institutional_agentFIX 35=A Logon acceptedRaw TCP/TLS FIX is usable for provisioned institutional sessions.
FIX Logon with api_agentConnection rejected/closedFIX uses the same institutional permission boundary as BSL.

Historical HTTP integration timings​

These timings are public-internet samples. They include client network path, Cloudflare/edge path where applicable, auth, proxying, and service response time. For the current long-canary order-entry numbers, use the table above.

FlowLatest sample
Create api_agent + HMAC394 ms
Create institutional_agent + HMAC169 ms
HMAC trading read108 ms
BSL sessions read279 ms
BSL execution replay metadata/read209 ms
BSL submit rejected for api_agent368 ms
BSL submit accepted for institutional_agent219 ms
BSL cleanup cancel258 ms
FIX institutional Logon318 ms
FIX api_agent rejected419 ms

For latency benchmarking, separate these integration timings from engine-local hotpath measurements. The important client-facing fact here is determinism: the correct credential gets a clear result, the wrong credential gets a fast reject, and the response contract is stable enough to automate.

Contract To Use​

For professional beta order-entry, use the BSL compact route:

POST /api/v1/bsl/orders/compact
Content-Type: application/x-senticore-order-entry-batch
Accept: application/x-senticore-order-entry-batch-response, application/json
X-BSL-Result-Mode: ack
X-Senticore-Response-Mode: detailed
SC-Auth-Version: 2
SC-Key: <institutional apiKeyId>
SC-Nonce: <fresh tuple nonce>
SC-Timestamp: <unix ms>
SC-Passphrase: <apiPassphrase>
SC-Signature: <hmac over method/path/query/body>

The submitted action inside the compact batch must still be signed by the account or an authorized signer. The HMAC credential authorizes the machine session and business-line route; it does not replace per-action authorization.

Reproduce The Public Audit​

From the repository root:

node scripts/e2e/mm-docs-contract-audit.cjs

The audit writes tmp/mm-docs-contract-audit-last.json and checks:

  • platform status and BSL metadata,
  • protected private-read rejection without auth,
  • signed compact order submit on the canonical BSL route using the documented compact signed action envelope (SpotPlaceOrder for spot markets, PlaceOrder for prediction markets),
  • ACK-mode reconciliation against the open-order read model,
  • nonce resync on a one-time stale nonce race.

The audit gate requires 200 on signed BSL submit and, when the test order rests, 200 on cleanup cancel. The generated JSON report stores the exact timings for the run.

The institutional conformance run used for onboarding additionally creates a temporary institutional_agent, submits over BSL with HMAC, cleans up over BSL, and validates FIX Logon over raw TCP/TLS.

Boundaries​

TopicCurrent beta stance
ACK result modeDefault for BSL beta submit. It proves accepted boundary, not terminal order state.
DURABLE result modeUse when an account needs a durability boundary in the response.
FULL result modeProvisioned account-level conformance required before relying on it for IOC/FOK/cancel/replace terminal truth.
Private streams/drop-copyMust be validated per account before a market maker treats them as primary reconciliation.
FIX connectivityRaw TCP/TLS direct endpoint; not an HTTPS route behind Cloudflare.
Production cutoverRequires account policy, rate tier, cancel-on-disconnect, drop-copy, and kill-switch review.

Next​