hive-intelligence 1.7.1 → 1.7.3

package/README.md

@@ -112,7 +112,7 @@ Expected output shape:
     "source": "live",
     "receipt_id": "00000000-0000-4000-8000-000000000000",
     "receipt_version": "1.0",
-    "server_version": "1.7.1",
+    "server_version": "1.7.3",
     "build_sha": null,
     "digest_algorithm": "sha256",
     "input_digest": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",

package/agent-skills/packs/hive/SKILL.md

@@ -6,15 +6,15 @@ metadata:
   package: "@hiveintelligence/agent-skills"
   category: "routing"
   requires_network: "true"
-version: 1.7.0
+version: 1.7.1
 ---
 
 # Hive: one skill, all crypto intelligence
 
-Hive answers live crypto questions from 15 data providers through one MCP
-server and one CLI, and every answer carries a receipt: provider, fetch time,
-cache state, runtime status, and digests of the input and result. Three things
-Hive has that most crypto data tools do not:
+Hive answers live crypto questions from more than a dozen data providers
+through one MCP server and one CLI, and every answer carries a receipt:
+provider, fetch time, cache state, runtime status, and digests of the input
+and result. Three things Hive has that most crypto data tools do not:
 
 - **History that venues no longer serve.** Perp funding settlements, open
   interest, basis, long/short ratios, and liquidations for one coin across up
@@ -61,12 +61,12 @@ Version check, once per session on the CLI path:
 npx -y -p hive-intelligence@latest hive --version
 ```
 
-Compare the printed version with this skill's `metadata.version`. When the CLI
-is older, rerun the setup incantation; when the CLI is newer by a minor
+Compare the printed version with this skill's frontmatter `version`. When the
+CLI is older, rerun the setup incantation; when the CLI is newer by a minor
 version, refresh this skill:
 
 ```bash
