# Machine-Readable Market Event Sources Updated: 2026-04-26T00:00:00Z This directory lists public APIs, feeds, and source-linked resources that market-monitoring agents may inspect. It is an observability surface, not trading advice. ## SEC EDGAR APIs ID: `sec-edgar-apis` Category: `filings` Authority: `official` Formats: JSON, RSS, bulk ZIP Auth required: `no` Update cadence: throughout the day as filings disseminate Best endpoint: https://www.sec.gov/edgar/sec-api-documentation Last verified: `2026-04-26` Machine readability score: `3` URL: https://www.sec.gov/edgar/sec-api-documentation Official SEC APIs for company submissions and XBRL data, useful for filings, corporate events, and regulatory monitoring. Agent use: Monitor submissions, company facts, filing histories, and structured disclosure updates. Market relevance: Useful for equities, credit, crypto-company filings, M&A, insider activity, and event-driven workflows. Notes: - SEC documentation says data.sec.gov provides RESTful JSON APIs without authentication or API keys. - SEC documentation says JSON structures update throughout the day as submissions are disseminated. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Polymarket APIs ID: `polymarket-apis` Category: `prediction-markets` Authority: `official` Formats: JSON, REST, CLOB API Auth required: `mixed` Update cadence: market-data endpoints vary by API Best endpoint: https://docs.polymarket.com/api-reference Last verified: `2026-04-26` Machine readability score: `3` URL: https://docs.polymarket.com/api-reference Official Polymarket API documentation for market discovery, events, pricing, order books, and trading operations. Agent use: Discover markets and events through the Gamma API, monitor pricing and order books through public CLOB endpoints, and link market wording to source evidence. Market relevance: Directly relevant for prediction-market agents and market-research workflows. Notes: - Polymarket documentation describes Gamma and Data APIs as public. - Trading endpoints require authentication. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Kalshi API ID: `kalshi-api` Category: `prediction-markets` Authority: `official` Formats: JSON, REST, WebSocket, OpenAPI, AsyncAPI Auth required: `mixed` Update cadence: market-data endpoints vary; WebSocket available Best endpoint: https://docs.kalshi.com/ Last verified: `2026-04-26` Machine readability score: `3` URL: https://docs.kalshi.com/ Official Kalshi API documentation for regulated event market data, order books, and trading workflows. Agent use: Monitor event markets, contract metadata, prices, order books, and market status. Market relevance: Directly relevant for macro, politics, weather, economics, and other event-contract workflows. Notes: - Useful as a primary market-data source for Kalshi-specific monitoring. - Authentication and exchange rules apply for trading actions. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## FRED Release Dates API ID: `fred-release-dates` Category: `macro` Authority: `official` Formats: JSON, XML, REST Auth required: `yes` Update cadence: release calendar / API dependent Best endpoint: https://fred.stlouisfed.org/docs/api/fred/releases_dates.html Last verified: `2026-04-26` Machine readability score: `3` URL: https://fred.stlouisfed.org/docs/api/fred/releases_dates.html St. Louis Fed API endpoint for economic data release dates across FRED releases. Agent use: Build macro release calendars and monitor when economic series are expected to update. Market relevance: Useful for rates, FX, equities, inflation, employment, and macro prediction-market workflows. Notes: - FRED release dates are published by data sources and may not equal the exact time data appears on FRED. - A FRED API key is required. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Federal Reserve RSS Feeds ID: `federal-reserve-rss` Category: `macro` Authority: `official` Formats: RSS, XML Auth required: `no` Update cadence: on publication Best endpoint: https://www.federalreserve.gov/feeds/feeds.htm Last verified: `2026-04-26` Machine readability score: `2` URL: https://www.federalreserve.gov/feeds/feeds.htm Official Federal Reserve RSS feeds for press releases, speeches, policy updates, working papers, and data announcements. Agent use: Monitor Fed communications and trigger text comparison or source-following workflows. Market relevance: Relevant for central-bank event monitoring, FOMC statement changes, rates, FX, equities, and crypto. Notes: - RSS is suitable for repeated low-frequency polling. - Agents should follow primary release links for final source material. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## GDELT Cloud ID: `gdelt-cloud` Category: `news-events` Authority: `third-party` Formats: JSON API, MCP tools Auth required: `unknown` Update cadence: varies by endpoint Best endpoint: https://docs.gdeltcloud.com/ Last verified: `2026-04-26` Machine readability score: `3` URL: https://docs.gdeltcloud.com/ Structured global news-event data with APIs and MCP tools for agent and analyst workflows. Agent use: Monitor global events, clustered stories, entities, summaries, and article evidence. Market relevance: Useful for geopolitical, conflict, commodity, policy, and broad news-event monitoring. Notes: - GDELT Cloud documentation explicitly references AI agents and MCP access. - News-derived data is broad and noisy; filtering quality matters. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## National Weather Service Alerts API ID: `nws-alerts` Category: `weather` Authority: `official` Formats: JSON-LD, CAP XML, Atom Auth required: `no` Update cadence: near real time via Atom indexes Best endpoint: https://www.weather.gov/documentation/services-web-alerts Last verified: `2026-04-26` Machine readability score: `3` URL: https://www.weather.gov/documentation/services-web-alerts Official National Weather Service alert service for watches, warnings, advisories, and active weather alerts. Agent use: Monitor active alerts through Atom indexes and pull structured alert details as needed. Market relevance: Useful for weather, agriculture, energy, insurance, disaster, and prediction-market workflows. Notes: - NWS documentation identifies JSON-LD as the default API format for indexes and products. - NWS documentation recommends Atom index files for tracking active alerts in near real time. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## PredMktData ID: `predmktdata` Category: `prediction-markets` Authority: `third-party` Formats: llms.txt, API, WebSocket, Parquet, CSV Auth required: `mixed` Update cadence: service dependent Best endpoint: https://predmktdata.com/ Last verified: `2026-04-26` Machine readability score: `3` URL: https://predmktdata.com/ Polymarket data service exposing on-chain prediction-market data through dumps, APIs, and agent-readable documentation. Agent use: Monitor Polymarket market data, historical data, resolution data, and integration guidance through a purpose-built data surface. Market relevance: Useful for prediction-market analytics, backtesting, market lookup, and agent workflows that need normalized Polymarket data. Notes: - The site advertises an agent-readable llms.txt at https://predmktdata.com/llms.txt. - Commercial terms, coverage, and latency should be verified before production use. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Metaculus API ID: `metaculus-api` Category: `forecasting` Authority: `platform` Formats: JSON, REST Auth required: `unknown` Update cadence: platform dependent Best endpoint: https://www.metaculus.com/api2/questions/ Last verified: `2026-04-26` Machine readability score: `2` URL: https://www.metaculus.com/api2/questions/ Machine-readable Metaculus question endpoint useful for monitoring forecasting questions, statuses, dates, and resolution criteria. Agent use: Discover and monitor forecasting questions that may map to public events or prediction-market topics. Market relevance: Useful for event discovery, question wording, resolution logic, and comparing expert forecasting activity with market prices. Notes: - The endpoint is directly machine-readable, but agents should verify current API behavior and terms. - Metaculus is a forecasting platform, not a financial exchange. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Manifold API ID: `manifold-api` Category: `forecasting` Authority: `platform` Formats: JSON, REST Auth required: `mixed` Update cadence: platform dependent Best endpoint: https://docs.manifold.markets/api Last verified: `2026-04-26` Machine readability score: `2` URL: https://docs.manifold.markets/api Public Manifold API documentation for markets, users, bets, comments, and related forecasting-platform activity. Agent use: Monitor long-tail forecasting questions, market discussion, and social prediction signals. Market relevance: Useful for signal discovery and research, but Manifold is not a cash financial market. Notes: - Good for broad question discovery and qualitative signal monitoring. - Agents should distinguish play-money forecast signals from tradable market prices. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## PredScope Prediction Market API ID: `predscope-api` Category: `prediction-markets` Authority: `third-party` Formats: JSON, REST Auth required: `no` Update cadence: documentation advertises frequent updates; verify current cadence Best endpoint: https://predscope.com/guide/prediction-market-api Last verified: `2026-04-26` Machine readability score: `2` URL: https://predscope.com/guide/prediction-market-api Public JSON prediction-market endpoint describing live odds, volume, liquidity, categories, and outcomes. Agent use: Poll normalized prediction-market data for discovery and lightweight monitoring. Market relevance: Useful for monitoring prediction-market odds and identifying large changes for follow-up. Notes: - PredScope documentation advertises no-auth JSON access and a fair-use rate limit. - Agents should verify source coverage and attribution requirements. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## BLS Public Data API and RSS ID: `bls-api` Category: `macro` Authority: `official` Formats: JSON, RSS, XLSX Auth required: `mixed` Update cadence: on official release / endpoint dependent Best endpoint: https://www.bls.gov/developers/home.htm Last verified: `2026-04-26` Machine readability score: `3` URL: https://www.bls.gov/developers/home.htm Bureau of Labor Statistics machine-readable access for labor, inflation, wages, productivity, and related releases. Agent use: Monitor official macroeconomic data releases and related RSS/news updates. Market relevance: Useful for CPI, jobs, unemployment, wages, PPI, and other market-moving economic indicators. Notes: - Useful for official data after publication; low-latency trading use should follow source release mechanics carefully. - Pair with release calendars and RSS feeds for update detection. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Federal Register API ID: `federal-register-api` Category: `regulatory` Authority: `official` Formats: JSON, RSS Auth required: `no` Update cadence: on publication / API dependent Best endpoint: https://www.federalregister.gov/developers/documentation/api/v1 Last verified: `2026-04-26` Machine readability score: `3` URL: https://www.federalregister.gov/developers/documentation/api/v1 Official API for rules, proposed rules, notices, agency actions, and regulatory documents. Agent use: Monitor regulatory catalysts and agency actions affecting markets, crypto, banking, energy, healthcare, and other sectors. Market relevance: Useful for policy-sensitive prediction markets and regulatory event-driven workflows. Notes: - Good source for official regulatory documents and agency actions. - Agents should map documents to affected sectors and source-of-truth agencies. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source. ## Treasury FiscalData API ID: `treasury-fiscaldata` Category: `macro` Authority: `official` Formats: JSON, CSV, XML Auth required: `no` Update cadence: dataset dependent Best endpoint: https://fiscaldata.treasury.gov/api-documentation/ Last verified: `2026-04-26` Machine readability score: `3` URL: https://fiscaldata.treasury.gov/api-documentation/ U.S. Treasury API documentation for fiscal datasets including debt, auctions, rates, exchange rates, and fiscal flows. Agent use: Monitor Treasury and fiscal datasets relevant to rates, liquidity, debt issuance, and macro workflows. Market relevance: Useful for rates, liquidity, debt ceiling, Treasury auctions, and macro prediction markets. Notes: - Useful as an official source for Treasury datasets. - Agents should inspect dataset-specific update cadence and fields. Rate-limit notes: Check source documentation before production use. Production caveat: Verify terms, latency, coverage, and endpoint behavior before relying on this source.