autotouch-cli 0.2.80__tar.gz → 0.2.81__tar.gz

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.80
+Version: 0.2.81
 Summary: Autotouch Smart Table CLI
 Project-URL: Homepage, https://app.autotouch.ai
 Project-URL: Documentation, https://github.com/nicolonic/autotouch_main/tree/main/docs/research-table/reference
@@ -146,11 +146,13 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 
 Autotouch has two different company/people discovery paths.
 
-Use `autotouch search companies` and `autotouch search people` for neural search when the target is niche, semantic, or hard to express with structured filters. Examples: "companies like Clay for healthcare", "AI workflow startups selling to law firms", or "RevOps operators at PLG SaaS companies". Neural company/people search returns at most 10 results per API call and costs 1 credit per API call.
+Use `autotouch search companies` and `autotouch search people` for neural search when the target is niche, semantic, or hard to express with structured filters. Examples: "AI workflow platforms for healthcare", "AI workflow startups selling to law firms", or "RevOps operators at PLG SaaS companies". Neural company/people search returns at most 10 results per API call and costs 1 credit per API call.
 
-Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable list construction. This is the default path for larger company and lead lists using filters like geography IDs, company size, industry IDs, title/persona, and current company IDs. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
+Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable list construction. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, add the records to a research table, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This is the default path for larger LinkedIn-sourced company and lead lists using filters like geography IDs, company size, industry IDs, title/persona, and current company IDs. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
 
-For account-first prospecting, build companies first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use neural search as a default pre-step for every list build; use it when the user's target is genuinely semantic or niche.
+For structured company builds, start with industry IDs plus geo/company-size filters. Company builds still need a broad `keywords` anchor (for example, `software`), but keywords are less reliable because they depend on company/profile text; use them to refine, disambiguate, or recover hard-to-classify targets instead of carrying the whole target definition.
+
+For account-first prospecting, build companies/accounts first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use neural search as a default pre-step for every list build; use it when the user's target is genuinely semantic or niche.
 
 ## More
 
@@ -158,7 +160,7 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.80` or newer for the 10-result neural search cap and provider-hidden `autotouch list-build ...`; older CLIs may still show the removed `autotouch linkedin list-build` surface
+- `autotouch --version` should be `0.2.81` or newer for the research-workspace list-build guidance, 10-result neural search cap, and provider-hidden `autotouch list-build ...`; older CLIs may still show the removed `autotouch linkedin list-build` surface
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch list-build companies` and `autotouch list-build leads` for durable provider-hidden company and lead list builds with Smart Table-owned background workers, visible progress, and no user-owned network connection requirement
 - `autotouch linkedin search` for one-page LinkedIn/Sales Navigator replay/debug searches; it is not the recommended path for large lists

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/README.md

@@ -121,11 +121,13 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 
 Autotouch has two different company/people discovery paths.
 
-Use `autotouch search companies` and `autotouch search people` for neural search when the target is niche, semantic, or hard to express with structured filters. Examples: "companies like Clay for healthcare", "AI workflow startups selling to law firms", or "RevOps operators at PLG SaaS companies". Neural company/people search returns at most 10 results per API call and costs 1 credit per API call.
+Use `autotouch search companies` and `autotouch search people` for neural search when the target is niche, semantic, or hard to express with structured filters. Examples: "AI workflow platforms for healthcare", "AI workflow startups selling to law firms", or "RevOps operators at PLG SaaS companies". Neural company/people search returns at most 10 results per API call and costs 1 credit per API call.
 
-Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable list construction. This is the default path for larger company and lead lists using filters like geography IDs, company size, industry IDs, title/persona, and current company IDs. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
+Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable list construction. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, add the records to a research table, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This is the default path for larger LinkedIn-sourced company and lead lists using filters like geography IDs, company size, industry IDs, title/persona, and current company IDs. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
 
