Bulk data enrichment. Adds web-sourced fields (CEO names, funding, contact info) to lists of companies, people, or products. Use for enriching CSV files or inline data. Supports multi-turn: pass --previous-interaction-id from a prior research task to carry context forward.

Data Enrichment Enrich: $ARGUMENTS Before starting Inform the user that enrichment may take several minutes depending on the number of rows and fields requested. Optional: Suggest output columns If the user gave a vague intent ("enrich these companies with useful info") and you're not sure what columns to add, ask the API for a suggestion before kicking off the run: The response is an envelope: {title, processor, enriched columns, warnings} . Extract just the enriched columns array (not the whole envelope) and pass it as the value of enriched columns on enrich run , in place of intent — the two flags are alternative ways to specify what to enrich, not combined. If suggest returned a processor , pass it through explicitly via processor on the run call (it's a tuned recommendation for the schema). Skip this whole section if the user already specified the fields they want. enrich suggest requires parallel cli ≥ 0.3.0. If it errors with anything resembling no such command / No such command / unknown command , do not bail — skip the suggestion step, fall through to step 1 with intent , complete the run, and mention parallel cli update (or pipx upgrade parallel web tools ) in the final response so the user picks up the feature next time. Step 1: Start the enrichment Use ONE of these command patterns (substitute user's actual data): For inline data: For CSV file: If this is a follow up to a previous research task and you have its interaction id , add context chaining: The enrichment will run with the full context of that prior research — so you can enrich entities discovered earlier without restating what was already found. Note: enrichment does not itself produce a new interaction id , so you cannot chain a further follow up off of an enrichment. IMPORTANT: Always include no wait so the command returns immediately instead of blocking. Parse the json output to extract taskgroup id and url . The output is {taskgroup id, url, num runs} — there is no interaction id field, do not look for one. Immediately tell the user: Enrichment has been kicked off The monitoring URL where they can track progress Tell them they can background the polling step to continue working while it runs. Step 2: Poll for results Pick a concrete output path (e.g., /tmp/enrichment acme.json ). Note: the file is JSON regardless of the extension you choose — it's an array of {input, output} objects, not a CSV. Name it .json to avoid confusing yourself or the user. Important: Use timeout 540 (9 minutes) to stay within tool execution limits The target from step 1 is unused in no wait mode — only output here determines where results are saved, and the file is always JSON If the poll times out Enrichment of large datasets can take longer than 9 minutes. If the poll exits without completing: 1. Tell the user the enrichment is still running server side 2. Re run the same parallel cli enrich poll command to continue waiting Response format After step 1: Share the monitoring URL (for tracking progress). After step 2: 1. Report number of rows enriched 2. Preview first few rows from the output file (it's a JSON array of {input, output} objects) 3. Tell the user the full path to the output file Do NOT re share the monitoring URL after completion — the results are in the output file. Setup If parallel cli is not found, install and authenticate: If any parallel cli enrich command returns 403 , tell the user balance is likely required. Offer to run parallel cli balance get , and if needed ask for explicit confirmation before running parallel cli balance add <amount cents . Then retry the original enrichment command.

parallel-data-enrichment