Imperative Execution Authentication

generated: '2026-08-04'
method: searched
source: https://www.imperativex.com/faq
docs: https://www.imperativex.com/faq
summary:
  types: [none-public, network-access-control, contractual-eligibility]
  api_key_in: []
  oauth2_flows: []
  note: 'IntelligentCross publishes no public credential-based authentication scheme -
    there is no API key, OAuth or OIDC surface, because neither of its interfaces is an
    HTTP API. Access is controlled contractually (registered US broker-dealer subscribers
    only) and at the network layer (private cross-connects into Equinix NY4). Identity on
    the wire is carried by FIX session and order-level identifiers rather than a bearer
    credential.'
schemes:
- name: subscriber-eligibility
  type: contractual
  applies_to: IntelligentCross FIX Order Entry API
  description: IntelligentCross only permits registered US broker-dealers to be subscribers.
    A subscriber must be in good standing with a self-regulatory organization and satisfy
    additional eligibility requirements before connectivity is provisioned.
  onboarding_contact: ops@intelligentcross.com
  source: https://www.imperativex.com/faq
- name: network-access-control
  type: network
  applies_to: [IntelligentCross FIX Order Entry API, IntelligentCross IQX Market Data Feed]
  description: Subscribers connect to the ATS from a specified internet protocol address
    over FIX, reaching primary matching engines in the Equinix NY4 data center via NY4
    cross-connects or a network service provider with an NY4 presence. Pico is the venue's
    co-location and network provider. There is no public internet endpoint for either
    surface.
  source: https://www.imperativex.com/faq
- name: fix-session-and-order-identity
  type: protocol
  applies_to: IntelligentCross FIX Order Entry API
  protocol: FIX 4.2
  description: Order-entry identity is asserted on each message through the FIX fields the
    ATS requires - notably ClientID and the subscriber's Broker MPID, which are also the
    keys the venue's anti-internalization (self-match prevention) control is enforced by.
    Book selection is asserted with ExDestination (tag 100). The full FIX specification is
    released to subscribers on request and is not public.
  spec_availability: subscriber-only, on request from ops@intelligentcross.com
  source: https://www.imperativex.com/faq
- name: multicast-subscription
  type: none
  applies_to: IntelligentCross IQX Market Data Feed
  description: The IQX feed is disseminated over multicast UDP inside the venue's connectivity
    footprint and carries no per-consumer authentication. Reachability is the access control.
    IntelligentCross does not charge for market data through IQX. The specification, the
    daily symbol mapping file and sample PCAP captures are published openly over HTTPS with
    no credential.
  source: http://iqx.imperativex.com/IntelligentCrossMarketDataFeedSpec.v.1.11.pdf
public_unauthenticated_resources:
- url: https://s3.amazonaws.com/iqx.imperativex.com/Symbol-Mapping.txt
  http_status: 200
- url: https://s3.amazonaws.com/iqx.imperativex.com/20230103-IQX-mdA.pcap.gz
  http_status: 200
- url: http://iqx.imperativex.com/IntelligentCrossMarketDataFeedSpec.v.1.11.pdf
  http_status: 200
not_present:
  oauth2: true
  openid_connect: true
  api_keys: true
  mutual_tls_documented: true
  note: Probed for /.well-known/openid-configuration and /.well-known/oauth-authorization-server
    on imperativex.com and www.imperativex.com - both 404. See well-known/imperative-execution-well-known.yml.
x-evidence:
- fetched: '2026-08-04'
  url: https://www.imperativex.com/faq
  http_status: 200
- fetched: '2026-08-04'
  url: http://iqx.imperativex.com/IntelligentCrossMarketDataFeedSpec.v.1.11.pdf
  http_status: 200