> ## Documentation Index > Fetch the complete documentation index at: https://docs.kairos.trade/llms.txt > Use this file to discover all available pages before exploring further. # Search for a trader's public profile by wallet address > Fetches public profile information (display name, pseudonym, bio, avatar, X/Twitter handle, verification badge, associated user IDs) for a wallet address from the upstream provider. Provider is auto-detected from address format when omitted — Ethereum (0x...) addresses default to Polymarket and Solana addresses default to Kalshi; auto-detection maps **every** 0x address to Polymarket, so other EVM venues (Opinion, predictfun, ...) must pass `provider` explicitly. `provider`, when given, is validated against the central provider registry shared with `/trader-stats`; any registered provider is accepted, and non-Polymarket venues currently receive a synthetic (service-generated) profile rather than a live upstream fetch. This is a live provider read, not served from cached data. **Auth**: accepts an admin secret (`X-Admin-Secret`), an API key (`X-Client-Id` + `X-Api-Key` + `X-Api-Secret`), or a first-party JWT (Authorization header or `turnkey_session_jwt` cookie). No API-key scope is required — any valid credential can read a public profile. Rate-limited by the `heavy` group at 10 requests/minute, matching `/trader-stats`, because every call is a live upstream provider read. ## OpenAPI ````yaml /openapi/data-api.yaml get /search-traders openapi: 3.1.0 info: title: Kairos Data API version: 1.0.0 summary: >- The full Kairos data plane — markets, candles, trades, search, discover, sports, trader analytics, and PnL. description: | The Kairos Data API at `data.kairos.trade` is the platform's primary data plane: market metadata and prices, OHLCV candles, live venue trade proxies, normalized trade history, full-text search, discovery feeds, the sports catalog, public trader analytics, and account PnL. ## Authentication Most endpoints accept a Kairos **API key** (`X-Client-Id` + `X-Api-Key` + `X-Api-Secret`, all three) or a first-party session JWT. Endpoints tagged `public` (trader analytics, provider configs, several sports feeds) need no credentials at all. Some endpoints additionally require an API-key **scope** (`trade:read`, `position:read`) — stated per operation. For high-volume market-data consumption (candles/trades/metadata at scale), prefer the dedicated **Market Data API** at `md.kairos.trade` — it has higher budgets, ETag caching, and a binary candle format. ## Rate limits Rate limits use a sliding window keyed on the authenticated user (JWT `sub`) or, for anonymous callers, the trusted client IP. Routes belong to a named **bucket** (`x-kairos-bucket`) whose per-minute budget is shared by every route in it; routes with no bucket run under the service default of 100/minute. `x-kairos-rate-limit` states the bucket's compile-time default — operators can raise or lower a bucket at runtime, so treat the documented number as the baseline, not a contract. 429 responses carry `Retry-After` and `X-RateLimit-*`. ## Conventions - Prices are on the **0–100 cents scale** unless a field says otherwise (trader-analytics position/trade prices use the 0–1 scale; each field's description states its scale). - Errors: `{"detail": ""}` for handler errors; FastAPI's standard validation envelope for 422s. Errors surfaced from a venue adapter instead use `{"error", "provider", "operation", "message"}` — see `DataProviderError`. Unhandled failures always return the generic 500 body; internal details are logged, never returned. - Every request body is capped at 8 MiB service-wide (413). contact: name: Kairos url: https://app.kairos.trade/docs/api-reference termsOfService: https://kairos.trade/terms servers: - url: https://data.kairos.trade description: Production - url: https://staging-data.kairos.trade description: Staging security: - apiKeyClientId: [] apiKeyKey: [] apiKeySecret: [] paths: /search-traders: get: tags: - Trader Analytics summary: Search for a trader's public profile by wallet address description: > Fetches public profile information (display name, pseudonym, bio, avatar, X/Twitter handle, verification badge, associated user IDs) for a wallet address from the upstream provider. Provider is auto-detected from address format when omitted — Ethereum (0x...) addresses default to Polymarket and Solana addresses default to Kalshi; auto-detection maps **every** 0x address to Polymarket, so other EVM venues (Opinion, predictfun, ...) must pass `provider` explicitly. `provider`, when given, is validated against the central provider registry shared with `/trader-stats`; any registered provider is accepted, and non-Polymarket venues currently receive a synthetic (service-generated) profile rather than a live upstream fetch. This is a live provider read, not served from cached data. **Auth**: accepts an admin secret (`X-Admin-Secret`), an API key (`X-Client-Id` + `X-Api-Key` + `X-Api-Secret`), or a first-party JWT (Authorization header or `turnkey_session_jwt` cookie). No API-key scope is required — any valid credential can read a public profile. Rate-limited by the `heavy` group at 10 requests/minute, matching `/trader-stats`, because every call is a live upstream provider read. operationId: searchTraders parameters: - name: address in: query required: true schema: type: string description: Wallet address to search for (any non-empty string; trimmed). example: '0x1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b' - name: provider in: query required: false schema: type: string description: > Provider override. Auto-detected from address format (0x -> polymarket, Solana -> kalshi) if omitted. example: polymarket responses: '200': description: >- Trader search result. `profile` is null if no profile was found; `error` carries a provider-supplied message in that case. content: application/json: schema: $ref: '#/components/schemas/TraderSearchResponse' '400': description: Missing/blank `address` or an invalid `provider`. '401': $ref: '#/components/responses/DataUnauthorized' '403': $ref: '#/components/responses/DataForbidden' '422': $ref: '#/components/responses/DataValidationError' '429': $ref: '#/components/responses/DataRateLimited' '502': description: Upstream provider error searching for the trader. components: schemas: TraderSearchResponse: type: object description: > Result of a trader-profile search. `profile` is null (with `error` populated) when the provider found no profile for the address. required: - provider - address - profile - error properties: provider: type: string example: polymarket address: type: string example: '0x1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b' profile: allOf: - $ref: '#/components/schemas/TraderSearchProfile' nullable: true error: type: string nullable: true description: Provider-supplied error message when no profile was found. example: null TraderSearchProfile: type: object description: Public trader profile fields returned by the upstream provider. required: - displayUsernamePublic - verifiedBadge - users properties: proxyWallet: type: string nullable: true example: '0x1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b' name: type: string nullable: true example: Jane Trader pseudonym: type: string nullable: true example: QuietFalcon-2201 bio: type: string nullable: true example: Macro and elections. profileImage: type: string nullable: true example: https://cdn.polymarket.com/avatars/jane.png xUsername: type: string nullable: true example: janetrades verifiedBadge: type: boolean displayUsernamePublic: type: boolean createdAt: type: string format: date-time nullable: true example: '2023-11-02T18:20:44Z' users: type: array items: $ref: '#/components/schemas/TraderSearchUserInfo' DataError: type: object description: Handler error envelope (FastAPI HTTPException). required: - detail properties: detail: type: string description: Human-readable error message. example: Invalid provider TraderSearchUserInfo: type: object description: >- An associated Polymarket user record linked to a profile (e.g. multi-role accounts). required: - id - creator - mod properties: id: type: string example: usr_polymarket_884211 creator: type: boolean description: Whether this user record has market-creator privileges. mod: type: boolean description: Whether this user record has moderator privileges. responses: DataUnauthorized: description: > No valid credential presented — missing/invalid API-key headers, or an invalid/expired session token. content: application/json: schema: $ref: '#/components/schemas/DataError' example: detail: Not authenticated DataForbidden: description: > Authenticated but not permitted. Three distinct causes: the session user is not invited (`Invite required`), the API key lacks the operation's scope, or API-key access to the requested venue is switched off (`API access is disabled for `). Admin and API-key callers bypass the invite check; session and admin callers bypass scope and venue checks. content: application/json: schema: $ref: '#/components/schemas/DataError' example: detail: Invite required DataValidationError: description: Request failed FastAPI parameter validation. content: application/json: schema: type: object required: - detail properties: detail: type: array description: >- One entry per failed field, with location, message, and error type. items: type: object additionalProperties: true DataRateLimited: description: > Rate limit exceeded for this route's sliding window, keyed on the session `sub` when authenticated and on the trusted client IP otherwise. Honor `Retry-After`. A per-API-key data ceiling (set per credential) rejects with `{"detail": "API key data rate limit exceeded"}` instead of the `error` envelope below. headers: Retry-After: schema: type: integer X-RateLimit-Limit: schema: type: integer X-RateLimit-Remaining: schema: type: integer X-RateLimit-Reset: schema: type: integer content: application/json: schema: type: object properties: error: type: string example: 'Rate limit exceeded: 100 per 1 minute' securitySchemes: apiKeyClientId: type: apiKey in: header name: X-Client-Id description: >- Credential client id (`kairos_ck_...`). Must be sent together with X-Api-Key and X-Api-Secret. apiKeyKey: type: apiKey in: header name: X-Api-Key description: 64-char hex API key. apiKeySecret: type: apiKey in: header name: X-Api-Secret description: 64-char hex API secret. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.