hive-intelligence 1.6.7 → 1.7.1

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

@@ -0,0 +1,50 @@
+{
+  "skill_name": "hive",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Show me BTC funding settlements across venues since January 2024 and tell me where funding diverged most.",
+      "expected_output": "Detects the transport, calls archive_get_funding_history (or hive archive funding) with base_coin BTC, a from bound and a limit, reports per-venue rates with settled_at and funding_annualized, names the divergence, and ends with a receipt built from _hive.",
+      "files": [],
+      "assertions": [
+        "Uses the archive funding tool rather than a live venue endpoint.",
+        "Bounds the call with limit and a time window.",
+        "Reports funding_annualized as computed from each row's own interval.",
+        "Ends with receipt ids, provider, and runtime status."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "What is ethereum trading at right now?",
+      "expected_output": "Calls get_token_price with token ethereum on the detected transport, answers with price, provider, and fetch time, and does not print the credit balance.",
+      "files": [],
+      "assertions": [
+        "Uses the hero tool, not a discovery walk.",
+        "Does not answer from memory.",
+        "Reports provider and fetched_at."
+      ]
+    },
+    {
+      "id": 3,
+      "prompt": "I have no Hive account. Can you still check whether 0x6982508145454Ce325dDbE47a25d4ec3d2311933 is a honeypot?",
+      "expected_output": "Runs check_token_safety keyless without asking for a key first; on ANON_QUOTA_EXCEEDED shows the keyless-exhausted message once with the setup incantation and does not retry.",
+      "files": [],
+      "assertions": [
+        "Tries the call before mentioning keys.",
+        "Handles ANON_QUOTA_EXCEEDED by message, not retry.",
+        "Never asks the user to paste a key into chat."
+      ]
+    },
+    {
+      "id": 4,
+      "prompt": "That funding answer was useless, it only showed one exchange.",
+      "expected_output": "Asks once whether to send feedback, and on yes calls hive feedback or report_feedback with a one-line summary and the tool name, then retries the question with a cross-venue call.",
+      "files": [],
+      "assertions": [
+        "Asks before submitting feedback.",
+        "Keeps the feedback message to one line without keys or addresses.",
+        "Re-attempts with the cross-venue archive tool."
+      ]
+    }
+  ]
+}

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

@@ -0,0 +1,15 @@
+[
+  { "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": "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": "should I buy ethereum", "should_trigger": false },
+  { "query": "summarize this whitepaper", "should_trigger": false }
+]

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

@@ -24,7 +24,7 @@ If the user has a browser available on the same machine as their
 terminal:
 
 ```bash
-npx -y -p hive-intelligence@latest hive init --browser
+npx -y -p hive-intelligence@latest hive init --all --skip-verify --browser
 ```
 
 What happens:

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

@@ -24,8 +24,8 @@ installer. One install, multiple agent entrypoints.
 If the user doesn't have the CLI installed:
 
 ```bash
-# One-time install + auth
-npx -y -p hive-intelligence@latest hive init --browser
+# One-time install (adds --browser to sign in at the same time)
+npx -y -p hive-intelligence@latest hive init --all --skip-verify --browser
 
 # Or, install globally for repeated use
 npm install -g hive-intelligence

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

@@ -25,10 +25,12 @@ file path and shape vary per client.
   `Authorization: Bearer <HIVE_API_KEY>` from secret storage; `x-api-key` is a
   legacy fallback. Check protected-resource metadata before claiming the
   interactive path is live.
-- **Cost** — one credit per material endpoint execution regardless of payload
-  size. Search, schema lookup, task-result validation, category listing,
-  `tools/list`, and resource reads cost zero credits. 4xx errors don't consume
-  credits; 5xx errors are refunded.
+- **Cost** — discovery tools are free; every other tool costs one credit.
+  Keyed lanes debit only after validation and client resolution, so a
+  validation error or missing provider key costs 0 and a call that reaches the
+  provider costs 1 even when the provider fails. The keyless lane consumes one
+  allowance call per material request, valid or not. Every material response
+  reports `credit_cost`, `credits_used`, and `credits_remaining`.
 
 After hosted OAuth activation, interactive MCP setup does not require the user
 to create or paste an API key. Route to `hive-build-onboarding` for direct CLI,
@@ -41,9 +43,11 @@ If the user is on a machine with multiple MCP-capable clients and just
 wants Hive everywhere:
 
 ```bash
