API

The Hypertrade Aggregator API provides a unified interface for accessing Hypertrade R1 routing, quote simulation, and transaction construction. It is designed for integrations that require the best execution across all available liquidity sources on Hyperliquid.

The Aggregator API operates in two modes:

• EVM Hyper API

• EVM+CORE Hyper API

Both modes use our internal simulation engine for accurate route evaluation.

Aggregator API Overview

The Aggregator API computes the most efficient routing path for every swap by evaluating all available liquidity sources.

It scans:

• Hypertrade DEX pools (both v2 and v3)

• External HyperEVM DEXs

• HyperCore Spot liquidity

The API performs a full set of calculations required for optimal execution:

Quote simulations: Estimates output amounts across different liquidity sources and routes.

Slippage and price impact evaluation: Determines how trade size and pool depth affect execution quality.

Raw transaction construction: Builds the final transaction payload that can be submitted on-chain for execution.

The routing logic is fully deterministic and transparent — the same inputs always produce the same route, and every step of the calculation can be inspected and verified.

When to Use EVM Hyper API

Use the EVM Hyper API when your integration operates exclusively inside HyperEVM.

In this mode, the API:

• aggregates liquidity across supported HyperEVM DEXs

• simulates quotes and evaluates slippage

• computes final output amounts and price impact

• constructs executable transaction payloads

• handles token approval flows

• provides ready-to-use integration templates

Routing is strictly contained within HyperEVM, making this mode suitable for applications that do not require cross-environment swaps.

When to Use EVM+CORE Hyper API

Use the EVM+CORE Hyper API when you need to route swaps between HyperEVM and HyperCore.

This mode includes all EVM API capabilities, plus:

• routing between HyperEVM ↔ HyperCore

• paths that may start and end in different environments

• optional hybrid sequences such as:

  • HyperEVM → HyperCore → HyperEVM

  • HyperCore → HyperEVM → HyperCore

• access to HyperCore Spot liquidity for improved execution quality

Hybrid routing can be enabled or disabled via configuration parameters, depending on integration requirements.

Implementation Details

Aggregator API endpoints provide:

• quote simulation

• price impact metrics

• multi-hop and multi-market route breakdown

• raw transaction construction

• routing mode configuration

For more implementation details, refer to the API Documentation or Integration Guide.