Agent Access Overview
Self-service API for AI agents and programmatic users to register, configure venues, and trade across multiple DEXes
What is Agent Access?
Agent Access is a self-service system that allows external agents (AI agents or programmatic users) to register with HyperETH, configure trading venue credentials, and trade across multiple decentralized exchanges — all via API.
Instead of requiring manual configuration by an operator, agents can:
- Register using a wallet signature and receive an API key
- Configure venues through one of three setup models
- Trade using the same unified V2 trading APIs
Agent Access runs alongside the existing static configuration system. Existing API keys and configurations continue to work unchanged.
Design Principles
Agent Self-Service
Agents register via wallet signature, manage their own API keys, and set up venue access without operator intervention.
Private Key Minimization
Where possible, HyperETH generates internal API wallets so agents never need to expose their main wallet private key.
Per-Venue Optimal Model
Each venue has different delegation capabilities. The design uses the best available model per venue rather than forcing a single approach.
Simple API Key Auth
Both static and dynamic API keys use the same x-api-key header authentication, keeping the auth model uniform.
Supported Venues
| Venue | Type | Setup Model | Key Feature |
|---|---|---|---|
| Hyperliquid | Perpetuals DEX | Model 1 — Programmatic | Fully automated via Privy |
| HyENA | Perpetuals DEX | Model 1 — Programmatic | Fully automated via Privy |
| AsterDex | Perpetuals DEX | Model 2 — Prepare + Confirm | One-time UI action |
| Paradex | Perpetuals DEX | Model 2 — Prepare + Confirm | One-time UI action |
| GRVT | Perpetuals DEX | Model 2 — Prepare + Confirm | One-time UI action |
| Lighter | Perpetuals Protocol | Model 3 — User Credentials | Direct credential submission |
| Kuru | Spot DEX (Monad) | Model 3 — User Credentials | Direct credential submission |
| Nado | Perpetuals DEX | Model 3 — User Credentials | Direct credential submission |
Venue Setup Models
HyperETH classifies venues into three models based on their native delegation capabilities:
Model 1: Full Programmatic
Venues: Hyperliquid, HyENA
HyperETH generates an API wallet internally and registers it with the venue via Privy. The agent needs zero interaction with the venue directly.
- Agent/user never exposes any private key
- API wallet has trade-only permissions (no withdraw)
- Auto-expires via
valid_until, user can revoke anytime
Model 2: Prepare + Confirm
Venues: AsterDex, Paradex, GRVT
HyperETH generates a keypair and returns the address/public key. The agent or user then adds it in the venue's web UI, followed by a confirmation call.
- Agent/user never exposes any private key
- One-time UI action required per venue
- Venue-native permission scoping (e.g., Paradex subkeys are trade-only)
Model 3: User-Provided Credentials
Venues: Lighter, Kuru, Nado
The agent or user creates credentials on the venue side and submits them to HyperETH via API. HyperETH encrypts and stores them.
- Agent/user must provide venue-specific credentials
- HyperETH acts as encrypted credential custody
- User can revoke by rotating keys on the venue side
Quick Start
Sign a message with your wallet and call POST /v2/account/register to get an API key.
Choose one or more venues and follow the appropriate setup model (programmatic, prepare+confirm, or user credentials).
Call GET /v2/account/venues to confirm your venue is active.
Use the unified V2 trading APIs (POST /v2/{platform}/placeOrder, etc.) with your API key.