-For account-first prospecting, build companies first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use neural search as a default pre-step for every list build; use it when the user's target is genuinely semantic or niche.
+For structured company builds, start with industry IDs plus geo/company-size filters. Company builds still need a broad `keywords` anchor (for example, `software`), but keywords are less reliable because they depend on company/profile text; use them to refine, disambiguate, or recover hard-to-classify targets instead of carrying the whole target definition.
+
+For account-first prospecting, build companies/accounts first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use neural search as a default pre-step for every list build; use it when the user's target is genuinely semantic or niche.
 
 ## More
 
@@ -133,7 +135,7 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.80` or newer for the 10-result neural search cap and provider-hidden `autotouch list-build ...`; older CLIs may still show the removed `autotouch linkedin list-build` surface
+- `autotouch --version` should be `0.2.81` or newer for the research-workspace list-build guidance, 10-result neural search cap, and provider-hidden `autotouch list-build ...`; older CLIs may still show the removed `autotouch linkedin list-build` surface
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch list-build companies` and `autotouch list-build leads` for durable provider-hidden company and lead list builds with Smart Table-owned background workers, visible progress, and no user-owned network connection requirement
 - `autotouch linkedin search` for one-page LinkedIn/Sales Navigator replay/debug searches; it is not the recommended path for large lists

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/autotouch_cli/data/CLI_REFERENCE.md

@@ -1,6 +1,6 @@
 # Autotouch CLI Reference
 
