@0xinsider/mcp 3.19.0 → 3.20.0

package/README.md

@@ -55,6 +55,15 @@ received, followed by the hex-decoded nonce, with SHA-256 and compare the result
 `commitment_hash`. `0xinsider pick ledger` prints every published commitment in one
 document. Both reads are public and need no login or key.
 
+## Upgrade to 3.20.0
+
+Version 3.20 adds the record at the ask. `pick stats` and the `get_pick_of_the_day_stats`
+tool now return `ask_comparison`: the settled picks that recorded the best ask at
+publication (since 2026-10-17), valued at the midpoint the record uses and at that ask,
+each with units and ROI, before fees. It is in the default summary, and `sections`
+accepts `ask_comparison`. The record itself stays at the midpoint. Every other field,
+command, exit code and tool is unchanged.
+
 ## Upgrade to 3.19.0
 
 Version 3.19 treats wallet names the way the remote MCP server does. Tool results and

package/dist/constants.d.ts

@@ -1,7 +1,7 @@
 export declare const API_BASE_URL = "https://api.0xinsider.com";
 export declare const SITE_URL = "https://0xinsider.com";
 export declare const DEVELOPERS_URL = "https://0xinsider.com/developers";
-export declare const VERSION = "3.19.0";
+export declare const VERSION = "3.20.0";
 export declare const PACKAGE_NAME = "@0xinsider/mcp";
 export declare const SERVER_NAME = "0xinsider";
 export declare const API_KEY_ENV_VAR = "OXINSIDER_API_KEY";

package/dist/constants.js

@@ -14,7 +14,7 @@ export const DEVELOPERS_URL = `${SITE_URL}/developers`;
 // flow runs `cd mcp && npm ci` from a clean checkout, where `web/node_modules` need not
 // exist.
 // generated-package-version:start
-export const VERSION = "3.19.0";
+export const VERSION = "3.20.0";
 // generated-package-version:end
 export const PACKAGE_NAME = "@0xinsider/mcp";
 export const SERVER_NAME = "0xinsider";

package/dist/sdk/schema.d.ts

