# Market-Monitoring Task Routes For Agents Updated: 2026-04-26T00:00:00Z Task-oriented route map for agents deciding which machine-readable sources to use for market and prediction-market monitoring jobs. ## Discover Prediction Markets And Contract Metadata ID: `prediction-market-discovery` Category: `prediction-markets` Best formats: JSON, REST, WebSocket, llms.txt Last updated: `2026-04-26` Confidence: `experimental` Agent question: Which sources should I inspect to discover live prediction markets, event metadata, outcomes, prices, and order books? Setup value: Maps a monitoring job to source choices, formats, notes, and caveats for one-time workflow setup. Not for: Direct trading signals or authoritative market resolution. Primary sources: - Polymarket APIs (`polymarket-apis`) - Kalshi API (`kalshi-api`) - PredScope Prediction Market API (`predscope-api`) Supporting sources: - PredMktData (`predmktdata`) - Metaculus API (`metaculus-api`) - Manifold API (`manifold-api`) Agent notes: - Use official market APIs for live market state when available. - Distinguish market title, event metadata, outcome IDs, condition IDs, and resolution source. - Store identifiers needed to map API data back to a specific market or contract. Caveats: - Third-party normalized feeds may lag official APIs or have coverage limits. - Trading endpoints often require authentication even when market-data endpoints are public. - Market title alone is not enough to evaluate resolution risk. ## Evaluate Prediction-Market Resolution Risk ID: `prediction-market-resolution` Category: `prediction-markets` Best formats: JSON, Markdown, llms.txt Last updated: `2026-04-26` Confidence: `experimental` Agent question: How should I evaluate whether a prediction market has clear source-of-truth and resolution criteria? Setup value: Maps a monitoring job to source choices, formats, notes, and caveats for one-time workflow setup. Not for: Direct trading signals or authoritative market resolution. Primary sources: - Polymarket APIs (`polymarket-apis`) - Kalshi API (`kalshi-api`) Supporting sources: - Metaculus API (`metaculus-api`) - Manifold API (`manifold-api`) - GDELT Cloud (`gdelt-cloud`) Agent notes: - Capture exact market wording and any linked rules before market resolution. - Rank sources by authority: official market rules, explicit resolution source, primary institution, then secondary reporting. - Track ambiguous terms, deadlines, time zones, and whether evidence must be published before a cutoff. Caveats: - APIs may expose market metadata but not all off-platform evidence. - Market resolution can depend on platform discretion or UMA-style dispute processes. - A source can be official but still ambiguous for the market wording. ## Monitor Macro Release Timing And Updates ID: `macro-release-monitoring` Category: `macro` Best formats: JSON, RSS, XML Last updated: `2026-04-26` Confidence: `experimental` Agent question: Which sources should I use to monitor macroeconomic data release timing and official updates? Setup value: Maps a monitoring job to source choices, formats, notes, and caveats for one-time workflow setup. Not for: Direct trading signals or authoritative market resolution. Primary sources: - FRED Release Dates API (`fred-release-dates`) - BLS Public Data API and RSS (`bls-api`) - Federal Reserve RSS Feeds (`federal-reserve-rss`) Supporting sources: - Treasury FiscalData API (`treasury-fiscaldata`) - GDELT Cloud (`gdelt-cloud`) Agent notes: - Use release calendars to know when data is expected, then official source endpoints for actual release data. - Separate scheduled release timing from the moment data becomes available through an aggregator. - Record revisions and publication timestamps when the source exposes them. Caveats: - Aggregators can lag primary agency publication. - Some official APIs require keys or have usage guidelines. - Release calendars and data endpoints may be separate systems. ## Monitor Central Bank Communication Changes ID: `central-bank-communications` Category: `macro` Best formats: RSS, HTML, XML, diff snapshots Last updated: `2026-04-26` Confidence: `experimental` Agent question: Which sources should I use to monitor central bank statements, speeches, and policy communication changes? Setup value: Maps a monitoring job to source choices, formats, notes, and caveats for one-time workflow setup. Not for: Direct trading signals or authoritative market resolution. Primary sources: - Federal Reserve RSS Feeds (`federal-reserve-rss`) Supporting sources: - FRED Release Dates API (`fred-release-dates`) - GDELT Cloud (`gdelt-cloud`) Agent notes: - Use RSS for discovery, then fetch source pages for text comparison. - Store previous statement text so wording changes can be compared. - Track speaker, institution, timestamp, and policy category. Caveats: - RSS items indicate publication but not semantic importance. - Statement diffing requires stored snapshots. - Market relevance depends on context and expectations. ## Monitor Regulatory Catalysts ID: `regulatory-catalyst-monitoring` Category: `regulatory` Best formats: JSON, RSS, bulk ZIP Last updated: `2026-04-26` Confidence: `experimental` Agent question: Which sources should I monitor for regulatory actions that may affect markets, crypto, banking, energy, or prediction markets? Setup value: Maps a monitoring job to source choices, formats, notes, and caveats for one-time workflow setup. Not for: Direct trading signals or authoritative market resolution. Primary sources: - Federal Register API (`federal-register-api`) - SEC EDGAR APIs (`sec-edgar-apis`) Supporting sources: - Treasury FiscalData API (`treasury-fiscaldata`) - GDELT Cloud (`gdelt-cloud`) Agent notes: - Use official agency document APIs for source-of-truth records. - Map agency actions to affected sectors, companies, tokens, or market questions. - Track comment deadlines, effective dates, publication dates, and document types. Caveats: - Regulatory documents can be long and require domain-specific interpretation. - News coverage may appear before structured official metadata is easy to query. - Agency source hierarchy matters. ## Monitor Weather And Disaster Event Markets ID: `weather-disaster-markets` Category: `weather` Best formats: JSON-LD, CAP XML, Atom, RSS Last updated: `2026-04-26` Confidence: `experimental` Agent question: Which sources should I use for weather, disaster, energy, insurance, or event contracts tied to official alerts? Setup value: Maps a monitoring job to source choices, formats, notes, and caveats for one-time workflow setup. Not for: Direct trading signals or authoritative market resolution. Primary sources: - National Weather Service Alerts API (`nws-alerts`) Supporting sources: - GDELT Cloud (`gdelt-cloud`) - PredScope Prediction Market API (`predscope-api`) Agent notes: - Use official alert feeds for watches, warnings, and advisories. - Map alert geography, severity, event type, and effective/expiration times to market wording. - Use prediction-market APIs separately for prices and outcomes. Caveats: - Weather markets often depend on exact geography, thresholds, and measurement source. - Official alert wording may not match market wording directly. - Alert updates can be frequent and require deduplication.