Public Vendor Registry Intelligence

What you get: one row per public vendor-registry or supplier-portal page with the organization, portal type, registration status, procurement categories, required documents, eligibility signals, a confidence score, and the source URLs.

Sample output from real runs (2026-10-18, maxResults: 1, maxLinkedPages: 1; the first row comes from the JSON below):

registryUrl	organizationName	portalType	registrationStatus	categories (first 4)	requiredDocuments	confidence	status
https://www.nyc.gov/site/mocs/passport/about-passport.page	About PASSPort | MOCS	government procurement	registry_page_detected	construction, professional services, information technology, maintenance	–	0.74	enriched
https://www.gsa.gov/small-business/find-opportunities/register-your-business	U.S. General Services Administration	government procurement	registration_available	professional services, information technology, logistics, transportation	tax ID, references	1	enriched

Each enriched row is one vendor_profile_enriched event. Pages that return an HTTP error come back as a not_found or blocked row with no row charge. Note: the Console form currently starts with two pages that return errors (the old NYC systems/passport.page link: HTTP 404, and the UNGM registration page: HTTP 403), so paste the JSON below for your first run.

Open Input Paid first-run JSON ≈ USD 0.01–0.03/result (1 bounded first run). Keep reports, exports, and movement options bounded for the first run. Open Console Input (deep link above) and run this JSON.

{
  "urls": [
    "https://www.nyc.gov/site/mocs/passport/about-passport.page"
  ],
  "domains": [],
  "buyerType": "",
  "region": "United States",
  "maxLinkedPages": 1,
  "maxResults": 1,
  "dryRun": false
}

Paste registry URL and Start.

Extract procurement-ready B2B fields from public vendor registry, supplier portal, supplier onboarding, and registration pages. V1 is direct-source only: it uses URLs or domains you provide plus same-domain vendor/procurement links found on those pages. It does not use search engines, private portals, authentication, or paid supplier data.

Store Quickstart

Run the single-input JSON above first; keep optional reports, exports, and movement options bounded.

Use with Apify MCP

Exact actor: taroyamada/public-vendor-registry-intelligence

Sample input JSON:

{
  "urls": [
    "https://www.nyc.gov/site/mocs/passport/about-passport.page",
    "https://www.gsa.gov/small-business/find-opportunities/register-your-business"
  ],
  "domains": [],
  "maxLinkedPages": 2,
  "maxResults": 3
}

What It Returns

• Organization and registry names
• Registry URL, website, portal type, and registration status
• Supplier categories, required documents, eligibility language, contacts, and deadlines
• Confidence, status, chargedEvent, sourceUrls, and errors on every dataset row

PPE Events

• vendor_profile_enriched: useful enriched vendor registry profile
• vendor_partial: useful partial registry evidence
• invalid, blocked, not_found, not_vendor_registry, and error: no-charge diagnostic rows

Inputs

Use urls for exact registration or supplier portal pages, or domains when you want the actor to inspect a public buyer domain for same-domain vendor registration links. Keep maxLinkedPages low for the cheapest proof path.

Positioning

Use this after Procurement Intel identifies a buyer, agency, or opportunity and you need onboarding evidence: supplier registration pages, required documents, eligibility signals, and public contact paths.