Claw-Net

Ask a question in plain English, get data from 13,000+ APIs in one call. Crypto prices, social data, market intelligence. Every response is cryptographically...

Security Scan

Claw-Net is internally coherent: it’s an instruction-only wrapper for a public web API that expects a CLAWNET_API_KEY; there are no unexplained credentials or install steps, but a few small inconsistencies and usage cautions merit review before use.

Purpose & Capability

The skill’s name/description (query many APIs, orchestrate responses) matches the runtime instructions: all examples call https://api.claw-net.org and require CLAWNET_API_KEY. The requested credential is the single, expected item for this purpose.

Instruction Scope

Runtime instructions stay focused on calling ClawNet endpoints. Two items to note: (1) the MCP example shows an env var CLAWNET_BASE_URL and an npx/tsx command — that would run remote code if followed and is not declared in requires.env; (2) the x402 option implies wallet-based on-chain payments (agent wallet access), which is not spelled out as an explicit required credential. These are examples rather than mandatory actions, but the MCP example could lead to executing third-party code if used verbatim.

Install Mechanism

No install spec and no code files — this is instruction-only. That is the lowest-risk pattern since nothing is written to disk by the skill itself.

Credentials

Only CLAWNET_API_KEY is declared as required (primaryEnv), which is proportionate. Minor inconsistency: SKILL.md references CLAWNET_BASE_URL in the MCP example but that env var is not declared. Also consider that the x402 payment option could require a wallet or on-chain signing outside the declared env model, so understand how your agent/wallet would be invoked before enabling that flow.

Persistence & Privilege

always:false and no required config paths or persistent installation. The skill does not request elevated or always-on privileges.

Assessment

This skill looks like a straightforward client for a public API and only needs your CLAWNET_API_KEY. Before installing: (1) confirm the API domain (https://api.claw-net.org) and the homepage/repo URLs are legitimate and match the project you expect; (2) do not run the MCP npx/tsx example without auditing the referenced code — it will fetch and run third-party packages; (3) if you plan to use x402 (USDC) payment flows, understand how your agent/wallet will sign transactions and avoid granting persistent signing access to untrusted code; (4) give the API key least privilege, monitor usage, and be ready to revoke it if you see unexpected calls; and (5) inspect the referenced soma.json / cryptographic provenance endpoints if you need to validate the claimed data signing provenance.

Ask a question in plain English. Get data from 13,000+ APIs in one call. ClawNet figures out which data sources to query, runs them in parallel, and gives you one clean answer.

Quick Start

curl -X POST https://api.claw-net.org/v1/orchestrate \
  -H "X-API-Key: $CLAWNET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"query": "What is the price of SOL right now?"}'

{
  "answer": "SOL is currently trading at $148.23, up 3.2% in 24h. Volume: $2.1B...",
  "costBreakdown": { "creditsUsed": 8, "costUsd": 0.008 },
  "metadata": { "stepsExecuted": 3, "totalDurationMs": 1240 }
}

That's it. One question in, one answer out.

Setup (3 options)

Option A: API Key (most common)

1. Get a key at https://claw-net.org/dashboard
2. Set CLAWNET_API_KEY in your environment
3. Base URL: https://api.claw-net.org

Option B: x402 / USDC (no account needed) Pay per call with USDC on Base. No API key, no signup. Your wallet-equipped agent just calls the endpoint and pays automatically.

POST https://api.claw-net.org/x402/orchestrate
POST https://api.claw-net.org/x402/skills/{id}

Option C: MCP (for AI coding tools) Connect ClawNet as an MCP server in Claude Code, Cursor, VSCode, or Windsurf:

{
  "mcpServers": {
    "clawnet": {
      "command": "npx",
      "args": ["tsx", "src/mcp/server.ts"],
      "env": { "CLAWNET_API_KEY": "your_key", "CLAWNET_BASE_URL": "https://api.claw-net.org" }
    }
  }
}

Data Skills (4 built-in)

Pre-built skills that return structured JSON. No LLM involved — fast and cheap:

Skill	Cost	What you get
price-oracle-data	1 credit ($0.001)	Real-time price, 24h change, volume, market cap
trending-tokens-data	2 credits ($0.002)	Top trending tokens by volume and social buzz
whale-tracker-data	2 credits ($0.002)	Large holder movements, net flow, holder changes
defi-yield-data	2 credits ($0.002)	DeFi yield opportunities, APY, TVL, risk tier

curl "https://api.claw-net.org/v1/skills/price-oracle-data/query?token=SOL" \
  -H "X-API-Key: $CLAWNET_API_KEY"

How to Use ClawNet

Step 1: Browse (free, no auth)

See what's available without an API key:

# Browse the skill catalog
GET /v1/marketplace/skills

# Check a specific skill's input format and pricing
GET /v1/marketplace/skills/price-oracle-data

Step 1b: Search & estimate (free, but needs API key)

# Semantic search for skills by topic
POST /v1/discover  {"query": "solana token prices"}

# Preview cost before running a query
GET /v1/estimate?query=What is SOL worth?

Step 2: Ask (uses credits)

Send a natural language query. ClawNet's LLM picks the best endpoints, runs them in parallel, and synthesizes the answer:

POST /v1/orchestrate  {"query": "Compare SOL vs ETH performance this week"}

Every response includes cryptographic proof of where the data came from (see Provenance below).

Step 3: Call directly (after discovery)

Once you know which skill you need, skip the LLM routing and call it directly — faster and cheaper:

# With API key
POST /v1/skills/price-oracle-data/invoke  {"variables": {"token": "SOL"}}

# With USDC (no API key needed)
POST /x402/skills/price-oracle-data  {"variables": {"token": "SOL"}}

Step 4: Come back when needs change

The registry updates every 4 hours with new endpoints from 7 discovery sources. New question? New data need? Use /v1/orchestrate again to discover the right endpoints.

Verify Data (optional)

Cross-reference any answer against independent sources before acting on it:

curl -X POST https://api.claw-net.org/v1/manifest \
  -H "X-API-Key: $CLAWNET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tier": "standard", "verify": {"claims": [{"type": "price", "subject": "SOL", "value": 148.23}]}}'

