Install the Commet Skills before upgrading an integration with the current SDK contracts.
npx skills add commet-labs/skillsAPI version 2026-06-10 separates the feature catalog from customer feature access: every route now says exactly what it returns. All five SDKs ship v7 the same day, and CLI 3.0 completes the set.
Features and feature access are now separate resources
Three renames, one principle: a route should say what it returns.
| Before | After |
|---|---|
GET /features returned a customer's feature access | GET /features returns your feature catalog — the definitions you created |
Customer access mixed into /features | GET /feature-access and GET /feature-access/{code} (with a canUse check) |
GET /addons/active | GET /active-addons |
A catalog of definitions and a customer's access to them are different things — now each has its own resource.
All SDKs v7, same day
@commet/node 7.0.0, commet-go v7, commet-sdk (Python) 7.0.0, commet-java 7.0.0, and commet-php 7.0.0 — every SDK regenerated from the same contract, exposing identical surfaces: features (catalog), featureAccess (per-customer), addons.listActive.
Migrating is one rename:
// v6 — access checks lived under features
const { data } = await commet.features.canUse({
code: "api_calls",
customerId: "user_123",
});
// v7 — access checks live under featureAccess
const { data } = await commet.featureAccess.canUse({
code: "api_calls",
customerId: "user_123",
});
// and features is now the catalog
const catalog = await commet.features.list();npm install @commet/node@7
pip install commet-sdk==7.0.0
go get github.com/commet-labs/commet-go/v7
composer require commet/commet-php:^7.0
implementation("co.commet:commet-java:7.0.0") // GradleCLI 3.0
The same split lands in the CLI: commet features now manages the catalog, and access checks moved to commet feature-access.
commet features list
commet feature-access can-use --customer-id user_123 --code api_callsThree new command groups — commet payouts, commet test-clock, and commet quota — complete 1:1 coverage of the SDK surface. Everything you can do from an SDK, you can now do from your terminal.
No action required. Existing integrations pinned to older versions keep working unchanged — pin 2026-06-07 or earlier and /features still returns feature access, exactly as it always did. The same goes for the SDKs: v6 and earlier keep working as-is. The new routes apply only when you request 2026-06-10 or upgrade to SDK v7.
Visit the SDK reference for the full v7 surface, or the CLI docs to run it all from your terminal.