Wallet Intelligence
Inspect portfolio equity, realized PnL, open positions, rankings, and trading behavior.
Overview
Documentation for real product integrations.
Reyzen exposes a structured production-facing data surface for teams that need wallet intelligence, live open positions, market snapshots, rankings, and operational status without scraping UI payloads or rebuilding product views from raw infrastructure.
Performance Metrics
Access win rate, drawdown, Sharpe score, volume, trader style, and historical performance.
Market Data
Use clean Reyzen datasets for live perp activity, coin-level exposure, and position analytics.
Production Ready
Designed for dashboards, bots, trading tools, social cards, and advanced DeFi workflows.
Quickstart
Go from zero to first request quickly.
Start with the health probe, then move into the wallet, live-trade, and symbol-level surfaces that power the core Reyzen product pages.
▣ Quickstart Request
const response = await fetch(
"/api/profile?address=0xf32f...3f4a",
{
headers: {
"Content-Type": "application/json"
}
}
);
const wallet = await response.json();
console.log(wallet.pnl, wallet.winRate, wallet.openPositions);
▣ Example Response
{
"wallet": "0xf32f...3f4a",
"equity": "310.84 USD",
"pnl": "-96.74K USD",
"winRate": 49,
"openPositions": {
"total": 14,
"long": 8,
"short": 6
},
"traderStyle": "Swing Trader"
}
Conventions
Authentication, response shape, and runtime expectations.
The public Reyzen read surface is JSON over HTTPS. Use documented fields, respect cache headers, and treat unavailable metrics differently from zero-value metrics.
Authentication
Public read endpoints documented here do not currently require an API key.
Pagination
List endpoints typically return page, pageSize, pages, and totals.
Timestamps
Use UTC and treat timestamps as Unix epoch milliseconds unless the field says otherwise.
Freshness
Honor Cache-Control, generatedAt, updatedAt, and availability flags.
Core API
Live Perp Data
Powers the exchange-wide live perp monitor. Optimized for current open positions, wallet drill-down, symbol filters, and latest-action labeling.
GET
/api/live-trades
Returns paginated live open positions together with symbol filters, totals, search, and sort controls.
| Query parameter | Type | Description |
|---|---|---|
page, pageSize | number | Pagination controls. |
symbol | string | Restrict rows to one market symbol. |
query | string | Search by wallet or symbol text. |
sortBy, sortDir | string | Sort field and direction. |
Core API
Wallet Explorer
Explorer routes are built for wallet discovery, address lookup, dashboard drill-down, and trader profile analysis using Reyzen’s wallet datasets.
GET
/api/traders
Returns the Wallet Explorer table with ranking, equity, PnL, win rate, and wallet summary fields.
GET
/api/profile?address={address}
Returns the selected wallet dashboard state, including summary cards, positions, chart data, and profile stats.
Core API
Wallet Performance
Wallet Performance is the scored wallet surface. It is built from the full wallet universe and filtered by the internal score logic rather than a simple positive-PnL subset.
GET
/api/wallet-performance
Returns scored wallets, ranking metadata, trader style, and performance windows for the Wallet Performance table.
GET
/api/wallet-performance/status
Returns scoring pipeline readiness, total scored wallet count, and freshness status.
Core API
Coin Analysis
Symbol-level market intelligence including long/short pressure, wallet positioning, funding, open interest, and daily history for supported symbols.
GET
/api/coin-analysis
Returns symbol summary data, history, wallet positions, long/short pressure, and market metrics for the selected coin.
Availability Rule
If historical funding, open interest, or pressure are not stored as source-of-truth datasets, they should be treated as unavailable rather than guessed.
Core API
Markets & Funding
Exchange-wide market snapshot routes for prices, 24-hour change, volume, open interest, and funding used across Reyzen.
GET
/api/markets/ticker
Exchange-wide market snapshot with price, change, open interest, volume, and current funding fields.
GET
/api/live-trades/funding
Funding and long/short distribution surface used by Live Trade and symbol-level market views.
Reference
Leaderboard & ranking surfaces
Ranking-oriented consumers should use the Wallet Explorer and Wallet Performance tables as the primary leaderboard surfaces, depending on whether the use case is broad discovery or score-qualified discovery.
Operations
API Status & pipeline observability
Operational endpoints are intended for monitoring, admin surfaces, and service-health visibility.
GET
/api/health
Minimal health probe for service reachability.
GET
/api/pg-tracking/status
Forward indexer status, current progress, date/symbol position, and tracked-wallet counts.
Best Practice
Design for live trading context.
Reyzen data is built for real trading interfaces. Cache stable metrics, stream live positions carefully, and always make positive/negative values visually clear for traders.
Cache rankings
Do not repoll scored or leaderboard surfaces like a live tape.
Color PnL clearly
Positive and negative values should be instantly readable in any UI consuming these responses.
Validate wallet input
Guard address parsing and empty states rather than assuming every lookup resolves cleanly.
Read freshness fields
Use generatedAt, updatedAt, and availability flags instead of guessing staleness.
Reference
Errors and response handling
Error bodies are intentionally simple. Treat status codes and route-specific availability rules as the primary control plane for retries and UI behavior.
| Status | Meaning | Typical body |
|---|---|---|
400 | Bad request or invalid input | {"error":"Bad request"} |
404 | Route missing, feature disabled, or runtime-mode mismatch | {"error":"Endpoint unavailable in this service mode."} |
429 | Rate limited request | Read Retry-After and back off |
500 | Internal processing or upstream failure | {"error":"Internal server error"} |
Changelog
Track contract changes and release notes.
Use the dedicated changelog for builder-facing updates, route changes, behavior shifts, and deprecation guidance.
No documentation sections match this search.