-npx skills check hive-intel/hive-skills --skill hive
+npx skills add hive-intel/hive-skills --skill hive
 ```
 
 ## First run: the routing block
@@ -79,7 +79,7 @@ CLAUDE.md; only the routing verb does.
 Ask once per project, with AskUserQuestion when available:
 
 > Add a short "Hive MCP Routing" block to this project's AGENTS.md (or
-> CLAUDE.md) so every turn reaches for live crypto data through Hive? About 40
+> CLAUDE.md) so every turn reaches for live crypto data through Hive? About 50
 > lines, removable with `hive routing remove`.
 >
 > A) Add it (recommended)
@@ -153,7 +153,7 @@ Loop:
    have not called before. Read `operation`, required fields, and enums.
 3. `invoke_api_endpoint {"endpoint": "<tool>", "args": {...}}` with `limit`,
    `page`, `per_page`, or `offset` set. Stop at the route's stop condition or
-   at four material calls.
+   at its `maxMaterialCalls`, which is 2, 3, or 4 depending on the route.
 4. Copy each material response's `_hive` block into the receipt, cite receipt
    ids from every material claim, and run `validate_task_result` before
    presenting a typed result.
@@ -186,14 +186,22 @@ Domain namespaces wrap the common tools: `market`, `defi`, `portfolio`,
 `archive` (`coverage`, `funding`, `oi`, `basis`, `long-short`,
 `liquidations`, all taking `--base-coin`). Run `hive <domain> --help`.
 
-Output is the envelope `{ok, data, meta}`; JSON is automatic when stdout is
-not a TTY and forced with `--json`. `--jq '<expr>'` filters `data` in place.
-`meta` carries `credit_cost`, `credits_used`, `credits_remaining`, and the
-`_hive` receipt fields. The human footer prints `credits: used N, remaining M`
-on keyed lanes and `free calls left today: N` keyless.
-
-Diagnostics: `hive doctor` (connectivity, auth, and today's keyless
-allowance, read without spending it) and `hive status` (plan and usage).
+Output is the envelope `{ok, data, meta}`, where `error` replaces `data` on a
+failure; JSON is automatic when stdout is not a TTY and forced with `--json`
+(`--pretty` forces human output when piped). `--jq '<expr>'` filters `data` in
+place, but it is a small built-in jq subset (`.field`, `.a.b`, `.[N]`,
+`.[] | select(...)`), not the jq binary. `meta` carries `credit_cost`,
+`credits_used`, `credits_remaining`, and the receipt fields flattened into
+`meta` itself (`receipt_id`, `receipt_version`, `runtime_status`,
+`fetched_at`, `observed_at`, `cache_age_ms`, `source`, `truncated`,
+`warnings`); there is no `_hive` block on this lane. The human footer prints
+`credits: used N, remaining M` on keyed lanes (`remaining unlimited` on an
+unlimited plan) and, keyless, `free calls left today: N` followed by a
+parenthetical pointing at `hive auth login`.
+
+Diagnostics: `hive doctor` (connectivity, whether a key is set, and today's
+keyless allowance, read without spending it), `hive status` (version, profile,
+and API reachability), and `hive usage` (plan and usage).
 
 ## Domain guide
 
@@ -252,7 +260,9 @@ or `error.data.code` on a JSON-RPC cap error). Every error carries `cause`,
 | `ANON_QUOTA_EXCEEDED` | MCP, REST, CLI (exit 6) | this IP's 25 keyless calls are spent; resets 00:00 UTC | show the keyless-exhausted message; do not retry |
 | `ANON_GLOBAL_CAP_EXCEEDED` | MCP, REST, CLI (exit 6) | Hive's shared keyless allowance for today is spent | same message; a key is not subject to it |
 | `ANON_AUTH_REQUIRED` | MCP, REST, CLI (exit 6) | `hive_*` state tools need a signed-in account | say so; offer the setup command |
+| `ANON_QUOTA_UNAVAILABLE` | MCP, REST | the keyless limiter is unreachable, so the lane fails closed; nothing was spent | retry once in a few seconds, then offer a key |
 | `QUOTA_EXCEEDED` | MCP, REST, CLI (exit 6) | the account's credits are spent for the period | show the top-up message; do not retry |
+| `QUOTA_SERVICE_UNAVAILABLE` | MCP, REST | the billing service could not debit; nothing was debited | retry once in a few seconds |
 | `NO_WALLET` | MCP, REST, CLI (exit 4) | the account has no credit wallet yet | send the user to the dashboard billing page |
 | `RATE_LIMITED` | all | per-minute limit | wait the `retry_after` seconds, retry once |
 | `VALIDATION_ERROR` | all (exit 2) | an argument is wrong; the message names the field and accepted values | fix the args; `hive tools info <name>` has the table |
@@ -303,10 +313,16 @@ file.
   GeckoTerminal `network` id (`eth`, `base`, `solana`); Alchemy tools take a
   network slug (`eth-mainnet`, `base-mainnet`). Read the schema.
 - Address versus symbol: `get_token_price` takes `token` (id or ticker) or
-  `chain` + `address`, never both. Ambiguous tickers resolve to the
-  highest-cap coin; say which one you used.
-- Solana addresses are auto-detected; do not pass `chain: "eth"` with a
-  base58 address.
+  `chain` + `address`. Pass one, never both: the schema does not reject the
+  pair, it silently takes `address` and drops `token`. A ticker is tried as a
+  CoinGecko id first and retried as a symbol only if that came back empty;
+  there is no market-cap tie-break, so on an ambiguous ticker say which coin
+  the receipt actually returned.
+- Solana addresses are auto-detected by `check_token_safety` and
+  `get_wallet_portfolio` only, and only when `chain` is omitted; an explicit
+  `chain` always wins, so never pass `chain: "eth"` with a base58 address.
+  `get_token_price` does no detection at all: a bare mint defaults to
+  Ethereum, so pass `chain: "solana"` with it.
 - Retired names: `codex_*` and the old Codex-era tool names return
   `TOOL_RETIRED` with the replacement in copyable form. Prediction markets
   are the `polymarket_*` tools since 1.7.0.
@@ -344,7 +360,13 @@ On yes:
 hive feedback "<one line: what was asked, what came back>" --tool <tool-name>
 ```
 