Tiers: quick (0.5 credits), standard (2 credits), deep (5 credits).

All Endpoints

Free (no auth needed)

Endpoint	What it does
GET /v1/marketplace/skills	Browse the skill catalog
GET /v1/marketplace/skills/:id	Skill details, input schema, pricing
GET /v1/soma/:did/trust	Check any agent's verification history
GET /v1/soma/:did/verdicts	Recent verification verdicts for an agent
GET /.well-known/soma.json	ClawNet's cryptographic identity

Requires API key (but no credit cost)

Endpoint	What it does
POST /v1/discover	Semantic search for skills by topic
GET /v1/estimate?query=...	Preview cost before running a query
GET /v1/balance	Check your credit balance

Paid (API key or x402)

Endpoint	Cost	What it does
POST /v1/orchestrate	2+ credits	Natural language query across 13,000+ sources
GET /v1/skills/:id/query	1-2 credits	Query a data skill (structured JSON)
POST /v1/skills/:id/invoke	varies	Invoke a skill directly with variables
POST /v1/manifest	0.5-5 credits	Cross-reference data against independent sources

Pricing

1 credit = $0.001. Credits never expire. Buy at https://claw-net.org (Stripe or USDC).

A typical orchestration query costs 2-10 credits ($0.002-$0.01). Data skills cost 1-2 credits each.

Endpoint Discovery

ClawNet doesn't just have a static list of APIs. It auto-discovers new endpoints every 4 hours from 7 sources:

Source	Endpoints
Built-in registry	274 curated
ClawAPIs	Dynamic providers
402index	15,000+ community directory
Coinbase Bazaar	Official x402 discovery
Zauth	Pre-verified (only WORKING status)
Dexter	Facilitator marketplace
x402list	17,000+ services

When you ask a question, ClawNet searches across all of these to find the best data source.

Provenance

Every response is cryptographically signed. You don't have to trust ClawNet — you can verify.

What this means in practice: Each response includes proof of what data was fetched, from where, and that it hasn't been tampered with. This happens automatically — no extra steps needed.

Response headers (on every orchestration and x402 response):

X-Soma-Protocol: soma/1.0
X-Soma-Data-Hash: <hash of the response data>
X-Soma-Signature: <cryptographic signature>
X-Soma-Model-Verified: true
X-Soma-Discovery: /.well-known/soma.json

Want to go deeper?

• GET /.well-known/soma.json — ClawNet's full cryptographic identity
• GET /v1/soma/:did/trust — verification history for any agent (free, public)
• Install soma-sense to independently verify ClawNet's model usage via MCP
• Read the Soma paper for the full protocol

On-chain identity: ClawNet (36119) and Soma (37696) are registered on Base Mainnet via ERC-8004.

Error Codes

Code	Status	Meaning
INSUFFICIENT_CREDITS	402	Out of credits — buy more or use x402
INVALID_API_KEY	401	Bad or missing API key
RATE_LIMITED	429	Too many requests — wait and retry
SOURCE_ERROR	502	Upstream data source failed — try again