MEXC Spot API

Name: MEXC Spot API
Brand: MEXC Spot API
Availability: InStock

✓ Official Vendor SpecFinanceBankingapiKey32 EndpointsREST

For Agents

Read live MEXC market data, place and cancel spot orders, query balances and trade history, and move funds between accounts on the MEXC exchange.

Install Jentic One Beta

Connect the MEXC Spot API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MEXC Spot API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MEXC Spot API.

Read live market data including order book depth, recent trades, candlesticks, and 24-hour ticker statistics

Place, query, and cancel spot orders, including batch orders of up to 20 at a time

List open orders, historical orders, and personal trade fills for a symbol

GET STARTED

Start building with MEXC Spot API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MEXC Spot API for, with concrete tasks.

★ Algorithmic Spot Trading on MEXC

Quant teams running spot strategies use /api/v3/order to place limit and market orders, /api/v3/depth and /api/v3/klines to feed model inputs, and /api/v3/openOrders for execution monitoring. Batch placement via /api/v3/batchOrders allows up to 20 orders per call, suitable for grid and market-making strategies that need to refresh quotes quickly.

Fetch /api/v3/depth for BTCUSDT, then place a limit buy at the top bid via POST /api/v3/order with quantity 0.001 and verify with GET /api/v3/order.

Portfolio and Risk Reporting

Treasury or fund operations teams pull /api/v3/account for balances, /api/v3/myTrades for fills, and /api/v3/allOrders for order history to build daily P&L and exposure reports. Combined with /api/v3/tradeFee per symbol, these endpoints supply the data needed to reconcile execution costs across the trading desk.

Call /api/v3/account, then for each non-zero balance call /api/v3/myTrades with the corresponding symbol over the last 24 hours.

Treasury Movements and Withdrawals

Operations teams managing exchange treasury use /api/v3/capital/deposit/address to provision deposit addresses, /api/v3/capital/withdraw to push funds to external wallets, and /api/v3/capital/transfer to move balances between MEXC accounts. Withdrawal history endpoints close the audit loop for compliance.

Generate a USDT deposit address on TRC-20 via POST /api/v3/capital/deposit/address, then later submit a withdrawal of 100 USDT via POST /api/v3/capital/withdraw.

Agent-Driven Crypto Workflows

An AI agent monitoring a portfolio can call MEXC through Jentic to rebalance, place hedges, or pull live quotes. The agent searches by intent, loads the operation schema, and executes with the signed payload handled by the SDK — and the MEXC API key plus secret stay inside the Jentic vault rather than appearing in the agent's context.

Search Jentic for 'place a spot order on MEXC', load POST /api/v3/order, then submit a market sell of 10 USDT worth of BTC.

Key Endpoints

32 endpoints — the mexc spot api v3 is the public rest interface for mexc's cryptocurrency exchange and supports market data, spot trading, account management, and wallet operations across hundreds of trading pairs.

METHOD

PATH

DESCRIPTION

POST

/api/v3/order

Place a new spot order

DELETE

/api/v3/order

Cancel an open order

GET

/api/v3/depth

Get order book depth for a symbol

GET

/api/v3/klines

Get candlestick data for a symbol

GET

/api/v3/account

Get account information and balances

POST

/api/v3/capital/withdraw

Submit a withdrawal request

GET

/api/v3/openOrders

List current open orders

POST

/api/v3/order

Place a new spot order

DELETE

/api/v3/order

Cancel an open order

GET

/api/v3/depth

Get order book depth for a symbol

GET

/api/v3/klines

Get candlestick data for a symbol

GET

/api/v3/account

Get account information and balances

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

MEXC API keys and secret signing material are stored encrypted in the Jentic vault. Agents request operations and Jentic applies the X-MEXC-APIKEY header plus HMAC-SHA256 signature at execution time, so neither key nor secret enters the agent's context.

Intent-based discovery

Agents search Jentic with intents like 'place a spot order' or 'get my account balances' and Jentic returns the matching MEXC operation with its parameter and signature schema, so the agent does not browse the 32-endpoint catalogue manually.

Time to first call

Direct MEXC integration: 1-3 days to handle HMAC signing, server time sync, and weight-based rate limiting. Through Jentic: under 1 hour for the common trade and account flows.

FAQs

Specific to using MEXC Spot API through Jentic.

What authentication does the MEXC Spot API use?

MEXC uses an API key in the X-MEXC-APIKEY header along with HMAC-SHA256 request signing for private endpoints. Through Jentic the API key is stored encrypted and the SDK applies the signature when executing private operations.

Can I place batch orders on MEXC?

Yes — POST /api/v3/batchOrders accepts up to 20 orders in a single call, which is the recommended pattern for market-making and grid strategies that need to refresh many quotes at once.

What are the rate limits for the MEXC Spot API?

MEXC publishes weight-based limits on the public docs rather than in this OpenAPI spec — market data and account endpoints have separate buckets, and order endpoints use a per-second order rate limit. Watch for 429 and 418 responses and respect the Retry-After header.

How do I cancel all open orders for a symbol through Jentic?

Search Jentic for 'cancel all MEXC open orders', load DELETE /api/v3/openOrders, and execute with the symbol parameter. Jentic adds the X-MEXC-APIKEY header and the request signature from your stored credential.

Is the MEXC Spot API free?

API access is free for MEXC account holders. Trading still incurs MEXC's standard maker and taker fees per symbol, which you can query via GET /api/v3/tradeFee.

Does this API cover futures or perpetual contracts?

No — this is the spot v3 API. MEXC's futures and contract products live on a separate API surface and are not part of these 32 endpoints.

MEXC Spot API

Connect the MEXC Spot API to your agent

Capabilities

Start building with MEXC Spot API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs