Core Concepts
Non-custodial unified execution gateway for multi-DEX trading with TEE-protected credentials
What is XATA API?
XATA API is a non-custodial unified execution gateway for multi-DEX trading across Hyperliquid, Aster, Lighter, Kuru, Hyena, GRVT, Nado, and Paradex. The V2 interface keeps request and response shapes consistent across supported venues.
Core API Categories
V2 Unified Trading APIs
/v2/{platform}/*: Unified endpoints for all exchanges- Platforms:
hyperliquid,aster,lighter,kuru,hyena,grvt,nado,paradex - Single spec, consistent data models
V2 Cross-DEX Aggregation
/v2/all/balances: Aggregated balances across all DEXes/v2/all/strategy/*: Cross-exchange arbitrage strategies
V2 Agent Access APIs
/v2/account/register: Wallet registration via EIP-191 signature/v2/account/venues: Venue credential setup and management/v2/account/api-keys: API key lifecycle management
Advanced APIs
- TEE Protected APIs via Agent Wallet
- MCP APIs for AI Agent trading
V2 Unified API Architecture
The V2 API provides a unified abstraction layer over multiple decentralized exchanges through path-based routing.
How It Works
Choose your target exchange via the URL path: /v2/{platform}
/v2/hyperliquid- Routes to Hyperliquid/v2/aster- Routes to Aster DEX/v2/lighter- Routes to Lighter Protocol/v2/kuru- Routes to Kuru Protocol (Spot DEX)/v2/hyena- Routes to Hyena/v2/grvt- Routes to GRVT/v2/nado- Routes to Nado/v2/paradex- Routes to Paradex
All platforms support the same endpoints:
- Market data:
/getTOB,/getOrderBook,/getSymbolInfo - Trading:
/placeOrder,/batchPlaceOrder,/cancelOrder,/cancelAllOrders - Account:
/getBalance,/getPosition,/getOpenOrders,/getUserFills
Responses use consistent field names and structures across all exchanges
XATA translates between the unified V2 format and each exchange's native protocol
System Overview
System Overview
The XATA API provides a unified layer above supported DEXes, offering:
- Clients: Authenticate with API keys and use the same V2 interface across venues
- Routing: XATA normalizes requests and routes them to the selected platform
- Settlement: Orders settle on the target exchange
- Safety: TEE-protected credential handling, venue-specific permission models, and auditable state changes
Agent Access Architecture
Agent Access enables dynamic, self-service credential management for external agents. Instead of requiring static configuration at startup, agents register via wallet signature and manage venue credentials at runtime.
Dynamic Credential Management
- Agents register via EIP-191 wallet signature
- Venue credentials encrypted with AES-256-GCM
- Hot reload: credentials loaded from DB at runtime
- Coexists with existing static configuration
Three Venue Models
- Programmatic (HL/HyENA): Fully automated via Privy
- Prepare + Confirm (Aster/Paradex/GRVT): Generated keypair + UI confirmation
- User Credentials (Lighter/Kuru/Nado): Direct credential submission
API Quick Reference
Unified Trading
/v2/{platform}/placeOrder- Place orders/v2/{platform}/getOrderBook- Order book data/v2/{platform}/getBalance- Account balance
Cross-DEX & Strategy
/v2/all/balances- Aggregated balances/v2/all/strategy/submit/*- Strategy submission/v2/all/strategy/status/*- Strategy monitoring
Agent Access & MCP
/v2/account/register- Wallet registration/v2/account/venues- Venue management- MCP APIs for AI agent trading