api-compatChange public APIs without breaking clients—versioning schemes, additive vs breaking changes, deprecation windows, and comms. Use when shipping breaking chan...
Install via ClawdBot CLI:
clawdbot install codenova58/api-compatGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 11, 2026
A SaaS company needs to deprecate an old v1 API endpoint while supporting mobile apps that take months to update. They use additive changes first, then communicate a sunset date with response headers like Sunset and Deprecation, and gate removal on usage metrics.
An e-commerce platform is sunsetting a legacy 'category_id' field in favor of a new 'category_slug' field. They add the new field as nullable and optional, track callers of the old field via logging, and only remove after a 6-month deprecation window and no traffic.
A mobile API provider must change authentication from API key to OAuth2 without breaking existing mobile clients. They introduce OAuth2 as an alternative, keep the old key method alive for 12 months, and coordinate releases with app store updates.
An analytics company switches from offset-based pagination to cursor-based pagination to improve performance. They add cursor pagination as an option, maintain the old offset mechanism, and migrate clients over 3 months with detailed migration docs.
Companies charge per API call or subscription. API compatibility ensures clients stay on supported versions without breaking, reducing churn and support tickets.
Platforms like Shopify or Salesforce allow third-party integrations. Maintaining API compatibility encourages app developers to build on the platform, increasing stickiness and ecosystem value.
Enterprise contracts include uptime and non-breaking change guarantees. API compatibility enables smooth upgrades, justifying higher price tiers and longer commitments.
💬 Integration Tip
Start by auditing your current API usage to identify deprecated fields and clients; then implement additive changes first and set up telemetry for old endpoints before any removal.
Scored May 11, 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...