hive-intelligence 1.1.4 → 1.4.0

package/agent-skills/packs/hive-mcp/references/clients.md

@@ -1,141 +1,154 @@
 # Per-client install instructions
 
-The MCP endpoint is the same everywhere — `https://mcp.hiveintelligence.xyz/mcp`
-with `Authorization: Bearer <HIVE_API_KEY>`. Only the config file path and JSON
-shape vary. Read the block for the user's specific client.
+Use the canonical hosted endpoint everywhere:
+
+```text
+https://mcp.hiveintelligence.xyz/mcp
+```
+
+After hosted OAuth activation, interactive clients use URL-only OAuth
+discovery. Headless API and backend paths keep `HIVE_API_KEY` in server-side
+secret storage. Before giving any native connector instruction, verify that
+`https://mcp.hiveintelligence.xyz/.well-known/oauth-protected-resource/mcp`
+returns valid metadata; otherwise use a trusted headless path and say that the
+native connector is not live yet.
 
 ## Claude Code
 
 ```bash
-claude mcp add --transport http hive https://mcp.hiveintelligence.xyz/mcp \
-  --header "Authorization: Bearer $HIVE_API_KEY"
+claude mcp add --transport http --scope user hive https://mcp.hiveintelligence.xyz/mcp
 ```
 
-Add `--scope user` to install globally, or `--scope project` to commit to the
-repo's `.mcp.json`. Default scope is local. Restart isn't required — tools
-appear in the next chat session.
+After OAuth activation, Claude opens Hive authorization on first connect. Use
+`--scope user` for a global entry or `--scope project` for the current project.
+
+## Claude Desktop / Claude.ai
+
+Do not put a remote URL in `claude_desktop_config.json`; that file is for local
+stdio servers. Open **Settings → Connectors → Add custom connector**, enter the
+Hive URL, and, after OAuth activation, complete browser authorization.
 
 ## Cursor
 
-Edit `~/.cursor/mcp.json`. Add the `hive` server block:
+Edit `~/.cursor/mcp.json`:
 
 ```json
 {
   "mcpServers": {
     "hive": {
-      "url": "https://mcp.hiveintelligence.xyz/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_HIVE_API_KEY"
-      }
+      "url": "https://mcp.hiveintelligence.xyz/mcp"
     }
   }
 }
 ```
 
-Reload the MCP server list from Cursor's command palette (`Cmd+Shift+P` → "MCP:
-Reload Servers"). Or use the deeplink:
-
-```
-cursor://anysphere.cursor-deeplink/mcp/install?name=hive&config=<base64-encoded-config>
-```
+After OAuth activation, reload MCP servers, approve the public URL, and
+complete OAuth when Cursor opens the browser. Never add a placeholder
+Authorization header.
 
-## Claude Desktop
+## VS Code (GitHub Copilot Chat)
 
-Settings → Developer → Edit Config. The file opens in your default editor. Same
-shape as Cursor:
+Create `.vscode/mcp.json` or use the MCP user configuration:
 
 ```json
 {
-  "mcpServers": {
+  "servers": {
     "hive": {
-      "url": "https://mcp.hiveintelligence.xyz/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_HIVE_API_KEY"
-      }
+      "type": "http",
+      "url": "https://mcp.hiveintelligence.xyz/mcp"
     }
   }
 }
 ```
 
-Quit Claude Desktop fully (⌘Q on macOS — the menu bar icon must disappear) and
-reopen. Tools become available on next chat.
+The official one-click form is a `vscode:mcp/install?` URL containing the
+URL-encoded object `{ "name": "hive", "type": "http", "url": "..." }`.
+The Hive CLI installs workflow skills for Copilot-compatible agents under
+`~/.copilot/skills`.
 
-## VS Code (GitHub Copilot Chat)
+## Windsurf / Devin Desktop
 
-Requires VS Code 1.101 or newer. Create `.vscode/mcp.json` in the project root
-(or use User Settings for a global install):
+Edit `~/.codeium/windsurf/mcp_config.json`:
 
 ```json
 {
-  "servers": {
+  "mcpServers": {
     "hive": {
-      "type": "http",
-      "url": "https://mcp.hiveintelligence.xyz/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_HIVE_API_KEY"
-      }
+      "serverUrl": "https://mcp.hiveintelligence.xyz/mcp"
     }
   }
 }
 ```
 
-Reload the window. Note the `type: "http"` field — this is required in VS Code's
-schema and differs from Cursor / Claude Desktop.
+After OAuth activation, reload the client and complete native OAuth.
 
