Networks & Endpoints
Superhero runs on æternity mainnet (ae_mainnet) or testnet (ae_uat). The network is selected
at build time with VITE_NETWORK, and a deployed container can override any individual endpoint
at runtime through window.__SUPERCONFIG__.
Endpoints
Mainnet (ae_mainnet) | Testnet (ae_uat) | |
|---|---|---|
| Superhero API | https://api.superhero.com | Not publicly documented |
| Node | https://mdw.wordcraft.fun | https://testnet.aeternity.io |
| Middleware | https://mdw.wordcraft.fun/mdw | https://testnet.aeternity.io/mdw |
| WebSocket | https://api.superhero.com | Not publicly documented |
| Compiler | https://v7.compiler.aepps.com | https://v7.compiler.aepps.com |
| Explorer | https://aescan.io | https://testnet.aescan.io |
| Governance API | https://governance-server-mainnet.prd.service.aepps.com/ | https://governance-server-testnet.prd.service.aepps.com/ |
| DEX backend | https://dex-backend-mainnet.prd.service.aepps.com | https://dex-backend-testnet.prd.service.aepps.com |
| Wallet | https://wallet.superhero.com | https://wallet.superhero.com |
| Chat relay | wss://relay.superhero.chat | wss://relay.superhero.chat |
Contract addresses differ per network too; see Deployed addresses.
api.superhero.com, mdw.wordcraft.fun, wallet.superhero.com and relay.superhero.chat are
operated by Superhero. The *.aeternity.io and *.aepps.com hosts are æternity Foundation
infrastructure, and æScan is built by æLabs.
Node and middleware
The node host serves the æternity node HTTP API under /v3/... and the middleware under
/mdw/.... The public æternity Foundation mainnet node at https://mainnet.aeternity.io serves
the same two APIs on the same paths. Both hosts serve ae_mainnet, and a transaction submitted
through one is visible through the other; for your own integration, either works.
# Node API
GET <NODE_URL>/v3/transactions/<txHash>?int-as-string=false
GET https://mainnet.aeternity.io/v3/headers/top
# Middleware
GET <MIDDLEWARE_URL>/v3/transactions/<hash>
GET https://mainnet.aeternity.io/mdw/v3/names?owned_by=ak_...Middleware routes are not all on the same version. Check the call you need:
| Call | Path |
|---|---|
| Transaction status | /v3/transactions/... |
| AEX-9 account balances | /v2/aex9/account-balances/... |
| Owned names | /v3/names?owned_by=... |
Rate limits
api.superhero.com allows 10 requests per minute per client IP and route path, in a fixed
60-second window, and returns HTTP 429 with a retryAfter field when you exceed it. The limit
applies to the generic entity endpoints and to the profile, notification-feed and room
endpoints. See the developer FAQ for what that means for a polling client.
No limit is documented for the node, middleware, compiler, governance or DEX-backend hosts. Treat them as best-effort, back off on failure, and cache what you can.
Related
- Node & middleware API: the endpoints above, with request and response shapes.
- Deployed addresses: the per-network contract addresses that pair with these endpoints.
- Testnet: running against
ae_uatend to end. - Explorers: checking what these endpoints return.
- æternity node API reference (opens in a new tab): the node HTTP API served at
/v3. - ae_mdw middleware (opens in a new tab): what is served under
/mdw, and its OpenAPI spec.