/search
Use when the user wants real-time web or news results with AI-summarized answers and citations — Grok Live Search via BlockRun. Cheapest path for "what just happened" questions where freshness beats neural-semantic ranking.
$ npx -y skills add BlockRunAI/blockrun-mcp --skill search --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/search
Context preview
The summary Claude sees to decide when to auto-load this skill.
Use when the user wants real-time web or news results with AI-summarized answers and citations — Grok Live Search via BlockRun. Cheapest path for "what just happened" questions where freshness beats neural-semantic ranking.
SKILL.md
search.SKILL.mdname: search
description: Use when the user wants real-time web or news results with AI-summarized answers and citations — Grok Live Search via BlockRun. Cheapest path for "what just happened" questions where freshness beats neural-semantic ranking.
triggers:
- "live search"
- "grok live"
- "what just happened"
- "real time news"
- "breaking news"
- "today's news"
- "search with citations"
- "cited search"
- "news search"
Live Search (Grok)
Real-time web + news search with AI-summarized results and citations. **PRICED PER SOURCE and expensive by default: $0.025 × `max_results`, +5% +$0.001 → default 10 settles $0.2635 per call.** Best for *fresh* queries; for semantic / neural research use `blockrun_exa` instead.
How to Call from MCP
blockrun_search({ body: {
query: "what's the consensus on the Fed's next move",
sources: ["web", "news"],
max_results: 10
}})Body Shape
| Field | Required | Type | Notes | |---|---|---|---| | `query` | yes | string | Natural-language search query | | `sources` | no | string[] | Subset of `["web","news"]`. Default: both. Does NOT multiply price. | | `max_results` | no | number | 1–50, default 10. **Drives the price** — ~$0.0263 charged per source. Pass a small number to cap spend; the gateway prices the raw value and does not floor fractions. | | `from_date` | no | string | `YYYY-MM-DD` lower bound on result date | | `to_date` | no | string | `YYYY-MM-DD` upper bound |
When to Reach for Which Source
| User intent | `sources` setting | |---|---| | Breaking news / today's headlines | `["news"]` | | What's the CT / KOL sentiment on X | `["x"]` | | Backgrounder / explainer / docs | `["web"]` | | General "find current info" question | omit — defaults to all three |
Worked Examples
1. "What's the latest on the ETH ETF approval timeline?"
blockrun_search({ body: { query: "Ethereum ETF approval SEC", sources: ["news","web"], max_results: 8 } })**Cost: ~$0.2110** (8 sources: $0.025 × 8 × 1.05 + $0.001).
2. "What is X saying about Solana's latest outage?"
blockrun_search({ body: { query: "Solana outage today", sources: ["x"], max_results: 15 } })**Cost: ~$0.3948** (15 sources: $0.025 × 15 × 1.05 + $0.001).
3. "Background on Pectra upgrade, last 90 days only"
blockrun_search({ body: {
query: "Ethereum Pectra upgrade",
sources: ["web","news"],
from_date: "2026-02-17"
}})**Cost: $0.2635** (10 sources, the default — verified live).
search vs exa — Pick the Right Tool
| Use case | Tool | |---|---| | "What's happening *right now*?" — freshness matters | `blockrun_search` | | "Find the canonical paper on X" — semantic relevance matters | `blockrun_exa` | | "Pull the full text of these 5 URLs" — content fetch | `blockrun_exa` `contents` | | "Cited answer to a question" | both work; `blockrun_exa answer` is grounded in pre-indexed corpus, `blockrun_search` searches the live web |
Notes
- Returns AI-summarized text + a list of sources with URLs. The summary is one paragraph; sources let you drill in.
- **Price is per result, not per source.** `max_results: 20` with one source or three sources both charge **$0.526** ($0.025 × 20 × 1.05 + $0.001 — verified live). Pass a smaller `max_results` to cap spend.
- Date filters are strict — results outside the window are dropped, not down-ranked.
Reference
- Endpoint: `POST /v1/search`
- Upstream: xAI Grok Live Search
Read more
name: search description: Use when the user wants real-time web or news results with AI-summarized answers and citations — Grok Live Search via BlockRun. Cheapest path for "what just happened" questions where freshness beats neural-semantic ranking. triggers: - "live search" - "grok live" - "what just happened" - "real time news" - "breaking news" - "today's news" - "search with citations" - "cited search" - "news search"
Live Search (Grok)
Real-time web + news search with AI-summarized results and citations. **PRICED PER SOURCE and expensive by default: $0.025 × `max_results`, +5% +$0.001 → default 10 settles $0.2635 per call.** Best for *fresh* queries; for semantic / neural research use `blockrun_exa` instead.
How to Call from MCP
blockrun_search({ body: {
query: "what's the consensus on the Fed's next move",
sources: ["web", "news"],
max_results: 10
}})Body Shape
| Field | Required | Type | Notes | |---|---|---|---| | `query` | yes | string | Natural-language search query | | `sources` | no | string[] | Subset of `["web","news"]`. Default: both. Does NOT multiply price. | | `max_results` | no | number | 1–50, default 10. **Drives the price** — ~$0.0263 charged per source. Pass a small number to cap spend; the gateway prices the raw value and does not floor fractions. | | `from_date` | no | string | `YYYY-MM-DD` lower bound on result date | | `to_date` | no | string | `YYYY-MM-DD` upper bound |
When to Reach for Which Source
| User intent | `sources` setting | |---|---| | Breaking news / today's headlines | `["news"]` | | What's the CT / KOL sentiment on X | `["x"]` | | Backgrounder / explainer / docs | `["web"]` | | General "find current info" question | omit — defaults to all three |
Worked Examples
1. "What's the latest on the ETH ETF approval timeline?"
blockrun_search({ body: { query: "Ethereum ETF approval SEC", sources: ["news","web"], max_results: 8 } })**Cost: ~$0.2110** (8 sources: $0.025 × 8 × 1.05 + $0.001).
2. "What is X saying about Solana's latest outage?"
blockrun_search({ body: { query: "Solana outage today", sources: ["x"], max_results: 15 } })**Cost: ~$0.3948** (15 sources: $0.025 × 15 × 1.05 + $0.001).
3. "Background on Pectra upgrade, last 90 days only"
blockrun_search({ body: {
query: "Ethereum Pectra upgrade",
sources: ["web","news"],
from_date: "2026-02-17"
}})**Cost: $0.2635** (10 sources, the default — verified live).
search vs exa — Pick the Right Tool
| Use case | Tool | |---|---| | "What's happening *right now*?" — freshness matters | `blockrun_search` | | "Find the canonical paper on X" — semantic relevance matters | `blockrun_exa` | | "Pull the full text of these 5 URLs" — content fetch | `blockrun_exa` `contents` | | "Cited answer to a question" | both work; `blockrun_exa answer` is grounded in pre-indexed corpus, `blockrun_search` searches the live web |
Notes
- Returns AI-summarized text + a list of sources with URLs. The summary is one paragraph; sources let you drill in.
- **Price is per result, not per source.** `max_results: 20` with one source or three sources both charge **$0.526** ($0.025 × 20 × 1.05 + $0.001 — verified live). Pass a smaller `max_results` to cap spend.
- Date filters are strict — results outside the window are dropped, not down-ranked.
Reference
- Endpoint: `POST /v1/search`
- Upstream: xAI Grok Live Search
Live data for AI agents — search, research, markets, crypto, X/Twitter. Pay-per-call via x402 micropayments.
Repo: BlockRunAI/blockrun-mcp
Other skills on blockrun-mcp.
- /blockrun
Pay-per-call access to AI models, real-time data, media generation and multi-chain RPC over x402 micropayments (USDC on Base or Solana). No API keys, no accounts, no subscriptions. Start here when you have the BlockRun MCP installed and need to know WHICH tool answers a
Open skill - /crypto-data
Use for any crypto data question — token/coin prices, FX, commodities, stocks, OHLC history, DEX pairs and liquidity, DeFi TVL, yield/APY pools, on-chain SQL, wallet labels and net worth, social mindshare, news, or raw JSON-RPC against a chain. Routes across five tools that
Open skill - /exa-research
Use when researching products, finding academic papers, discovering competitors, reading webpage content, or getting cited answers grounded in real web sources. Use over generic search when semantic relevance matters.
Open skill - /gentech-blockrun
GenTech Labs' integration patterns for BlockRun MCP from Hermes Agent. Covers daily usage patterns, cost-optimized workflows, multi-tool pipelines, and reliable error handling for BlockRun's full toolset.
Open skill - /image-prompting
Use when generating or editing images via `blockrun_image` — especially with GPT Image 2, Nano Banana, or Grok Imagine for posters, UI mockups, marketing assets, product shots, or anything with on-image text. Turns vague user requests ("make me a cool poster") into structured,
Open skill - /modal
Use when the user needs to run isolated code remotely — a disposable container, optional GPU access (T4 → H100), or a safer place for untrusted / heavy code. Prefer local execution for normal repo work; use Modal sandboxes for isolation, hardware access, or one-shot heavy
Open skill