-## Windsurf
+## Gemini CLI
 
-Edit `~/.codeium/windsurf/mcp_config.json`:
+Edit `~/.gemini/settings.json`:
 
 ```json
 {
   "mcpServers": {
     "hive": {
-      "url": "https://mcp.hiveintelligence.xyz/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_HIVE_API_KEY"
-      }
+      "httpUrl": "https://mcp.hiveintelligence.xyz/mcp"
     }
   }
 }
 ```
 
-Reload Windsurf.
+After OAuth activation, Gemini CLI discovers OAuth for the remote HTTP server
+and stores tokens in its credential store. Hive workflow skills install under
+`~/.gemini/skills`.
+
+## ChatGPT custom app
 
-## OpenAI Responses API
+In ChatGPT open **Settings → Apps**, enable Developer mode if the workspace
+requires it, choose **Create app**, enter the Hive URL, scan tools, and complete
+Hive OAuth. If the production protected-resource metadata is unavailable, use
+the server-side Responses API path until the OAuth deployment is activated.
 
-Use Hive as a server-side remote MCP tool from your application code. Keep the
-Hive API key on your server and pass it in the remote MCP tool headers.
+## Grok
 
-Direct ChatGPT app connector setup is beta and auth-dependent; do not promise a
-verified bearer-token ChatGPT app connector unless Hive has shipped the auth
-shape that workspace requires.
+After OAuth activation, open `grok.com/connectors`, add a custom MCP connector
+with the Hive URL, and complete OAuth. Verify a visible Hive tool call and
+runtime receipt rather than accepting an answer generated only from model
+memory.
 
-## Codex CLI
+## OpenAI Responses API (headless)
 
-Edit `~/.codex/config.toml`:
+Use Hive as a server-side remote MCP tool. Keep `HIVE_API_KEY` in backend secret
+storage and pass it through the Responses API authorization field; never expose
+it to a browser or prompt.
 
