higherdata 0.6.0 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "higherdata",
-  "version": "0.6.0",
+  "version": "0.7.0",
   "type": "module",
   "bin": {
     "higherdata": "dist/index.js"
@@ -50,7 +50,7 @@
     "directory": "packages/cli"
   },
   "higherdata": {
-    "minimumServerVersion": "0.2.0"
+    "minimumServerVersion": "0.7.0"
   },
   "optionalDependencies": {
     "@napi-rs/keyring": "2.1.0"

package/skills/higherdata-enrich-csv/SKILL.md

@@ -17,7 +17,7 @@ Inspect the input headers locally. Choose the operation and exact target-to-colu
 higherdata --json enrich companies.csv --operation enrich.company --map domain=Website --dry-run
 ```
 
-This uploads and validates the mapping without running enrichment. Read the row count and compare it with the file limit. File uploads are retained privately for up to seven days. Email operations need explicit confirmation because provider submissions use the monthly verification allowance. If the file or mapping changes, preview again.
+This uploads and validates the mapping without running enrichment. Read the row count and compare it with the file limit. File uploads are retained privately for up to seven days. Email operations need explicit confirmation because terminal provider answers use purchased verify credits, while cache hits are free. If the file or mapping changes, preview again.
 
 ```sh
 higherdata --json enrich companies.csv --operation enrich.company --map domain=Website --wait

package/skills/higherdata-usage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: higherdata-usage
-description: Check HigherData plan limits, email verification allowance, monthly activity and resets.
+description: Check HigherData plan limits, purchased verify credits and monthly activity.
 ---
 
 Use the CLI's JSON output to read actual workspace state:
@@ -11,10 +11,10 @@ higherdata --json usage
 higherdata --json limits
 ```
 
-All plans offer unlimited searches, lookups and enrichment under fair use. Identify the plan, effective request rate, concurrency, monthly email verification allowance, used and remaining counts, UTC reset time and monthly activity. Do not invent missing values or assume the top plan has no protective ceilings.
+All plans offer unlimited searches, lookups and enrichment under fair use. Identify the plan, effective request rate, concurrency, available `verifyCreditsRemaining` balance and monthly activity. Do not invent missing values or assume the top plan has no protective ceilings.
 
-Paid email verification submissions use the monthly allowance. Cache hits and polling do not. Core includes 2,000, Insights 10,000, and Unlimited 50,000 per UTC month; configured staff overrides can change these values. Read the actual returned allowance rather than assuming the default. AI uses the workspace's configured mode and credit separately.
+Email verification uses purchased verify credits, with one credit per terminal provider answer. Cache hits and polling are free, and provider failures release reservations. No plan includes verifications, staff limits cannot grant credit, and credits never expire. Read the actual returned balance. AI uses the workspace's configured mode and its own credit separately.
 
-Limits combine protective ceilings, the plan, staff overrides and tighter customer rate or record caps. Honor reset times and returned retry delays. Never split a request across keys or spaces to evade a limit. A verification allowance refusal stops new paid submissions until reset or an authorized plan change. Search remains available. Use the returned upgrade link to open HigherTools, select the account, then Billing.
+Limits combine protective ceilings, the plan, staff overrides and tighter customer rate or record caps. Honor reset times and returned retry delays. Never split a request across keys or spaces to evade a limit. A `credits_required` refusal stops new provider submissions until credits are added through HigherTools. Finds can still return an explicitly unverified pattern guess. Search remains available. Use the returned billing link to open HigherTools, select the account, then Billing.
 
 Do not adjust caps or create keys under a usage-check request.

package/skills/higherdata-work-email/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: higherdata-work-email
-description: Find and verify work emails in HigherData using company pattern evidence, a preview and explicit confirmation of the verification allowance.
+description: Find and verify work emails in HigherData using company pattern evidence, a preview and explicit confirmation of the verify credits.
 ---
 
 Use `--json` and the intended space. Check usage and limits before a paid request. For finding, use the person's known first and last names and a company domain or opaque company id. Do not invent an address and describe it as verified.
@@ -10,7 +10,7 @@ higherdata --json tools email.find --input '{"firstName":"Ava","lastName":"Reed"
 higherdata --json tools email.verify --email ava@cedar.example
 ```
 
-These generic commands preview by default. Read the candidates, suppression outcome and monthly verification allowance. Each candidate sent to the paid provider uses one verification; cache hits and polling are free. Confirm the request with the user, then execute the identical input with `--execute --yes`.
+These generic commands preview by default. Read the candidates, suppression outcome and available purchased verify credits. Each terminal provider answer uses one credit; cache hits and polling are free. Confirm the request with the user, then execute the identical input with `--execute --yes`.
 
 If the result is pending, retain its `requestId`. Read it through the same tool, rather than submitting a new address search:
 
@@ -21,4 +21,4 @@ higherdata --json tools email.verify --request-id REQUEST_ID
 
 A preview read does not advance pending work. To continue an approved request, use its existing request id with `--execute --yes`. Honor the returned retry delay, bound waiting, and report pending status if it does not finish. Never treat a timeout as permission to restart.
 
-Report the returned `deliverable`, `undeliverable`, `risky` or `unknown` status, timestamp and verification allowance used. Suppressed records must stay hidden. Do not label risky or unknown addresses as deliverable. This skill finds data only; sending email is a separate task.
+Report the returned `deliverable`, `undeliverable`, `risky` or `unknown` status, timestamp and available verify credit balance. At zero, a find may return `unverified: true` with a pattern guess. Label it unverified; never invent a verification timestamp. A `credits_required` refusal links to HigherTools billing. Suppressed records must stay hidden. Do not label risky or unknown addresses as deliverable. This skill finds data only; sending email is a separate task.