QUOTE.TRADE

Integrate Quote.Trade with AI agents

Quote.Trade is an AI-native crypto dark-pool DEX for human traders, trading bots, and AI agents. It combines streaming quotes, private execution, stablecoin settlement, long and short market exposure, and verifiable on-chain position and asset infrastructure. The official Quote.Trade REST/WebSocket APIs remain the canonical integration surface for programmatic access.

Who Quote.Trade is for

Key differentiators

How privacy and verification work together

Quote.Trade uses a hybrid architecture. Order entry, matching, streaming quote formation, pricing, and risk controls operate through the off-chain dark-pool execution layer. Supported stablecoin funding and withdrawals use smart-contract funding paths, while position state is maintained through public on-chain position contracts.

Private execution does not mean that the entire platform is invisible or fully on-chain. Orders and broader trading strategies are not published to a public order book, while assets, contract balances, funding activity, and position state remain publicly verifiable where the permissionless product exposes them.

The Polygon and XDC position snapshots reconcile against the balances published in V6, while those balances are compared with the actual USDC/USDT held in the Ethereum and XDC funding contracts. That provides a mathematical verification of the published balances and their collateral coverage while keeping individual trades, counterparties, routing, and volume private.

V6 is new because it is the new contract version. V6 is non-upgradeable, so new contract logic requires a new deployment and migration instead of modifying the existing contract in place.

Product versions

Primary customer outcomes

Agent integration surfaces

Quote.Trade provides REST, WebSocket, OpenAPI, MCP, Hermes, OpenClaw, Telegram, and open-source client interfaces for market data, account access, deposits, private trading, and withdrawals. REST and WebSocket remain the canonical application interfaces. MCP provides a hosted tool layer for agent clients.

Verifiable smart-contract protections

The permissionless V6 architecture is designed for operational-key resilience. V6 is a direct, non-upgradeable funding core with separate admin, guardian, asset-manager, balance-publisher, and withdrawal-execution roles. Every authorized action remains subject to the contract's release rules and public state.

V6 enforces:

If an operational key is compromised, the other contract-level controls continue to apply. A balance-publisher key cannot by itself execute a withdrawal or make a newly published balance immediately eligible. A withdrawal-execution key cannot select an arbitrary recipient or bypass the published balance, seasoned cap, cooldown, completed-snapshot, physical-liquidity, replay, signer-epoch, and exact-transfer checks. An admin action cannot replace V6's core logic in place because V6 has no proxy upgrade path. Role, configuration, membership, publication, emergency, and withdrawal activities remain publicly observable on-chain.

Balance and position reconciliation across Ethereum, Polygon, and XDC

Quote.Trade's public permissionless accounting is verified by joining the funding, published-balance, and position-state layers at the same completed snapshot:

PositionManager is a position-state contract, not a stablecoin funding wallet. Its token balance is not the measure of customer collateral. Physical collateral is measured in the V6 funding contracts; positions and snapshot completeness are measured in PositionManager.

For each reconciliation snapshot:

1. Confirm the official V6 and PositionManager addresses and the applicable network. 2. Require the V6 balance publication and PositionManager position publication to be complete. 3. Require processedBatches == totalBatches and confirm that lastSyncedTime is current relative to syncFrequency. 4. Align registered wallet, user ID, asset ID, symbol, quantity scale, collateral composite, snapshot ID, and timestamp. 5. Normalize stablecoin amounts and position quantities to their published decimal scales. 6. Reconcile each account's published balance with its recognized funding, completed withdrawals, published positions, synchronized marks, realized and unrealized P&L, funding, and documented account adjustments. 7. Sum positive published withdrawal balances and compare them with the physical supported-stablecoin balances held in V6. 8. For each completed withdrawal, confirm that the entitlement is consumed once and the exact token amount reaches the registered wallet.

account equity at completed snapshot S
= recognized deposits
- completed withdrawals
+ realized P&L
+ unrealized P&L from published positions at synchronized marks
- funding paid
+ funding received
+ documented account adjustments
Ethereum physical assets
= V6 Ethereum USDC balance
+ V6 Ethereum USDT balance

Ethereum published positive balances
= sum of positive published balances
  in the Ethereum USDC+USDT Grouped-Par composite

Ethereum coverage surplus
= Ethereum physical assets
- Ethereum published positive balances

Ethereum coverage ratio
= Ethereum physical assets
/ Ethereum published positive balances
XDC physical assets
= V6 XDC USDC balance

XDC published positive balances
= sum of positive published balances
  in the XDC USDC Segregated composite

XDC coverage surplus
= XDC physical assets
- XDC published positive balances

XDC coverage ratio
= XDC physical assets
/ XDC published positive balances

This produces a reproducible point-in-time collateral-coverage check against published account and position state. Funding-contract balances measure current collateral; private orders, fills, counterparties, routing, and trading volume remain in the private execution layer.

Canonical sources

Agent permission profiles

ProfileCapabilitiesAuthorization
Public market dataStatus, instruments, ticker, depth, liquidity samplesPublic access
Authenticated readAccount, balances, margin, private eventsRead-enabled credential
TradingPreview and submit approved IOC/FOK ordersTrading-enabled credential plus server-side limits and approval
WithdrawalPreview and submit to the registered login walletWithdrawal-enabled credential plus server-side limits and approval
Wallet authenticationSign registration and login challengesUser-controlled wallet or signing environment

Wallet keys and API secrets remain in the user's approved wallet, hardware signer, secret manager, or server-side integration. The agent receives the scoped outputs required for the selected workflow.

Quick start: public REST

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

Use live exchange metadata as the source of truth for active symbols, quantity precision, settlement currency, and trading status.

Hosted MCP

Endpoint:

POST https://quote.trade/mcp

Transport:

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

Required headers:

