Integration Overview
Senticore exposes six logical integration surfaces, each optimized for a different user profile.
API surfaces
| Surface | Best for | Latency | Protocol |
|---|---|---|---|
| Public Market Data HTTP | Apps, dashboards, data consumers | Standard | JSON over HTTPS |
| Trading HTTP | Retail traders and application backends | Standard | JSON over HTTPS |
| Public WebSocket | Real-time market data | Low | JSON over WSS |
| Private WebSocket | Account, order, fill, and risk streams | Low | Authenticated JSON over WSS |
| FIX Gateway | Quant funds, institutional desks, OMS integrations | Low | FIX 4.4 / 5.0 SP2 over TLS |
| Market Maker API | Liquidity providers and quote engines | Lowest available tier | HTTP, WebSocket, and binary paths |
All surfaces commit to the same canonical sequencer, the same matching engine, the same risk checks, and the same settlement guarantees. Choose by latency, operational model, and tooling fit.
Quick decision guide
| If you are building... | Start with |
|---|---|
| A web or mobile application | Public/Trading HTTP + WebSocket |
| A Python, Java, or C++ trading system | HTTP + WebSocket, or FIX |
| An existing OMS or institutional trading system | FIX |
| A latency-sensitive market-making strategy | Market Maker API with binary submission and private streams |
| Off-the-shelf trading infrastructure | FIX |
Common concepts
Every surface shares:
- EIP-712 signed actions for wallet or delegated credential authorization,
- canonical action hashes for deterministic encoding across clients,
- idempotency through client order identifiers,
- rate limit envelopes per surface and tier,
- stable error codes with retryable and non-retryable classification.