Integrate Quote.Trade with AI agents

Quote.Trade already exposes official REST/WebSocket APIs. Agents should treat the official docs and API base as the canonical integration surface. MCP is an optional agent-facing adapter around the existing APIs; it is not a replacement API.

Canonical sources

Quick-start: direct Quote.Trade REST API

Start with verified public endpoints that require no credentials:

GET https://app.quote.trade/api/status
GET https://app.quote.trade/api/exchangeInfo
GET https://app.quote.trade/api/getInstrumentPairs
GET https://app.quote.trade/api/ticker?symbol=BTC
GET https://app.quote.trade/api/depth?symbol=BTC&limit=100

Use timeouts, bounded retries, and respect 429/418 Retry-After responses.

Quick-start: WebSocket/API docs

Use https://doc.quote.trade for the canonical WebSocket and authenticated API behavior. Do not infer private endpoint request/response schemas from Binance compatibility alone.

Hosted MCP adapter

Quote.Trade hosts an optional MCP adapter for agent clients that prefer MCP tool calls.

POST https://quote.trade/mcp

Transport:

Streamable HTTP
JSON-RPC 2.0 over HTTP POST
MCP protocol version: 2025-06-18

The MCP adapter does not replace the official REST/WebSocket APIs. It exposes selected Quote.Trade API workflows as discoverable tools with input schemas, output schemas, safety annotations, guardrails, and structured responses.

Core MCP methods:

initialize
notifications/initialized
ping
tools/list
tools/call

Public MCP tools call existing public endpoints such as:

quote_trade_status         -> GET /api/status
quote_trade_exchange_info  -> GET /api/exchangeInfo
quote_trade_instruments    -> GET /api/getInstrumentPairs
quote_trade_ticker         -> GET /api/ticker
quote_trade_depth          -> GET /api/depth

Private/account/trading MCP tools call existing authenticated endpoints and streams such as:

quote_trade_account               -> GET /api/account
quote_trade_order_preview         -> local validation only; no API call
quote_trade_place_order           -> POST /api/order
quote_trade_liquidity_sample      -> wss://app.quote.trade/ws/liquidity
quote_trade_private_events_sample -> wss://app.quote.trade/ws/listenKey

GET /mcp is not a human-readable docs page. It should return 405 unless server-initiated SSE is separately enabled. Use this guide and the MCP discovery file for documentation.

Authenticated trading reference

Quote.Trade also documents authenticated trading and account workflows. See https://doc.quote.trade/trading-reference.

Do not expose withdrawals, wallet private-key handling, seed phrases, unrestricted autonomous live trading, or unreviewed staking/unstaking flows to agents.

MCP trading safety

Live trading through MCP is disabled unless server-side trading is enabled and the request passes the configured guardrails.

  1. Call quote_trade_order_preview.
  2. Show the normalized order, estimated notional, symbol, side, price, quantity, leverage flag, and account to the user.
  3. Require explicit human approval.
  4. Call quote_trade_place_order only if server-side trading is enabled and all limits pass.

The live order tool should require:

humanApproved=true
approvalText="APPROVE QUOTE.TRADE LIVE ORDER"
server-side API credentials
allowed-symbol check
max-notional check
leverage disabled unless explicitly allowed

Do not expose withdrawals, transfers, wallet signing, staking, unstaking, or unrestricted live order loops through MCP.

Agent Skill usage

Install/copy quote-trade-api-operator for agent instructions. OpenClaw users can use the existing skill with:

openclaw skills install quote-trade-operator

Direct REST/WebSocket calls remain canonical. The hosted MCP endpoint is optional for MCP-aware clients.

OpenAPI/GPT Actions

Use https://doc.quote.trade/openapi/quote-trade.openapi.yaml only for verified public endpoints. Authenticated/trading endpoint schemas should not be used as autonomous agent action schemas unless Quote.Trade explicitly approves the scope, signing flow, risk limits, and human-approval requirements.

If adding an OpenAPI cross-reference, prefer externalDocs pointing to the MCP reference/discovery rather than modeling each MCP trading tool as an ordinary unaudited REST action.

Authenticated trading safety

Trading is high-risk and not financial advice. Use official docs, scoped credentials, dry-run/order-preview logic in the calling application where possible, explicit human approval, max-notional limits, allowed-symbol limits, and no withdrawals. Do not build unrestricted autonomous live trading loops from this package.

Production resources

The production public OpenAPI schema is intentionally read-only. Execution MCP, live trading MCP, nonexistent MCP endpoint URLs, and guessed authenticated schemas are not part of this deployment.