Data Researcher - Verify & Extend a 120+ Source Connector Catalog (APIs, ToS, Pricing, JSON Schemas)

We maintain a catalog of roughly 120 public-record, government-filing, and commercial data sources ("connectors") that feed a lead-sourcing system. Each connector is mapped to one or more specific qualification criteria it's supposed to satisfy. Where a connector's raw output doesn't resolve all the way down to a named, contactable individual, we route it through one or more secondary "screen point" services (business registries, identity-resolution tools, contact-append APIs, etc.) that carry the record the rest of the way — we already have a diagram mapping out which screen points follow which connectors. We need a sharp, technically-comfortable researcher to systematically verify and stress-test this catalog. This is real due-diligence work, not simple data entry: you'll be reading Terms of Service documents, testing or reading API docs to capture exact JSON response shapes, and using judgment about whether a proposed resolution chain actually makes sense. Part 1 — Verify the connector list (~120 sources) For each connector, confirm and document: Signal relevance — does the source still plausibly satisfy the qualification criterion it's assigned to? Flag anything that looks mismatched. Pricing — verify our recorded pricing/tier is current and accurate. Link the pricing page (or note "quote-only" / provide a dated screenshot if pricing isn't public). Terms of Service — does the source's current ToS allow automated collection (API use, bulk download, or scraping)? If scraping/automation is prohibited: identify a working alternative — an official API, a licensed data feed, or a third-party scraping/proxy service (e.g., Bright Data, ScrapingBee, Scrape.do) — and note its cost. If no viable alternative exists: recommend a replacement source that serves the same qualification criterion, and briefly describe how it would resolve to a contact (see Part 2 logic). JSON response — using a free tier, trial, sandbox, or published API docs (a live pull isn't required if not feasible), capture the exact JSON an API call or export returns for that source. Paste it as-is. If no live/documented schema exists, say so explicitly rather than guessing. Resolution check — does that JSON output already contain a named, contactable individual? Or does it stop at a company/entity level with no owner name? Flag which. Part 2 — Verify the screen points (resolution-layer services) We'll share a diagram/reference file showing which secondary lookups ("screen points") each connector routes through when its raw output isn't already a resolved contact. For each screen point in a chain: Confirm it's a sensible choice given what the upstream connector's output actually contains — flag it if a screen point can't realistically consume that input. Repeat the same checklist as Part 1: pricing, ToS, exact JSON response. Confirm explicitly whether the output fields of one step in the chain match the expected input of the next step. We want to know if the chain is genuinely chainable, not just conceptually connected. Part 3 — Extend the list (stretch goal) If in the course of research you come across additional legitimate sources serving criteria we haven't yet captured — public records, disclosure filings, licensed datasets (not brokered or "in-market" lead lists) — flag them with the same pricing/ToS/JSON detail. Bonus, not core scope; we'll scope this separately if the core work goes well. Skills Required Strong research skills — comfortable reading ToS/legal pages and API documentation, not just marketing pages Basic familiarity with REST APIs and JSON (you don't need to code, but you need to be able to read a response and know what you're looking at) Meticulous, low-error-rate documentation habits Comfortable working in spreadsheets (Google Sheets/Excel) with a structured, repeatable format English fluency (written) sufficient for concise, accurate notes Nice to Have Prior exposure to B2B data providers (e.g., data brokers, business registries, contact-enrichment tools) Experience with API testing tools (Postman or similar) Familiarity with data compliance basics (GDPR, CCPA/data broker rules) — helpful context, not required for every source Past lead-gen, growth, or sales-ops research experience Note: we'll require a short NDA before sharing the actual working files, since the underlying source list and screen-point mapping are proprietary.