-MCP: `report_feedback {"message": "...", "tool": "<tool-name>", "receipt_id": "<from _hive>"}`.
+MCP: `report_feedback` is not one of the eight root tools, so send it the
+same way as any other endpoint:
+
+```json
+invoke_api_endpoint {"endpoint": "report_feedback", "args": {"message": "...", "tool": "<tool-name>", "receipt_id": "<from _hive>"}}
+```
+
 Free on every lane, ten per day, one line, no keys or wallet addresses in
 the message. The CLI attaches the last receipt automatically when `--receipt`
 is omitted.

package/agent-skills/packs/hive/evals/triggers.json

@@ -1,15 +1,39 @@
 [
-  { "query": "BTC funding history across exchanges since 2024", "should_trigger": true },
+  {
+    "query": "BTC funding history across exchanges since 2024",
+    "should_trigger": true
+  },
   { "query": "what is solana trading at right now", "should_trigger": true },
-  { "query": "is this token a honeypot 0x6982508145454Ce325dDbE47a25d4ec3d2311933", "should_trigger": true },
-  { "query": "compare basis between binance and hyperliquid for ETH over the last quarter", "should_trigger": true },
+  {
+    "query": "is this token a honeypot 0x6982508145454Ce325dDbE47a25d4ec3d2311933",
+    "should_trigger": true
+  },
+  {
+    "query": "compare basis between binance and hyperliquid for ETH over the last quarter",
+    "should_trigger": true
+  },
   { "query": "set up hive in this project", "should_trigger": true },
   { "query": "polymarket odds on the next fed cut", "should_trigger": true },
-  { "query": "run the hive cli to get the top defi protocols by tvl", "should_trigger": true },
-  { "query": "what does this wallet hold 0xd8dA6BF26964aF9D7eEd9e03E51415D37aA96045", "should_trigger": true },
-  { "query": "explain how perpetual funding rates work in theory", "should_trigger": false },
-  { "query": "write a python function that parses a csv", "should_trigger": false },
-  { "query": "what was bitcoin's price at the 2017 peak", "should_trigger": false },
+  {
+    "query": "run the hive cli to get the top defi protocols by tvl",
+    "should_trigger": true
+  },
+  {
+    "query": "what does this wallet hold 0xd8dA6BF26964aF9D7eEd9e03E51415D37aA96045",
+    "should_trigger": true
+  },
+  {
+    "query": "explain how perpetual funding rates work in theory",
+    "should_trigger": false
+  },
+  {
+    "query": "write a python function that parses a csv",
+    "should_trigger": false
+  },
+  {
+    "query": "what was bitcoin's price at the 2017 peak",
+    "should_trigger": true
+  },
   { "query": "should I buy ethereum", "should_trigger": false },
   { "query": "summarize this whitepaper", "should_trigger": false }
 ]

package/agent-skills/packs/hive-query/SKILL.md

@@ -30,7 +30,8 @@ data.
 5. Call reads through `invoke_api_endpoint`. For an explicitly approved
    Hive-native state change, use `invoke_stateful_endpoint`; never auto-approve
    that router.
-6. Stop when the route's stop condition is met or four material calls are used.
+6. Stop when the route's stop condition is met or its `maxMaterialCalls` (2,
+   3, or 4, depending on the route) is used.
    Copy server-returned `_hive` blocks into the task receipt and run
    `validate_task_result` with the selected `route_id` before presenting a structured result.
 7. Report source recency, provider/runtime status, and missing-data caveats.

package/build/{api-client-UGNFUZ2L.js → api-client-POBN6Y5S.js}