-npx -y -p hive-intelligence@latest hive init --all
+npx -y -p hive-intelligence@latest hive init --all --skip-verify
 ```
 
+`--skip-verify` keeps it non-interactive; add `--browser` to sign in too.
+
 This writes URL-only config for supported local clients and prints the native
 UI steps for clients such as Claude and ChatGPT. When protected-resource
 metadata is live, each interactive client opens Hive browser authorization on

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

@@ -0,0 +1,145 @@
+---
+name: hive-prediction-markets
+description: Use this skill when the user asks about prediction markets, meaning Polymarket events, markets, outcomes, odds, prices, order books, liquidity, odds history, or a wallet's positions and trades, including "what are the odds of X", "find markets about Y", or Kalshi questions (answer from Polymarket and say Kalshi is not covered). Use it whenever live prediction-market evidence is needed. Never present market probability as ground truth.
+license: MIT
+metadata:
+  package: "@hiveintelligence/agent-skills"
+  category: "prediction-markets"
+  requires_network: "true"
+version: 1.7.0
+---
+
+# hive-prediction-markets: Prediction Markets
+
+Discover and analyze Polymarket prediction markets with prices, order books,
+odds history, and wallet positions and trades, always framed as
+market-implied odds rather than truth. Polymarket's Gamma, CLOB, and Data
+APIs are keyless, so these tools work on the keyless lane. Kalshi is not
+covered: its developer agreement requires a data license Hive does not hold,
+so answer Kalshi questions from Polymarket where a matching market exists and
+say plainly that the Kalshi side is unavailable.
+
+## Task toolset and identifiers
+
+Toolset: `prediction_markets`. Read `hive://toolsets/prediction_markets` before
+execution; it is authoritative for the current output schema, material-call
+budget, phases, fallback condition, and stop conditions.
+
+- Polymarket: `polymarket_search_markets` (topic), `polymarket_get_events`
+  (event slug), `polymarket_get_market` (market slug or condition id),
+  `polymarket_get_price_history` and `polymarket_get_orderbook` (CLOB token
+  id), `polymarket_get_wallet_positions` and `polymarket_get_wallet_activity`
+  (EVM wallet address).
+- Required: a market slug, condition id, token id, wallet address, or a
+  search query, depending on the request.
+- Optional: status filter, limit, interval, depth, outcome.
+
+If the user starts with a topic, search candidates first and ask for selection
+when multiple markets match; similar markets can have different resolution
+criteria.
+
+Before choosing endpoints, select exactly one matching entry from the exact
+workflow's routes[]. Follow its ordered steps, use a fallback only under that
+step's published condition, stop at three material calls, and preserve the
+selected route_id in the typed result. The broad coverageCatalog is discovery
+coverage, not an execution plan.
+
+## Procedure
+
+1. Call `search_tools` with the venue and need, or read
+   `hive://toolsets/prediction_markets`.
+2. Call `get_api_endpoint_schema` for each endpoint before calling it.
+3. Search markets or events for topic prompts; resolve the exact slug,
+   ticker, condition id, or token id before pulling books, history, or
+   trades.
+4. Add liquidity, spread, and freshness context before interpreting prices.
+5. Report the implied odds per outcome, volume or liquidity, venue, provider,
+   and freshness, and never present probability as ground truth.
+
+## Bounded calls
+
+- Use small search limits and page through only when needed.
+- Do not fetch all trades or a wallet's full history unless the user asks
+  for a deep dive.
+- Keep outcome-token prices separate from event-level interpretation.
+
+## Worked example
+
+User: "What are the odds on the next Fed rate decision, and how has that
+moved this month?"
+
+1. `polymarket_search_markets` with `{"query": "fed rate decision", "limit": 5}`.
+2. If several markets match, list candidates with resolution criteria and ask
+   which to inspect, or pick the highest-liquidity exact match and say so.
+3. `polymarket_get_orderbook` for the YES token, then
+   `polymarket_get_price_history` with `{"token_id": "...", "interval": "1m"}`,
+   and report bid, ask, mid, spread, liquidity, and the month's move.
+4. Frame the prices as market-implied odds with volume and freshness.
+
+## Report template
+
+```markdown
+## Summary
+[Market or event read and top outcomes in one or two sentences.]
+
+## Calls made
+- Toolset: prediction_markets
+- Endpoint(s): [exact endpoint names]
+- Identifiers: [slug, condition id, token id, wallet]
+
+## Evidence
+- Outcomes and prices: [per outcome, per venue]
+- Liquidity, spread, volume: [values plus as-of]
+- Provenance: [provider, fetched_at, observed_at or cache_age_ms, runtime status per call]
+
+## Caveats
+[Market probability is not truth, thin liquidity, stale history, candidate ambiguity.]
+
+## Next action
+[Inspect the selected market, book, history, or wallet, only if needed.]
+```
+
+## Gotchas
+
+- Market prices reflect trading and liquidity, not verified probability.
+- Similar markets can have different resolution criteria; quote them when
+  comparing venues.
+- Prices are per outcome token in the 0 to 1 range; the YES and NO tokens of
+  one market are separate books.
+- Event-level and market-level data are not interchangeable.
+
+## Evidence receipt (required)
+
+End every Hive-backed answer with a compact receipt built from the `_hive`
+object on each material tool response:
+
+- `provider`, `tool`, `fetched_at`, `observed_at`, `cache_age_ms`, and `runtime_status`
+- `receipt_id`, `receipt_version`, server/build version, and SHA-256 input/result
+  digests when present (self-checks, not signatures)
+- `source`, `cache_status`, `truncated`, and any warnings
+- canonical market identifiers (slug, condition id, token id) present
+  in provider data
+- material provider disagreements and how they were handled
+- checks that were unavailable, gated, stale, truncated, or intentionally not run
+- a `claims[]` citation from each material statement to exact receipt IDs
+- one `coverage[]` entry for every canonical evidence phase, with each gap explained
+
+Never turn missing evidence into a clean result, silently merge conflicting
+provider values, or omit a degraded/fallback call from the receipt.
+`observed_at` is Hive's first-observation/original cache-population time, and
+`cache_age_ms: 0` only means newly retrieved by Hive. Use provider time or
+trade time for source recency; if absent, mark it unknown. Run
+`validate_task_result` before presenting the typed workflow result; it checks
+structure but cannot authenticate an invented receipt.
+
+## Runtime status handling
+
+If a market search succeeds but the book or history read is `degraded`,
+return the candidates and label the missing market details clearly.
+
+## Hand-offs
+
+- General crypto market prices: `hive-market-research`.
+- A trader's full wallet activity outside Polymarket: `hive-wallet-investigation`.
+- Standing "alert me when odds move" requests: `hive-stateful-monitoring`
+  with a `prediction_market` monitor.

