Build with market news

Developers and traders who want to call a stock news API, stream headlines, or hand the feed to an AI app. Posts are tagged Product, Tutorial, or Guide. They assume you can run a short code sample. The API reference, with every parameter, lives in the docs. A guide is not a substitute for the reference when you are debugging a request.

Signup starts a 7-day Pro trial, and a card is required. That trial includes real-time REST, WebSocket, and MCP, which is what the streaming tutorials use. If you do not subscribe, the account moves to Free: 100 requests a day, a 15-minute delay, and the last year of history. Free can still run the REST examples inside those limits.

The docs cover quickstart, REST, WebSocket, MCP, authentication, errors, and the ticker list. OpenAPI is at /openapi.json and a short map for agents is at /llms.txt. Blog posts show one path through a feature. When a sample and the docs disagree, follow the docs. The changelog notes breaking changes before they ship.

Guides are written against the live API: REST at /v1/news, the WebSocket, and the MCP server. If a sample and the docs disagree, follow the docs. Breaking changes are written in the changelog before they ship. The streaming tutorials need Pro, which the 7-day trial includes. A card is required.

Not as a live product. A post may say those markets are planned. The API today is English-language US equities and ETFs: stock news, press releases, and legal notices. Query category=stocks until another category ships. The same plans and the same article fields are what a new category would use.