FINTRX

Browse a saved list page by page. Best for small lists. For larger lists, use the search tools with a list_id to filter and narrow down results.

fintrx_get_list_records

Get an activity summary for a saved list over a date window (default: the last 30 days). Summary types: - additions: records added to the list. - updates: list records whose data changed. - news_mentions: news articles mentioning list records. - reps_joined / reps_left: reps who joined or left firms in the list. - reps_movements: one aggregate view of movement activity — totals, top firms gaining and losing reps, and notable movers. - holdings_changes: 13F position changes at firms in the list. - investments: tracked direct + real estate investments made by the family offices in the list (FO lists only). This tool answers "what happened on this list in a window". For what the list looks like right now (geographic footprint, AUM, custodian concentration, macro 13F holdings) use fintrx_get_list_composition; to check the list's exposure to specific tickers use fintrx_get_list_ticker_exposure. Paging: every type paginates except reps_movements, which always returns one fixed aggregate — paging it just returns the same content again. Decide whether to fetch another page from _limits.has_more_pages, never from is_truncated: on the last page of a multi-page set is_truncated is still true while has_more_pages is false, so paging on is_truncated never terminates. (On reps_movements, is_truncated means a row ceiling was hit and is not a paging signal at all.) Page rows come back under items. Date windows: holdings_changes' window filters how recently a firm's 13F was filed, not when a holding changed; its position deltas always compare the two most recent quarters on file, so "what changed in June" really answers "firms whose filings were refreshed in June". news_mentions' window filters when an article was ingested, while each row reports its publication date (written_at), so an article published months ago can legitimately appear in a one-week window. investments is the opposite: its window filters investment_date — when the deal actually happened, not when FINTRX tracked it — so a recently ingested deal with an old investment date will not appear in a recent window. Freshness: reps_joined, reps_left and reps_movements carry as_of — the newest movement date actually on file, typically a few days behind today. Qualify movement figures with it instead of presenting them as current. If _limits.window_beyond_as_of is true, the requested window starts after the newest data on file, so a zero result means "not loaded yet", not "nothing happened". Empty results: supported=false means this summary type does not exist for this list type — a permanent gap, so say it is not available for this list rather than reporting no activity. has_data=false means the query ran fine and nothing matched the window. has_data describes the whole matched set, not the current page, so never infer "no results" from an empty array. Prefer output=markdown for reading or summarizing — especially holdings_changes, whose JSON is large and deeply nested; use json when filtering or aggregating across rows.

fintrx_get_list_summary

Check a saved list's exposure to specific tickers: which firms in the list hold them per 13F filings, with a cross-list rollup under aggregate, per-ticker breakdowns under tickers, and per-firm rows under items. Coverage: RIA lists only today. For any other list type the response comes back with supported=false — a permanent gap for that list, not an empty result. A firm missing from the rows means no 13F position on file for the requested tickers, which is not proof the firm never held them off-13F. Tickers: pass 1-10 symbols. Case-insensitive — uppercased before matching. More than 10 are silently dropped; the applied set is declared in _limits. Paging: firm rows paginate. Fetch another page only while _limits.has_more_pages is true, never from is_truncated (still true on the last page). Prefer output=markdown for reading or summarizing; use json when filtering or aggregating across rows.

fintrx_get_list_ticker_exposure

Get a single RIA contact's (person's) full profile — role/title snapshot, contact info (email, phone, LinkedIn), current and past firms, education, licenses, hobbies, accolades, private wealth teams, an AI-generated biography, plus network/affinity context scoped to the authenticated user (introduction opportunities, teammate connections, conversation starters). Prefer output=markdown to read the biography and profile together as prose. id_type is required. Pass the identifier in crd_id: use a CRD (rep_crd) only when id_type=crd_id; when id_type=id, pass the contact's internal database ID instead. Never put a CRD in crd_id unless id_type=crd_id. This is the individual's identifier, not a firm CRD. To find a CRD, use fintrx_lookup_ria_entity with entity_type=contact (returns rep_crd), or fintrx_get_ria_investor_contacts to browse a firm's people.

