Deterministic extraction — no LLM, no hallucinated vendors
The subprocessor disclosure data API.
Does an entity publish a subprocessor list — and what's on it? One call returns where the disclosure lives and the vendors it names, as a structured stack across 13 categories, with the quoted row as evidence. Reverse lookup returns every entity that lists a given vendor.
{
"domain": "notify-hq.com",
"found": true,
"cache": "hit",
"vendor_stack": {
"sms_messaging": [{
"vendor": "twilio",
"evidence": {
"source": "https://notify-hq.com/legal/subprocessors",
"quote": "Twilio Inc. — SMS and voice message delivery"
}
}],
"email": [{ "vendor": "sendgrid", "...": "..." }],
"payments": [{ "vendor": "stripe", "...": "..." }]
},
"sends_sms": true,
"credits_used": 1,
"credit_balance": 24
}How it works
Three calls from zero to structured vendor data.
Get a key instantly
POST your email, get an API key back in the same response. No verification click, no dashboard, no sales call. 25 free credits to start.
curl -X POST https://vendorradar-production.up.railway.app
/v1/keys \
-d '{"email":"[email protected]"}'Check any entity
One call answers: does this entity publish a subprocessor/DPA disclosure, where does it live, and which vendors are on it — with the quoted row for every match.
curl "https://vendorradar-production.up.railway.app /v1/check?url=acme.com" \ -H "Authorization: Bearer $VR_KEY"
Reverse lookup
List entities by vendor or category. Every entity in the index that discloses a given vendor — structured pages of 10, ready for enrichment or segmentation.
curl "https://vendorradar-production.up.railway.app /v1/prospect?vendor=twilio&category=sms_messaging" \ -H "Authorization: Bearer $VR_KEY"
Use cases
One dataset, wherever your pipeline runs.
GTM teams
Enrich and qualify accounts by what's actually in their stack, not what a scraper guessed. Segment lists by vendor or category, route plays accordingly, and drop the API into Clay, n8n, or Zapier-style pipelines — it's plain JSON over HTTPS.
AI agents
A due-diligence tool your agent can call mid-run: instant key issuance, deterministic output that never hallucinates a vendor, and an OpenAPI spec, markdown docs, and llms.txt ready to wire in as a function-calling tool.
Competitive intel
Reverse-look-up the entities that list a competitor's product, evidence attached — published by the entities themselves. A solid displacement motion, and exactly one of the workflows this data supports.
Coverage
13 vendor categories, extracted verbatim.
Every match carries the source URL and the quoted sentence it was extracted from. If it's not in the disclosure, it's not in the response.
Agent-first
Built to be consumed by code — human optional.
An entity-due-diligence tool your agent can call. Key issuance is a single POST, output is deterministic JSON, and paywalls are machine-readable 402s with a topup_url. Wire it in as a function-calling tool via the OpenAPI spec, markdown docs, or llms.txt.
- vendorradar-production.up.railway.app /llms.txt
- vendorradar-production.up.railway.app /openapi.json
- vendorradar-production.up.railway.app /skill
Install instructions and the function-calling tool definition are on the skills page.
# Your agent, unsupervised: → POST /v1/keys # self-provisions a key → GET /v1/prospect?vendor=twilio&category=sms_messaging → GET /v1/company/each-prospect.com 402 Payment Required — {"topup_url": "…"} → escalates to human with exact price. Resumes on top-up.
The disclosures are already public. Now they're queryable.
25 free credits — enough for 25 lookups or 250 reverse-lookup rows. No card, no verification email.
Get your API key