@@ -8,8 +8,8 @@ import {
   getAnonQuota,
   getUsage,
   postFeedback
-} from "./chunk-TWYGJEVN.js";
-import "./chunk-3Z5VR53Z.js";
+} from "./chunk-RNVZIPNY.js";
+import "./chunk-ZSPPJW4G.js";
 import "./chunk-ZXKFJQDE.js";
 import "./chunk-6PC3HUAK.js";
 import "./chunk-OMO7XLC5.js";

package/build/{auth-5TLYP2DC.js → auth-6XVL5CE3.js}

@@ -12,7 +12,7 @@ import {
   runWhoami,
   saveProfile,
   switchProfile
-} from "./chunk-UPWYFTTJ.js";
+} from "./chunk-KQVPKTEO.js";
 import "./chunk-6PC3HUAK.js";
 import "./chunk-OMO7XLC5.js";
 export {

package/build/{call-args-NVOYX6DL.js → call-args-BUB6YNHW.js}

@@ -10,8 +10,8 @@ import {
   parseFlagTokens,
   planToolCall,
   reservedOptionNames
-} from "./chunk-XT6RURQV.js";
-import "./chunk-3Z5VR53Z.js";
+} from "./chunk-AZFOTKS2.js";
+import "./chunk-ZSPPJW4G.js";
 import "./chunk-OMO7XLC5.js";
 export {
   ALWAYS_RESERVED_OPTIONS,

package/build/{chunk-POPAEM4E.js → chunk-APBLB62S.js}

@@ -2,7 +2,7 @@ import { createRequire } from 'node:module'; const require = createRequire(impor
 import {
   CliError,
   ExitCode
-} from "./chunk-3Z5VR53Z.js";
+} from "./chunk-ZSPPJW4G.js";
 import {
   errorEnvelope,
   info,

package/build/{chunk-XT6RURQV.js → chunk-AZFOTKS2.js}

@@ -1,7 +1,7 @@
 import { createRequire } from 'node:module'; const require = createRequire(import.meta.url);
 import {
   CliError
-} from "./chunk-3Z5VR53Z.js";
+} from "./chunk-ZSPPJW4G.js";
 
 // src/cli/call-args.ts
 var BOOLEAN_LITERALS = /* @__PURE__ */ new Set(["true", "false", "1", "0", "yes", "no"]);

package/build/{chunk-UPWYFTTJ.js → chunk-KQVPKTEO.js}

@@ -294,11 +294,11 @@ async function runSwitch(name) {
   }
 }
 async function runUsage() {
-  const { getUsage } = await import("./api-client-UGNFUZ2L.js");
+  const { getUsage } = await import("./api-client-POBN6Y5S.js");
   const result = await getUsage();
   if (!result.ok) {
     const { outputError } = await import("./output-BBHBJI32.js");
-    const { CliError, classifyError } = await import("./errors-W3GXQN34.js");
+    const { CliError, classifyError } = await import("./errors-YQAVCXXO.js");
     const code = result.error?.code;
     const err = code === "AUTH_REQUIRED" || code === "INVALID_TOKEN" ? new CliError(
       "AUTH_REQUIRED",

package/build/{chunk-2C5FBG7B.js → chunk-QKVI3YHQ.js}

@@ -7,7 +7,7 @@ import {
   getSupabaseAdmin,
   resolveEndpoint,
   secureLogger
-} from "./chunk-3SQPLZW6.js";
+} from "./chunk-WDF56OFL.js";
 
 // src/services/wallet-service.ts
 async function consumeCredits(args) {

package/build/{chunk-TWYGJEVN.js → chunk-RNVZIPNY.js}

@@ -1,7 +1,7 @@
 import { createRequire } from 'node:module'; const require = createRequire(import.meta.url);
 import {
   NEVER_RETRY_ERROR_CODES
-} from "./chunk-3Z5VR53Z.js";
+} from "./chunk-ZSPPJW4G.js";
 import {
   SERVER_VERSION
 } from "./chunk-ZXKFJQDE.js";