-Generated from the installed parser for `autotouch-cli` `0.2.80`.
+Generated from the installed parser for `autotouch-cli` `0.2.81`.
 Manifest schema version: `2`.
 
 ## Output Modes

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/autotouch_cli/data/cli-manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.2.80",
+  "version": "0.2.81",
   "manifest_schema_version": 2,
   "entry_points": {
     "autotouch": "autotouch_cli.cli:main",

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/autotouch_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: autotouch-cli
-Version: 0.2.80
+Version: 0.2.81
 Summary: Autotouch Smart Table CLI
 Project-URL: Homepage, https://app.autotouch.ai
 Project-URL: Documentation, https://github.com/nicolonic/autotouch_main/tree/main/docs/research-table/reference
@@ -146,11 +146,13 @@ autotouch rows get --table-id "$TABLE_ID" --row-id "$ROW_ID" --output json
 
 Autotouch has two different company/people discovery paths.
 
-Use `autotouch search companies` and `autotouch search people` for neural search when the target is niche, semantic, or hard to express with structured filters. Examples: "companies like Clay for healthcare", "AI workflow startups selling to law firms", or "RevOps operators at PLG SaaS companies". Neural company/people search returns at most 10 results per API call and costs 1 credit per API call.
+Use `autotouch search companies` and `autotouch search people` for neural search when the target is niche, semantic, or hard to express with structured filters. Examples: "AI workflow platforms for healthcare", "AI workflow startups selling to law firms", or "RevOps operators at PLG SaaS companies". Neural company/people search returns at most 10 results per API call and costs 1 credit per API call.
 
-Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable list construction. This is the default path for larger company and lead lists using filters like geography IDs, company size, industry IDs, title/persona, and current company IDs. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
+Use `autotouch list-build companies` and `autotouch list-build leads` for structured, repeatable list construction. Treat list builds as the sourcing step for the Smart Table research workspace: build company/account records first by default, add the records to a research table, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows from that table. Use lead builds directly when the request is explicitly person/contact focused. This is the default path for larger LinkedIn-sourced company and lead lists using filters like geography IDs, company size, industry IDs, title/persona, and current company IDs. Durable list builds run as background jobs with status/results endpoints and cost 1 credit per successful non-empty result page.
 
-For account-first prospecting, build companies first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use neural search as a default pre-step for every list build; use it when the user's target is genuinely semantic or niche.
+For structured company builds, start with industry IDs plus geo/company-size filters. Company builds still need a broad `keywords` anchor (for example, `software`), but keywords are less reliable because they depend on company/profile text; use them to refine, disambiguate, or recover hard-to-classify targets instead of carrying the whole target definition.
+
+For account-first prospecting, build companies/accounts first, inspect the returned company IDs, then pass those IDs to `autotouch list-build leads --current-company-id ...`. Do not use neural search as a default pre-step for every list build; use it when the user's target is genuinely semantic or niche.
 
 ## More
 
@@ -158,7 +160,7 @@ For automation or agent-driven setup, use:
 - `autotouch cli-manifest --output json` for the local machine-readable command contract
 - `autotouch cli-reference` for the shipped parser-generated reference
 - `autotouch capabilities --output json` for provider/workflow contracts
-- `autotouch --version` should be `0.2.80` or newer for the 10-result neural search cap and provider-hidden `autotouch list-build ...`; older CLIs may still show the removed `autotouch linkedin list-build` surface
+- `autotouch --version` should be `0.2.81` or newer for the research-workspace list-build guidance, 10-result neural search cap, and provider-hidden `autotouch list-build ...`; older CLIs may still show the removed `autotouch linkedin list-build` surface
 - `autotouch capabilities --output json --select list_builds` for documented list-build inputs such as geography IDs, company size buckets, profile language, and company IDs
 - `autotouch list-build companies` and `autotouch list-build leads` for durable provider-hidden company and lead list builds with Smart Table-owned background workers, visible progress, and no user-owned network connection requirement
 - `autotouch linkedin search` for one-page LinkedIn/Sales Navigator replay/debug searches; it is not the recommended path for large lists

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/autotouch_shared/list_build_contract.py

@@ -16,7 +16,7 @@ _LIST_BUILD_ENDPOINTS: Dict[str, Dict[str, Any]] = {
         "body": {
             "kind": "required companies|leads",
             "list_name": "optional display name",
-            "keywords": "company keywords or optional lead keywords",
+            "keywords": "required broad anchor for company builds; optional lead keywords; use with structured filters, not as the sole targeting definition",
             "title": "optional lead title/persona query",
             "num_results": "optional 1-10000 target result count",
             "page_size": "optional provider page size; leads capped to 50",
@@ -29,7 +29,7 @@ _LIST_BUILD_ENDPOINTS: Dict[str, Dict[str, Any]] = {
                 "profile_language": "optional language code such as en",
             },
         },
-        "notes": "Provider-hidden durable list build. Does not require a user-owned professional-network connection.",
+        "notes": "Provider-hidden durable list build. Does not require a user-owned professional-network connection. Use it to source company/account or lead records for the Smart Table research workspace.",
     },
     "list_build_status": {
         "method": "GET",
@@ -67,13 +67,24 @@ _LIST_BUILD_CAPABILITIES: Dict[str, Any] = {
     "requires_connected_account": False,
     "recommended_scope": LIST_BUILD_SCOPE,
     "public_modes": ["companies", "leads"],
+    "workspace_model": {
+        "role": "List builds source company/account or lead records for the Smart Table research workspace.",
+        "default_flow": "Build company/account records first, add them to a research table, then enrich, score, segment, find related leads, attach signals/notes, and continue downstream workflows.",
+        "lead_flow": "Use lead builds directly when the request is explicitly person/contact focused; otherwise derive leads from company/account results.",
+    },
     "known_input_ids": {
         "geo_ids": {"United States": "103644278"},
         "company_size_buckets": ["1-10", "11-50", "51-200", "201-500", "501-1000", "1001-5000", "5001-10,000", "10,001+"],
         "profile_language_examples": ["en"],
     },
+    "targeting_guidance": [
+        "Start company/account targeting with industry_ids, geo_ids, and company_sizes.",
+        "Company builds still require a broad keywords anchor, but keywords are less reliable because they depend on company/profile text.",
+        "Use keywords to refine, disambiguate, or recover hard-to-classify targets; avoid keywords-only list builds except for exploratory searches.",
+    ],
     "workflow": [
         "Build companies first when the account universe is unknown.",
+        "Add company/account results to a Smart Table research workspace before enrichment, scoring, lead discovery, or downstream workflows.",
         "Use returned company IDs as current_company_ids for targeted lead lists.",
         "Run separate focused jobs for different markets, company sizes, or personas.",
     ],

{autotouch_cli-0.2.80 → autotouch_cli-0.2.81}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "autotouch-cli"
-version = "0.2.80"
+version = "0.2.81"
 description = "Autotouch Smart Table CLI"
 readme = "README.md"
 requires-python = ">=3.9"