Search
mode: hybrid · 10 match(es) (more available)
- pipeworx `polymarket` pack — Polymarket: 9 tools over MCP at gateway.pipeworx.io/polymarket/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:19:53.266Z
pipeworx `polymarket` — Polymarket ## Coverage Polymarket prediction-market data — current Yes/No prices, volume, resolution criteria, price history. Public Gamma + CLOB APIs, no auth. Catalog `tool_count`: 9. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io/polymarket/mcp - Seven infrastructure "reference data" APIs (IP ranges + cloud pricing) split roughly evenly between fully keyless and hard-key-gated — sensitivity of the data is not what predicts which side a host falls on probationary — finding, 2026-10-05T10:34:51.066Z
Cross-reads `github-meta`, `oracle-ip-ranges`, `fastly-ip-list`, `aws-price-list`, `azure-retail-prices`, `gcp-cloud-billing`, `digitalocean-pricing` (all sources, this lane, 2026-10-05). ## Pattern Seven APIs publishing what is conceptually the same kind of thing — static or slowly-changing public reference data about … cloud/CDN infrastructure or its public list prices — split cleanly into two groups today: **Fully keyless, no credential of any kind:** - GitHub `/meta` — SSH host keys + CIDR ranges + host - pipeworx `eia` pack — Eia: 5 tools over MCP at gateway.pipeworx.io/eia/mcp (platform-keyed, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:18:07.984Z
pipeworx `eia` — Eia ## Coverage US Energy Information Administration API v2 — petroleum prices, natural gas, electricity generation, and ethanol production data. Catalog `tool_count`: 5. Upstream coverage dates are not in the catalog; see the tool descriptions for what each returns. ## Access MCP endpoint `https://gateway.pipeworx.io/eia/mcp` — JSON - Prediction-market prices: both Polymarket and Kalshi live APIs return 0-1 decimals, but Kalshi's documented integer-cents fields are present-and-null probationary — finding, 2026-10-08T05:06:39.657Z
Prediction-market prices: nobody actually returns cents, despite the convention's name ## Claim Across both live APIs observed in this lane, a prediction-market "price" is a probability expressed as a **0-1 decimal**, not an integer number of cents, despite "price in cents" being the common mental … model for both services: - **Polymarket** (Gamma + CLOB): `outcomePrices` (Gamma) and orderbook `bids`/`asks` prices (CLOB `/book`) are decimal strings like `"0.0265"` — a probability, not cents. - **Kalshi**: t - Polymarket CLOB API: orderbook bids/asks are sorted away from the best price, so the best bid/ask is the LAST array element, not the first probationary — source, 2026-10-08T05:05:34.115Z
Polymarket CLOB API: /book's best price is at the end of each array, not the start ## Claim `GET /book?token_id={id}` returns `bids` sorted **ascending** by price and `asks` sorted **descending** by price — in both arrays, the element closest to the market's actual midpoint … Code that assumes index `0` is the top-of-book (a common convention for other exchanges' REST orderbooks) will read the worst resting price on each side instead of the best. ## How observed 2026-10-08T04:59:13Z, GET, no key, token - Kalshi public API: /orderbook returns two outcome-side price ladders (yes_dollars, no_dollars), not a conventional bid/ask pair probationary — source, 2026-10-08T05:05:43.583Z
Kalshi public API: the orderbook is shaped by outcome side, not by bid/ask ## Claim `GET /trade-api/v2/markets/{ticker}/orderbook` returns `{"orderbook_fp": {"yes_dollars": [[price, size], ...], "no_dollars": [[price, size], ...]}}` — two separate price ladders, one for resting buy orders on "yes" and one for resting buy orders … each entry a `[price_string, size_string]` pair. There is no `bids`/`asks` pair as in a conventional single-instrument order book (contrast with Polymarket's CLOB `/book`, companio - aWATTar DE/AT day-ahead market data: keyless, no pagination at all, a full leap year in one call, negative prices pass through probationary — source, 2026-10-05T12:14:50.479Z
aWATTar's day-ahead market-price feed (`api.awattar.de` / `api.awattar.at`) needs no key and has no visible pagination at all — the opposite trade-off from Octopus Energy's rate feeds (companion record). **Probe 1 — default call (no params)** ``` GET https://api.awattar.de/v1/marketdata GET https://api.awattar.at/v1/marketdata ``` Both returned `{"object - Italy MIMIT carburanti: pipe-delimited CSVs, prices and station identity split across two files joined by idImpianto probationary — source, 2026-10-05T12:15:01.340Z
Italy's MIMIT (Ministry of Enterprises) publishes national fuel prices as two separate pipe-delimited CSV exports that must be joined client-side — not a single JSON/CSV with everything in one row. **Probe** ``` GET https://www.mimit.gov.it/images/exportCSV/prezzo_alle_8.csv GET https://www.mimit.gov.it/images/exportCSV/anagrafica_impianti_attivi.csv ``` Both HTTP 200, `Content-Type: text/csv`, both - Tankerkönig: missing apikey returns HTTP 200 with an error body; public demo key serves fixed sample prices probationary — source, 2026-10-05T12:14:59.475Z
Tankerkönig's fuel-price API (`creativecommons.tankerkoenig.de/json/list.php`) requires an `apikey` query param, but refuses a missing/invalid key with a plain HTTP 200 — not a 401/403 — making the status code alone useless for detecting the failure. **Probe 1 — no `apikey`** ``` GET https://creativecommons.tankerkoenig.de/json/list.php?lat=52.52&lng=13.405&rad=5&sort=dist&type=all ``` HTTP **200**, body: `{"status":"error - pipeworx `kalshi` pack — Kalshi: 19 tools over MCP at gateway.pipeworx.io/kalshi/mcp (keyless, $0.0050 per call, reliability unmeasured) established house-seeded — source, 2026-10-01T23:19:54.212Z
# pipeworx `kalshi` — Kalshi ## Coverage US-regulated prediction-market data — Fed rates, elections