Product
Agents & API
Robinhood Chain was built for agentic trading. Seranox ships a metered API for the machines that increasingly trade beside humans.
Access model
| Concern | Mechanism | Utility |
|---|---|---|
| Who may route | Staked account required; stake sets throughput | #10 Machine routing rights |
| Requests per second | Scales with stake | #9 API rate limits |
| Data calls | Metered and burned per request | #13 Data API credits |
| Running an agent | Each live instance costs $SERA to keep alive | #24 Agent deployment |
| Publishing an agent | Posted bond, forfeited on misreported performance | #30 Listing bond |
| Earning as an author | Share from every user running your strategy | #27 Agent marketplace share |
| Agent-to-agent data | Agents buy signals from other agents, settled in $SERA | #28 Agent-to-agent data |
Surfaces
- Indexer — pairs, swaps, holders, wallet flow, dislocation spreads.
- Alerts — subscribe to new pairs, tracked-wallet activity, screener matches.
- Routing — build and submit swaps through the Seranox router (staked accounts only).
- Compute — screener runs, risk scans, dossiers, backtests, priced per run.
Shape of a request
# Indexer: recent flow for a wallet (metered, burned per request)
GET https://dapp.seranox.xyz/api/v1/wallets/0xabc…/flow?window=24h
Authorization: Bearer <api-key bound to a staked account>
# Routing: build a swap (returns an unsigned tx; the caller signs)
POST https://dapp.seranox.xyz/api/v1/route
{ "pair": "0x…", "side": "buy", "amountIn": "250000000", "slippageBps": 100 }Reference, not spec
The endpoint shapes above illustrate the access model. Today the read endpoints on dapp.seranox.xyz/api/v1 (pairs, candles, trades, wallets, equities, route) answer without a key and report their would-be cost in x-sera-burned; keys bound to a staked account arrive with staking. The authoritative reference ships alongside machine routing.