@pipeworx/polymarket-us

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/polymarket-us’s. Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 5

Market data from Polymarket US (polymarket.us) — the CFTC-regulated, US-licensed prediction-market exchange. This is a SEPARATE venue from the offshore Polymarket platform (see the polymarket pack) and from Kalshi (see the kalshi pack): different company, different markets, different slugs. A slug from one venue never resolves on another, and every response here carries venue: "polymarket-us" plus data_as_of so a caller comparing across packs never silently mixes venues.

Upstream: https://gateway.polymarket.us (docs: https://docs.polymarket.us/api-reference/introduction). This is Polymarket US’s public market-data host — no auth, no account, no API key for any endpoint this pack calls. A separate authenticated host, api.polymarket.us, handles order placement and portfolio/account data; this pack is read-only market data only, same posture as polymarket and kalshi.

Tools

All five need a market slug, which polymarket_us_search returns.

Auth

Keyless. The gateway.polymarket.us market-data endpoints need no API key, account or authentication of any kind — verified live, including from a Cloudflare Workers edge location (wrangler dev --remote), since the sibling kalshi pack discovered its upstream filters Cloudflare egress on some endpoints and this one does not share that problem.

Data sources

• GET /v1/search — full-text search across events/markets.
• GET /v1/markets — filterable market listing (used for category/volume browsing when polymarket_us_search is called without a query).
• GET /v1/markets/{slug}/bbo — best bid/offer (lightweight top-of-book).
• GET /v1/markets/{slug}/book — full order book + session stats.
• GET /v1/price-history?symbol={slug}&fidelity=…&fixedInterval=… — historical Yes/No display prices.
• GET /v1/markets/{slug}/settlement — settlement price; 404s until the market resolves (this pack reports that as settled: false, not an error).

Notes

• Price history’s longPrice/shortPrice (mapped here to yes_price / no_price) are display prices — yes_price is normally derived from the best ask and no_price from one minus the best bid — so they preserve the bid/ask spread and CAN sum to more than 1.0. That is expected, not a data error.
• The settlement endpoint returns a price only, no timestamp. Resolution- audit integration (fleet #1909) is explicitly out of scope for this pack — it would need (a) a stable per-market settlement timestamp, which this API does not expose, and (b) a bulk “settled since <date>” filter, which /v1/markets also does not have (only a boolean closed flag) — without one, auditing settlements means polling every known slug.
• /v1/search has no category filter (only seriesIds, marketType, time-range and status). polymarket_us_search’s category argument is therefore browse-mode only (routes to /v1/markets) and is silently ignored when query is set — the tool description says so.

Tools

• polymarket_us_search — Polymarket US markets matching a keyword, or the highest-volume open markets, each with live prices.
• polymarket_us_bbo — The best bid and ask for one Polymarket US market, with top-of-book depth and state.
• polymarket_us_book — The live bid/ask depth ladder and session stats for one Polymarket US market.
• polymarket_us_price_history — How a Polymarket US market’s Yes/No display prices moved over time, as a timestamped series.
• polymarket_us_settlement — The final settlement price for one Polymarket US market, once it has resolved.