package/agent-skills/packs/hive-prediction-markets/evals/evals.json

@@ -0,0 +1,29 @@
+{
+  "skill_name": "hive-prediction-markets",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Find active prediction markets about the next Fed decision and show the top outcomes with liquidity caveats.",
+      "expected_output": "Uses prediction_markets, searches Polymarket markets first, resolves candidate slugs, bounds results, reports price, liquidity, and freshness caveats, and ends with a runtime evidence receipt.",
+      "files": [],
+      "assertions": [
+        "Chooses prediction_markets.",
+        "Selects polymarket_odds_snapshot for an odds read and preserves route_id.",
+        "Searches markets before books or history.",
+        "States market price is not ground truth.",
+        "Includes receipt ids and missing evidence."
+      ]
+    },
+    {
+      "id": 2,
+      "prompt": "For this Polymarket wallet, summarize its open positions and recent trades.",
+      "expected_output": "Uses the exact wallet address, fetches bounded positions and activity through polymarket_trader_flow, and reports provider and runtime status.",
+      "files": [],
+      "assertions": [
+        "Uses the exact wallet address.",
+        "Bounds positions and activity.",
+        "Reports provider and runtime status."
+      ]
+    }
+  ]
+}

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

@@ -0,0 +1,14 @@
+[
+  { "query": "what are the odds on the next fed rate cut on polymarket", "should_trigger": true },
+  { "query": "find prediction markets about the 2026 world cup winner", "should_trigger": true },
+  { "query": "compare polymarket vs kalshi on the CPI print markets", "should_trigger": true },
+  { "query": "what is this polymarket wallet holding right now", "should_trigger": true },
+  { "query": "that 70% odds number, how much liquidity is actually behind it", "should_trigger": true },
+  { "query": "show recent trades from this polymarket wallet", "should_trigger": true },
+  { "query": "whats the POL token trading at", "should_trigger": false },
+  { "query": "what does this trader's wallet hold outside polymarket", "should_trigger": false },
+  { "query": "explain how prediction markets resolve disputes", "should_trigger": false },
+  { "query": "alert me when these odds move 10 points", "should_trigger": false },
+  { "query": "is using polymarket legal in my country", "should_trigger": false },
+  { "query": "top defi protocols by tvl", "should_trigger": false }
+]

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

