Harmonic
Discover and research startups
- Category
- Data & Analytics
- Primary Subcategory
- Private Markets, Deals & Expert Networks
View in the ChatGPT registry↗Integration details
Description
Search, enrich, and research startups, companies and investors using Harmonic's proprietary data on millions of companies and the people behind them. Get detailed company profiles with funding, location, founders, and network connections. Use natural language to find companies matching specific criteria. Create and manage lists of companies and people. Access your team's network mapping and saved searches. Discover startups earlier, research them faster, and act with confidence—an AI-powered research agent built into your workflow.
- Integration type
- Plugin
- Verification status
- Not applicable
- Platform
- ChatGPT
- Primary Subcategory
- Private Markets, Deals & Expert Networks
- Secondary Subcategories
- None listed
- Brand
- Harmonic
- Access
- Account required
- First tracked
- 2026-09-10
- Tool count
- 43
- Geography
- US
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Get alerts for Harmonic
Get updates when Harmonic’s Discoverability Score or category rank changes.
ChatGPT Plugin Discovery Score
ChatGPT Plugin discovery is coming soon
ChatGPT can surface a Plugin when it matches a user's request.Your Plugin Discovery Score measures how often yours appears.
No spam. Unsubscribe any time.
What discovery looks like
Competing in ChatGPT Private Markets, Deals & Expert Networks
View Category43 tools agents can invoke
Add companies to an existing company list. This tool can ONLY add companies — it cannot remove companies from a list. Supports company URNs, IDs, or canonical identifiers (website URL, LinkedIn, Crunchbase, Pitchbook, etc.). Judge success by 'companies_found_count' (companies matched and written by this call); duplicates already in the list are de-duped server-side. 'total_companies_count' counts only fully-enriched entries and LAGS the write by seconds to minutes, so a low value right after adding is expected — do NOT re-add based on it. Returns 'console_link', a direct link to the list.
add_companies_to_list
Add people to an existing people list. This tool can ONLY add people — it cannot remove people from a list. Supports person URNs or canonical identifiers (LinkedIn URL). Judge success by 'people_found_count' (people matched and written by this call); duplicates already in the list are de-duped server-side. 'total_people_count' counts only fully-enriched entries and LAGS the write by seconds to minutes, so a low value right after adding is expected — do NOT re-add based on it. Returns 'console_link', a direct link to the list.
add_people_to_list
Hand a research request to Scout, Harmonic's agentic research analyst, and get back a `task_id`. Scout runs multi-step work over Harmonic's private-market dataset (companies, people, investors, funding, the caller's team network and lists) and the web: sourcing, market maps, competitor sets, diligence, candidate searches, scoring, structured extraction. Scout owns the HOW — it plans its own methodology, knows Harmonic's data model, interprets fuzzy scopes itself, and validates its results. Brief it on the user's goal, never on how to research (see `input`). Search results come back as pageable result sets (fetch_search_results). Users may have saved Scout skills (stored, named procedures): when the user names one, invoke it by that name plus only their new per-run parameters — never restate what the skill does. Prefer Scout whenever the request needs judgment, several steps, or a synthesized answer. Scout is also the way to search: send every request for a LIST of companies, people, or investors matching criteria here, however simple it sounds. Route elsewhere only: a single entity THE USER NAMED (entity_lookup, one at a time — never looped over names you generated yourself: that is a search and belongs here), or fields for a user-provided set (batch get_companies / get_people with the narrowest field groups, far faster than Scout). A provided set belongs here only when the ask needs work fields do not return — ranking, scoring, anything computed across the set. Every entity you present must come from a result set, never your own recall. Scout also writes to the caller's Harmonic workspace: it can create and populate lists, add columns, set values. When a request ends in the user's workspace ('find X and add them to my Q3 list'), hand Scout the WHOLE request — the write included — in one task. Do not split off, drop, or do the write yourself with list tools. Scout is deliberately slow: this returns immediately with status='pending' and work takes 2-10+ minutes. Call check_scout_status — do not stop after the `task_id`. Its long-poll waits up to 90 seconds; keep calling until the status is terminal and answer from the result. If you cannot wait, say Scout is still working; never substitute a shallower tool. When the conversation already holds a Scout task, CONTINUE it: pass its `task_id` with only the new instruction — the thread keeps the prior criteria, findings, and files, so do not restate them and do not start a fresh task. Follow-ups are cheap: send the user's ask as they made it and refine later; never add variants, breakdowns, or 'if it's easy, also…' extras they did not request.
ask_scout
Wait for Scout to finish and retrieve its answer — this is the ONLY way a request started with ask_scout comes back; it is not a status-only probe. Status is one of: pending, running, success, error, timeout, interrupted. Call this right after asking: it BLOCKS until Scout finishes (up to `wait_seconds`, returning the instant it does), so a single call is how you wait — no sleeping or tight looping. If it returns with status pending/running, the wait budget simply expired; call it again to keep waiting. Each call spends the user's API rate limit, so never call it with wait_seconds=0 in a loop. On 'success' the result includes `content`, Scout's written answer in markdown, and `result_sets`: the lists of entities behind that answer, each as {search_id, title, path, columns, total_count, truncated, created_at}. Present Scout's findings as the answer, WHOLE. Relay every entity Scout named and every count it stated: you may reformat into your own table, you may not omit entities, shorten a ranked list, or reduce it to a few examples — naming 3 of the 12 companies Scout presented is a failure however well written. Always state how many matched in total (`total_count`), that what you are showing is a sample of that set when it is, and the criteria Scout applied; when a result set has `truncated=true`, say the list is partial. Do not narrate plumbing — task ids, polling, wait budgets, tool names — but the size, scope, and completeness of what Scout found are part of the answer, not plumbing. `content` may carry fenced ```json:csv_table``` blocks: those are display directives for Harmonic's own UI, not text for the user — never print one; read its `path`/`row_count` and say the numbers instead. Scout may also close by offering further work ('Want me to…?'). That line is addressed to YOU, not to the user: never repeat it back to them, and never treat it as licence to defer. Decide for yourself whether to do that work, offer it in your own words, or drop it. Treat terminal `content` as Scout's complete answer; do not verify or enrich it with other Harmonic tools unless the user separately asks you to. `content` quotes only a sample of a search: the full set is pageable with fetch_search_results (`search_id` in `result_sets`), and no re-search is ever needed to get it. Judge from the request and your surface whether the user is better served by the sample, the full set, or a filtered cut of it — someone who asked for a shortlist may not want every row of a set in the hundreds or thousands; someone who asked to filter, rank, or export needs them all. A thread that refined its results lists every version it presented, each pageable; `path` ends in `_vN.csv`, and the highest N of a given name is the current cut. Entries are ordered by most recent presentation, NOT by version. On the user-authenticated MCP surface, every terminal response also includes `scout_usage`, a snapshot taken when that status response is produced. Treat it as historical context; call check_scout_usage when the user asks for current usage after time has passed or freshness is uncertain. For an immediate question explicitly about that just-produced snapshot, use it without refreshing. Report usage facts and available actions neutrally: do not recommend conserving or spending usage, and do not infer whether another Scout task will fit within the remaining percentage. Terminal usage behavior is required in the SAME answer as Scout's result: for `limit_reached`, always say that another Scout task cannot run until usage resets or more is added, give `resets_on`, and present only the supplied recovery actions, including each action URL when present. For `approaching_limit`, always give `percent_remaining`, `resets_on`, and any supplied actions. Never offer other Harmonic tools as a workaround for exhausted Scout usage or tell the user to wait for the reset. Do not mention `within_limit` or `usage_unavailable` snapshots unless the user asks about usage; omit those snapshots entirely from the answer.
check_scout_status
Check how much Scout usage the user currently has left, when it resets, and the actions available if they need more. Use this whenever the user asks about current Scout usage or before Scout when they want to decide based on the remaining amount. Pass the user's IANA timezone when known; omitted timezone defaults to UTC. Do not refresh when the user explicitly asks about the usage snapshot attached to a just-completed Scout task; use that snapshot as historical context. Report the returned facts and available actions neutrally: do not recommend conserving or spending usage, and do not infer whether a particular Scout task will fit within the remaining percentage.
check_scout_usage
Create a new company list. Can optionally include companies using URNs, IDs, or canonical identifiers (website URL, LinkedIn, Crunchbase, Pitchbook, etc.). Can also create custom columns and set their values in a single operation. Returns a response with 'urn' field (e.g., 'urn:harmonic:company_watchlist:0f818bcf-...') and a 'console_link' field. IMPORTANT: use the 'console_link' field in the returned response to view the list in the console, rather than constructing the link yourself. When initial entries are provided, the response also surfaces counts from the entry-add step: 'companies_found_count' (matched and written — the success signal), 'companies_being_processed_count' (URNs still being enriched, not yet visible), and 'total_companies_count' (current size; LAGS due to enrichment, so a low value right after creation is expected).
create_company_list
Create a custom field (column) for a company list. Custom fields allow you to add additional data points to companies in your list. Returns the created custom field with its URN, which you'll need when setting values on list entries.
create_company_list_custom_field
Create a new global custom field for companies or people. Unlike list custom fields (columns on a specific list), global fields are properties on the company/person record itself, visible across all lists.
create_global_custom_field
Create a new people list. Can optionally include people using URNs or canonical identifiers (LinkedIn URL). Can also create custom columns and set their values in a single operation. Returns a response with 'urn' field (e.g., 'urn:harmonic:people_watchlist:0f818bcf-...'). and a 'console_link' field. IMPORTANT: use the 'console_link' field in the returned response to view the list in the console, rather than constructing the link yourself. When initial entries are provided, the response also surfaces counts from the entry-add step: 'people_found_count' (matched and written — the success signal), 'people_being_processed_count' (URNs still being enriched, not yet visible), and 'total_people_count' (current size; LAGS due to enrichment, so a low value right after creation is expected).
create_people_list
Create a custom field (column) for a people list. Custom fields allow you to add additional data points to people in your list. Returns the created custom field with its URN, which you'll need when setting values on list entries.
create_people_list_custom_field
Look up a SINGLE company, person, or investor by a natural-language reference and return its canonical Harmonic record(s). Use for individual lookups: an exact name ('Anthropic', 'Max Ruderman'), a name plus descriptor ('John Smith at Stripe'), or a short description of one entity. Returns a resolved match plus a few alternatives when the reference is ambiguous, each with its Harmonic URN. DO NOT use for multi-entity criteria search (e.g. 'fintech companies in NY that raised Series B') — use natural_language_search when it is available; otherwise use search_companies_natural_language. Resolves names, affiliations, descriptions, and typos.
entity_lookup
Read the complete list of entities behind one of the `result_sets` returned by check_scout_status. Given its `search_id` plus `offset`/`limit`, returns `columns`, parsed JSON `rows`, `total_count`, `returned_count`, `offset`, `has_more`, and `truncated`. A result set is immutable once presented — a later refinement publishes a NEW result set rather than changing this one — so pages never overlap or shift, no matter how long you take or how many follow-up tasks run in between: call repeatedly, advancing `offset` by `returned_count`, until `has_more` is false, and you will have every row exactly once. `truncated=true` means Scout hit its row cap and the list is partial — say so, or ask Scout for a narrower query. An unknown or purged `search_id` is an error, not an empty page. Max 1000 rows per call. Only works on Scout result sets; for a user's saved searches use get_saved_search_results.
fetch_search_results
Get detailed data for one or more companies. Accepts Harmonic company IDs, URNs, or external identifiers (website URL, domain, LinkedIn, etc.). Harmonic IDs and URNs identify existing company records. Supported external identifiers resolve company records when a Harmonic ID or URN is unavailable. For individual company name searches, use entity_lookup. For multi-company searches with criteria, use natural_language_search when it is available; otherwise use search_companies_natural_language. REQUIRED: You must specify field_groups to control which fields are returned. Additional field groups increase response size and latency. Available field groups: 'name_id_description_headcount_website' (basic info), 'funding' (funding data), 'location' (location data), 'highlights' (company highlights), 'team_correspondence_and_connections' (team connections), 'notes_and_list_membership' (notes and lists), 'web_social_headcount_timeseries' (traction metrics), 'founders_and_execs' (founders and executives), 'founders_ceo' (founders and CEO only), 'synced_affinity_lists' (affinity lists), 'mergers_acquisitions_subsidiaries' (M&A data), 'competitor_research_fields' (competitor research), 'date_added_to_harmonic' (initialization date), 'contact' (company emails, phone numbers, exec emails, and the primary contact email with the person it belongs to), 'external_profiles' (LinkedIn, Twitter, Crunchbase, Pitchbook URLs), 'founder_submissions' (founder-submitted data including fundraising status, founder story narrative, and file attachments like pitch decks), 'custom_fields' (the company's global custom field values; requires custom-field permission), 'all' (combined field set). Limit of 50 companies per request. Note: If a company ID is -1, that means we don't yet have a canonical company record. Company profiles can be viewed in Harmonic console at: https://console.harmonic.ai/dashboard/company/<id or urn>
get_companies
Get network connections into one or more companies — the people your team knows at each company, and through whom. Pick a mode: • Whole team (default, no scoping param set): every team member's connections. E.g. 'who on the team knows someone at', 'team connections to'. • Just me (only_my_connections=true): only the caller's OWN connections, scoped server-side to the authenticated user — do not pass a URN. E.g. 'do I know anyone at', 'my connections to'. • A specific teammate (connected_to_user_urn=<their URN>): only that teammate's connections; resolve the name to a URN via get_team_members first. E.g. 'who does Tyler know at'. userConnections is grouped by connected person: one row per distinct target person (name, LinkedIn, current role) with a connectedVia list of the teammate(s) who know them and each one's connectionSources — enough to answer 'who do we know / who is connected'. Email-only connections to people not resolved in Harmonic are summarized as an unresolvedEmailConnections count per company. Use connection_fields to additively pull more ONLY when needed: 'contact' for the target person's emails (outreach), 'correspondence' for each teammate's latest email + calendar event (meeting prep, last touchpoint).
get_company_connections
Get company list entries. Pass the ID or URN of the list to get entries. Supports cursor pagination. The response includes a top-level 'custom_field_definitions' array listing every custom field on the list (URN, name, type, and option URNs for SINGLE_SELECT/MULTI_SELECT/STATUS). When calling update_company_list_entries, look up the field URN — and option URN for select-typed fields — from this array. Do not infer URNs from the name keys in per-entry 'custom_fields'. To sort entries, pass 'sort_custom_field_urn' with the URN of the attribute to sort by (and 'sort_descending' for direction). You can sort by any of: - a Harmonic attribute — official record fields like name, funding total, or headcount; call explore_list_columns to get its URN (e.g. Name -> 'urn:harmonic:company_field:company_name'); - a custom list attribute the user added to this list; get its URN from the 'custom_field_definitions' in this response; - a custom global attribute on the company record; get its URN from list_global_custom_fields. If the attribute the user named is NOT in 'custom_field_definitions', do not give up — it may be a global attribute, so call list_global_custom_fields before concluding it isn't sortable. When sorting by a custom attribute (list or global), also pass 'sort_field_type' — the field's type from custom_field_definitions / list_global_custom_fields (e.g. TEXT, NUMBER, DATE).
get_company_list_entries
Get all company lists that the requesting user has access to. Returns lists with 'entityUrn' (e.g., 'urn:harmonic:company_watchlist:0f818bcf-...'), name, metadata, and `console_link`. IMPORTANT: use the 'console_link' field to view the list in the console instead of constructing the link yourself
get_company_lists
Poll a job returned by request_person_emails. Status is PENDING, IN_PROGRESS, COMPLETED, or FAILED. Enrichment commonly takes at least a minute, so do not poll immediately after submission: wait at least 60 seconds before the first status check. If the job is still PENDING or IN_PROGRESS, wait at least 15 seconds between later checks. A harness that can wait should keep polling; a chat client that cannot wait should explain that no email is available yet because enrichment is still running, and let the user check later with this job ID. Terminal responses include per-person outcomes: SUCCESS, NOT_FOUND, FAILED, or SKIPPED. Each SUCCESS result with a canonical person URN also includes its numeric person ID. When a person succeeds, call get_people with that person ID to retrieve the newly found email.
get_email_request_status
Get detailed investor data for one or more investors by URN or website URL. Accepts an array of investor identifier objects. Harmonic investor URNs identify existing records; website URLs resolve investor records when a Harmonic URN is unavailable. REQUIRED: You must specify field_groups to control which fields are returned. Additional field groups increase response size and latency. Investor profiles can be viewed in Harmonic console at: https://console.harmonic.ai/dashboard/investor/<urn>
get_investors
Get the caller's current team-level monthly email-enrichment quota. Email credits are a pooled allowance Harmonic provides to the team for requesting verified email lookups: one credit funds one eligible person's lookup, although finding an email is not guaranteed. Harmonic's documented standard allowance is 5,000 requests per customer account per month, resetting on the first of each month; use this tool's live result as the authority for the caller's actual plan. Call this immediately before asking the user to approve request_person_emails. Explain that the contemplated request may use up to one credit per submitted person, and tell the user how many credits remain out of the team's actual monthly limit. This result is a current snapshot, not a reservation or a guarantee of final consumption.
get_email_enrichment_usage
Get detailed data for one or more people. Accepts Harmonic person IDs, Harmonic person URNs, or LinkedIn profile URLs. Harmonic IDs and URNs identify existing person records. LinkedIn profile URLs resolve person records when neither is available. REQUIRED: You must specify field_groups to control which fields are returned. Additional field groups increase response size and latency. Available field groups: 'basic' (id, name, profile picture, headline, contact emails including the primary email, and email enrichment status), 'experience' (work experience with company details), 'education' (education history), 'location' (location data), 'socials' (social media links), 'custom_fields' (the person's global custom field values; requires custom-field permission), 'all' (all available groups). Limit of 50 people per request. Person profiles can be viewed in Harmonic console at: https://console.harmonic.ai/dashboard/person/<id or urn>
get_people
Get people list entries. Pass the ID or URN of the list to get entries. Supports cursor pagination. The response includes a top-level 'custom_field_definitions' array listing every custom field on the list (URN, name, type, and option URNs for SINGLE_SELECT/MULTI_SELECT/STATUS). When calling update_people_list_entries, look up the field URN — and option URN for select-typed fields — from this array. Do not infer URNs from the name keys in per-entry 'custom_fields'. To sort entries, pass 'sort_custom_field_urn' with the URN of the attribute to sort by (and 'sort_descending' for direction). You can sort by any of: - a Harmonic attribute — official record fields like name; call explore_list_columns to get its URN (e.g. Name -> 'urn:harmonic:person_field:person_name'); - a custom list attribute the user added to this list; get its URN from the 'custom_field_definitions' in this response; - a custom global attribute on the person record; get its URN from list_global_custom_fields. If the attribute the user named is NOT in 'custom_field_definitions', do not give up — it may be a global attribute, so call list_global_custom_fields before concluding it isn't sortable. When sorting by a custom attribute (list or global), also pass 'sort_field_type' — the field's type from custom_field_definitions / list_global_custom_fields (e.g. TEXT, NUMBER, DATE).
get_people_list_entries
Get all people lists that the requesting user has access to. Returns lists with 'entityUrn' (e.g., 'urn:harmonic:people_watchlist:0f818bcf-...'), name, metadata, and `console_link`. IMPORTANT: use the 'console_link' field to view the list in the console instead of constructing the link yourself
get_people_lists
Get network connections to one or more people by person ID. Returns all team members' connections by default. Pass a user URN in connected_to_user_urn to filter results to a single teammate's connections (either the caller themselves — e.g. 'my connections', 'do I know this person' — or a specific teammate, e.g. 'does Tyler know this person'). Leave connected_to_user_urn blank for general team-level queries (e.g. 'who on the team knows this person', 'team connections to'). Returns each person's profile (name, LinkedIn, current role) and userConnections. Each connection always includes the team member who has it and connectionSources — enough to answer 'do we know this person'. Add connection_fields=['correspondence'] to also include the latest email and calendar event, ONLY when the user needs correspondence/meeting context.
get_person_connections
Get net new results for a subscribed saved search (cursor pagination). Works for company, people, and investor saved searches — the entity type is determined by the saved search URN. Requires the saved search to be subscribed in the Harmonic console.
get_saved_search_net_new
Get saved search results with metadata (cursor pagination). Works for company, people, and investor saved searches — the entity type is determined by the saved search URN. Team API key can access only team-public saved searches. The saved search can be viewed in the Harmonic console at https://console.harmonic.ai/dashboard/companies/<urn> (people saved searches use /dashboard/people/<urn>).
get_saved_search_results
Watch a running Scout task and return what it is currently doing, as display copy for a progress view. Blocks for up to `window_seconds`, returning early when the task finishes. Intended for the interactive progress panel, not for reading results — use check_scout_status for the answer.
get_scout_progress
Get all team members for the current customer account. Returns each team member's email, name, entityUrn, role (ADMIN, MEMBER), and status (ACTIVE, INVITED). Use this tool to find team member emails for PERSON-type custom fields on watchlists.
get_team_members
Get the total number of people in the account's Team Network. Returns the count as network_connection_count.
get_team_network_connection_count
List all global custom fields for companies or people. Unlike list custom fields (columns on a specific list), global fields are properties on the company/person record itself, visible across all lists. Use this to discover available fields and their URNs before writing field values.
list_global_custom_fields
List all saved searches the user has access to. Returns saved searches with their query, type, name, creator, privacy status, and entity URN.
list_saved_searches
Set multiple global custom field values on a single company. Global fields are properties on the company record (not columns on a specific list). Use this when you need to update several fields at once on one company.
set_company_global_custom_fields
Set multiple global custom field values on a single person. Global fields are properties on the person record (not columns on a specific list). Use this when you need to update several fields at once on one person.
set_people_global_custom_fields
Submit a data issue report to Harmonic for a company or person. Use this to report incorrect, outdated, or missing data.
submit_data_report
Update a company list's name or shared_with_team setting. Returns 'console_link', a direct link to the list.
update_company_list
Update a custom field's name or metadata on a company list. You can update the field name or modify metadata like select options. For SINGLE_SELECT/MULTI_SELECT/STATUS fields: the options array in selectMetadata fully replaces the existing list. To rename, recolor, or reorder options without wiping data, first fetch the current field and pass each existing option's urn back unchanged in your payload; omit urn only for brand-new options. Any option whose urn is missing from the payload is deleted, which NULLs that option's value on every entry in the list.
update_company_list_custom_field
Update (upsert) custom field values on companies in a company list: if the company exists in the list its values are updated, otherwise it is added. Field URNs (custom_field_urn) and option URNs (data.selectData.value, every data.multiSelectData.value item) must come from 'custom_field_definitions' returned by get_company_list_entries; option display names (rather than URNs) are rejected. Judge success by 'companies_found_count' (entries matched and written); 'total_companies_count' reflects only fully-enriched entries and LAGS the write, so a low value right after the upsert is expected.
update_company_list_entries
Update a global custom field's name or metadata (e.g., select options, number format). The field type cannot be changed after creation. For SINGLE_SELECT/MULTI_SELECT/STATUS fields: the options array in selectMetadata fully replaces the existing list. To rename, recolor, or reorder options without wiping data, first fetch the current field and pass each existing option's urn back unchanged in your payload; omit urn only for brand-new options. Any option whose urn is missing from the payload is deleted, which NULLs that option's value on every entity the field is set on.
update_global_custom_field
Update a people list's name or shared_with_team setting. Returns 'console_link', a direct link to the list.
update_people_list
Update a custom field's name or metadata on a people list. You can update the field name or modify metadata like select options. For SINGLE_SELECT/MULTI_SELECT/STATUS fields: the options array in selectMetadata fully replaces the existing list. To rename, recolor, or reorder options without wiping data, first fetch the current field and pass each existing option's urn back unchanged in your payload; omit urn only for brand-new options. Any option whose urn is missing from the payload is deleted, which NULLs that option's value on every entry in the list.
update_people_list_custom_field
Update (upsert) custom field values on people in a people list: if the person exists in the list their values are updated, otherwise they are added. Field URNs (custom_field_urn) and option URNs (data.selectData.value, every data.multiSelectData.value item) must come from 'custom_field_definitions' returned by get_people_list_entries; option display names (rather than URNs) are rejected. Judge success by 'people_found_count' (entries matched and written); 'total_people_count' reflects only fully-enriched entries and LAGS the write, so a low value right after the upsert is expected.
update_people_list_entries
Set a global custom field value on one or more companies. Global fields are properties on the company record (not columns on a specific list). Sets the same field and value across all specified companies. To set different values per company, call this multiple times.
upsert_company_global_custom_field_values
Set a global custom field value on one or more people. Global fields are properties on the person record (not columns on a specific list). Sets the same field and value across all specified people. To set different values per person, call this multiple times.
upsert_people_global_custom_field_values
IMPORTANT: Email credits are a pooled allowance Harmonic provides to the team for requesting verified email lookups. One credit funds one eligible person's lookup, although finding an email is not guaranteed. Harmonic's documented standard allowance is 5,000 requests per customer account per month, resetting on the first; the caller's live plan may differ. Before asking for approval, call get_email_enrichment_usage and tell the user that this request may use up to one credit per submitted person, plus how many credits currently remain out of the team's actual monthly limit. People who already have an email, were attempted within the last 30 days, or cannot be resolved are dropped; if everyone is dropped, no credits are consumed. The usage result is a snapshot, not a reservation or final charge. The user must explicitly approve the possible credit use before this tool is called. Accepts either Harmonic person URNs or LinkedIn profile URLs, with up to 5,000 identifiers in one job. The response reports accepted and dropped identifiers plus a job_id. Email enrichment is asynchronous: plan for completion to take at least a minute and do not request status immediately. A harness that can wait should wait 60 seconds before the first get_email_request_status call; after completion, call get_people again to retrieve any newly found emails. A chat client that cannot wait should explain that no email is available yet because enrichment is still running, and let the user check the job status later with its job_id.
request_person_emails
How do I improve a ChatGPT Plugin's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
What are Harmonic alternatives on ChatGPT?
As of 2026-09-28, Harmonic competes with CapitalDart, CB Insights, Cookiedeal, Dakota Marketplace, Datasite, Evertrace, GLG, Guidepoint, Hadaly, Hebbia, In Practise, Mergr, PitchBook, PrefMark, Sacra, Specter, Third Bridge, TrustMRR, Venturu in ChatGPT Private Markets, Deals & Expert Networks, ranked by public Discoverability Score.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.