@@ -2814,11 +2814,11 @@ export type PickOfTheDay = {
     outcome?: "pending" | "win" | "loss" | "void";
     /** Pre-formatted SETTLEMENT STATUS for display: "Win" / "Loss" / "Void" / "Pending" -- the outcome enum above as a label. Convenience only; outcome is the source value. NOTE: this is the win/loss STATUS, not the backed side. The backed side is pick_outcome_label ("Belgium (-2.5)") -- a different field answering a different question. */
     outcome_display?: string;
-    /** The backed side phrased as a bet: a team for a moneyline (e.g. "Portugal"), the handicap line for a spread (e.g. "Belgium (-2.5)"), or "{team} to advance" for a knockout advancement market (e.g. "Spain to advance"). */
+    /** The backed side as a short label: a team for a moneyline (e.g. "Bengals"), the team and handicap for a spread (e.g. "Seahawks (-14.5)"), the line and side for a total (e.g. "O/U 38.5 (Under)"), or "{team} to advance" for a knockout advancement market (e.g. "Spain to advance"). */
     pick_outcome_label?: string;
     /** The Polymarket CLOB token id (ERC1155 asset id, decimal string) for the backed outcome; omitted when unavailable (e.g. unsynced markets). */
     token_id?: string;
-    /** The backed side phrased as a bet (e.g. "Portugal to win"). */
+    /** The backed side as the pick's headline reads it (e.g. "Bengals to win", "Seahawks (-14.5)", "O/U 38.5 (Under)"). */
     position?: string;
     /** One-line summary of which side sharp money is backing. On a pick dated 2026-08-12 or later it counts the S and A grade wallets the pick lists on the backed side, the sharp_wallet_count value, and names those grades: "26 S and A grade wallets on Alexander Shevchenko", or "1 S or A grade wallet on ...". The list can leave out wallets that hold the side. The site's "profitable wallets" counts the S, A and B grade wallets the pick lists, so its number can be larger for the same pick. A pick whose only recorded backing is its lead wallet reads "Recorded lead wallet on ...". Earlier picks, and a pick recorded without graded holders, keep the sentence recorded with them. Required on every item in `picks`: a current-day published pick whose required holder proof is not safely readable is listed in `proof_pending_picks` instead of being served with a partial success shape or a synthetic zero, and the route returns 503 read_model_warming only when no published pick has readable proof. */
     side_summary?: string;
@@ -2919,7 +2919,7 @@ export type PickOfTheDay = {
     disclaimer?: string;
     /** Entitled published picks whose holder proof is unreadable, ordered by rank. Unauthorized ranks appear only in locked_picks and cannot trigger proof warming. Read retry_at for the next read. */
     proof_pending_picks?: ProofPendingPickSlot[];
-    /** Optional full-response entry authorization. Missing or expired authorization cannot authorize an automated entry. */
+    /** Optional full-response entry authorization. The pick's release issues it once, only when a fresh check then finds the pick meets the selection standard in force at release and its current price still allows an entry. A pick released without one never gains one later, so read its absence as no automated entry for this pick, not as pending. Missing or expired authorization cannot authorize an automated entry. */
     entry_authorization?: PotdEntryAuthorization;
     /** Unauthorized unresolved published or scheduled ranks. Contains no game, provider identity, price, or identifying clock. Pro may upgrade to Max to open these ranks. */
     locked_picks?: {
@@ -2939,7 +2939,7 @@ export type PickOfTheDay = {
      * @deprecated
      */
     supersedes_pick_id: string | null;
-    /** Optional full-only lead wallet publication facts. Omitted on legacy picks or when the recorded evidence is unavailable. */
+    /** Optional full-only lead wallet publication facts: the profitable wallet whose position and record certified the pick when it was released. Many picks have no certified lead, and a pick released without one never gains one later. Also omitted on legacy picks or when the recorded evidence is unavailable in this response. */
     lead_backer?: PickLeadBacker;
     /** On the top level of today's set read. The instant until which today's list of published picks can still grow: present while another pick can still be added to the day, absent once the day is final. Absent for a past `date`, on `picks` items and on a `pick_id` read. A later pick is possible, not promised; schedule one read before this instant instead of polling. */
     more_picks_until?: string;
@@ -3006,6 +3006,8 @@ export type PickOfTheDay = {
     };
     /** When the pick was published: the recorded instant, the same one the archive returns for it. release_at is the scheduled release. Sent on every pick; absent with the other pick fields on a state=none body. */
     published_at?: string;
+    /** When outcome was LAST written to a settled value (RFC3339 UTC), the same instant the archive and the commitment ledger return for the pick. It moves with a corrected market re-mapping an already-settled pick. Omitted (not null) for a pending pick and for a pick that settled before the instant was recorded, so absence means the instant is unknown, never that the pick is unsettled -- outcome answers that. Additive and optional for mixed-version client compatibility. */
+    resolved_at?: string;
 };
 export type PickOfTheDayArchive = {
     /** Published Pick of the Day selections that have not been withdrawn, newest first by pick_date and then pick_rank within each product day. Withdrawn rows stay excluded after settlement. */
@@ -3849,6 +3851,23 @@ export type PickOfTheDayStats = {
         pick_id: string;
         pick_rank: number;
     }[];
+    ask_comparison: {
+        ask: {
+            roi_display: string | null;
+            roi_pct: number | null;
+            units: number | null;
+            units_display: string | null;
+        };
+        from_date: string | null;
+        from_date_display: string | null;
+        midpoint: {
+            roi_display: string | null;
+            roi_pct: number | null;
+            units: number | null;
+            units_display: string | null;
+        };
+        valued_decided: number;
+    };
 };
 /** The stats with `view=summary` or `sections`: only the named sections, listed in `sections`. `view=summary` names every section except `series`, `days`, `categories`, `months` and `voids`. */
 export type PickOfTheDayStatsSections = {
@@ -4289,6 +4308,23 @@ export type PickOfTheDayStatsSections = {
         pick_id: string;
         pick_rank: number;
     }[];
+    ask_comparison?: {
+        ask: {
+            roi_display: string | null;
+            roi_pct: number | null;
+            units: number | null;
+            units_display: string | null;
+        };
+        from_date: string | null;
+        from_date_display: string | null;
+        midpoint: {
+            roi_display: string | null;
+            roi_pct: number | null;
+            units: number | null;
+            units_display: string | null;
+        };
+        valued_decided: number;
+    };
 };
 /** A settled uncommitted pick's market, side and price. The same eight fields as PickOfTheDayCommitmentPayload, in the same key order, so a settled pick's side and price sit under payload whatever the entry's state. It is NOT a commitment: no hash was taken over it before the game, and it proves nothing about when the pick was made. */
 export type PickOfTheDayUncommittedPayload = {
@@ -4317,9 +4353,9 @@ export type PickSportsContext = {
     competition_label?: string;
     /** League logo URL (provider-owned). */
     league_logo: string | null;
-    /** The team mapped to the market's YES outcome, or the parent-event home/first team when event_matchup is true. */
+    /** The team mapped to the market's YES outcome, or the game's first team when event_matchup is true. To lay the two teams out in the game's order, read side_order. */
     yes_team: PickSportsTeam | null;
-    /** The team mapped to the market's NO outcome, or the parent-event away/second team when event_matchup is true. */
+    /** The team mapped to the market's NO outcome, or the game's second team when event_matchup is true. */
     no_team: PickSportsTeam | null;
     /** Provider game identifier (Polymarket Gamma gameId); omitted when the provider supplies none. */
     game_id?: number;
@@ -4327,14 +4363,16 @@ export type PickSportsContext = {
     event_matchup: boolean;
     /** Present only alongside event_matchup: the event team the binary leg is about (provider group_item_title matched to a matchup team, e.g. Belgium for "Will Belgium win?"), i.e. the winner on a Yes resolution. Omitted for teamless legs (draw, totals, prop). */
     event_subject_team?: PickSportsTeam;
-    /** The two teams as a single whole-game label, joined "<home> – <away>" (en-dash) in provider display order (e.g. "Portugal – Uzbekistan"). Composed server-side from the provider team names (no title/slug parsing). Present when both teams resolve a name; omitted for single-subject, teamless, or non-two-team contexts. */
+    /** Which of yes_team and no_team the game lists first, in Polymarket's order for the event (the order of its title: the away team first in US leagues, the home team first in soccer). yes_first when yes_team is the first team, no_first when no_team is. A spread's Yes side is the favorite, so it is often the game's second team. Lay the teams out in this order to show every pick on one game the same way; yes_team and no_team keep their Yes and No meaning. Omitted when the order is unknown: lay out yes_team first. */
+    side_order?: "yes_first" | "no_first";
+    /** The two teams as a single whole-game label, joined "<first> – <second>" (en-dash) in the game's order, the order side_order names (e.g. "LA Clippers – Phoenix Suns"), so every pick on one game carries the same title. Composed server-side from the provider team names (no title/slug parsing). Present when both teams resolve a name; omitted for single-subject, teamless, or non-two-team contexts. */
     matchup_title?: string;
 };
 /** A single sports team or competitor in a Pick of the Day market's sports context. Identity and score fields are provider-owned and nullable. The structured score fields (`sets`, `format`, `sets_won`) and the tennis fields (`headshot`, `headshot_revision`, `tour`) are backend-owned and are OMITTED rather than null when they do not apply, so a consumer must treat an absent key and a null the same way. */
 export type PickSportsTeam = {
     /** Team display label as it appears on the market outcome (e.g. "Portugal"). */
     label: string | null;
-    /** Abbreviated team label (e.g. "POR"). */
+    /** The team's abbreviation in upper case (e.g. "POR"), the same on every market of the game. A competitor Polymarket gives no abbreviation can carry its name here instead. */
     short_label: string | null;
     /** The name to show for this team or competitor, the same on every surface (e.g. "UCF Knights", "Oklahoma City Thunder", "Portugal"). `label` keeps the market outcome's own spelling. */
     full_name: string | null;
@@ -7125,10 +7163,10 @@ export interface OperationQuery {
     getPickOfTheDayStats: {
         /** full (default) is every section. summary returns view, sections and every section except the five that grow with the record: series, days, categories, months and voids. In summary and sections bodies hit_rate carries no series; series is its own top-level section. Ignored when sections is sent. Any other value returns 400 bad_request with error.param=view. */
         view?: "full" | "summary";
-        /** Exactly the sections to return, in the body's order whatever the request order. Repeatable and comma-separated: hit_rate, series, market_expectations, outcome_stats, days, categories, sports, tiers, months, price_bands, market_types, total_sides, streaks, records, voids. The body names them in sections and carries view=sections. An unrecognized name returns 400 bad_request with error.param=sections rather than being ignored. */
-        sections?: ("hit_rate" | "series" | "market_expectations" | "outcome_stats" | "days" | "categories" | "sports" | "tiers" | "months" | "price_bands" | "market_types" | "total_sides" | "streaks" | "records" | "voids")[];
+        /** Exactly the sections to return, in the body's order whatever the request order. Repeatable and comma-separated: hit_rate, series, market_expectations, outcome_stats, ask_comparison, days, categories, sports, tiers, months, price_bands, market_types, total_sides, streaks, records, voids. The body names them in sections and carries view=sections. An unrecognized name returns 400 bad_request with error.param=sections rather than being ignored. */
+        sections?: ("hit_rate" | "series" | "market_expectations" | "outcome_stats" | "ask_comparison" | "days" | "categories" | "sports" | "tiers" | "months" | "price_bands" | "market_types" | "total_sides" | "streaks" | "records" | "voids")[];
         /** Backward-compatible bracket alias for sections, for clients that emit array keys. Repeatable and comma-separated, with the same names. */
-        "sections[]"?: ("hit_rate" | "series" | "market_expectations" | "outcome_stats" | "days" | "categories" | "sports" | "tiers" | "months" | "price_bands" | "market_types" | "total_sides" | "streaks" | "records" | "voids")[];
+        "sections[]"?: ("hit_rate" | "series" | "market_expectations" | "outcome_stats" | "ask_comparison" | "days" | "categories" | "sports" | "tiers" | "months" | "price_bands" | "market_types" | "total_sides" | "streaks" | "records" | "voids")[];
     };
     getPlatforms: Record<string, never>;
     getPositionTimeline: {