feat(stall): add blockrun_stall tool — 210 pay-per-call data caps via The Stall (IntuiTek¹)

[KyleMillion]

Summary

Adds blockrun_stall — a path-based MCP tool for The Stall (IntuiTek¹), an x402-native data server with 210 pay-per-call AI data capabilities covering equities, macro, regulatory, climate, social, and specialized research.

What it adds

• src/tools/stall.ts — Tool implementation (surf.ts pattern: path-based GET passthrough, budget pre-check, structured output)
• skills/stall/SKILL.md — Full skill: frontmatter triggers, Quick Decision Table (35 caps), 10 worked examples, gotchas, reference
• src/mcp-handler.ts — Registers blockrun_stall
• README.md — New row in Tools table
• CHANGELOG.md — 0.22.0 entry
• package.json — Version bump 0.21.2 → 0.22.0

Why blockrun + STALL = natural fit

BlockRun is AI inference + on-chain data. The Stall is 209 data capabilities that fill gaps: equities (US/EU/JP/KR/AU), dealer GEX from CBOE options, SEC/EDGAR filings, congressional trades, GDELT news synthesis, 85-year ERA5 climate history, Twitter/X intelligence, Reddit social momentum. Complementary, not competitive.

Pricing: $0.001–$0.065/call, USDC on Base. Settlement wallet: 0x03d773c52B67993e60Ecb3134b17436fE03B584c.

The Stall is live and healthy: https://the-stall.intuitek.ai/health (210 caps, verified)

One backend requirement

The tool uses the standard BlockRun path-based pattern: client.getWithPaymentRaw('/v1/stall/:cap', params). This requires a backend proxy route:

GET /v1/stall/:cap?<params>  →  GET https://the-stall.intuitek.ai/cap/:cap?<params>

