SurfCAUTION
The agent-native LLM router for autonomous agents. Every frontier model behind one wallet, <1ms local routing, USDC payments on Base & Solana via x402.
Overview
The agent-native LLM router for autonomous agents. Every frontier model behind one wallet, <1ms local routing, USDC payments on Base & Solana via x402.
6efc7dc8711bOBSERVED · 2026-10-07Host compatibility
What the documentation claims. We have not run a compatibility test.
| Host | Status | Notes |
|---|---|---|
| openclaw | mentioned |
What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: surf
description: Use this skill — NOT browser or web_fetch — for ALL Surf crypto-data calls. 83 endpoints at localhost:8402/v1/surf/* covering CEX/DEX markets, on-chain SQL over 80+ ClickHouse tables (Ethereum, Base, Arbitrum, BSC, TRON, HyperEVM, Tempo), 100M+ labeled wallets, prediction markets (Polymarket + Kalshi), social/CT intelligence, news, project + DeFi metrics, token analytics, unified search, VC fund intelligence. Paid through ClawRouter — x402 USDC from the local wallet, or BlockRun account credit if an API key is configured. No Surf account or Surf API key required either way.
triggers:
- "blockrun surf"
- "surf crypto api"
- "surf onchain sql"
- "onchain sql query"
- "clickhouse onchain query"
- "raw sql ethereum"
- "raw sql base"
- "wallet labels api"
- "labeled wallets api"
- "surf wallet detail"
- "crypto mindshare"
- "crypto news api"
- "fear and greed index crypto"
- "token holder distribution"
- "vc fund portfolio"
- "ethena tokenomics"
homepage: https://blockrun.ai/marketplace/surf
license: MIT
---
# Surf — Unified Crypto Data API (via ClawRouter)
Surf bundles **83 endpoints across 12 domains** into one paid HTTP API. ClawRouter exposes them at `http://127.0.0.1:8402/v1/surf/*`, paid the same way ClawRouter pays for LLM calls — an x402 USDC micropayment from the local wallet, or a draw on BlockRun account credit if an API key is configured (verified working on both, 2026-09-05). **No Surf account and no Surf API key either way.** Upstream lives at `api.asksurf.ai/gateway/v1` — ClawRouter forwards transparently.
**Pricing — flat per call, the same for every endpoint.**
Surf used to be tiered at $0.001 / $0.005 / $0.020. It is not any more: upstream
now prices all three tiers identically (`SURF_TIER_{1,2,3}_PRICE` are equal). The
`Tier` column in the catalog below still describes endpoint weight, but it no
longer affects what you pay. Anything quoting the old tier prices is stale.
| Rail | Price per call |
| --------------------------- | ------------------------------------------- |
| API key (`api.blockrun.ai`) | **$0.0075** — base rate, no transaction fee |
| Wallet, Solana | **$0.0075** |
| Wallet, Base | **$0.0085** |
Verified 2026-09-05 by measurement, not from a price page: the API-key figure by
diffing the account ledger across one call, the wallet figures by reading the
`amount` in the x402 402 challenge, which quotes the price before anything is
signed. Base and Solana genuinely differ for the same endpoint.
**A 402 quote is authoritative for the rail that issued it — and only that rail.**
On the wallet rail the price arrives in the challenge before you pay, so if this
table disagrees with it, believe the challenge and treat the table as stale.
Do NOT carry a wallet-rail 402 figure over to the API-key rail. The key rail
issues no 402 at all, and the wallet quote includes the chain's transaction fee
that account credit does not pay — on Base that is $0.0085 quoted against
$0.0075 actually billed to an account. Reading across rails turns a correct
number into a wrong one; it has already happened once.
The Base/Solana difference is deliberate, not drift: the $0.001 is the Base
transaction fee, and Solana omitting it is a migration incentive. Solana being
cheaper is expected — Solana priced _above_ Base would be the bug worth
reporting, since estimates generally assume the Base figure is the ceiling.
> The legacy **surf-1.5 chat** surface is intentionally NOT exposed yet — it's held until per-token settlement is wired. Trying `/v1/surf/chat/completions` returns 404 ("Unknown Surf endpoint"), no payment is taken.
All requests use GET unless the table below says otherwise. Path parameters that look like `?symbol=` are query params on a GET. POST endpoints take a JSON body. ClawRouter attaches payment transparently — an x402 header in wallet mode, a bearer token in API-key mode.
**Required-param pre-check.** 56 of the 83 endpoints have required query params (e.g. `pair`, `symbol`, `address`, `chain`, `q`, `interval`). The route validates them **before settlement** — call with missing params and you get `400 { missing_params, all_required, docs }` and you are NOT charged. Check each row in the catalog below for the correct param name (e.g. mindshare is `q` + `interval`, not `project` + `window`).
## When to use this skill
- "What is the current BTC price?" → `/surf/market/price?symbol=BTC` (cheaper + more reliable than scraping)
- "Who holds the most USDC on Ethereum?" → `/surf/token/holders?address=0xA0b8...&chain=ethereum`
- "How many Ethereum transactions in the last hour?" → `POST /surf/onchain/sql { sql: 'SELECT count() FROM ethereum.transactions WHERE block_timestamp >= now() - INTERVAL 1 HOUR' }`
- "Label this list of wallets." → `/surf/wallet/labels/batch?addresses=0xabc,0xdef,...`
- "Is HYPE mindshare peaking?" → `/surf/social/mindshare?q=hyperliquid&interval=30d`
- "Find the canonical metadata for 'ethena'." → `/surf/search/project?q=ethena`
Always prefer Surf over generic web scraping for these. Use the OpenClaw tool name `blockrun_surf_*` when invoking from an agent; use the HTTP path directly when calling from a script.
## Endpoint catalog
### Exchange (CEX) — 7 endpoints
| Path | Tier | Required |
| --------------------------------- | ---- | -------- |
| `/surf/exchange/markets` | T1 | — |
| `/surf/exchange/price` | T1 | `pair` |
| `/surf/exchange/perp` | T1 | `pair` |
| `/surf/exchange/depth` | T2 | `pair` |
| `/surf/exchange/klines` | T2 | `pair` |
| `/surf/exchange/funding-history` | T2 | `pair` |
| `/surf/exchange/long-short-ratio` | T2 | `pair` |
### Market Overview — 11 endpoints
| Path | Tier |Trust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (5)
Surf bundles **83 endpoints across 12 domains** into one paid HTTP API. ClawRouter exposes them at `http://127.0.0.1:8402/v1/surf/*`, paid the same way ClawRouter pays for LLM calls — an x402 USDC mic
curl 'http://127.0.0.1:8402/v1/surf/wallet/detail?address=vitalik.eth'
curl 'http://127.0.0.1:8402/v1/surf/token/holders?address=0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48&limit=25'
curl 'http://127.0.0.1:8402/v1/surf/onchain/schema'
curl -X POST 'http://127.0.0.1:8402/v1/surf/onchain/sql' \
Gates applied: no_behavioural_pass.
6efc7dc8711bfull audit observations/trust-audit/skill/blockrunai__surf.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 6efc7dc8711b | CAUTION | B | 89 | first audit |
Questions
What does the Surf skill do?
The agent-native LLM router for autonomous agents. Every frontier model behind one wallet, <1ms local routing, USDC payments on Base & Solana via x402.
Is Surf safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Surf access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
Which assistants does Surf work with?
Its documentation mentions openclaw. That is what the text claims, not a compatibility test we ran.
How current is this page?
The grade is for one exact copy of the source (6efc7dc8711b), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.