fintrx_get_ria_contact_overview

Get an RIA firm's yearly AUM and account-count time series (with YoY % deltas) plus its Form ADV client breakdown: for every filed year, the total client count (client_breakdown.accounts.accounts_breakdown[].total_clients; the "Clients by Year" table in markdown, with AUM per client) and client counts and AUM by client type (HNWI, pension plans, corporations, etc). Clients and accounts are different counts — use total_clients for anything per client. The quarterly series is opt-in via include_quarterly. Not paginated; bounded by year range instead. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_aum_accounts

Get an RIA firm's Separately Managed Account (SMA) asset-class breakdown across 12 fixed categories (exchange/non-exchange equities, government/municipal/sovereign/corporate bonds, derivatives, public funds, private funds, cash, other) as both % and $ of the firm's estimated SMA assets, plus a most-used-asset-type and equities/fixed-income/other preference summary, current and year-over-year. Scoped to SMA assets specifically, not the firm's total AUM. No filters beyond the shared params. Numeric-heavy — default output=json. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_asset_breakdown

Get people at an RIA firm (executives, advisors, support staff), filterable by role, responsibility, title substring, location, status flags and has_regulatory_disclosures. title is the fallback when role/responsibility come back empty — those are curated fields, while most contacts carry a filed title. Basic rows already carry rep_aum, firm_tenure, industry_tenure, designations, office_phone_number, ownership_percentage and is_producing_advisor, with empty fields omitted — one basic call covers a roster or a contact table. Sort with sort_by=rep_aum, sort_direction=desc to rank the largest producing advisors. Set detail_level=full only for the rich profile (bio, education, licenses, work history, accolades, per-contact disclosures) — this drops the max per_page to 10. Prefer output=markdown for reading/summarizing; use json if filtering on many fields at once. Network context is scoped to the authenticated user: every row carries connection_type (in_network, teammate_connection or intro_opportunity — null or omitted when there is no path; the Network column in markdown), has_introduction_opportunity, teammate_connections (first 5, with teammate_connections_total), affinity_score and a conversation_starter; detail_level=full adds profile.best_path (the connector to go through, with title, firm, relationship kind and how they may know the contact) and up to 5 profile.conversation_starters. Filter with any_connection=true for only the people the user can reach through any of those paths (false for only the unreachable ones). If the user's team has no network features, these fields are empty and any_connection returns a 400 — report that as 'network not enabled', never as 'no connections'. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_contacts

Get an RIA firm's rep hiring/departure activity over a date window (default: trailing 1 year) — summary stats (total joins/departures, net flow, producing advisors moved), top firms people are coming from/going to, notable movers (by industry tenure), and up to 25 recently joined and 25 recently departed reps each with a plain-language summary and, when known, the firm they came from or went to. Note: a contact who left and later rejoined this same firm keeps their original join date, so a recent rejoin won't surface as a fresh join. Prefer output=markdown for reading. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_contacts_movements

Get an RIA firm's current custodian relationships (who holds its assets) plus a 12-quarter historical view. No filters — per-firm datasets are small (typically single-digit rows); either output format works equally well. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_custodians

Get RIA firms this firm has acquired (approved M&A transactions only), with acquired-firm details (AUM at acquisition, employee/owner counts, location, active status, AI-generated deal and firm bios) and linked news per deal, plus the acquiring firm's own M&A bio. This is the buyer side (deals this firm closed); for the firm as an acquisition target — FINTRX Acquisition Score and the metrics behind it — use fintrx_get_ria_investor_ma_evaluation. Filterable by acquired-firm name/CRD, acquired-firm state, and acquisition year; sortable on 7 fields. Note: owners/news sort orders are computed in-memory rather than in SQL and may be slower on firms with many acquisitions. Prefer output=markdown for reading; json if aggregating across deals. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_historical_acquisitions

