About Hyper API

💰 Additional Revenue for You, Best Swaps for Your Users

Hypertrade R1 Hyper API is the only API you ever need to experience or build the best swap experience on Hyperliquid. Available in two versions: EVM Hyper API for aggregation on HyperEVM only, and EVM+CORE Hyper API for enhanced routing including HyperCore.

It computes optimal routing paths across all DEXs on HyperEVM, performs quote simulations with slippage calculations, returns expected output amounts with price impact analysis, and constructs raw transactions for execution.

🚀 Why Use Hyper API

• Keep 98.5% of your fees (we keep only 1.5%)

• Earn up to 1% on every swap your users make

• 100% accurate quotes*

• Receive 50% of positive slippage shares**

• Ready-to-use-code - integrate in minutes, not days

*at the time of quote request

**after address approval

When to Use Hyper API (only EVM)

Use EVM Hyper API when integration is limited to HyperEVM:

• Handles aggregation across DEXs on HyperEVM, finding routes, simulating quotes with slippage calculations, and building raw transactions for execution.

• Routes are restricted to HyperEVM-only paths.

• Provides ready-to-use code for integration in minutes.

• Features quote simulations via Invisium Swap Simulations, multi-DEX aggregation, address approvals, and detailed reports.

When to Use

Use EVM+CORE Hyper API when integration requires enhanced routing:

• Contains all features of EVM Hyper API.

• HyperEVM + HyperCore routing: Enables direct swaps between HyperEVM and HyperCore (including HyperCore Spot), where the input and output tokens are in different execution environments.

• Routes Incorporating Other Layers for Better Prices: Incorporates HyperCore routes to optimize paths, even for swaps starting and ending on HyperEVM (e.g., HyperEVM → HyperCore → HyperEVM) or HyperCore (e.g., HyperCore → HyperEVM → HyperCore), delivering better rates through multi-hop and multi-market optimization while returning the output token to the original environment.

• All functions can be easily enabled as desired through simple configuration, allowing you to selectively turn on or off specific routing options (such as hybrid layer swaps or routes through other layers) based on what you need.

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