Developers

API & MCP

REST + a Model Context Protocol server so deal-sourcing agents can call Cassandra directly.

MCP tool: contractor_signals

Point any MCP client at https://ma.dropwatchhq.com/mcp. Tools: contractor_signals(name), rising_contractors(limit), search_awards(...).

curl -s https://ma.dropwatchhq.com/mcp -X POST -H 'content-type: application/json' \
 -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
      "params":{"name":"contractor_signals","arguments":{"name":"Palantir"}}}'

REST

GET  /v1/contractor_signals?name=Palantir      # full signal profile + EDGAR overlay
GET  /v1/rising                                # ranked rising-contractor feed
GET  /v1/search_awards?recipient=...&naics=5415&minAmount=5000000
POST /v1/watchlist  {"contractor":"...","webhook":"https://..."}   # paid tiers
GET  /v1/watchlist                              # list your watchlist

Auth: x-api-key header or ?key=. Free anonymous tier works with no key (capped). Webhooks fire when a watched contractor's score moves.

Webhook payload

{ "event":"signal_move", "contractor":"...", "date":"YYYY-MM-DD",
  "score": 78, "type":"score_up", "from": 66 }
How to read these scores. Cassandra computes leading-indicator signals strictly from public federal award history (USAspending.gov) and public SEC filings (EDGAR). Scores are pattern-based and probabilistic — they describe profiles that historically correlate with acquisitions and major corporate events. They are not predictions of certainty, not insider or material non-public information (MNPI), and not investment advice. Do your own diligence.