Get an RIA firm's 13F equity/ETF/options holdings for one filing quarter (omit year/quarter to get the firm's latest filed quarter — preferred unless the user names a period), with sector/style/ETF-category breakdowns and new/closed positions vs. the prior quarter. Every response, including an empty one, carries latest_filed_period — use it to label the quarter, and never walk back through quarters looking for data. For ETF-brand exposure questions ('total assets in ProShares ETFs'), filter with etf_provider and read total_value — no need to paginate the rows. total_value/total_count and the breakdowns always reflect the filtered set. Note: the new/closed position comparison is only available when the resolved quarter is the firm's latest filed one, and options are excluded unless holding_type is set. Numeric-heavy — default output=json. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_holdings

Get an RIA firm's M&A evaluation as an acquisition TARGET — the FINTRX Acquisition Score (score.value, 1-100, a proprietary measure of the firm's attractiveness and willingness to entertain M&A) with score.year, plus the metrics behind it: growth (total AUM, 1/3/5-year AUM CAGR with a 3-year percentile), advisor_composition (producing-advisor count, average advisor age, firm and industry tenure, AUM per producing advisor — each tenure/AUM figure with a peer percentile), ownership (institutional participation, individual vs entity owner counts, average owner age, ownership-concentration percentile) and team (employees, reps, offices, clients, regulatory-disclosure flag, year-by-year producing vs non-producing advisor counts). The buyer side — deals this firm itself closed — is fintrx_get_ria_investor_historical_acquisitions. Always cite the score with score.year: the score job writes the current and previous year together, so a firm not recomputed since January reports last year's score. Percentiles rank the firm against peers for that same year. cagr_1y_pct and cagr_5y_pct come back as 0 (not null) when the firm has no baseline filing that far back — do not read that 0 as a real growth rate; cagr_3y_pct is null in that case. has_data=false with empty_reason=not_covered means FINTRX has not computed a score for this firm — report the score as unavailable, never as low. No filters beyond the shared params. Prefer output=markdown for reading; json when comparing metrics across firms.

fintrx_get_ria_investor_ma_evaluation

Get news articles mentioning an RIA firm — hires, M&A, general coverage — optionally filtered by type and date range. Prefer output=markdown for reading/summarizing. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_news

Get an RIA firm's HQ and branch office addresses, deduplicated, with a per-state count summary. No location filter is exposed — pagination only. Prefer output=markdown for reading. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_office_locations

Get a single RIA firm's snapshot — SEC registration status/region, state registrations (states_registered codes plus state_registrations with per-state status and effective_date), AUM, employee and account counts, contact count, HQ location, phone/website/LinkedIn (other_websites lists the remaining Form ADV sites), brochure link, ma_score (latest FINTRX Acquisition Score, 1-100, null when not computed — fintrx_get_ria_investor_ma_evaluation has the metrics behind it), latest_filed_period (most recent 13F quarter, null if the firm has never filed one), and the Form ADV Part 1 label arrays fee_structure (Item 5.E), advisory_activities (Item 5.G), client_base and client_types (Item 5.D) — plus an AI-generated firm biography and a disclosures block with the firm's own Form ADV Item 11 answers (has_disclosures, count, the items answered yes, as_of; null when not reported). No filters beyond the shared params. Prefer output=markdown to read the biography and snapshot together as prose.

fintrx_get_ria_investor_overview

Get who owns an RIA firm, from Form ADV Schedule A: individuals, domestic entities and foreign entities, each with their stake, control-person flag, owner-since date and, when the owner is itself a tracked firm or contact, a profile link. Filter with owner_type, control_person and name_contains; sort by stake, name, owner-since or type. Stakes are the filed bands ("25% but less than 50%", "75% or more") — Schedule A never reports an exact percentage, so do not present one. The summary block always describes the whole firm and ignores your filters (owner counts by type, control persons, the band breakdown); only owners and its pagination respond to them. summary.majority_owners is the direct answer to "who controls this firm" — owners at 50%+, listed up to 10 with majority_owners_count for the true total, so it survives paging and filtering. An entity owner's crd_id is that owner's own firm CRD: feed it back into the other fintrx_get_ria_investor_* tools to profile a parent company. Prefer output=markdown for reading. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_ownership

