Skip to main content

​
Enrichment provider field matrix

Status: Tomba and Hunter contact reveal are restricted pilots. A selected result may be displayed and contacted in-product, never exported. Each vendor has its own emergency-brake flag (Tomba’s TOMBA_PILOT_ENABLED, Hunter’s HUNTER_CONTACT_ENRICHMENT_ENABLED); API keys alone do not activate either. Hunter’s masked company/person directory remains approved only for evaluation in staging: display is restricted, while export and contact remain blocked. This matrix describes what the adapters can parse, not what Brein is currently authorized to display, export, retain or use for contact.

​
Provider fields

An empty sources array means the provider supplied no source. It is preserved as absent evidence and is never rewritten as “public”. fetchedAt records when Brein received the response; observedAt is derived only from provider-returned source or verification dates. Generic mailboxes such as info@, ventas@ or contacto@ are stored only as a company fallback. They never become the selected person’s work email and never settle a personal-contact purchase.

​
Evidence still required

Public availability of a source, policy page or email is evidence of origin, not evidence that Brein may redistribute it. A governance policy must explicitly approve the provider and the requested rights before the adapter can be called.

​
Runtime sequence

  1. The caller confirms a server-issued quote and an exact record selection.
  2. Brein persists a short-lived enrichment authorization tied to the actor, workspace, records, purpose, provider policy and idempotency key.
  3. The governance port checks authorization, provider policy and domain/person suppression.
  4. A denied or suppressed decision stops before customer debit and provider I/O.
  5. The provider response is normalized with provenance, then exact-email suppression runs before persistence.
  6. Governance attaches display/export/contact rights to the result.
  7. Only the governance-owned contact-path write stores the result and its authorization ID.
The pilot requires TOMBA_PILOT_ENABLED=true. There is no workspace allowlist: the provider’s license already covers production, and every plan publishes a contact-credit allowance, so scope is enforced by that credit balance (debited before the provider is called), not by a manually maintained list of workspace IDs. The flag itself is the emergency brake, not a scope control. There is no end-user OAuth, provider token passthrough or customer-owned API key. The adapters use Brein-managed server credentials only. Hunter directory evaluation requires HUNTER_DIRECTORY_EVALUATION_ENABLED=true and the exact staging deployment branch. The config validator and runtime adapter both refuse it in production. The dashboard may load a bounded first directory page automatically. Its initial company view is scoped to Mexico; its initial people view is scoped to Mexico and decision-makers, with a 25-row limit. These calls only browse the masked directory and never invoke Finder or Reveal. Public-market explorers may also load their first bounded page automatically. Supplier discovery remains explicitly narrowed because the market-data API refuses an unbounded supplier scan. Provider response references: Hunter API documentation and Tomba Email Finder documentation.