# EarlyWave API

> EarlyWave reads news from tens of thousands of sources and groups articles into stories (trends). Its read-only API gives developers and AI agents the trends detected across every source — filtered by the country a story is about, the countries of its publishers, category, stage and reach — with their articles and coverage by country, plus the account's own monitors, feeds, folders, articles and saved items. REST: https://api.earlywave.ai/api/v1 (Bearer key with the `rest` scope). MCP: https://api.earlywave.ai/mcp (Streamable HTTP, stateless, Bearer key with the `mcp` scope). Included with Pro and Max; 60 or 300 requests a minute and 10,000 or 50,000 a month by plan.

18 GET operations, each also an MCP tool. Errors are `{"error": {"type", "code", "message"}}`; lists take `limit` (1–100) and `offset` and answer `has_more`.

## Docs

- [EarlyWave API](https://www.earlywave.ai/developers/docs/index.md): EarlyWave reads news from tens of thousands of sources and groups the articles into stories, called trends.
- [Quickstart](https://www.earlywave.ai/developers/docs/quickstart.md): Create a key, list the trends about France, then plug the same data into your AI assistant. It takes about five minutes.
- [Authentication](https://www.earlywave.ai/developers/docs/authentication.md): Every request carries an API key in the Authorization header, as a Bearer token. There is no other way to authenticate: keys in the query string are refused, so they never land in access logs.
- [Errors, limits and paging](https://www.earlywave.ai/developers/docs/errors-and-limits.md): What every response of the REST API has in common: one error shape, a rate limit with its headers, the same paging on every list, and a request ID.
- [MCP server](https://www.earlywave.ai/developers/docs/mcp.md): The Model Context Protocol (MCP) lets an AI assistant call tools on your behalf.
- [Trends](https://www.earlywave.ai/developers/docs/trends.md): A trend is a story: the articles that many sources publish about the same event, grouped by EarlyWave as they arrive.
- [Monitors](https://www.earlywave.ai/developers/docs/monitors.md): A monitor watches a subject for you: it checks EarlyWave's sources on a schedule, keeps what matches (events, mentions or a briefing), extracts the fields you asked for and answers your standing questions.
- [Changelog](https://www.earlywave.ai/developers/docs/changelog.md): Changes to the REST API and the MCP server. Version 1 only grows: new operations, parameters and fields are added; nothing is removed or renamed without a new version and a notice here first.

## Reference

- [OpenAPI 3.1 document](https://api.earlywave.ai/api/v1/openapi.json): the contract, every operation with its parameters, response schema and `x-mcp-tool` name (also at https://www.earlywave.ai/openapi/v1.json).
- [API reference](https://www.earlywave.ai/developers/reference): the same document, rendered.
- [Full docs in one file](https://www.earlywave.ai/llms-full.txt): every page above, concatenated.