Get the Form ADV Schedule D private funds an RIA firm advises — aggregate stats (fund count, most common fund type, average gross asset value and ownership %, owner count), a per-fund list, and a year-over-year breakdown by fund type. has_data can be true even with zero current funds if the firm has historical filings — check it rather than treating an empty fund list as 'never advised any.' Prefer output=markdown for reading; json if aggregating across funds. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_private_funds

Check whether an RIA firm has ever held one or more specific tickers, plus open/closed/never-held status and the value trend over time. Distinguishes never-held from closed, which a plain holdings query can't. Known limitation: an options-only position reads as never_held, since this only tracks non-options rows. Numeric trend data — default output=json. Not paginated; bounded by the number of tickers requested. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_ticker_positions

Get private wealth teams at an RIA firm (roster, AUM, specialties), filterable by location and AUM range. Set detail_level=full for a per-team historical blueprint timeline (name/parent-company changes, M&A movement, linked news) — this drops the max per_page to 10. Note: if the authenticated user lacks private-wealth-team access, the response degrades to has_data=false with an empty team list and empty_reason=no_access regardless of filters — never read that as 'this firm has no teams.' Prefer output=markdown unless aggregating AUM across teams. An empty result carries empty_reason: no_records (the firm has none), no_access (your account cannot see them) or not_covered (FINTRX has no filing for this firm) — report that distinction rather than 'none'.

fintrx_get_ria_investor_wealth_teams

Retrieve recent news articles from the FINTRX platform. Use this tool to browse and filter news across the wealth management industry. Articles can be filtered by date range, article type, entity type, and optionally a specific entity ID. Article types: - New Hire: Personnel changes, new appointments, and executive moves. - Investment Activity: Investment-related news, fund launches, and portfolio changes. - General News: General industry coverage, market commentary, and firm updates. - Mergers & Acquisitions: M&A activity, firm acquisitions, and mergers. Entity types: - investor: News related to Family Office firms. - contact: News related to Family Office contacts. - ria_investor: News related to RIA firms. - ria_contact: News related to RIA contacts.

fintrx_get_recent_news

Retrieve the affinity context for the current user. Use this tool to discover shared personal and professional background details between the user and their prospects, enabling warm, personalized outreach. Returns a JSON object with the user's personal and professional background: - hobbies: List of personal interests and activities. - universities: Educational institutions attended, including start and end years. - companies: Previous employers or professional affiliations, including tenure. - societal_affiliations: Civic, cultural, or professional society memberships. - cities: Cities the user has lived in or is connected to. - designations: Professional designations (e.g., CFA, CFP). - board_affiliations: Board memberships or advisory roles. - charity: Charitable organizations the user supports. - military_experience: Whether the user has military service background. Use this tool when you need to: - Find common ground between the user and a prospect - Craft personalized conversation starters based on shared backgrounds - Identify networking angles (shared alumni networks, cities, interests)

fintrx_get_user_affinity_data

Retrieve the ETF (Exchange-Traded Fund) context for the current user. Use this tool to understand the user's ETF product offerings and how they compare to competitors within a prospect's portfolio. Returns a JSON object with the user's ETF configuration: - etf_context: An array of ETF entries, each containing: - user_ticker: The ETF ticker the user manages or sells. - context: Additional context or notes about the ETF. - user_investment: The user's ETF details (name, ticker, category). - competitor_investments: List of competing ETFs held by the prospect (name, ticker, category). - custodial_platforms: Custodial platforms where the ETF is available. Use this tool when you need to: - Understand which ETFs the user offers and their competitive positioning - Identify prospects already holding competitor ETFs for targeted outreach - Tailor ETF-related messaging to a specific prospect's holdings

