MEXC
MEXC is a global cryptocurrency exchange providing REST and WebSocket APIs for spot trading, perpetual futures, market data, order management, account management, and wallet operations across 1,200+ trading pairs. MEXC supports institutional users through a Broker API with sub-account management and a Market Maker Program with tiered rate limits and competitive fee schedules.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles MEXC the way a machine reads it — 37 machine-readable artifacts across 12 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 — MEXC scores 53.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile MEXC
Each block below is one kind of artifact we hold for MEXC. 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 12
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.
MEXC Spot WebSocket Streams
The MEXC Spot WebSocket Streams deliver real-time market data and user account updates via persistent WebSocket connections. Public channels provide ticker data, order book dept...
MEXC Futures WebSocket API
The MEXC Futures WebSocket API streams real-time derivatives market data and account events over persistent WebSocket connections. Public channels include ticker data, trade tra...
MEXC Broker API
The MEXC Broker API enables institutional partners to manage sub-accounts and provide trading services to their users. MEXC supports three broker modes: API Broker for copy-trad...
MEXC Accounts and Transactions API
The Accounts and Transactions API from MEXC — 59 operation(s) for accounts and transactions.
MEXC EFT API
The EFT API from MEXC — 1 operation(s) for eft.
MEXC Margin API
The Margin API from MEXC — 14 operation(s) for margin.
MEXC Market Date Endpoints API
The Market Date Endpoints API from MEXC — 13 operation(s) for market date endpoints.
MEXC Parent child account API
The Parent child account API from MEXC — 6 operation(s) for parent child account.
MEXC Quote API
The Quote API from MEXC — 12 operation(s) for quote.
MEXC Rebate API
The Rebate API from MEXC — 4 operation(s) for rebate.
MEXC Spot Account/Trade API
The Spot Account/Trade API from MEXC — 8 operation(s) for spot account/trade.
MEXC Wallet API
The Wallet API from MEXC — 10 operation(s) for wallet.
Scroll within the panel for all 12 ·
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 six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Mexc 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.
Mexc 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.
Mexc Finops
FINOPSFeatures 8
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Spot Trading
Buy and sell 1,200+ cryptocurrency pairs with limit, market, and stop-loss orders.
Futures Trading
Trade perpetual futures contracts with leverage via REST and WebSocket APIs.
Market Data
Real-time and historical price tickers, order book depth, klines, and funding rates.
WebSocket Streams
Low-latency real-time market data and account event streams.
Wallet Management
Manage deposits, withdrawals, deposit addresses, and currency information.
Sub-Account Management
Create and manage up to 30 sub-accounts per master account with independent API keys.
Broker Program
API Broker, Independent Broker, and OAuth Broker modes for institutional partners.
Market Maker Program
Tiered market maker program with enhanced API rate limits and competitive fee rebates.
Scroll within the panel for all 8 ·
Spectral 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.
MEXC 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.
MEXC Order
JSON SCHEMAMEXC Ticker
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Mexc Get Ticker Example
EXAMPLEMexc Place Order Example
EXAMPLESecurity 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.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Algorithmic Trading
Build automated trading bots using MEXC REST and WebSocket APIs for spot and futures.
Market Data Aggregation
Aggregate real-time prices, order books, and trade feeds across 1,200+ pairs.
Portfolio Management
Track and rebalance cryptocurrency portfolios across spot and futures accounts.
Arbitrage Trading
Exploit price differences across MEXC spot and futures markets programmatically.
Broker Integration
Build copy-trading platforms, trading bots, and wallet apps using the Broker API.
Resources
Every other property we hold for MEXC — 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.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 1
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/mexc · machine-readable index on apis.io