{ "generated_at": "2026-04-26T08:48:20Z", "schema_version": "0.1.0", "updated_at": "2026-04-26T00:00:00Z", "purpose": "Task-oriented route map for agents deciding which machine-readable sources to use for market and prediction-market monitoring jobs.", "tasks": [ { "id": "prediction-market-discovery", "title": "Discover Prediction Markets And Contract Metadata", "category": "prediction-markets", "agent_question": "Which sources should I inspect to discover live prediction markets, event metadata, outcomes, prices, and order books?", "primary_sources": [ "polymarket-apis", "kalshi-api", "predscope-api" ], "supporting_sources": [ "predmktdata", "metaculus-api", "manifold-api" ], "best_formats": [ "JSON", "REST", "WebSocket", "llms.txt" ], "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." ], "last_updated": "2026-04-26", "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.", "confidence": "experimental" }, { "id": "prediction-market-resolution", "title": "Evaluate Prediction-Market Resolution Risk", "category": "prediction-markets", "agent_question": "How should I evaluate whether a prediction market has clear source-of-truth and resolution criteria?", "primary_sources": [ "polymarket-apis", "kalshi-api" ], "supporting_sources": [ "metaculus-api", "manifold-api", "gdelt-cloud" ], "best_formats": [ "JSON", "Markdown", "llms.txt" ], "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." ], "last_updated": "2026-04-26", "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.", "confidence": "experimental" }, { "id": "macro-release-monitoring", "title": "Monitor Macro Release Timing And Updates", "category": "macro", "agent_question": "Which sources should I use to monitor macroeconomic data release timing and official updates?", "primary_sources": [ "fred-release-dates", "bls-api", "federal-reserve-rss" ], "supporting_sources": [ "treasury-fiscaldata", "gdelt-cloud" ], "best_formats": [ "JSON", "RSS", "XML" ], "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." ], "last_updated": "2026-04-26", "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.", "confidence": "experimental" }, { "id": "central-bank-communications", "title": "Monitor Central Bank Communication Changes", "category": "macro", "agent_question": "Which sources should I use to monitor central bank statements, speeches, and policy communication changes?", "primary_sources": [ "federal-reserve-rss" ], "supporting_sources": [ "fred-release-dates", "gdelt-cloud" ], "best_formats": [ "RSS", "HTML", "XML", "diff snapshots" ], "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." ], "last_updated": "2026-04-26", "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.", "confidence": "experimental" }, { "id": "regulatory-catalyst-monitoring", "title": "Monitor Regulatory Catalysts", "category": "regulatory", "agent_question": "Which sources should I monitor for regulatory actions that may affect markets, crypto, banking, energy, or prediction markets?", "primary_sources": [ "federal-register-api", "sec-edgar-apis" ], "supporting_sources": [ "treasury-fiscaldata", "gdelt-cloud" ], "best_formats": [ "JSON", "RSS", "bulk ZIP" ], "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." ], "last_updated": "2026-04-26", "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.", "confidence": "experimental" }, { "id": "weather-disaster-markets", "title": "Monitor Weather And Disaster Event Markets", "category": "weather", "agent_question": "Which sources should I use for weather, disaster, energy, insurance, or event contracts tied to official alerts?", "primary_sources": [ "nws-alerts" ], "supporting_sources": [ "gdelt-cloud", "predscope-api" ], "best_formats": [ "JSON-LD", "CAP XML", "Atom", "RSS" ], "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." ], "last_updated": "2026-04-26", "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.", "confidence": "experimental" } ] }