fintrx_get_user_etf_data

Get all saved lists for the current user.

fintrx_get_user_lists

Retrieve the AI personalization context configured by the current user. Use this tool to get information that helps tailor prospecting, analysis, and messaging to the user's business goals and target audience within the wealth management industry. Returns a JSON object containing the user's AI configuration: - about_my_company: Description of the user's company, products, services, and positioning within the financial services ecosystem. - ideal_contact: Description of the types of professionals the user wants to connect with (for example: CIOs, portfolio managers, research directors, advisors). - ideal_firm: Description of the types of firms that best match the user's target prospect profile. Use this tool when you need to: - Personalize outreach messages - Evaluate whether a contact or firm fits the user's target profile - Generate prospecting insights aligned with the user's goals - Prioritize leads - Understand the user's company and market focus

fintrx_get_user_personalization_settings

Get a private wealth team's year-by-year history (newest first) — firm moves, renames, and AUM/AUA/headcount snapshots with narrative bios and linked press per transition. Compare previous/current team-name and parent-company pairs to infer renames and firm moves (the markdown output renders these inferences directly). Not paginated — the full set returns at once. This is the standalone team-scoped timeline, keyed by a single wealth_team_id; it differs from the firm-scoped fintrx_get_ria_investor_wealth_teams detail_level=full blueprint view, which lists blueprints across all of a firm's teams. Get the wealth_team_id from an overview (has_historical_blueprints=true) or the wealth_teams search/topic.

fintrx_get_wealth_team_historical_blueprints

Get news articles tagged to a private wealth team, newest first — hires, investment activity, M&A, general coverage — optionally filtered by type and date range, paginated. This team-scoped endpoint is the only way to pull team news (wealth_team is intentionally not an entity_type on fintrx_get_recent_news). Note: each article's own entity_type reads "ria_investor" because team news is stored as parent-firm news tagged with team ids — the endpoint still filters correctly by team, so don't filter on that label. Get the wealth_team_id from an overview (has_news=true) or the wealth_teams search/topic. Prefer output=markdown for reading/summarizing.

fintrx_get_wealth_team_news

Get a private wealth team's office addresses (principal first, then branches by state) plus a per-state count summary covering the whole set, paginated. Check has_data before treating an empty result as "no offices." Get the wealth_team_id from an overview (has_offices=true) or the wealth_teams search/topic. Prefer output=markdown for reading.

fintrx_get_wealth_team_office_locations

Get a single private wealth team's snapshot in one call — name, AUM, minimum account size, principal-office location and contact info (phone, email, website), team_size and the member roster (each with ria_contact_id, name, title, email, LinkedIn, ownership %), bio, specialties, client types, investments utilized, accolades, and the parent_firm block (id, crd_id, name, url). Also returns has_news / has_offices / has_historical_blueprints flags telling you which sibling tools will return data. Prefer output=markdown unless aggregating AUM across teams. Takes a single wealth_team_id (the team's integer FINTRX id) — there is no id_type; a team's crd_id is its shared parent-firm CRD and cannot identify it. Get the id from fintrx_search_ria_wealth_teams, fintrx_lookup_ria_entity, or an RIA investor's wealth_teams topic. Cross-entity hops: each member's ria_contact_id feeds fintrx_get_ria_contact_overview, and parent_firm.crd_id feeds the fintrx_get_ria_investor_* tools. Follow has_news → fintrx_get_wealth_team_news, has_offices → fintrx_get_wealth_team_office_locations, has_historical_blueprints → fintrx_get_wealth_team_historical_blueprints. A 403 means your subscription does not include Private Wealth Teams data; a 404 means no such team.

fintrx_get_wealth_team_overview

