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.
Last verified against https://api.sentico-labs.xyz on June 22, 2026 from
an external EU client path. These are public-internet integration timings, not
co-located engine benchmarks.
What Is Verified
| Area | Result | Client impact |
|---|---|---|
| Public status | 200, operational | Clients can health-check the venue before connecting. |
| BSL metadata | GET /api/v1/bsl/limits, /executions, /sessions, quote obligations return expected beta contracts | Market makers can discover the live BSL envelope before submitting flow. |
| Protected BSL reads | Private execution replay without auth returns 401 | Private account data is not exposed by metadata routes. |
api_agent creation | Wallet-authorized api_agent with HMAC credential succeeds | Standard trading bots can use normal HTTP/private read flows. |
institutional_agent creation | Wallet-authorized institutional_agent with HMAC credential succeeds | Market makers can self-create the credential family used for BSL/FIX beta access. |
BSL submit with api_agent | Rejected with 403 | Standard bot credentials cannot accidentally enter institutional order-entry. |
BSL submit with institutional_agent | 200, one signed action accepted, derived order id returned | Professional compact order-entry is live on the canonical BSL route. |
| BSL cleanup cancel | 200 in the institutional conformance run | A resting test order can be cleaned up through the same BSL path. |
FIX Logon with institutional_agent | FIX 35=A Logon accepted | Raw TCP/TLS FIX is usable for provisioned institutional sessions. |
FIX Logon with api_agent | Connection rejected/closed | FIX uses the same institutional permission boundary as BSL. |
Latest Observed Timings
These timings are a single live conformance sample over the public internet. They include client network path, Cloudflare/edge path where applicable, auth, proxying, and service response time.
| Flow | Latest sample |
|---|---|
Create api_agent + HMAC | 394 ms |
Create institutional_agent + HMAC | 169 ms |
| HMAC trading read | 108 ms |
| BSL sessions read | 279 ms |
| BSL execution replay metadata/read | 209 ms |
BSL submit rejected for api_agent | 368 ms |
BSL submit accepted for institutional_agent | 219 ms |
| BSL cleanup cancel | 258 ms |
| FIX institutional Logon | 318 ms |
FIX api_agent rejected | 419 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-bsl-batch-response, application/json
X-BSL-Result-Mode: ack
X-MM-Response-Mode: detailed
SC-Auth-Version: 2
SC-Key: <institutional apiKeyId>
SC-Nonce: <monotonic 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,
- 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
| Topic | Current beta stance |
|---|---|
ACK result mode | Default for BSL beta submit. It proves accepted boundary, not terminal order state. |
DURABLE result mode | Use when an account needs a durability boundary in the response. |
FULL result mode | Provisioned account-level conformance required before relying on it for IOC/FOK/cancel/replace terminal truth. |
| Private streams/drop-copy | Must be validated per account before a market maker treats them as primary reconciliation. |
| FIX connectivity | Raw TCP/TLS direct endpoint; not an HTTPS route behind Cloudflare. |
| Production cutover | Requires account policy, rate tier, cancel-on-disconnect, drop-copy, and kill-switch review. |