@@ -1,6 +1,6 @@
 ---
 name: hive-query
-description: Default entry point for any live crypto question when Hive MCP is connected — prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps. Use it whenever the answer depends on live or on-chain data instead of answering from memory, even if the user never mentions Hive. Routes intent to a canonical Hive task toolset, then schema lookup and bounded endpoint invocation. If a domain-specific hive-* skill clearly matches, prefer it; if routing cannot surface the exact tool or schema, hand off to hive-tool-discovery.
+description: Use this skill when the hive skill hands off a live crypto question that needs the full task-toolset walk (prices, wallets, tokens, DeFi, NFTs, Solana, security, markets, DEX, networks, RWA perps, prediction markets) and no hero tool answers it in one call. Install hive first; reach for this directly only when the hive pack is absent. Routes intent to a canonical Hive task toolset, then schema lookup and bounded endpoint invocation. If a domain-specific hive-* skill clearly matches, prefer it; if routing cannot surface the exact tool or schema, hand off to hive-tool-discovery.
 license: MIT
 metadata:
   package: "@hiveintelligence/agent-skills"
@@ -55,6 +55,7 @@ without loading the full provider catalog into context.
 | Blocks, gas, logs, receipts, RPC diagnostics | `network_infrastructure` |
 | Solana wallets, SPL accounts, DAS assets, priority fees | `solana_analysis` |
 | Tokenized RWA perps, cross-venue funding, carry, open interest | `rwa_perp_analysis` |
+| Polymarket odds, events, order books, odds history, wallet positions | `prediction_markets` |
 | Durable monitors, alerts, scheduled reports, agent memory | `stateful_monitoring` |
 | Ambiguous request or schema lookup | `search_discovery` |
 

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

@@ -25,8 +25,8 @@ material-call budget, phases, fallback condition, stop conditions, and the
 read/write routing policy.
 
 Required identifiers: monitor kind and target object. Worker-supported monitor
-kinds are `wallet`, `token`, `protocol`, `market`, `watchlist_digest`,
-`token_discovery_risk`, and `risk_watch`.
+kinds are `wallet`, `token`, `protocol`, `market`, `prediction_market`,
+`watchlist_digest`, `token_discovery_risk`, and `risk_watch`.
 
 Before choosing endpoints, select exactly one matching entry from the exact
 workflow's routes[]. Follow its ordered steps, use a fallback only under that
@@ -78,7 +78,7 @@ User: "Watch this Ethereum wallet and tell me when it moves more than $100k."
 User: "Send every customer a daily crypto watchlist brief."
 
 Create a `watchlist_digest` monitor per B2B subject with saved wallets,
-tokens, protocols, and markets in the target —
+tokens, protocols, markets, and optional prediction markets in the target —
 after reading the B2B reference above.
 
 ## Evidence receipt (required)

package/agent-skills/references/agents-routing.md

@@ -10,7 +10,8 @@ mode where the skill exists but the agent answers from memory before loading it.
 For live crypto intelligence, prefer Hive retrieval over model memory.
 
 - User asks about live crypto data, prices, wallets, tokens, DeFi, NFTs,
-  Solana, security, DEX pools, or network state: use `hive-query`.
+  Solana, security, DEX pools, network state, or prediction markets:
+  use `hive` (it loads `hive-query` for the full toolset walk).
 - Exact Hive endpoint, provider, schema, or argument shape is unknown:
   use `hive-tool-discovery`.
 - Clear domain request:
@@ -29,6 +30,8 @@ For live crypto intelligence, prefer Hive retrieval over model memory.
     `hive-solana-analysis`
   - blocks, gas, receipts, logs, RPC diagnostics:
     `hive-network-infrastructure`
+  - Polymarket odds, events, order books, odds history, wallet positions:
+    `hive-prediction-markets`
 - User asks Hive to remember, monitor, schedule, alert, or report crypto
   intelligence across sessions: use `hive-stateful-monitoring`.
 - Setup, API key, CLI, or app integration:

