Skip to main content
GET
cURL
Use this endpoint to give a person or a model a wallet brief. It formats the same values as Trader context as Markdown. Use the JSON route when your client needs structured fields or conditional requests with an ETag.

Parameters

What the document holds

The document opens with the wallet’s name, one sentence of provenance, and the clock the numbers reflect. Under that come four sections, each written as a short bullet list. A section whose values are all missing is omitted rather than printed empty, so an untracked wallet gets a short document rather than a list of blanks. The document closes with a line saying which figures come from Polymarket and which 0xinsider computes.

Example

The document opens by naming the clock it reflects:

What it does not return

  • An ETag. Sending If-None-Match has no effect and there is no 304 on this route. Use the JSON route for a conditional read.
  • A 404 for a wallet 0xinsider does not track yet. You get a 200 and a short “not yet synced” document.
  • JSON. Parse the JSON route instead of this 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).

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

Path Parameters

address
string
required

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

Response

Trader context document (Markdown)

The response is of type string.