Imperative Execution
Imperative Execution is a New York financial technology company and the parent of IntelligentCross, an SEC-registered US equities Alternative Trading System (ATS) that applies machine learning to order matching and price discovery. IntelligentCross operates a non-displayed Midpoint book and ASPEN, a full limit order book with optional displayed capability that is split into three independent books by fee model (Fee/Fee, Maker/Taker, Taker/Maker), all under MPID INCR, with primary matching engines in the Equinix NY4 data center in Secaucus, New Jersey. Registered broker-dealer subscribers reach the venue for order entry over FIX 4.2 across Pico cross-connects, and the venue publishes its own IQX market data feed - a binary, multicast-UDP full depth-of-book and execution feed whose message specification, recovery/rerequest specification, daily symbol mapping file and sample PCAP captures are all published openly.
Imperative Execution publishes 1 API on the APIs.io network: IntelligentCross IQX Market Data Feed. Tagged areas include Company, Financial Services, Capital Markets, Trading, and Market Data.
The Imperative Execution catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Imperative Execution’s developer surface includes documentation, API reference, support, engineering blog, code examples, sandbox, changelog, and 14 more developer resources.
Kin Score
APIs 2
Individual APIs this provider publishes, each with its own machine-readable definition.
IntelligentCross IQX Market Data Feed
IQX is the IntelligentCross proprietary market data feed. It disseminates all visible ASPEN resting orders, cancels for ASPEN visible orders, and all ASPEN executions, plus per-...
IntelligentCross FIX Order Entry API
Order entry into the IntelligentCross ATS books (Midpoint, ASPEN Fee/Fee, ASPEN Maker/Taker, ASPEN Taker/Maker) is accepted only over FIX connections; the ATS currently supports...
Event Specifications 1
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Imperative Execution Authentication
none-public/network-access-control/contractual-eligibility · 4 schemes
SECURITYResources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type