Resolve a specific Family Office firm or contact from a name (fuzzy), CRD number, email address, LinkedIn URL, or web domain. Use this FIRST whenever the user references a specific family office or its people — it is cheaper and more reliable than the search tools. Returns top candidates ranked by match confidence, each with what the query matched on and a thin profile (type, location, AUM range, firm affiliation) to confirm which entity is meant. Firm results carry id — pass it as family_office_id to the fintrx_get_family_office_* tools. Contact results carry the contact's own id (not directly usable in another tool call) plus profile.current_firm.id, the firm's family_office_id — feed that into fintrx_get_family_office_contacts to see the contact in context. If several candidates plausibly match an ambiguous name, present them to the user rather than guessing. Covers the Family Office dataset only — no wealth teams (RIA-only; use fintrx_lookup_ria_entity for those). CRD matches firms only, and only the small minority that are SEC-registered — a miss doesn't mean the firm isn't in FINTRX, retry with name. LinkedIn matches contacts only (FO firms have no LinkedIn column); email and web-domain queries match both firms (company email/website) and contacts (email). NOT for building lists by criteria (use fintrx_search_fo_firms or fintrx_search_fo_contacts) and NOT for deep data on an already-identified firm (use the fintrx_get_family_office_* tools with its family_office_id).

fintrx_lookup_family_office_entity

Resolve a specific RIA firm, contact, or private wealth team from a name (fuzzy), CRD number, email address, LinkedIn URL, or web domain. Use this FIRST whenever the user references a specific entity — it is cheaper and more reliable than the search tools. Returns top candidates ranked by match confidence, each with its ids (crd_id for firms, rep_crd for contacts — the fintrx_get_ria_investor_* tools take these), what the query matched on, and a thin profile (title/classification, location, AUM, firm affiliation) to confirm which entity is meant. If several candidates plausibly match an ambiguous name, present them to the user rather than guessing. Covers the RIA dataset only. Email and web-domain queries match contacts by email address; LinkedIn '/in/' URLs match contacts and '/company/' URLs match firms. NOT for building lists by criteria (use fintrx_search_ria_firms / fintrx_search_ria_contacts / fintrx_search_ria_wealth_teams) and NOT for deep data on an already-identified firm (use the fintrx_get_ria_investor_* tools with its crd_id).

fintrx_lookup_ria_entity

Resolve a free-text value to the canonical value(s) stored in FINTRX for a given filter field — custodian names, universities, metro areas, tickers, licenses, designations, hobbies, TAMPs, family office types, wealth origins. Use BEFORE filtering on an open-vocabulary field when unsure of the exact stored form ('Schwab' vs 'Charles Schwab & Co., Inc.'). An unmatched value passed to a search filter matches no records — it is not ignored. Returns candidates with match scores.

fintrx_match_filter_values

Search family office contacts (executives, investment staff, advisors) by role, title, responsibilities, education, hobbies, location, and current/previous family office. Use for people prospecting across family offices (e.g. "CIOs at multi-family offices in New York"). NOT for firm searches (use fintrx_search_fo_firms). For contact filters not exposed here, use advanced_filters with paths from fintrx_get_filter_catalog(entity='fo_contact', scope='advanced'). Filters are flat parameters. Array parameters include values; the sibling '<name>_exclude' parameters exclude them — never set a parameter and its _exclude sibling together. Use within_radius (not state/city/zip) whenever the user mentions a distance. Set result_mode='count' for how-many questions. Results are paged: per_page max 100 for RIA tools, 25 for family office tools; default 25. The response carries total_count and a pagination block (page, per_page, returned, has_more, next_page). detail_level defaults to basic (list-building fields, no biography); full adds the AI biography and network details per row and caps per_page at 10. output defaults to json; output='markdown' returns a compact table with linked names, the total and the view_in_fintrx link — prefer it when presenting a list to a user, and json when chaining ids into other tools. For open-vocabulary values (custodians, universities, tickers, …) whose exact stored form you don't know, resolve them first with fintrx_match_filter_values — unmatched values match no records. fintrx_get_filter_catalog lists every parameter with its allowed values. To filter by CRM sync status (synced to Salesforce/HubSpot/Dynamics/DealCloud), use advanced_filters with the sync_filters.* paths from the catalog's 'advanced' scope. If the response contains 'warnings', read them: they explain values that matched nothing or clauses that were dropped, and how to fix the query. Always present the returned view_in_fintrx to the user as a clickable link labeled "To view these results in full within FINTRX, click here".

