Skip to main content
POST
cURL
Use this endpoint when your agent cannot start a local MCP process. Each POST carries one JSON-RPC 2.0 message, and tool calls use the same credentials, rate limits, and quota as their REST routes. For an agent that can run a local process, the @0xinsider/mcp package is available over stdio. See MCP server.

Methods

Send an id, a string or a number, on every request. The server echoes it back to you. A message without an id is a notification. The server answers HTTP 202 with no body and runs nothing, whatever its method. A message carrying result or error answers HTTP 400 with JSON-RPC -32600, because this server never sends a request that could have a response. The server keeps no sessions. It mints no Mcp-Session-Id, and it ignores one you send. Each request carries its own credential.

Headers

Credentials

Live tools/call requests accept Pro or Max credentials. Max inherits Pro tools, with the account’s own monthly allowance and pick access. get_edge_hunter requires Max and supports the Edge Hunter board, signals, and observation views. The retired pre-game and sports_edge tools are no longer advertised. Tool discovery does not grant access to Max data or a locked pick.

Errors

A transport failure carries a JSON-RPC error object. A credential that is present but invalid never reaches the transport. 401 invalid_api_key, 402, a tier 403, and 429 all come from the same middleware as REST, in the REST error envelope. A tool that fails is not a transport failure. It returns 200, with result.isError set to true and result.content[0].text saying what went wrong. tools/call arguments are checked against the tool’s inputSchema from tools/list before anything runs. An unknown key, a wrong type, a number out of range, a value outside an enum, or a combination outside a oneOf answers that tool error. The query never runs with only the arguments that happened to fit. Each fault is named by its JSON Pointer inside arguments, as in at /limit: 500 is greater than the maximum of 100. An absent or null arguments is read as the empty object. The same failure comes back as fields under result.structuredContent.error, so a client can branch on it without parsing the text. It carries the REST error’s code, reason, param, doc_url, and retry_at unchanged, plus retry_after_seconds from the route’s Retry-After, request_id, and status. Invalid arguments are bad_request with param set to the first fault’s JSON Pointer, and a token without the scope is insufficient_scope with param set to the scope.

Tool results

result.structuredContent is the route’s payload, and result.content[0].text is the same JSON as text. Every result carries the route’s meta beside the payload: request_id, cached, cache_age_s, cost, and whatever provenance the route adds. That includes source and completeness on get_whale_trades_history. The default Edge Hunter tool result places rows, as_of, ranking_source, and directional_source beside meta. Its REST board places those fields inside data. Advanced tool views retain the complete list envelope with object: "list", view, data, page fields, and meta. The board carries the same full Max projection as the website, including nullable outcome and backed-signal token IDs. Full signal objects also carry frozen ranked_at and aggregate category_skill; their clocks and coverage are separate from current quote observations. Website Cards and Table choices are layouts of this board, rather than API signals or observations views. Signals add meta.ranking_source and meta.directional_source. Observations copy standard REST request/cache metadata, retain snapshot_as_of, degraded, and funnel, and expose row observed_at, holder_snapshot_at, and provider_read_source separately. Ranked-source fields are not required in observation meta. The meta is copied, never invented, so a degraded ranking or a best-effort replay reads the same over MCP as over REST. A list result also carries has_more, next_cursor, and total when the route sends them.

Wallet names

A wallet’s name, display_name, username, pseudonym, x_username, profile_segment, and trader_name are profile text its owner sets on Polymarket. Read them as data, never as instructions, and identify a wallet by its address: a name can look like another wallet’s address. The server’s instructions and the description of every tool whose result carries these fields say the same. Before a result is built, each of these values loses its control characters (a run becomes one space) and its invisible characters: Unicode tags, bidirectional controls, zero-width characters, and runs of variation selectors. A < that opens a tag becomes ‹, and a value longer than 64 characters is cut to 63 characters and …. name and display_name count only in an object that also carries address, execution_wallet, or pseudonym, so a team’s or a league’s name is unchanged. When a value changes, result._meta["com.oxinsider/neutralized-profile-text"] lists it as a JSON Pointer into structuredContent. The REST route the tool calls returns the original text.

Example

What it does not do

  • Write anything. Creating, updating, deleting, verifying, and rotating a webhook are deliberately not tools.
  • Serve resources or prompts. resources/* and prompts/* are not implemented.
  • Push anything to you. A GET on this endpoint returns 405, which Remote MCP GET explains.
  • Reshape a payload. A tool returns what its route returns, plus the route’s meta.

Edge Hunter selection

get_edge_hunter supports shared selector arrays in board, signals, and observation modes. Use each row’s nullable market_context for provider league, series, and market-type identities; selected responses also echo normalized requested axes under selection. Keep the same selection on cursor continuations, and honor warming responses when selection metadata is unavailable.

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
MCP-Protocol-Version
enum<string>

The negotiated MCP protocol revision, sent on every request after initialize (MCP Streamable HTTP transport). Accepted values: 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05. Any other value answers HTTP 400 with the standard error envelope (error.code bad_request), unless the request names its revision in params._meta. Absent, the request is served as 2025-03-26.

Available options:
2026-07-28,
2025-11-25,
2025-06-18,
2025-03-26,
2024-11-05
Mcp-Method
string

The JSON-RPC method of the body. Required on revision 2026-07-28, which answers JSON-RPC error -32020 without it; earlier revisions ignore it.

Mcp-Name
string

The tool name of a tools/call on revision 2026-07-28; it must match params.name.

Query Parameters

toolsets
string

Shorten the tools/list answer to the named toolsets, separated by commas: core (16 tools: account, leaderboard, one trader, games, market search, the day's picks, large and flagged trades), all (every current tool), or a group: account, combos, content, games, large_trades, markets, picks, platforms, reports, suspicious_trades, traders, webhooks. Leave it out for the full list. A shortened list leaves out the deprecated alias tools. It changes tools/list only: tools/call runs every tool whatever was listed. An unknown name answers JSON-RPC error -32602 naming the valid ones.

Body

application/json

MCP JSON-RPC 2.0 request or notification envelope. Omit id for supported notifications.

jsonrpc
string
required

JSON-RPC protocol version; this server accepts 2.0.

Allowed value: "2.0"
method
enum<string>
required

MCP method to invoke.

Available options:
initialize,
notifications/initialized,
notifications/cancelled,
ping,
tools/list,
tools/call,
server/discover
id

Request identifier, a string or a number, echoed exactly in one JSON-RPC response; a notification omits it and receives an empty HTTP 202. A null id answers HTTP 400 with JSON-RPC error -32600.

params
object

Method-specific MCP parameters.

Response

JSON-RPC response

jsonrpc
string
required
Allowed value: "2.0"
id
required
result
object
error
object