Skip to main content
GET
cURL
Use this endpoint to inspect a wallet’s record after finding it in a leaderboard, market, or trade. Its profit and loss, volume, markets, and win rate cover sports and esports markets only. Every response carries the wallet’s edge over the price it paid. Optional expansions add strategy, category rankings, the profile’s strategy breakdowns, and data-source details. For up to 25 wallets in one request, use Batch traders. It takes every expansion except breakdowns.

Parameters

Key response fields

Strategy breakdowns

expand=breakdowns returns the measures behind the wallet profile’s Insights tab, over the wallet’s sports and esports markets. They are computed from the wallet’s whole history on each request and are not cached, so a wallet with tens of thousands of markets can take several seconds. If the read cannot finish within 30 seconds, the response is 503 with Retry-After. The size, concentration, and entry-price measures each carry state with value: read state first. not_computed means an input such as a position’s cost is unknown, and no value is sent rather than a zero.

Data age

Different profile fields update at different times. data_quality reports each group’s age and status, so you can decide whether the values are recent enough for your use. data_quality.status is fresh when every group is fresh, unavailable when every group is unavailable, stale when every group is fresh or stale and at least one is stale, and partial otherwise. data_quality.as_of is the oldest supporting timestamp. Each entry in data_quality.field_groups carries group, owner (the table and column that writes it), status, an as_of where one exists, max_age_s where its writer refreshes on a schedule, and a reason where the status is not fresh. max_age_s is the longest gap in seconds that the writer’s schedule leaves between refreshes. A group is stale when its as_of is older than that: the writer has missed a refresh it promises. sync, ranking, volume and positions carry 604800 (7 days, the longest gap between full syncs) and leaderboard_rank carries 22620. sports_record carries none: its timestamp moves only when the record changes, so it is never stale. Neither status is an age limit for your use; compare as_of with your own. last_active belongs to no group, because the value is itself the time of a trade. unknown means the value is present but has no reliable timestamp. Do not use another group’s as_of to estimate its age. untracked means that group is not tracked for the wallet; for example, only S, A, and B wallets get a leaderboard rank. data_quality uses stored timestamps for the underlying values, and a cached response is judged again when it is served. meta.cached and meta.cache_age_s describe the response cache separately. For the per-field version of the same question, including where each number comes from and how it was reconciled, request expand=trust.

Example

What it does not return

  • A 404 for a wallet 0xinsider does not track yet. You get a 200 with sync_status set to unknown. Request it again later.
  • strategy before 0xinsider has classified the wallet. The field is omitted until then.
  • P&L for the last week or month. pnl.last_7d and pnl.last_30d are deprecated and never sent.
  • Open positions. Use Trader context.

Caching

Save the response’s ETag and send it in If-None-Match on your next request. If the profile has not changed, the server returns 304 Not Modified with no body.

Authorizations

Authorization
string
header
required

Legacy default or named integration API key, or OAuth 2.1 access token, in the Authorization header as Bearer oxi_sk_live_... or Bearer oxi_at_.... Default keys retain full access; integration keys are limited to their approved read, webhooks, export and usage scopes and expire within 90 days. All credentials share the owner's account limits. Data calls require an active Pro subscription and return live data. A 401 carries WWW-Authenticate: Bearer resource_metadata="https://api.0xinsider.com/.well-known/oauth-protected-resource" (RFC 6750 section 3, RFC 9728).

Scopes

read

Read markets, traders, large trades, positions, reports, search, the event stream and every MCP tool

Headers

X-Query-Validation
enum<string>

Opt into strict query-name validation. The default is compatible: unknown names are ignored and reported in X-Query-Ignored. With strict, an unknown name returns 400 bad_request with error.reason unknown_query_parameter before the handler runs, including when its percent escape is incomplete.

Available options:
strict
If-None-Match
string

Conditional GET validator from a previous ETag. Matching values return 304 Not Modified with an empty body.

Path Parameters

address
string
required

Ethereum wallet address (0x...), known trader username, or trd_-prefixed trader ID emitted by this API.

Query Parameters

expand[]
enum<string>[]

Backward-compatible alias for expand. Repeatable: strategy, categories, trust, breakdowns. quant_metrics is accepted and returns nothing since 2026-10-27.

Available options:
strategy,
categories,
quant_metrics,
trust,
breakdowns
expand
enum<string>[]

Include heavy fields and trust metadata. Repeatable: strategy, categories, trust, breakdowns. breakdowns adds the profile's strategy measures (Trader.breakdowns), computed on the read, and is served on this route only. quant_metrics is accepted and returns nothing since 2026-10-27.

Available options:
strategy,
categories,
quant_metrics,
trust,
breakdowns
max_age_s
integer<int64>

Opt into a whole-response freshness ceiling in seconds. The server returns 200 only when data_quality.status is fresh or stale and data_quality.as_of is no older than this value; otherwise it returns 409 with error.reason=freshness_ceiling_unsatisfied. No refresh or alternate read is attempted.

Required range: x >= 0

Response

Trader profile

object
string
required
Allowed value: "trader"
data
object
required
meta
object
required