fintrx_search_fo_contacts

Search family office firms by criteria — location, AUM, family office type, wealth origin, investment preferences (asset classes, co-investing, impact/ESG, emerging managers, emerging markets), and direct-investment sectors/industries/stages. Use for family office list-building and prospecting (e.g. "$1B+ single family offices in California active in venture capital"). NOT for people searches (use fintrx_search_fo_contacts). For firm filters not exposed here, use advanced_filters with paths from fintrx_get_filter_catalog(entity='fo_firm', scope='advanced'). Filters are flat parameters. Array parameters include values; the sibling '<name>_exclude' parameters exclude them — never set a parameter and its _exclude sibling together. Use within_radius (not state/city/zip) whenever the user mentions a distance. Set result_mode='count' for how-many questions. Results are paged: per_page max 100 for RIA tools, 25 for family office tools; default 25. The response carries total_count and a pagination block (page, per_page, returned, has_more, next_page). detail_level defaults to basic (list-building fields, no biography); full adds the AI biography and network details per row and caps per_page at 10. output defaults to json; output='markdown' returns a compact table with linked names, the total and the view_in_fintrx link — prefer it when presenting a list to a user, and json when chaining ids into other tools. For open-vocabulary values (custodians, universities, tickers, …) whose exact stored form you don't know, resolve them first with fintrx_match_filter_values — unmatched values match no records. fintrx_get_filter_catalog lists every parameter with its allowed values. To filter by CRM sync status (synced to Salesforce/HubSpot/Dynamics/DealCloud), use advanced_filters with the sync_filters.* paths from the catalog's 'advanced' scope. If the response contains 'warnings', read them: they explain values that matched nothing or clauses that were dropped, and how to fix the query. Always present the returned view_in_fintrx to the user as a clickable link labeled "To view these results in full within FINTRX, click here".

fintrx_search_fo_firms

Search contacts (advisors, executives, staff) across all RIA/BD firms by role, title, licenses/designations, location, AUM, tenure, movement, and more. Use for people prospecting across firms (e.g. "producing advisors with a CFP in Texas who joined a new firm in the last year"). NOT for firm searches (use fintrx_search_ria_firms). Location parameters refer to the contact's branch office, not the firm HQ. To restrict by employer characteristics pass at_firms_matching (criteria on the contact's CURRENT firm); to target specific employers by name use current_firm. For contact filters not exposed here, use advanced_filters with paths from fintrx_get_filter_catalog(scope='advanced'). Filters are flat parameters. Array parameters include values; the sibling '<name>_exclude' parameters exclude them — never set a parameter and its _exclude sibling together. Use within_radius (not state/city/zip) whenever the user mentions a distance. Set result_mode='count' for how-many questions. Results are paged: per_page max 100 for RIA tools, 25 for family office tools; default 25. The response carries total_count and a pagination block (page, per_page, returned, has_more, next_page). detail_level defaults to basic (list-building fields, no biography); full adds the AI biography and network details per row and caps per_page at 10. output defaults to json; output='markdown' returns a compact table with linked names, the total and the view_in_fintrx link — prefer it when presenting a list to a user, and json when chaining ids into other tools. For open-vocabulary values (custodians, universities, tickers, …) whose exact stored form you don't know, resolve them first with fintrx_match_filter_values — unmatched values match no records. fintrx_get_filter_catalog lists every parameter with its allowed values. To filter by CRM sync status (synced to Salesforce/HubSpot/Dynamics/DealCloud), use advanced_filters with the sync_filters.* paths from the catalog's 'advanced' scope. If the response contains 'warnings', read them: they explain values that matched nothing or clauses that were dropped, and how to fix the query. Always present the returned view_in_fintrx to the user as a clickable link labeled "To view these results in full within FINTRX, click here".

