TMoM
INTEGRATION

One policy service. Three ways to call it.

Algorithmic trading systems can use the Python Client or REST API. MCP-compatible trading agents can use the Hosted MCP endpoint. Every hosted interface reaches the same TMOM policy engine.

Quintus is the development environment. Fabius is the production control service. Maximus expands the same service into shared multi-agent governance. Customers may connect through MCP, Python or REST without changing the underlying policy engine or pricing model.

The interface does not determine the plan. Server-side entitlements determine available strategies, agents, hosted checks, retention, replay and shared-risk capabilities.

1. LOCAL DEVELOPMENT

Author strategy contracts, validate schemas, detect rule conflicts and test integration behavior before connecting to the hosted production service.

  • Best for: Contract development · Unit testing · Paper trading · Integration testing · Local MCP development · Mock decision handling
QUINTUS

The Quintus toolkit does not contain TMOM’s production policy engine.

2. PYTHON APPLICATIONS

Use the official Python Client to call TMOM’s hosted policy service from algorithmic trading systems, quant infrastructure and Python execution services.

  • Best for: Python algorithmic-trading systems · Quant research platforms moving into production · Python execution services · Programmatic strategy infrastructure
FABIUS + MAXIMUS

The Python Client is a thin wrapper around TMOM’s hosted API. It does not contain the production policy engine.

3. MCP-COMPATIBLE AGENTS

Expose TMOM policy tools directly to MCP-compatible trading agents without embedding policy logic inside the agent.

  • Best for: AI trading agents · Agent frameworks with MCP support · Tool-calling execution agents · Multi-agent orchestration systems
FABIUS + MAXIMUS

The hosted MCP endpoint is an agent-native interface to the same hosted service used by the REST API and Python Client.

4. ANY LANGUAGE OR SERVICE

Call TMOM from JavaScript, Go, Java, Rust or any backend capable of making authenticated HTTPS requests.

  • Best for: Non-Python execution systems · Trading platforms · Backend services · Custom infrastructure · Language-independent integrations
FABIUS + MAXIMUS

The REST API is the core hosted service boundary. The Python Client and Hosted MCP endpoint provide different developer interfaces to the same backend.

ALGORITHMIC TRADING SYSTEM │ └── PYTHON CLIENT ───────────────┐ │ MCP-COMPATIBLE TRADING AGENT │ │ │ └── HOSTED MCP ──────────────────┼── TMOM HOSTED POLICY SERVICE │ │ OTHER APPLICATION OR BACKEND │ ├── POLICY ENGINE │ │ ├── VERSIONED STRATEGIES └── REST API ────────────────────┘ ├── SHARED STATE └── DECISION LEDGER │ ALLOW · WARN · JUSTIFY · THROTTLE · BLOCK │ CUSTOMER EXECUTION CLIENT │ CUSTOMER BROKER
QUINTUS DEVELOPMENT TOOLKIT │ ├── CONTRACT AUTHORING ├── VALIDATION ├── STATIC LINTING ├── MOCK RESPONSES └── PAPER-TRADING TESTS