Architecture

Web / App
  → Platform API (session, plan, approval, events)
      → AORAMPC Gateway
           → Hyperliquid
           → ASTER
           → Risk rules / approval / audit

Gateway

• Which tools the current session may use
• Input, limit, and idempotency checks
• Timeouts, retries, and cancels
• Full audit trail
• Session and audit records stay on the platform; private keys stay with the user

Venue services

• Map enabled venues into a shared market and order model
• Handle tick size, symbols, and order types
• Call write APIs after Gateway approval
• Adapt the venue; strategy is chosen upstream

What Agents call

Read-only:

market.read
account.read
strategy.simulate
risk.preview
execution.preview

Writes go through the Gateway:

execution.submit

Before submit, the Gateway re-checks approval, limits, expiry, and the original order intent.