Introduction
Read an account's radars and signals, and set them up, from your own code or from an AI assistant.
Market Radar searches the news for what an account watches and keeps what it finds as signals, on radars; a tender radar watches public calls for tender instead. The API gives a program the same account the app shows: its radars and the folders they live in, their signals and calls for tender, its companies, its custom sources, its filters and its newsletters.
Two doors, one account
| URL | Status | |
|---|---|---|
| REST API | https://app.trymarketradar.com/api/v1 | Available |
| MCP server | https://app.trymarketradar.com/api/mcp | Available |
Both use the same keys and see the same data as the app. The MCP server page says how to connect an assistant.
A first request
Create a key (see Keys), then list the account's radars:
curl https://app.trymarketradar.com/api/v1/radars \
-H "Authorization: Bearer $MARKET_RADAR_KEY"Where to read next
Keys
How to get a key, what each access allows, and how to send it.
Conventions and errors
JSON, ids, dates, paging, the rate limit, and every error code.
Objects
Radar, Signal, Tender, Sweep, Company, Filter and Newsletter, each with its JSON.
Endpoints
Every path, and the rules for creating and editing radars, companies, custom sources and newsletters.
API reference
Each endpoint's parameters, bodies and responses, from the OpenAPI document.
Examples
curl and TypeScript, from a week of signals to a new radar.
MCP server
Connect Claude, ChatGPT or Cursor to the account.