package/agent-skills/scripts/validate-agent-skills-package.mjs

@@ -16,7 +16,9 @@ const receiptSkills = new Set([
   "hive-defi-research",
   "hive-nft-research",
   "hive-solana-analysis",
+  "hive",
   "hive-network-infrastructure",
+  "hive-prediction-markets",
   "hive-stateful-monitoring",
 ]);
 

package/agent-skills/skills.sh.json

@@ -2,6 +2,13 @@
   "$schema": "https://skills.sh/schemas/skills.sh.schema.json",
   "notGrouped": "bottom",
   "groupings": [
+    {
+      "title": "Start here",
+      "description": "The one skill to install first: live crypto intelligence on MCP or the hive CLI, with setup, routing, credits, error handling, and feedback built in.",
+      "skills": [
+        "hive"
+      ]
+    },
     {
       "title": "Setup and Build",
       "description": "Skills for installing Hive MCP, getting API keys, using the Hive CLI, and integrating Hive into application code.",
@@ -22,7 +29,7 @@
     },
     {
       "title": "Crypto Research Workflows",
-      "description": "Focused workflows for market, token, wallet, security, DEX, DeFi, NFT, Solana, network, and stateful monitoring analysis.",
+      "description": "Focused workflows for market, token, wallet, security, DEX, DeFi, NFT, Solana, network, prediction-market, and stateful monitoring analysis.",
       "skills": [
         "hive-market-research",
         "hive-token-diligence",
@@ -33,6 +40,7 @@
         "hive-nft-research",
         "hive-solana-analysis",
         "hive-network-infrastructure",
+        "hive-prediction-markets",
         "hive-stateful-monitoring"
       ]
     }

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

@@ -1,16 +1,25 @@
 import { createRequire } from 'node:module'; const require = createRequire(import.meta.url);
 import {
+  attachResponseMeta,
+  errorCodeFromBody,
   executeRemoteTool,
   fetchToolCatalog,
   fetchWithRetry,
-  getUsage
-} from "./chunk-P7NLFSZQ.js";
+  getAnonQuota,
+  getUsage,
+  postFeedback
+} from "./chunk-TWYGJEVN.js";
+import "./chunk-3Z5VR53Z.js";
 import "./chunk-ZXKFJQDE.js";
 import "./chunk-6PC3HUAK.js";
 import "./chunk-OMO7XLC5.js";
 export {
+  attachResponseMeta,
+  errorCodeFromBody,
   executeRemoteTool,
   fetchToolCatalog,
   fetchWithRetry,
-  getUsage
+  getAnonQuota,
+  getUsage,
+  postFeedback
 };

package/build/{auth-4LPSQJXD.js → auth-5TLYP2DC.js}

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

package/build/call-args-NVOYX6DL.js

@@ -0,0 +1,27 @@
+import { createRequire } from 'node:module'; const require = createRequire(import.meta.url);
+import {
+  ALWAYS_RESERVED_OPTIONS,
+  canonicalParamName,
+  coerceFlagsToArgs,
+  describeParameters,
+  firstSentence,
+  isNestedSchema,
+  parseArgsJson,
+  parseFlagTokens,
+  planToolCall,
+  reservedOptionNames
+} from "./chunk-XT6RURQV.js";
+import "./chunk-3Z5VR53Z.js";
+import "./chunk-OMO7XLC5.js";
+export {
+  ALWAYS_RESERVED_OPTIONS,
+  canonicalParamName,
+  coerceFlagsToArgs,
+  describeParameters,
+  firstSentence,
+  isNestedSchema,
+  parseArgsJson,
+  parseFlagTokens,
+  planToolCall,
+  reservedOptionNames
+};

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

@@ -7,7 +7,7 @@ import {
   getSupabaseAdmin,
   resolveEndpoint,
   secureLogger
-} from "./chunk-J2PXISXW.js";
+} from "./chunk-3SQPLZW6.js";
 
 // src/services/wallet-service.ts
 async function consumeCredits(args) {
@@ -134,7 +134,8 @@ async function executeToolByName(toolName, args, options) {
     requestId: options?.requestId,
     clients: getSharedClients(),
     analytics: options?.analytics,
-    beforeExecution: options?.beforeExecution
+    beforeExecution: options?.beforeExecution,
+    creditCost: options?.creditCost
   });
   if (result.validationErrors) {
     return {