fintrx_search_ria_contacts

Search RIA/BD/ERA firms by criteria — location, AUM, classification, custodian, growth, size, holdings, hybrid rep presence, and more. Use for firm list-building and prospecting (e.g. "$1B+ independent RIAs in Texas that use Schwab"). NOT for people searches (use fintrx_search_ria_contacts) or wealth teams (use fintrx_search_ria_wealth_teams). For firm filters not exposed here, use advanced_filters with paths from fintrx_get_filter_catalog(entity='ria_firm', scope='advanced'). Every result row includes crd_id for chaining into other tools. Filters are flat parameters. Array parameters include values; the sibling '<name>_exclude' parameters exclude them — never set a parameter and its _exclude sibling together. Use within_radius (not state/city/zip) whenever the user mentions a distance. Set result_mode='count' for how-many questions. Results are paged: per_page max 100 for RIA tools, 25 for family office tools; default 25. The response carries total_count and a pagination block (page, per_page, returned, has_more, next_page). detail_level defaults to basic (list-building fields, no biography); full adds the AI biography and network details per row and caps per_page at 10. output defaults to json; output='markdown' returns a compact table with linked names, the total and the view_in_fintrx link — prefer it when presenting a list to a user, and json when chaining ids into other tools. For open-vocabulary values (custodians, universities, tickers, …) whose exact stored form you don't know, resolve them first with fintrx_match_filter_values — unmatched values match no records. fintrx_get_filter_catalog lists every parameter with its allowed values. To filter by CRM sync status (synced to Salesforce/HubSpot/Dynamics/DealCloud), use advanced_filters with the sync_filters.* paths from the catalog's 'advanced' scope. If the response contains 'warnings', read them: they explain values that matched nothing or clauses that were dropped, and how to fix the query. Always present the returned view_in_fintrx to the user as a clickable link labeled "To view these results in full within FINTRX, click here".

fintrx_search_ria_firms

Search private wealth teams/groups by name, parent company, location, AUM, clients served, services, team size, and acquisition history. Use for cross-firm team prospecting. NOT for firm or contact searches (use fintrx_search_ria_firms / fintrx_search_ria_contacts). For team filters not exposed here, use advanced_filters with paths from fintrx_get_filter_catalog(entity='ria_wealth_team', scope='advanced'). Filters are flat parameters. Array parameters include values; the sibling '<name>_exclude' parameters exclude them — never set a parameter and its _exclude sibling together. Use within_radius (not state/city/zip) whenever the user mentions a distance. Set result_mode='count' for how-many questions. Results are paged: per_page max 100 for RIA tools, 25 for family office tools; default 25. The response carries total_count and a pagination block (page, per_page, returned, has_more, next_page). detail_level defaults to basic (list-building fields, no biography); full adds the AI biography and network details per row and caps per_page at 10. output defaults to json; output='markdown' returns a compact table with linked names, the total and the view_in_fintrx link — prefer it when presenting a list to a user, and json when chaining ids into other tools. For open-vocabulary values (custodians, universities, tickers, …) whose exact stored form you don't know, resolve them first with fintrx_match_filter_values — unmatched values match no records. fintrx_get_filter_catalog lists every parameter with its allowed values. To filter by CRM sync status (synced to Salesforce/HubSpot/Dynamics/DealCloud), use advanced_filters with the sync_filters.* paths from the catalog's 'advanced' scope. If the response contains 'warnings', read them: they explain values that matched nothing or clauses that were dropped, and how to fix the query. Always present the returned view_in_fintrx to the user as a clickable link labeled "To view these results in full within FINTRX, click here".

fintrx_search_ria_wealth_teams