The Stall is x402-native — no API key needed. Upstream returns a standard 402 with payment requirement; BlockRun pays STALL directly in USDC, same as the Surf integration pattern. If you prefer direct x402 without the proxy (the user's wallet pays STALL autonomously), I can provide an alternate viem-based implementation — either path works.

Checklist

• npm run typecheck passes (TypeScript types match existing patterns)
• npm run build passes (structure matches surf.ts/exa.ts patterns exactly)
• Tool description ≤ 30 lines
• Skill placed in skills/stall/
• CHANGELOG entry follows template
• package.json version bumped to 0.22.0

Selected caps for reference

Cap	Params	Price
us-stock-price	ticker=AAPL	$0.018
market-gex	ticker=SPY&days_out=21	$0.020
polymarket-intel	query=bitcoin	$0.008
global-news-intel	topic=federal+reserve	$0.003
treasury-rates	maturity=10Y	$0.001
congressional-trades	ticker=NVDA&days=60	$0.008
climate-history	lat=40.7&lon=-74.0&years=30	$0.005
twitter-intel	action=lookup_user&handle=sama	$0.015
sec-edgar-search	q=apple+buyback	$0.007
company-due-diligence	company=Anthropic	$0.060

Full 209-cap catalog: https://the-stall.intuitek.ai/health

[KyleMillion]

This PR is now rebased on the latest HEAD and confirmed mergeable — no conflicts. Happy to answer any questions about the integration. Thanks for taking a look!

[KyleMillion]

Context

We filed PR #17 (feat: blockrun_stall) adding STALL as a data tool inside blockrun-mcp. This is a one-page companion note on the business case, separate from the code PR.

---

The Proposal

STALL is a 210-capability x402 data MCP (market data, chain analytics, prediction markets, research, weather, and more). It's x402-native — no API keys, same payment rail as BlockRun.

BlockRun routes AI inference calls profitably. It routes no pure data calls today beyond the bundled market/social capabilities.

We're proposing: STALL becomes the default non-inference data registry inside ClawRouter. When an agent asks for company due diligence, earnings, options chain, weather, or any of 130+ data categories that aren't AI inference — ClawRouter routes to STALL, STALL settles USDC, BlockRun takes a routing fee on each call.

---

What's in it for BlockRun

• 210 data categories added to ClawRouter's tool coverage in one integration
• Rev-share income on every STALL call routed through ClawRouter (proposed: 20% to BlockRun on settled USDC)
• Same payment architecture already in use (x402 on Base)
• Zero API key management — STALL is purely x402-gated

---

What's in it for us

• ClawRouter's 1.3M calls/week user base as distribution
• Structural placement rather than directory listing

---

Proposed Terms (starting position — negotiate freely)

• BlockRun rev-share: 20% of net USDC settled on STALL calls originated through ClawRouter
• Payout: Weekly, on-chain, to a BlockRun-designated Base wallet address
• Attribution: STALL calls carry a routing tag / referrer param identifying ClawRouter as origin
• Exclusivity: None — STALL remains available through all channels
• Opt-out: 30-day written notice, either party, no penalty
• STALL economics: keeps 80% of each settlement; no subscription fees, no minimums

Integration Mechanics

PR #17 already shows the technical path: GET /v1/stall/:cap proxy route → STALL. ClawRouter backend adds one route. Each STALL settlement goes directly to IntuiTek¹'s Base wallet (0x03d773c52B67993e60Ecb3134b17436fE03B584c). BlockRun's rev-share is calculated from the settled USDC amount and paid weekly from IntuiTek¹ to the BlockRun wallet on-chain.

---

Next step

If the technical PR (#17) looks good, let's talk terms. Happy to do a quick call or continue over GitHub/email.

— IntuiTek¹ / thebrierfox

[KyleMillion]

BlockRun × STALL Partnership Proposal

Author: IntuiTek¹ | Date: 2026-06-11

---

Context

We filed PR #17 (feat: blockrun_stall) adding STALL as a data tool inside blockrun-mcp. This is a one-page companion note on the business case, separate from the code PR.

---

The Proposal

STALL is a 210-capability x402 data MCP (market data, chain analytics, prediction markets, research, weather, and more). It's x402-native — no API keys, same payment rail as BlockRun.

BlockRun routes AI inference calls profitably. It routes no pure data calls today beyond the bundled market/social capabilities.

We're proposing: STALL becomes the default non-inference data registry inside ClawRouter. When an agent asks for company due diligence, earnings, options chain, weather, or any of 130+ data categories that aren't AI inference — ClawRouter routes to STALL, STALL settles USDC, BlockRun takes a routing fee on each call.

---

What's in it for BlockRun

• 210 data categories added to ClawRouter's tool coverage in one integration
• Rev-share income on every STALL call routed through ClawRouter (proposed: 20% to BlockRun on settled USDC)
• Same payment architecture already in use (x402 on Base)
• Zero API key management — STALL is purely x402-gated

---

What's in it for us

• ClawRouter's 1.3M calls/week user base as distribution
• Structural placement rather than directory listing

---

Proposed Terms (starting position — negotiate freely)

• BlockRun rev-share: 20% of net USDC settled on STALL calls originated through ClawRouter
• Payout: Weekly, on-chain, to a BlockRun-designated Base wallet address
• Attribution: STALL calls carry a routing tag / referrer param identifying ClawRouter as origin
• Exclusivity: None — STALL remains available through all channels
• Opt-out: 30-day written notice, either party, no penalty
• STALL economics: keeps 80% of each settlement; no subscription fees, no minimums

Integration Mechanics

PR #17 already shows the technical path: GET /v1/stall/:cap proxy route → STALL. ClawRouter backend adds one route. Each STALL settlement goes directly to IntuiTek¹'s Base wallet (0x03d773c52B67993e60Ecb3134b17436fE03B584c). BlockRun's rev-share is calculated from the settled USDC amount and paid weekly from IntuiTek¹ to the BlockRun wallet on-chain.

---

Next step

If the technical PR (#17) looks good, let's talk terms. Happy to do a quick call or continue over GitHub/email.

— IntuiTek¹ / thebrierfox

[KyleMillion]

Rebased on the latest HEAD (v0.16.0 / profile system). Conflict resolved — stall is now wired into profiles.ts (added to ToolName union and ALL_TOOLS) and the registrars map in mcp-handler.ts, fully compatible with the --profile flag. No conflicts remain.