FoxAPIs: Inbound Vetter
AI-generatedSummary
Enriches an inbound person with FoxAPIs and, when enabled and a company domain is available, generates a company sales dossier. Derives seniority, vetting confidence, and a recommended action from the person results, and returns those alongside mapped and raw API responses.
Inputs
- Name — Person’s full name; used as the identity anchor. If omitted, the name is derived from the email’s local part. At least a name or email is required.
- Email — Inbound email address. A non-free-webmail domain can supply the company domain, and the email’s local part can supply a fallback name.
- Company Domain — Company domain; takes precedence over a domain derived from a work email. When available, it is used for person matching and, if company intel is enabled, dossier generation.
- Company — Company name hint sent with the person enrichment request to help disambiguate the match.
- Title — Job title hint sent with the person enrichment request.
- Mode — Select Light (default) for contact and identity resolution, or Deep for a full behavioral profile; Deep uses more FoxAPIs credits.
- Include Company Intel — Defaults to true. Generates a sales dossier when a domain is available; disable it to vet only the person.
- Seller / Vetting Context — Optional context sent with the company dossier request to focus it on the vetting decision.
Output shape
One item per input item, each containing a single JSON object; with Continue On Fail enabled, failed items instead contain an error field.
Successful results include subject, mapped person enrichment, company_intel (null if not generated), company_leg_skipped (disabled or no_domain when skipped), derived signals, top-level vetting_confidence and recommended_action, and raw responses from both API calls. The person request always runs; the company dossier runs only when enabled and a domain is available.