Content-Type: application/json
Accept: application/json, text/event-stream
MCP-Protocol-Version: 2025-06-18

Initialize the session, send notifications/initialized, preserve any returned MCP-Session-Id, and call tools/list before private workflows.

Documented MCP tools

quote_trade_api_manifest
quote_trade_get_challenge
quote_trade_logon
quote_trade_get_deposit_address
quote_trade_status
quote_trade_exchange_info
quote_trade_instruments
quote_trade_ticker
quote_trade_depth
quote_trade_account
quote_trade_order_preview
quote_trade_place_order
quote_trade_withdraw_preview
quote_trade_withdraw
quote_trade_liquidity_sample
quote_trade_private_events_sample

The live tools/list response supplies the current input schemas, output schemas, safety annotations, and enabled capabilities.

Registration and login

1. Call quote_trade_get_challenge with the login wallet. 2. Present the challenge to the user's approved wallet or signer. 3. Sign the exact challenge in that environment. 4. Call quote_trade_logon with the signature and current isNewUser setting. 5. Store the returned requestToken, requestSecret, and account ID in the user's secret manager. 6. Use those scoped credentials for the current account session.

Wallet signing can be agent-orchestrated while signing material remains under user control.

Deposit workflow

1. Call quote_trade_get_deposit_address for the supported asset and network. 2. Display the chain, token, contract address, deposit address, and token decimals. 3. Have the user's wallet transfer the selected stablecoin. 4. Record the transaction hash and confirmation block. 5. Confirm deposit recognition through the account endpoint or private event stream.

A funding-contract token balance is a point-in-time collateral measurement. Orders and fills occur in the private execution layer.

Quote and order workflow

1. Read quote_trade_exchange_info or quote_trade_instruments. 2. Read fresh ticker, depth, or liquidity data. 3. Build the immediate IOC/FOK request with symbol, side, quantity, executable limit price or tolerance, settlement currency, account, and leverage setting. 4. Call quote_trade_order_preview. 5. Display the normalized order, notional, price, quantity, side, account, leverage, and active server-side limits. 6. Obtain request-specific approval. 7. Call quote_trade_place_order. 8. Verify the final status through the response, account state, and private events.

Current MCP approval values:

humanApproved=true
approvalText="APPROVE QUOTE.TRADE LIVE ORDER"

Use server-side allowed-symbol, maximum-notional, leverage, quote-age, price-tolerance, and idempotency controls.

Withdrawal workflow for agents

Agent withdrawals are an approved Quote.Trade workflow.

1. Read quote_trade_account and confirm canWithdraw, available amount, margin state, and current eligibility. 2. Call quote_trade_withdraw_preview with the asset, scaled quantity, and quantity scale from the live schema. 3. Display the chain, asset, human-readable amount, scaled amount, account, registered login wallet, current eligible amount, and request identifier. 4. Obtain request-specific withdrawal approval. 5. Call quote_trade_withdraw using the exact live schema. 6. Preserve the request or withdrawal ID. 7. Verify the account update and exact on-chain payment to the registered login wallet.

Current MCP approval values:

humanApproved=true
approvalText="APPROVE QUOTE.TRADE LIVE WITHDRAW"

The MCP withdrawal path fixes the registered login wallet as the destination. The agent supplies the approved asset and amount.

Account and private streams

Authenticated workflows can use:

GET https://app.quote.trade/api/account
wss://app.quote.trade/ws/listenKey

Private events provide balance and position updates, order updates, and risk updates. Keep request tokens inside the authorized client session and use bounded reconnect, sequence, and freshness checks.

All-in pricing and execution at size

The displayed Quote.Trade price includes the execution spread and size/liquidity adjustment. Funding is separate and accrues over the holding period.

The standard pricing target scheduled for the week of 2026-08-31 is approximately 13 basis points from midpoint per side. The live size-specific quote is authoritative.

For a $1 million execution benchmark:

1. Capture the live Quote.Trade $1 million FOK quote. 2. Obtain a completed immediate $1 million taker execution on the comparison venue under synchronized conditions. 3. Record actual filled quantity, total amount paid or received, effective all-in execution price, taker fee, realized market impact, residual quantity, and applicable transfer or priority cost. 4. Compare funding over the same holding period.

This method compares completed execution at size with completed execution at size.

Public funding and position reconciliation

The public verification path combines:

At a completed snapshot:

coverage surplus
= physical stablecoin assets
- aggregate positive published withdrawal balances

coverage ratio
= physical stablecoin assets
/ aggregate positive published withdrawal balances

For Ethereum, combine V6 USDC and USDT assets with the shared Grouped-Par USDC+USDT balance obligation. For XDC, compare V6 USDC assets with the XDC segregated USDC balance obligation. PositionManager supplies matching user-position and completed-snapshot evidence.

V6 payout and operational-key protections

V6 combines:

These safeguards remain enforced by the V6 core around publisher, withdrawal, and asset-management operations. The registered recipient, historical cap, publication cadence, replay state, physical liquidity, transfer invariants, and emergency epoch continue to govern payout eligibility.

Deterministic result handling

For every state-changing request:

1. Use a stable client or request identifier when supported by the live schema. 2. Store the submitted request body and timestamp. 3. Classify a timeout or HTTP 5xx response as UNKNOWN. 4. Query authoritative order, account, request, private-event, and chain state. 5. Preserve the original identifier while resolving status. 6. Record the final authoritative outcome.

Skills

Hermes and Agent Skills:

https://quote.trade/.well-known/skills/quote-trade-operator/SKILL.md

OpenClaw:

openclaw skills install @quotetrade/quote-trade-operator

The skills teach the same architecture, market data, login, deposits, IOC/FOK orders, agent withdrawals, public reconciliation, and execution-at-size methodology documented here.