Polymarket Scraper - Prediction Market Odds API
Pricing
from $1.75 / 1,000 results
Polymarket Scraper - Prediction Market Odds API
Polymarket unofficial API alternative: scrape events, odds, sports scores, AI analysis and tweet signals. Export prediction market data to CSV/JSON.
Pricing
from $1.75 / 1,000 results
Rating
0.0
(0)
Developer
Logiover
Maintained by CommunityActor stats
2
Bookmarked
74
Total users
3
Monthly active users
8 days ago
Last modified
Categories
Features
Share
📈 Polymarket Scraper — Prediction Market Odds API, Live Sports Scores, AI Analysis & Twitter Signals
The most comprehensive Polymarket data extractor on Apify. Scrape every active Polymarket event, every sports market with live scores, every AI-generated betting analysis, and the high-significance Twitter signal feed — all in one Actor. It is the unofficial Polymarket odds & prediction market data API you can run without an account, without a wallet, and without writing a single line of scraping code.
Polymarket is the dominant on-chain prediction market with billions in cumulative volume across politics, sports, crypto, and world events. This Actor turns its live surface into structured, export-ready data: market-level odds (outcomes, prices, spreads, liquidity, and volumes at 5m / 1h / 6h / 24h / all-time), live sports games (home/away teams with logos, scores, period, game status), per-event AI betting analysis (recommended option, rationale, market context, key data, X sentiment), and a curated Twitter activity feed where every tweet is tagged with the exact prediction-market events it moves. No login, no API key, no rate-limit headaches — one clean dataset you can pull as JSON, CSV, or Excel.
🏆 Why this Polymarket scraper?
4 pluggable feeds in one run · every active event, market & outcome · live sports scores · AI betting rationale · tweet → market impact map · volumes at 5m/1h/6h/24h/all · no API key / no wallet / no login · unofficial Polymarket odds API alternative · export to JSON / CSV / Excel
✨ What this Actor does
- 📊 Every active event & market — pulls all live Polymarket events with markets, outcomes, prices, spreads, liquidity, and multi-window volumes (
volume5m,volume1h,volume6h,volume24h,volumeAll). - 🎯 Outcome-level odds — explode each market into individual outcomes (Yes / No / team A / team B) with
outcomePrice,outcomeBestAsk,outcomeBestBid, and implied chance. - 🏟️ Live sports scores — sports markets enriched with
homeTeamName/awayTeamName(plus logos), livescore,period,gameStatus,gameType, andgameEnded. - 🤖 AI betting analysis — per-event LLM analysis:
aiBettingOption,aiBettingRationale,aiContextAnalysis,aiKeyDataEvidence, andaiXSentiment. - 🐦 Twitter signal feed — a curated activity feed where each tweet carries a
tweetSignificancescore (0–100) and atweetEventsmap linking it to the events, markets, probabilities, and outcomes it affects. - 🔀 Four pluggable feeds — toggle
events_rank,sports,twitter_activity, andai_analysisindependently; every row carries a_kinddiscriminator so mixed exports stay clean. - 🔎 Built-in filtering — drop low-volume events with
minVolume24hUsd, keep only live games withonlyLive, and filter tweets by significance or category. - 🧩 Flatten or nest —
explodeMarketsandexplodeAssetsgive you one-row-per-event, one-row-per-market, or one-row-per-outcome for spreadsheets and databases. - 🔑 No auth, no wallet — reads only public prediction-market data through a clean aggregator surface; no API key, token, or login required.
- 📤 Export anywhere — every run writes to an Apify dataset you can download as JSON, CSV, or Excel, or stream via the REST API and webhooks.
🚀 Quick start (3 steps)
- Configure — pick which feeds you want in
feeds(defaults toevents_rank+sports+twitter_activity). Optionally setminVolume24hUsd,onlyLive, ortwitterMaxItems. - Run — click Start. The Actor fetches every enabled feed in parallel and streams rows into the dataset.
- Get your data — download the results as JSON, CSV, or Excel from the Output / Dataset tab, or pull them via the API and pipe them into your dashboard, bot, or database.
📥 Input
Configure the run with a handful of fields — the only thing you really need to decide is which feeds to pull. Here are three ready-to-run scenarios:
Scenario A — Live odds + sports scores dashboard
{"feeds": ["events_rank", "sports"],"explodeMarkets": true,"explodeAssets": true,"onlyLive": true,"minVolume24hUsd": 1000}
Scenario B — AI-driven betting bot (events auto-feed the AI analysis)
{"feeds": ["events_rank", "ai_analysis"],"explodeMarkets": true,"minVolume24hUsd": 5000,"aiAnalysisType": 1}
Scenario C — High-significance politics tweet alerts
{"feeds": ["twitter_activity"],"twitterMaxItems": 200,"minTwitterSignificance": 70,"twitterCategories": ["2", "100265"]}
| Field | Type | Description |
|---|---|---|
feeds | array | Which feeds to fetch: events_rank (all active events + series), sports (markets with live scores), twitter_activity (curated tweet feed), ai_analysis (per-event AI analysis). Default ["events_rank","sports","twitter_activity"]. |
explodeMarkets | boolean | One row per market within an event (an event with 5 markets → 5 rows). When off, markets stay nested. Default true. |
explodeAssets | boolean | One row per outcome (Yes/No/team) within a market. Default true. |
twitterMaxItems | integer | Cap on twitter_activity items (paginated 10 per page). ~100 ≈ 1 min. Default 100. |
minTwitterSignificance | integer | Drop tweets below this significance score (0–100). Default 0. |
twitterCategories | array | Polymarket category IDs to keep in the tweet feed. Empty = all. |
aiAnalysisSlugs | array | Event slugs to run AI analysis on. Auto-filled from events_rank when both feeds run. |
aiAnalysisType | integer | AI analysis variant ID. 1 is the standard betting-recommendation analysis. Default 1. |
minVolume24hUsd | number | Drop events / markets with 24h volume below this threshold. Default 0. |
onlyLive | boolean | Sports feed only: keep games where liveStatus is true. Default false. |
useProxy | boolean | Route requests through Apify Proxy (strongly recommended). Default true. |
proxyConfiguration | object | Apify Proxy config. Residential group is recommended for the highest success rate. |
maxConcurrency | integer | Max parallel API calls (1–10). 3–5 is safe. Default 3. |
Additional input fields
These optional fields are also available in the input form and API:
| Field | Type | Default | Description |
|---|---|---|---|
eventsStatus | string | "active" | Which Polymarket events to include in the events_rank feed by resolution status. |
eventsOrderBy | string | "volume24h" | How to rank events in the events_rank feed. |
📤 Output
Every run writes one row per event, market, outcome, sports game, tweet, or AI analysis — all distinguished by the _kind field. Here is a trimmed, realistic sample of the main row kinds (fields shown are exactly those the Actor emits):
[{"_kind": "event","seriesSlug": "presidential-election-winner-2028","seriesTitle": "2028 Presidential Election Winner","eventSlug": "trump-xi-summit-what-will-china-announce-by-may-22","eventTitle": "Trump-Xi Summit: What will China announce by May 22?","eventDescription": "Resolves YES if an official Chinese government announcement is made before the deadline.","eventIcon": "https://polymarket-upload.s3.us-east-2.amazonaws.com/trump-xi.png","exchange": "polymarket","tagIds": ["2", "100265"],"marketId": "0xecbc0f0a1b4e...","marketQuestion": "Will China announce a Boeing aircraft purchase?","marketGroupItem": "Boeing Aircraft Purchase","outcome": "Yes","outcomePrice": "0.5","outcomeBestAsk": "0.51","outcomeChance": "0.5","price": "0.5","spread": "0.02","liquidity": "184203.55","volume5m": "1204.10","volume1h": "8801.42","volume6h": "20551.88","volume24h": "25698.89","volumeAll": "412887.03","endTimestamp": "2026-05-22T23:59:00.000Z","liveStatus": "false","resolutionSource": "https://www.reuters.com/","scrapedAt": "2026-07-06T12:00:00.000Z"},{"_kind": "sports","eventSlug": "atp-carabelli-kecmanovic-2026-05-15","eventTitle": "Valencia: Camilo Ugo Carabelli vs Miomir Kecmanovic","homeTeamName": "Camilo Ugo Carabelli","awayTeamName": "Miomir Kecmanovic","homeTeamLogo": "https://polymarket-upload.s3.us-east-2.amazonaws.com/country-flags/arg.png","awayTeamLogo": "https://polymarket-upload.s3.us-east-2.amazonaws.com/country-flags/srb.png","score": "0-1","period": "S1","gameStatus": "in_progress","gameType": "tennis","gameEnded": "false","thesportsMatchId": "9y2xk8mob7d4qjp","marketId": "0x9439f1eaac30c73e9780a5eebedcd9b1a7a7a6d429cd15ebba69672b6877e757","marketQuestion": "Camilo Ugo Carabelli vs Miomir Kecmanovic — Moneyline","outcome": "Camilo Ugo Carabelli","outcomePrice": "0.385","volume24h": "26600.28","totalVolume": "26702.56","scrapedAt": "2026-07-06T12:00:00.000Z"},{"_kind": "twitter_activity","tweetId": "2055259399174619490","tweetUserHandle": "MOSSADil","tweetUserName": "Mossad Commentary","tweetUserVerifiedType": "blue","tweetText": "NEW—President Trump says he may lift sanctions on Chinese companies buying Iranian oil…","tweetTimestamp": "2026-07-06T11:10:00.293Z","tweetSignificance": "95","tweetCategory": ["2", "100265"],"tweetEvents": [{"eventSlug": "trump-xi-summit-what-will-china-announce-by-may-22","eventTitle": "Trump-Xi Summit: What will China announce by May 22?","marketTitle": "Boeing Aircraft Purchase","marketId": "0xecbc0f0a1b4e...","volume24h": 25698.89,"probability": 0.5,"outcome": "Yes"}],"tweetUrl": "https://x.com/MOSSADil/status/2055259399174619490","scrapedAt": "2026-07-06T11:10:00.000Z"},{"_kind": "ai_analysis","eventSlug": "trump-xi-summit-what-will-china-announce-by-may-22","aiStatus": "SUCCESS","aiUpdatedAt": "2026-07-06T07:13:19.000Z","aiBettingOption": "Boeing Aircraft Purchase: Buy No","aiBettingRationale": "Summit concluded without an official Chinese announcement on Boeing purchases…","aiContextAnalysis": "The Trump-Xi summit in Beijing aimed to stabilize trade amid Iran tensions…","aiKeyDataEvidence": "Reuters: pre-summit, both sides eyed tariff cuts on non-sensitive imports…","aiXSentiment": "Hype around Trump securing 200 Boeing jets and Iran cooperation from Xi…"}]
Additional output fields
These fields are also present in the dataset:
| Field | Type | Description |
|---|---|---|
eventTitleTrans | string | Upstream translated event title when available. |
endTimestampMs | number | Raw numeric upstream event end timestamp. |
seriesRecurrence | string | Recurrence interval reported for the event series. |
maxChance | number | Highest outcome probability reported for the event. |
maxSpread | number | Maximum bid/ask spread reported for the event. |
liveStreamUrl | string | Event live-stream URL when supplied upstream. |
cryptoCurrentPrice | number | Current reference-asset price for crypto threshold events. |
cryptoPriceToBeat | number | Resolution threshold price for crypto events. |
gameElapsed | string | Upstream elapsed-time label for a sports game. |
gameClockStartAt | string | Game clock start as an ISO-8601 timestamp. |
gameClockEndAt | string | Game clock end as an ISO-8601 timestamp. |
gameEndAt | string | Scheduled or actual game end as an ISO-8601 timestamp. |
homeTeamColor | string | Home team color value reported upstream. |
homeTeamAbbr | string | Home team abbreviation. |
awayTeamColor | string | Away team color value reported upstream. |
awayTeamAbbr | string | Away team abbreviation. |
marketIcon | string | Market icon URL when available. |
marketStatus | string | Upstream market status. |
marketEndTimestamp | string | Market end time as an ISO-8601 timestamp. |
marketGroupItemTrans | string | Translated grouped-market label when supplied upstream. |
marketResolutionSource | string | Market-level resolution source URL or text. |
marketResolvedAssetId | string | Asset/token identifier selected when the market resolves. |
marketLiveStartAt | string | Market live-start time as an ISO-8601 timestamp. |
marketSportsType | string | Sports wager/market type reported upstream. |
marketLine | number | Numeric line or handicap for the market. |
marketGroupItemThreshold | number | Numeric threshold for a grouped market item. |
marketRewardsDailyRate | number | Daily liquidity-reward rate reported for the market. |
marketRewardsMinSize | string | Minimum reward-eligible order size, retained as an upstream precision string. |
marketRewardsMaxSpread | string | Maximum reward-eligible spread, retained as an upstream precision string. |
marketRewardsAmount | string | Market reward amount, retained as an upstream precision string. |
marketEnableOrderBook | boolean | True only when the upstream market enables its order book. |
price5m | number | Market price approximately five minutes earlier. |
price1h | number | Market price approximately one hour earlier. |
price6h | number | Market price approximately six hours earlier. |
price24h | number | Market price approximately 24 hours earlier. |
outcomeTrans | string | Translated outcome label when supplied upstream. |
outcomeTokenId | string | Polymarket token identifier for the outcome. |
seriesVolume5m | number | Series volume in the last five minutes, in USD. |
seriesVolume1h | number | Series volume in the last hour, in USD. |
seriesVolume6h | number | Series volume in the last six hours, in USD. |
seriesVolume24h | number | Series volume in the last 24 hours, in USD. |
seriesVolumeAll | number | Series all-time volume in USD. |
currentEventSlug | string | Current event slug on a recurring series row. |
currentEventTitle | string | Current event title on a recurring series row. |
currentEventStatus | string | Current event status on a recurring series row. |
currentEventEndAt | string | Current event end time as an ISO-8601 timestamp. |
currentEventLiveStartAt | string | Current event live-start time as an ISO-8601 timestamp. |
currentEventVolume24h | number | Current series event volume in the last 24 hours, in USD. |
currentEventLiquidity | number | Current series event liquidity in USD. |
id | string | Upstream twitter_activity record identifier. |
originTweetId | string | Original status identifier for repost/reply activity. |
tweetUserId | string | X/Twitter author identifier. |
tweetUserAvatar | string | X/Twitter author avatar URL. |
tweetOriginUserHandle | string | Original author's handle for repost/reply activity. |
tweetOriginUserName | string | Original author's display name for repost/reply activity. |
tweetType | string | Upstream tweet type. |
activityType | string | Upstream activity type. |
tweetThumbnails | array | Media thumbnail URLs or objects reported for the tweet. |
tweetTimestampMs | number | Raw numeric timestamp reported by the activity feed. |
tweetPlatform | string | Source-platform label reported by the activity feed. |
aiRawContent | string | Raw AI-analysis content returned upstream for traceability. |
💡 Use cases
- 📉 Prediction-market trading dashboards — power your own UI with live event, market, and outcome odds refreshed every minute.
- 🗳️ Election & politics forecasting — pull political-event markets on a schedule and build a real-time "structured pollster" view like ElectionBettingOdds, but live.
- ⚽ Sports betting analytics — live odds and live scores in a single export, ready for arbitrage or model backtesting.
- 🤖 AI-driven betting bots — feed
aiBettingOption+ currentpriceinto a buy / no-buy decision pipeline. - 📰 News ↔ market correlation — the Twitter feed shows which tweets are moving which markets, with probability shifts attached.
- 🧪 Research & ML datasets — labelled Polymarket events × tweets × AI takes for quantitative and NLP research.
👥 Who uses it
Quant & prop traders · sports-betting analysts · election forecasters · crypto and Web3 builders · trading-bot developers · data journalists · hedge-fund researchers · ML engineers building market-signal datasets · newsletter and Substack authors
💰 Pricing
This Actor uses Apify's pay-per-result model — you pay for the \1 it \2, with no separate platform fees and no monthly subscription. Narrow runs (a single feed, filtered by volume) are extremely cheap; full nightly bundles across all four feeds cost more because they emit far more rows. See the Pricing tab on the Actor's Apify page for exact, up-to-date figures, and use maxResults-style controls (twitterMaxItems, minVolume24hUsd, onlyLive) to keep runs lean.
❓ Frequently Asked Questions
Is this a Polymarket API alternative?
Yes — it's an unofficial Polymarket API alternative. Instead of stitching together prediction-market endpoints yourself, you get structured events, odds, sports scores, AI analysis, and tweet signals in one Apify run, with no auth required.
Can I use it without an API key or login?
Yes. The Actor needs no login, no wallet, and no API key. It reads only public Polymarket events, live odds, and sports scores, making it a drop-in Polymarket odds data extraction tool.
How do I export Polymarket data to CSV or JSON?
Every run writes to an Apify dataset you can download as CSV, JSON, or Excel, or pull via the dataset REST API — so you can scrape Polymarket odds and export prediction-market data to CSV/JSON directly, no code required.
Is it legal to scrape Polymarket odds?
The Actor only accesses publicly available prediction-market data — the same information any visitor can see. It does not log in, place trades, or touch private account data. You are responsible for complying with the source's Terms of Service and applicable law in your jurisdiction. Nothing here is financial advice.
How much data can I get in one run?
A typical events_rank pull returns 50–200 active events plus 20–30 series; sports adds ~50–100 live/upcoming games; twitter_activity is capped by twitterMaxItems. With markets and outcomes exploded, a full run easily produces thousands of rows.
What's a Polymarket "event" vs "series"?
An event is a single resolvable market (e.g. "Will China announce X by May 22"). A series is a recurring sequence of events (e.g. a "BTC Up or Down 5m" series spawns a new event every 5 minutes). The _kind field tells them apart.
What does tweetSignificance mean?
It's a 0–100 score of how impactful a tweet is for prediction markets. High-significance tweets (95+) typically move odds; use minTwitterSignificance to keep only the market-movers.
How is the AI analysis generated?
An LLM is run over the event description, recent news, and X sentiment to produce a structured betting recommendation (aiBettingOption, aiBettingRationale, and supporting context). Treat it as a research input, not financial advice — quality varies by event.
Can I pass my own event slugs to the AI analysis?
Yes — set aiAnalysisSlugs: ["slug-1", "slug-2"] to analyze specific events, or leave it empty and enable events_rank so the Actor auto-fills slugs for you.
How fresh is the odds data?
Each run captures a live snapshot plus 5m / 1h / 6h / 24h rolling aggregates. For a near-real-time feed, schedule the Actor every 1–5 minutes; for longer history, run daily and stitch the snapshots.
🔗 More crypto & web3 scrapers by logiover
| Actor | What it does |
|---|---|
| Polymarket Top Wallets & PnL Leaderboard | See who's winning on Polymarket — top wallets ranked by profit |
| GMGN Trending Memecoin Scanner | Live trending memecoins across chains |
| DexScreener Boosted Tokens Scraper | Boosted / promoted tokens on DexScreener |
| CoinGecko Coins Market Scraper | Market data for thousands of coins |
| Binance Spot Market Scraper | Binance spot tickers & market stats |
| Web3 Crypto Jobs Scraper | Web3 & crypto job listings |
👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.
⏰ Scheduling & integration
- Schedule — use Apify Schedules to run this Actor every 1–5 minutes (live odds + sports), every 5–15 minutes (tweet alerts), or hourly/daily (AI bundle).
- Export — download any run as JSON, CSV, or Excel, or query the dataset via the REST API.
- Automate — wire results into Make, n8n, or Zapier to push new events, moving markets, or high-significance tweets straight to Slack, Telegram, Google Sheets, or a database.
- API & webhooks — start runs and stream results programmatically with the Apify API, and attach webhooks to fire your pipeline the moment a run finishes.
🤖 AI Agents, MCP & RAG Integration
Polymarket Scraper works natively as an on-demand data tool for AI assistants and autonomous workflows.
Connect this Actor directly to Apify AI, Claude Desktop, Cursor, VS Code, Windsurf, LangChain, or LlamaIndex via the official Apify MCP Server — no custom wrapper code needed:
{"mcpServers": {"apify": {"type": "http","url": "https://mcp.apify.com?tools=logiover/polymarket-events-odds-ai-scraper"}}}
- Schema-typed inputs & outputs: Clean JSON records with explicit
.actor/input_schema.jsonand.actor/output_schema.jsondefinitions so LLM agents infer parameters and parse fields accurately without HTML noise. - Bounded & predictable runs: Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
- RAG & automation ready: Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.
💬 Support, Issues & Reviews
- Bug reports & target-site changes: Hit an unexpected empty result or selector change? Open a ticket in the Issues tab with your Run ID or sample input — we actively monitor issues and ship fixes fast.
- Feature & field requests: Need an additional data attribute or filter? Request it in the Issues tab.
- Enjoying this Actor? If it saved you engineering time, please consider leaving an honest review on Apify Store or bookmarking logiover/polymarket-events-odds-ai-scraper — organic developer feedback helps others discover reliable tools and keeps maintenance prioritized.
⚖️ Legal
This Actor collects only publicly available prediction-market data — the same information any visitor to Polymarket can view — and performs no login, trading, or access to private account data. You are responsible for using the output in compliance with the source's Terms of Service, applicable laws, and (where relevant) GDPR. Nothing produced by this Actor constitutes financial, investment, or betting advice.
This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Polymarket; Polymarket and all other trademarks mentioned here are the property of their respective owners.
📝 Changelog
2026-11-14
- Verified live high-volume benchmark (2026-11-14): extracted 23,424 structured records in 53.6s on the production build.
- Hardened internal proxy stall fallback and pay-per-event dataset instance budget protection.
2026-11-11
- Added reliable terminal run status telemetry and structured Apify AI / MCP Server (
mcp.apify.com) tool configuration. - Added direct Issues & Reviews support links and refreshed live maintenance verification.
2026-11-01
- Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
- README refreshed: 1 link to renamed Actors updated, 6 links to retired Actors removed; independence disclaimer added; documented 2 additional input fields; documented 61 additional output fields.
- README pricing text corrected: platform usage is included in the per-result price, with no separate platform fees to calculate.
2026-10-15
- Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
- A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
- A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
- Runs with a short timeout (API and AI-agent calls) now finish inside it with what they collected, instead of being cut off.
- Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.
2026-09-23
- Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
- Output verified on a live run: 12757 row(s) across 89 columns, 55.6% of cells populated.
- Run reliability reviewed: 92.9% of public runs succeeded in the last 30 days.
- Input schema, output schema and pricing configuration reviewed.
- Noted that 10 column(s) came back empty in this sample (
eventTitleTrans,eventDescription,gameElapsed,gameClockStartAt,gameClockEndAt,gameEndAtand others); these are under review.
2026-09-20
- Fixed the intermittent failures behind the "Under maintenance" flag. On a busy day the events feed returns ~11 MB of JSON — about 9,500 markets and 19,000 assets — and every resulting row was collected into one array before a single write, peaking at 447 MB against a 512 MB allocation. Rows are now flushed to the dataset in blocks of 1,000 as they are built, and the allocation was raised, so a heavy day no longer runs the container out of memory.
- No change to inputs, output fields or the data itself; only when rows are written.
2026-07-18
- Maintenance & reliability pass — re-verified end-to-end against live data via the Apify API; confirmed the Actor completes successfully and returns non-empty, well-formed results within the 5-minute quality window on its default input.
- Refreshed build so the latest version is current; no change to inputs, output fields or scraping logic.
2026-07-12
- Proxy now defaults to Apify's automatic group instead of forcing RESIDENTIAL, and the client falls back to a direct connection on its final retry — cheaper, faster, and still resilient to rate limits.
- Added two dropdown filters for the Events Rank feed: event status (active / closed / resolved / all) and sort order (24h volume, liquidity, ending soonest, etc.).
- Empty input
{}still returns broad data (active events with markets & odds, sports with live scores, and the Twitter signal feed). - Added a ~4-minute time budget: long Twitter/AI paginations stop, push what's collected, and exit successfully within the quality window.
- Documented every output column with titles/descriptions in the dataset schema.
2026-07-06
- ✨ README overhaul: richer output sample, ready-to-run example scenarios, cross-promo links, and clearer quick-start.
2026-07-01
- Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
- Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
- Added ready-to-run example tasks that cover common real-world use cases.
2026-06-15
- Reliability pass: re-verified end-to-end on live data with real-world inputs. Routine maintenance build.
2026-06-07
- Docs: added coverage for Polymarket API alternative usage, exporting prediction market odds to CSV/JSON, and scraping Polymarket odds without login.
2026-06-05
- 🛡️ Reliability fix: results are no longer dropped by strict output validation — runs now complete cleanly even at high volume (thousands of results).
- ⚡ Stability & performance hardening; fresh rebuild.
2026-06-04
- Verified live & refreshed build — reliability/maintenance pass.