who_to_contact

io.github.Capital-W-Holdings/us-property-parcel-real-estate-debt · Verify this server

For one organization (dfx_id, or its name in `organization`, resolved through the identity layer so every graph the institution is on is read) or one opportunity (opportunity_id from search_opportunities): ONE recommended person and up to two DISTINCT backups, ranked for a purpose (private_credit, advisor_recruiting, acquisitions, capital_raising, lending_desk, lp_fundraising ...). People come from every contact source DFX holds: the organization's own team pages, Form ADV Schedule A officers, sponsor and provider principals, private equity, venture, family office and allocator staff, and named contact routes. Each person carries title, role family, why they fit the purpose, decision authority (inferred from the title, or observed, labelled which), the contact route TYPES on record with their rights class (RESALEABLE, REVEALABLE, INTERNAL_USE) and verification, the kind and host of the evidence, and confidence by dimension. Never an email address, phone number or a person's page: routes are types only, and a person known only from a data provider is returned as a role with name null. If nobody on record holds a role that owns the purpose it says so and lists the roles that would; a generic inbox is never offered as a substitute. ACCESS: without a paid DFX plan on the vertical, a list returns its first 5 rows in full and a count of the rest by type (locked.count, locked.by_type), never the rows; a record names its subject and the first 3 related names per section; contact values (email, phone, profile URLs) and decision-maker names are never returned, only their types and counts. Every answer says what it withheld in `entitlement` and `locked`. Full access: DFX Intelligence, 3 days for $1 at https://dfxintel.com/data-factory/plans.