Murex
Murex is a global fintech leader in trading, treasury, risk management and post-trade operations software. Their MX.3 platform provides comprehensive solutions for capital markets across asset classes.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Murex the way a machine reads it — 63 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Murex scores 30.3/100 (thin), with a separate agent-readiness read of 22/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Murex's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/murex/"
title="Murex on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/murex.svg"
alt="Murex Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/murex/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/murex/"
title="Murex on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/murex/card.svg"
alt="Murex Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Murex
Each block below is one kind of artifact we hold for Murex. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 24
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Murex MX.3 Platform
Comprehensive capital markets platform providing trading, risk management, and post-trade operations across all asset classes.
Murex Accounting API
Accounting entries and journal operations
Murex Cash Flows API
Cash flow projections and management
Murex Collateral API
Collateral management and margin operations
Murex Confirmations API
Trade confirmation generation and matching
Murex Curves API
Yield curves and forward curves
Murex FX Rates API
Foreign exchange rates and crosses
Murex Instruments API
Financial instrument reference data
Murex Limits API
Risk limit monitoring and management
Murex Orders API
Order creation, modification, and lifecycle management
Murex P&L API
Profit and loss calculations and reporting
Murex Portfolios API
Trading portfolio and book management
Murex Positions API
Portfolio position retrieval and management
Murex Quotes API
Real-time and historical price quotes
Murex Reconciliations API
Position and cash reconciliation operations
Murex Reference Data API
Market reference and static data
Murex Regulatory API
Regulatory capital and compliance metrics
Murex Regulatory Reporting API
Regulatory trade and transaction reporting
Murex Sensitivities API
Greek and sensitivity calculations
Murex Settlements API
Settlement instruction management and processing
Murex Stress Testing API
Stress testing and scenario analysis
Murex Trades API
Trade execution and trade blotter operations
Murex VaR API
Value at Risk calculations and reports
Murex Volatility API
Volatility surfaces and skew data
Scroll within the panel for all 24 ·
Open Collections 29
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONMurex MX.3 Market Data Accounting API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Cash Flows API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Collateral API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Confirmations API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Curves API
OPEN COLLECTIONMurex MX.3 Market Data Accounting FX Rates API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Instruments API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Limits API
OPEN COLLECTIONMurex MX.3 Market Data API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Orders API
OPEN COLLECTIONMurex MX.3 Market Data Accounting P&L API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Portfolios API
OPEN COLLECTIONMurex MX.3 Position API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Positions API
OPEN COLLECTIONMurex MX.3 Post-Trade API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Quotes API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Reconciliations API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Reference Data API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Regulatory API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Regulatory Reporting API
OPEN COLLECTIONMurex MX.3 Risk API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Sensitivities API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Settlements API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Stress Testing API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Trades API
OPEN COLLECTIONMurex MX.3 Trading API
OPEN COLLECTIONMurex MX.3 Market Data Accounting VaR API
OPEN COLLECTIONMurex MX.3 Market Data Accounting Volatility API
OPEN COLLECTIONScroll within the panel for all 29 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Murex Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Murex Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Murex Finops
FINOPSSemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Murex Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Murex API Rules
SPECTRALJSON Schema 2
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Murex Position
JSON SCHEMAMurex Trade
JSON SCHEMASecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Murex — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/murex · machine-readable index on apis.io
This is an independent, third-party profile of Murex, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.