ClawHub API Usage Guide

Problem

ClawHub API integrations can stumble on authentication scope, public endpoints, rate-limit headers, and 429 handling. This skill is a practical reference for teams that need to read skill catalogs, download packages, or check moderation and scan signals, turning quickstart, auth, endpoints, and error handling into a consistent integration checklist.

How It Works

• Quickstart: covers the first API call with curl or Python requests, API key retrieval, and common questions.
• Auth boundaries: distinguishes public read endpoints from write and account operations that require a Bearer Token, including 401 and 403 handling.
• Endpoint map: groups common endpoints such as GET /api/v1/search, GET /api/v1/skills, and GET /api/v1/packages, with full reference pointed to reference/api-reference.md.
• Limits and errors: explains X-RateLimit-Remaining, Retry-After, exponential backoff, and handling for 400, 404, 415, and 429.

Boundaries

It fits third-party directory builds, safety checks, and package download flows, but not bypassing authentication, mirroring private content, or implying platform endorsement. Live server responses, endpoint behavior, and official docs remain authoritative.