clawby-data

Clawby Data Analysis

Fetch real financial data through the Clawby aggregated data API and analyze it. The single source of truth for every interface — its params (required · format · example) and ⚠️ pitfalls — is api/catalog/ (start at api/catalog/_index.yaml). Always read the relevant category yaml before calling. The full machine catalog is api/clawby.yaml (server-generated, versioned).

Works with any AI agent — Claude Code, Codex, OpenClaw, Hermes, and anything that can run shell commands or call an HTTP API: just an API key + the catalog + plain curl.

Quick start

# 1. Auth (once): sign in at https://www.openclawby.com/ → export CLAWBY_API_KEY=pk_xxx
# 2. Find the interface in api/catalog/<category>/  (routing table below)
# 3. Call it:
curl -s -X POST https://api.openclawby.com/api/relay \
  -H "X-API-Key: $CLAWBY_API_KEY" -H "Content-Type: application/json" \
  -d '{"name":"<interface name from catalog>","params":{ ... }}'
# → {source, data, credits:{remaining,used_total}}

Core workflow · Gather ALL available data first, then analyze

Completeness is the goal. A thin answer from a single source is a failure even when correct — go broad first, analyze second. Apply this to every request.

1. Turn the request into a data checklist. Ask "what would a thorough analyst pull?" and list every relevant dimension. Over-collect on purpose (a stock → quote, short data, dark pool, options, financials, sentiment, peers; a token → DEX price/liquidity, holders, funding & OI, odds, social buzz).
2. For each item, sweep ALL FOUR source layers — never stop at the first hit:
   • Layer 1 — Clawby data (/api/relay + on-chain /api/rpc): scan the catalog for every interface that touches the item and call them all. Primary, authoritative.
   • Layer 2 — Local akshare (akdata/, read-only): China markets (A-shares · HK · futures · convertible bonds · ETFs · boards · northbound flows · dragon-tiger list · shareholder data) and global macro (CPI · non-farm · PMI · rate decisions) — 1080 interfaces Layer 1 does not carry. Runs locally on the user's machine with no Clawby key and no credits. Guide: akdata/akshare.md.
   • Layer 3 — Execution connectors (exec/, read-only use): the Binance / Bitget / OKX / Polymarket CLIs expose market data, order books, funding, smart-money and news the other layers may not have. Read-only needs no confirmation.
   • Layer 4 — Your own web access: news, filings, official docs, macro context — fill every remaining gap.
3. Maximize coverage. If two layers supply the same metric, fetch both and cross-check. Fire independent fetches in parallel. Never skip a reachable source.
4. Track coverage, then analyze. Ground every claim in collected data; if a source failed, say so instead of silently dropping the dimension.
5. Offer a formal report when it fits — for substantial asset analysis, offer a professional PDF research report (see Professional analysis reports). Ask first.