GMX
GMX is a decentralized perpetual and spot exchange deployed on Arbitrum, Avalanche, Botanix, and MegaETH, supporting trades with up to 100x leverage and low-price-impact token swaps powered by oracle-based pricing. The platform exposes four integration surfaces: a GMX REST API (primary, OpenAPI-documented) for account data, orders, analytics, and relayed workflows; an Oracle API (stable) for oracle prices, markets, liquidity snapshots, and APY; a GraphQL API via Subsquid for historical on-chain data; and an MCP server plus TypeScript SDK for AI-agent and programmatic access. Data coverage includes markets, tickers, tokens, positions, orders, rates, APY, performance, wallet balances, GLP/GM/GLV token analytics, OHLCV, buyback stats, and staking power.
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 GMX the way a machine reads it — 140 machine-readable artifacts across 22 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 — GMX scores 41.6/100 (thin), with a separate agent-readiness read of 39/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile GMX
Each block below is one kind of artifact we hold for GMX. 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 22
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.
GMX Oracle API
Stable, read-only REST API providing oracle prices, market information, liquidity snapshots, APY data, and GM/GLV token info for Arbitrum, Avalanche, Botanix, and MegaETH. Prima...
GMX GraphQL API
Historical on-chain data for GMX via Subsquid-powered GraphQL endpoints. Enables deep queries over trades, liquidity events, positions, and protocol metrics indexed from Arbitru...
GMX Integration API
CoinGecko-compatible trading pairs API for GMX markets on Arbitrum and Avalanche, returning ticker IDs, base and target currencies, product type (Spot or Perpetual), last price,...
GMX TypeScript SDK
Official @gmx-io/sdk package shipping two clients: GmxSdk (SDK v1) for full read/write access via RPC, and GmxApiSdk (SDK v2) for lightweight read-only HTTP access covering mark...
GMX Allowances API
The Allowances API from GMX — 1 operation(s) for allowances.
GMX APY API
The APY API from GMX — 1 operation(s) for apy.
GMX Balances API
The Balances API from GMX — 1 operation(s) for balances.
GMX Buyback API
The Buyback API from GMX — 1 operation(s) for buyback.
GMX GMX Account API
The GMX Account API from GMX — 4 operation(s) for gmx account.
GMX JIT API
The JIT API from GMX — 2 operation(s) for jit.
GMX Markets API
The Markets API from GMX — 5 operation(s) for markets.
GMX Order Transactions API
The Order Transactions API from GMX — 6 operation(s) for order transactions.
GMX Orders API
The Orders API from GMX — 2 operation(s) for orders.
GMX Pairs API
The Pairs API from GMX — 1 operation(s) for pairs.
GMX Performance API
The Performance API from GMX — 2 operation(s) for performance.
GMX Positions API
The Positions API from GMX — 2 operation(s) for positions.
GMX Prices API
The Prices API from GMX — 1 operation(s) for prices.
GMX Rates API
The Rates API from GMX — 1 operation(s) for rates.
GMX Staking API
The Staking API from GMX — 1 operation(s) for staking.
GMX Subaccounts API
The Subaccounts API from GMX — 2 operation(s) for subaccounts.
GMX Tokens API
The Tokens API from GMX — 2 operation(s) for tokens.
GMX Trades API
The Trades API from GMX — 2 operation(s) for trades.
Scroll within the panel for all 22 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
GMX GraphQL API
GMX exposes historical on-chain data through a Subsquid-powered GraphQL API. The primary endpoint indexes the GMX Synthetics protocol on Arbitrum and provides deep query capabil...
GRAPHQLPricing 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.
Gmx 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.
Gmx 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.
Gmx Finops
FINOPSSemantic Vocabularies 2
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.
Api Context
JSON-LDcontext 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.
GMX API Rules
SPECTRALJSON Schema 72
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.
ApiParameterPeriod
JSON SCHEMAApprovalPrepareRequest
JSON SCHEMAApprovalPrepareResponse
JSON SCHEMAApyEntry
JSON SCHEMAApyResponse
JSON SCHEMABigIntToString_BuybackWeeklyStatsData_
JSON SCHEMABigIntToString_StakingPowerData_
JSON SCHEMABridgeOutParamsDto
JSON SCHEMABuybackWeeklyStatsResponse
JSON SCHEMACancelPrepareRequest
JSON SCHEMACollateralOperation
JSON SCHEMACollateralPrepareRequest
JSON SCHEMACrossChainDepositPrepareRequest
JSON SCHEMACrossChainDepositPrepareResponse
JSON SCHEMACrossChainWithdrawPrepareRequest
JSON SCHEMACrossChainWithdrawPrepareResponse
JSON SCHEMACrossChainWithdrawSubmitRequest
JSON SCHEMACrossChainWithdrawSubmitResponse
JSON SCHEMAEditPrepareRequest
JSON SCHEMAGasPaymentParamsDto
JSON SCHEMAGlvShiftParamsResponse
JSON SCHEMAGmxAccountStatusRequest
JSON SCHEMAGmxAccountStatusResponse
JSON SCHEMAJitLiquidityHistoryPeriod
JSON SCHEMAJitLiquidityHistoryResponse
JSON SCHEMAJitLiquidityInfoItemResponse
JSON SCHEMAJitLiquidityInfoResponse
JSON SCHEMAJitLiquiditySnapshotResponse
JSON SCHEMALeverageTierResponse
JSON SCHEMAMarketConfigResponse
JSON SCHEMAMarketDirectionFilter
JSON SCHEMAMarketInfoResponse
JSON SCHEMAMarketRatesResponse
JSON SCHEMAMarketTickerResponse
JSON SCHEMAMarketValuesResponse
JSON SCHEMAMarketWithTiersResponse
JSON SCHEMAOhlcvCandle
JSON SCHEMAOrderEventCombination
JSON SCHEMAOrderKind
JSON SCHEMAOrderResponse
JSON SCHEMAOrderTransactionStatus
JSON SCHEMAPairResponse
JSON SCHEMAPositionResponse
JSON SCHEMAPrepareRequest
JSON SCHEMAPrepareResponse
JSON SCHEMARatesResponse
JSON SCHEMARatesSnapshotResponse
JSON SCHEMARecord_string.ApyEntry_
JSON SCHEMARecord_string.any_
JSON SCHEMARecord_string.unknown_
JSON SCHEMASimpleOrderType
JSON SCHEMAStakingPowerResponse
JSON SCHEMAStatusRequest
JSON SCHEMAStatusResponse
JSON SCHEMASubaccountStatusRequest
JSON SCHEMASubaccountStatusResponse
JSON SCHEMASubmitRequest
JSON SCHEMASubmitResponse
JSON SCHEMATokenAllowance
JSON SCHEMATokenInfoResponse
JSON SCHEMATokenResponse
JSON SCHEMATradeActionResponse
JSON SCHEMATradeDirection
JSON SCHEMATradeResponse
JSON SCHEMATradesListResponse
JSON SCHEMATradesSearchRequest
JSON SCHEMATransactionMode
JSON SCHEMAWalletBalance
JSON SCHEMAScroll within the panel for all 72 ·
Examples 37
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.
Cancelprepare
EXAMPLECollateralprepare
EXAMPLEEditprepare
EXAMPLEFetchstatus
EXAMPLEGetallowances
EXAMPLEGetannualized
EXAMPLEGetapy
EXAMPLEGetliquidityhistory
EXAMPLEGetliquidityinfo
EXAMPLEGetmarkets
EXAMPLEGetmarketsconfig
EXAMPLEGetmarketsinfo
EXAMPLEGetmarketstickers
EXAMPLEGetmarketsvalues
EXAMPLEGetohlcv
EXAMPLEGetorderbykey
EXAMPLEGetordersbyaddress
EXAMPLEGetpairs
EXAMPLEGetpositionbykey
EXAMPLEGetpositionsinfo
EXAMPLEGetrates
EXAMPLEGetsnapshots
EXAMPLEGetstakingpower
EXAMPLEGettokens
EXAMPLEGettokensinfo
EXAMPLEGettrades
EXAMPLEGetwalletbalances
EXAMPLEGetweeklystats
EXAMPLEPrepare
EXAMPLEPrepareapproval
EXAMPLEPreparecrosschaindeposit
EXAMPLEPreparecrosschainwithdraw
EXAMPLESearchtrades
EXAMPLEStatus
EXAMPLEStatuscrosschainwithdraw
EXAMPLESubmit
EXAMPLESubmitcrosschainwithdraw
EXAMPLEScroll within the panel for all 37 ·
Security Posture 1
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 GMX — 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.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/gmx · machine-readable index on apis.io