Workflow walkthrough · Competitive intel

Displacement intelligence with evidence

Scenario: you compete with an incumbent vendor and want to know which entities run it today, how central it looks in each stack, and when that changes. Disclosure data answers all three — from statements the entities published themselves. This is one workflow the API supports, and it composes from the same three endpoints as the others.

Step 1 — Who discloses the competitor?

Request

curl "https://vendorradar-production.up.railway.app
/v1/prospect?vendor=twilio&page=1" \
  -H "Authorization: Bearer $VR_KEY"

Response (sample)

{
  "vendor": "twilio",
  "total": 1417,
  "companies": [
    {
      "domain": "notify-hq.com",
      "confidence": "vendor_keyword",
      "evidence": {
        "source": "https://notify-hq.com/legal/subprocessors",
        "quote": "Twilio Inc. — SMS and voice message delivery"
      }
    }
  ],
  "credits_used": 1
}

Note the omitted category parameter: unfiltered, you also catch entities using the competitor outside your core category — useful for sizing the whole footprint.

Step 2 — Read the row, not just the match

The quoted evidence carries more information than the boolean. A row that reads "Twilio Inc. — SMS and voice message delivery" describes a production dependency. One that reads "Twilio (Authy) — two-factor authentication" describes a narrower, easier-to-displace integration. The confidence tier formalizes part of this — vendor_keyword means the row itself describes the category function — but the verbatim quote is there so your team (or your model) can judge nuance directly.

Step 3 — Cross-reference the rest of the stack

For priority targets, pull the full profile and look at the adjacent categories:

Request

curl "https://vendorradar-production.up.railway.app
/v1/company/notify-hq.com" \
  -H "Authorization: Bearer $VR_KEY"

An entity disclosing the competitor plus a modern adjacent stack (say, Segment and Datadog) is likely mid-modernization — a good displacement conversation. An entity whose disclosure hasn't changed in two years is probably not shopping.

Step 4 — Track changes over time

Disclosures are legally maintained, so changes are meaningful. Re-pull profiles monthly (1 credit each, always instant) and diff:

Competitor disappears from a disclosure — the displacement already happened; find out who won it.
Your category appears at an entity that lacked it — a new buyer entering the market.
A second vendor appears in the same category — often a migration in progress; both incumbency and displacement are live.

For entities where the indexed scan is stale and the deal is active, a fresh=true lookup (same 1 credit, just slower) re-reads the disclosure today. If the scan can't locate a disclosure page, it charges nothing.

Keeping it honest

Everything above is built from public, first-party statements — there's no inference about private contracts, spend, or renewal dates, and found: false only ever means no disclosure was located. What you get is a defensible, citable map of disclosed vendor relationships, refreshed on your schedule.

Start with the 25 free credits — two pages of reverse lookup and a handful of profiles — or see the API reference for full parameter details.