rest-api-designREST API design patterns: resource naming, HTTP methods, status codes, pagination, filtering, authentication, rate limiting, versioning, and response formats...
Install via ClawdBot CLI:
clawdbot install djc00p/rest-api-designGrade Limited — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 22, 2026
Designing REST endpoints for order management, including creation, retrieval, update, and cancellation. Uses sub-resources for order items and returns appropriate status codes for each operation.
Building a user CRUD API with pagination, filtering by role or status, and authentication via API keys. Implements rate limiting to protect against abuse.
Designing endpoints for transaction history, balance inquiries, and fund transfers. Emphasizes idempotency for POST requests and error handling with consistent response formats.
Creating a public API to search for providers by specialty, location, and insurance. Uses cursor-based pagination and versioning to evolve without breaking clients.
Designing endpoints to register, configure, and monitor IoT devices. Implements resource naming with device IDs and sub-resources for telemetry data, with rate limiting per device.
Charge based on API call volume (per request or per 1000 requests). Rate limiting and pagination ensure fair usage, while token-based authentication enables billing.
Offer basic endpoints for free (e.g., 1000 calls/day) and premium features (higher rate limits, advanced filtering, dedicated support) via subscription tiers.
Provide free public API to drive ecosystem adoption, then monetize through partner integrations, data insights, or premium SLA guarantees.
💬 Integration Tip
Start with the quick start checklist: define resource URLs, HTTP methods, status codes, error format, and authentication before adding advanced features like pagination and rate limiting.
Scored May 22, 2026
API reference for CoinMarketCap DEX endpoints including token lookup, pools, transactions, trending, and security analysis. Use this skill whenever the user...
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project structure, or making codebases more accessible to new developers. The skill provides templates, best practices, and structured approaches for creating clear, beginner-friendly documentation.
API Design Reviewer
Cut AI token costs by 60-85% with deterministic query validation and intelligent caching. Standalone or integrates with Company Brain Core OS. Free, open-sou...
EU MDR 2017/745 compliance specialist for medical device classification, technical documentation, clinical evidence, and post-market surveillance. Covers Ann...