News
Ratings
Learn
Companies
Open Companies →
Who runs each service, how it works, where the risks are.All 30 companies A–Z →
About
New to crypto? Start here
Perpetual DEXs · OBOL rating

ApeX Protocol review

A competent second-tier venue with StarkEx settlement and no incidents, competing in a market where depth decides everything.

6.8/10
Mixed
#11 of 15 perpetual dexsChecked August 2026
The short answer

ApeX runs on proven zero-knowledge settlement infrastructure with competitive fees and a clean record, and its problem is not engineering but gravity: perpetual liquidity concentrates, and traders go where the depth is. Fills outside major markets show it.

Best forOrder-book perps with an elastic automated market maker

Score breakdown

Category rubric →
  1. Risk engine & liquidationsweight 25%
    6.5avg 7.0
  2. Depth & slippageweight 20%
    6.0avg 6.7
  3. Funding & feesweight 20%
    7.5avg 7.6
  4. Security recordweight 20%
    7.5avg 7.5
  5. Transparencyweight 15%
    6.5avg 7.3

this service category average across 15Score = Σ mark × weight. Usable, but there are better options for most people. Methodology.

The evidence behind each mark

Scoring rules →
CriterionMarkWhat we foundSourceChecked
Risk engine & liquidations6.5not sourced yetnot sourced yet—
Depth & slippage6.0not sourced yetnot sourced yet—
Funding & fees7.5not sourced yetnot sourced yet—
Security record7.5not sourced yetnot sourced yet—
Transparency6.5not sourced yetnot sourced yet—

What we liked, and what fell short

Liked
  • StarkEx-based settlement with proven validity proofs
  • Competitive fee schedule and broad market list
  • No exploit history
Fell short
  • Liquidity well behind the leading venues
  • Backed by a single ecosystem sponsor, which concentrates support risk

Why the marks landed where they did

There is nothing wrong with ApeX. It settles through StarkEx, the same validity-proof infrastructure that secured dYdX v3, charges roughly 0.02% maker and 0.05% taker, supports a broad market list, and has never been exploited. In most categories that would make it a strong recommendation.

Why depth decides this category

Derivatives liquidity is reflexive. Traders go where fills are good, market makers go where traders are, and the gap between the leading venue and the fifth compounds. ApeX's books on BTC and ETH are usable for retail size; beyond that, slippage on a moderate order will exceed any fee advantage the venue offers. The fee schedule is a marketing lever when liquidity is the binding constraint.

Architecture

StarkEx settlement means trades are proven and settled on Ethereum, with custody enforced by validity proofs rather than trust in the operator. Order matching is off-chain. Users can force-withdraw through the settlement layer if the operator stops serving them, which is the meaningful protection this architecture provides.

Risk profile

No exploit history, audits in place, and an insurance fund. The notable structural point is sponsorship: ApeX's development and liquidity support have been closely tied to a single backer in the Bybit ecosystem, which concentrates the risk that support is withdrawn or redirected.

Who should use ApeX

Traders already in its ecosystem, or those wanting a second venue for specific markets where its book happens to be adequate. For primary derivatives trading, Hyperliquid, dYdX and the larger centralised venues all offer materially better execution.

FAQ

Is ApeX safe?
It settles through StarkEx with validity proofs and has no exploit on record. Custody protections are strong; the practical risk is liquidity rather than security.
What are ApeX's fees?
Roughly 0.02% maker and 0.05% taker, tiering with volume — competitive with the category leaders.
Why is ApeX's liquidity thin?
Perpetual liquidity concentrates on a few venues because traders follow fills and market makers follow traders. Smaller venues struggle to break that loop regardless of their engineering.
Can I withdraw if ApeX stops operating?
Yes. StarkEx settlement includes a forced-withdrawal path enforced on Ethereum, so custody does not depend on the operator's cooperation.