-```toml
-[mcp_servers.hive]
-url = "https://mcp.hiveintelligence.xyz/mcp"
-bearer_token_env_var = "HIVE_API_KEY"
+## Codex
+
+Use Codex's supported CLI flow so the server entry is URL-only and Codex owns
+the OAuth token lifecycle:
+
+```bash
+codex mcp add hive --url https://mcp.hiveintelligence.xyz/mcp
+codex mcp login hive
 ```
 
-Set `HIVE_API_KEY` in the shell that launches Codex, then verify with `codex
-/mcp` after restart.
+Complete Hive authorization in the browser. Hive workflow skills install under
+`~/.codex/skills`. For a truly headless Codex process that cannot open a
+browser, `bearer_token_env_var = "HIVE_API_KEY"` remains an explicit fallback;
+keep the key in the launching process's secret store, never in a shared file.
 
-## Gemini CLI
+## Local stdio fallback
 
-Edit `~/.gemini/settings.json`:
+For local-only clients, self-hosting, or provider-key experiments:
 
 ```json
 {
   "mcpServers": {
-    "hive": {
-      "url": "https://mcp.hiveintelligence.xyz/mcp",
-      "headers": {
-        "Authorization": "Bearer YOUR_HIVE_API_KEY"
-      }
+    "hive-local": {
+      "command": "npx",
+      "args": ["-y", "-p", "hive-intelligence@latest", "hive"]
     }
   }
 }
 ```
+
+Local stdio does not need `HIVE_API_KEY`; optional upstream provider keys can be
+supplied locally when needed.

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

@@ -1,44 +1,129 @@
 ---
 name: hive-network-infrastructure
-description: Use this skill for chain infrastructure and RPC questions covering gas, blocks, receipts, logs, transaction status, supported networks, fee data, and diagnostics. Use it when the user needs current chain state or transaction evidence.
+description: Use this skill when the user asks about chain state or transaction plumbing — gas prices, blocks, transaction receipts and status ("did my tx go through"), event logs, supported networks, fee data, or RPC diagnostics. Use it whenever the answer needs current chain-level evidence. For wallet holdings use hive-wallet-investigation; for Solana slots/fees use hive-solana-analysis.
 license: MIT
 metadata:
   package: "@hiveintelligence/agent-skills"
   category: "network"
   requires_network: "true"
-version: 1.0.0
+version: 1.4.0
 ---
 
 # hive-network-infrastructure — Network Infrastructure
 
-Use this skill for block, gas, transaction receipt, logs, supported network, or
-RPC diagnostic questions.
+Read chain state — gas, blocks, receipts, logs, transaction status, supported
+networks — and run RPC diagnostics with auditable, timestamped evidence.
 
-## Task toolset
+## Task toolset and identifiers
 
-Use `network_infrastructure`.
+Toolset: `network_infrastructure`. Read
+`hive://toolsets/network_infrastructure` before execution; it is authoritative
+for the current output schema, material-call budget, phases, fallback
+condition, and stop conditions.
 
-Required identifiers: chain. Optional identifiers include block number,
-transaction hash, contract address, or log filter.
+- Required: chain/network.
+- Optional: block number/hash, transaction hash, contract address, log
+  filter, account address, time window.
 
-## Procedure
+Ask for the exact chain plus transaction/block identifiers before status
+checks — a transaction hash is not globally unique without chain context.
+
+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 four material calls, and preserve the
+selected route_id in the typed result. The broad coverageCatalog is discovery
+coverage, not an execution plan.
 
-Read `references/workflow.md` when the request needs transaction diagnostics,
-RPC/provider comparison, gas/fee context, or a structured network report.
+## Procedure
 
 1. Confirm the chain/network id.
-2. Use block/gas/chain-id tools for current state.
-3. Use transaction, receipt, or logs tools only when the user provides exact
-   identifiers.
-4. Report the block/slot/fetched time so the answer is auditable.
+2. Use `filter_networks` when comparing chains by current liquidity,
+   transactions, or volume. Otherwise call `search_tools` for gas, block,
+   transaction, receipt, log, supported-network, or RPC-diagnostic
+   capabilities.
+3. Call `get_api_endpoint_schema` for each endpoint before calling it.
+4. Use current-state tools for gas and block questions; use
+   transaction/receipt/log tools only with exact identifiers.
+5. Report the block/slot/fetched time so the answer is auditable.
+
+## Bounded calls
+
+- Bound log queries by block range and topics.
+- Do not run broad chain scans for a single transaction question.
+- Retry transient RPC failures once when appropriate.
+
+## Worked example
+
+User: "Did my transaction go through? Hash is 0x… — I think it was on Base."
+
+1. Confirm the chain (Base) and the exact hash.
+2. `search_tools` → `{"query": "transaction receipt status base", "limit": 5}`
+3. `get_api_endpoint_schema` for the receipt/status endpoint returned, then
+   `invoke_api_endpoint` with schema-valid arguments.
+4. Report status, block number, gas used, and the fetched time. If the
+   receipt is missing, say whether that means pending, dropped, or wrong
+   chain — do not guess success.
+
+## Report template
+
+```markdown
+## Summary
+[Network or transaction state in one or two sentences.]
 
-## Example
+## Calls made
+- Toolset: network_infrastructure
+- Endpoint(s): [exact endpoint names]
+- Identifiers: [chain, hash/block/address, filters]
 
-If the user asks whether a transaction succeeded, ask for chain and transaction
-hash before selecting a receipt or transaction lookup tool.
+## Evidence
+- State: [block/slot, gas/fee, receipt/log/status]
+- Provenance: [provider, fetched_at, observed_at/cache_age_ms, runtime status per call]
+
+## Caveats
+[Provider mismatch, stale block, rate limit, incomplete logs.]
+
+## Next action
+[Narrower log filter, alternate provider, or retry — only if needed.]
+```
+
+## Gotchas
+
+- A transaction hash is not globally unique without chain context.
+- Logs require bounded block ranges.
+- HTTP health does not prove provider data freshness.
+
+## 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 chain/entity identifiers plus block, slot, transaction, or query ids
+  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, block,
+slot, transaction, or candle close 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
 
-Use `ok`, `missing_key`, `plan_required`, `rate_limited`, `degraded`, and
-`failing`. For transient RPC failures, retry once or fall back to another
+Use `ok`, `invalid_input`, `missing_key`, `plan_required`, `rate_limited`,
+`degraded`, and `failing`. For transient RPC failures, retry once or fall back to another
 network read and state the limitation.
+
+## Hand-offs
+
+- Wallet balances/holdings rather than chain state → `hive-wallet-investigation`.
+- Solana slots, priority fees, parsed transactions → `hive-solana-analysis`.
+- Gas context for a risky transaction → pair with `hive-security-risk`.

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

@@ -4,12 +4,14 @@
     {
       "id": 1,
       "prompt": "Check whether this Ethereum transaction succeeded and summarize the receipt evidence.",
-      "expected_output": "Uses network_infrastructure, asks for chain/tx hash if missing, inspects receipt schema, and reports block/freshness/runtime status.",
+      "expected_output": "Uses network_infrastructure, asks for chain/tx hash if missing, inspects the transaction receipt schema, and ends with a Hive runtime evidence receipt containing block/freshness/status and receipt ids.",
       "files": [],
       "assertions": [
         "Chooses network_infrastructure.",
+        "Selects transaction_debug for this intent and follows its ordered receipt/log steps.",
         "Requires chain and transaction hash.",
-        "Reports receipt/block evidence."
+        "Reports transaction receipt/block evidence.",
+        "Includes Hive runtime receipt ids."
       ]
     },
     {

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

@@ -0,0 +1,50 @@
+[
+  {
+    "query": "did my tx go through? 0x… i think it was on base",
+    "should_trigger": true
+  },
+  {
+    "query": "whats gas on mainnet right now",
+    "should_trigger": true
+  },
+  {
+    "query": "pull logs for this contract between blocks 19m and 19.1m",
+    "should_trigger": true
+  },
+  {
+    "query": "is the arbitrum rpc lagging? my reads look stale",
+    "should_trigger": true
+  },
+  {
+    "query": "which networks does hive support for receipts and logs",
+    "should_trigger": true
+  },
+  {
+    "query": "latest block on polygon and the current base fee pls",
+    "should_trigger": true
+  },
+  {
+    "query": "what does this wallet hold",
+    "should_trigger": false
+  },
+  {
+    "query": "solana priority fees right now",
+    "should_trigger": false
+  },
+  {
+    "query": "is this contract a honeypot",
+    "should_trigger": false
+  },
+  {
+    "query": "explain how eip-1559 burns fees",
+    "should_trigger": false
+  },
+  {
+    "query": "alert me when gas drops below 10 gwei",
+    "should_trigger": false
+  },
+  {
+    "query": "whats eth trading at",
+    "should_trigger": false
+  }
+]

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

@@ -1,41 +1,128 @@
 ---
 name: hive-nft-research
-description: Use this skill for NFT collection, ownership, metadata, floor, sale, rarity, spam, or Solana asset research. Use it whenever the user needs current NFT evidence rather than a general explanation of NFTs.
+description: Use this skill when the user asks about NFT collections or assets on EVM chains — ownership, metadata, traits, floor prices, sales, rarity, spam/authenticity checks — like "what's the floor on this collection", "who owns this NFT", "is this collection spam". Use it whenever the user needs current NFT evidence rather than a general explanation of NFTs. For Solana-native assets (mints, DAS, compressed NFTs) use hive-solana-analysis.
 license: MIT
 metadata:
   package: "@hiveintelligence/agent-skills"
   category: "nft"
   requires_network: "true"
-version: 1.0.0
+version: 1.4.0
 ---
 
 # hive-nft-research — NFT Research
 
-Use this skill for NFT ownership, metadata, collection, floor, sale, rarity, or
-spam/authenticity questions.
+Research NFT collections and assets — ownership, metadata, floors, sales,
+rarity, spam — with collection-level and token-level facts kept separate.
 
-## Task toolset
+## Task toolset and identifiers
 
-Use `nft_research`.
+Toolset: `nft_research`. Read `hive://toolsets/nft_research` before execution;
+it is authoritative for the current output schema, material-call budget,
+phases, fallback condition, and stop conditions.
 
-Required identifiers: chain and collection contract or asset id.
+- Required: chain/network plus collection contract, token id, asset id, or
+  wallet address.
+- Optional: marketplace, time window, trait filter, owner.
 
-## Procedure
+Ask for chain and contract/asset identifiers when the user gives only a
+collection name — collection names are not unique and copycat collections are
+common.
+
+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 four material calls, and preserve the
+selected route_id in the typed result. The broad coverageCatalog is discovery
+coverage, not an execution plan.
 
-Read `references/workflow.md` when the request needs collection resolution,
-ownership/floor/sale context, spam caveats, or a structured NFT report.
+## Procedure
 
 1. Resolve collection contract, token id, wallet, or asset id.
-2. Pull metadata, owners, floors, sales, rarity, or spam checks as requested.
-3. Separate collection-level and token-level facts.
-4. Preserve raw metadata when the user asks about traits or provenance.
+2. Call `search_tools` for metadata, owner, floor, sales, rarity, and spam
+   capabilities.
+3. Call `get_api_endpoint_schema` for each endpoint before calling it.
+4. Start with metadata/identity; add floor/sales or owner/rarity only when
+   relevant.
+5. Preserve raw metadata when the user asks about traits or provenance.
+
+## Bounded calls
+
+- Limit owner and sales lists.
+- Keep collection-level and token-level evidence separate.
+- Do not treat one marketplace floor as the entire market without a caveat.
+
+## Worked example
+
+User: "What's the floor and recent sales for this collection? Contract is
+0x… on Ethereum."
+
+1. `search_tools` → `{"query": "nft collection metadata floor price sales ethereum", "limit": 5}`
+2. `get_api_endpoint_schema` for the metadata, floor, and sales endpoints
+   returned, then `invoke_api_endpoint` with schema-valid arguments and a
+   bounded sales window.
+3. Report floor (with marketplace scope), recent sales, and freshness using
+   the template below.
+
+## Report template
+
+```markdown
+## Summary
+[Collection/token ownership or market read in one or two sentences.]
 
-## Example
+## Calls made
+- Toolset: nft_research
+- Endpoint(s): [exact endpoint names]
+- Identifiers: [chain, contract, token/asset ids]
 
-For a collection-level question, ask for the chain and contract if the user only
-gave a collection name.
+## Evidence
+- Identity/metadata: [name, supply, verification]
+- Market: [floor + marketplace, sales in window]
+- Ownership/rarity/spam: [if requested]
+- Provenance: [provider, fetched_at, observed_at/cache_age_ms, runtime status per call]
+
+## Caveats
+[Marketplace coverage, stale floor, missing metadata, degraded data.]
+
+## Next action
+[Trait drilldown, ownership verification, or market comparison — only if needed.]
+```
+
+## Gotchas
+
+- NFT metadata can be mutable or stale.
+- Spam checks can lag new collections — "not flagged" is not "authentic".
+- Floor price is marketplace-scoped unless the provider aggregates.
+
+## 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 chain/entity identifiers plus block, slot, transaction, or query ids
+  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, block,
+slot, transaction, or candle close 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 market data is `degraded`, still return metadata/ownership that succeeded
-and label floor or sales metrics as unavailable.
+If market data is `degraded`, still return the metadata/ownership that
+succeeded and label floor or sales metrics as unavailable.
+
+## Hand-offs
+
+- Solana mints, DAS assets, compressed NFTs → `hive-solana-analysis`.
+- Wallet-wide NFT exposure → `hive-wallet-investigation`.
+- Mint/contract safety before buying → `hive-security-risk`.

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

@@ -4,12 +4,14 @@
     {
       "id": 1,
       "prompt": "Research this NFT collection's floor, recent sales, owners, and metadata freshness.",
-      "expected_output": "Uses nft_research, asks for or resolves chain/collection contract, fetches bounded floor/sales/owner/metadata data, and reports marketplace/provider caveats.",
+      "expected_output": "Uses nft_research, asks for or resolves chain/collection contract, fetches bounded floor/sales/owner/metadata data, reports marketplace/provider caveats, and ends with a runtime evidence receipt.",
       "files": [],
       "assertions": [
         "Chooses nft_research.",
+        "Selects collection_market or authenticity_check from routes[] and follows its stop condition.",
         "Requires chain and collection/asset identifier.",
-        "Reports floor/sales metadata caveats."
+        "Reports floor/sales metadata caveats.",
+        "Includes receipt ids and source freshness."
       ]
     },
     {

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

@@ -0,0 +1,50 @@
+[
+  {
+    "query": "whats the floor on collection 0x… on ethereum and recent sales",
+    "should_trigger": true
+  },
+  {
+    "query": "who owns the most of this collection? any whale concentration?",
+    "should_trigger": true
+  },
+  {
+    "query": "is this nft that showed up in my wallet spam",
+    "should_trigger": true
+  },
+  {
+    "query": "how rare is token id 4242 in this collection",
+    "should_trigger": true
+  },
+  {
+    "query": "the metadata on this nft looks wrong, pull the raw traits",
+    "should_trigger": true
+  },
+  {
+    "query": "sales volume for this collection across marketplaces this month",
+    "should_trigger": true
+  },
+  {
+    "query": "check this compressed nft on solana",
+    "should_trigger": false
+  },
+  {
+    "query": "what nfts does wallet 0x28C6… hold",
+    "should_trigger": false
+  },
+  {
+    "query": "is minting from this drop site safe? it wants wallet connect",
+    "should_trigger": false
+  },
+  {
+    "query": "explain how erc-721 royalties work",
+    "should_trigger": false
+  },
+  {
+    "query": "alert me when the floor drops below 1 eth",
+    "should_trigger": false
+  },
+  {
+    "query": "whats the APE token trading at",
+    "should_trigger": false
+  }
+]