Creates a new feature.
Use this to programmatically create features for metering usage, managing access, or building credit systems.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The name of the feature.
The type of the feature. 'single_use' features are consumed, like API calls, tokens, or messages. 'continuous_use' features are allocated, like seats, workspaces, or projects. 'credit_system' features are schemas that unify multiple 'single_use' features into a single credit system.
boolean, metered, credit_system The ID of the feature to create.
Whether this feature is consumable. A consumable feature is one that periodically resets and is consumed rather than allocated (like credits, API requests, etc.). Applicable only for 'metered' features.
Singular and plural display names for the feature in your user interface.
A schema that maps 'single_use' feature IDs to credit costs. Applicable only for 'credit_system' features.
OK
The unique identifier for this feature, used in /check and /track calls.
Human-readable name displayed in the dashboard and billing UI.
Feature type: 'boolean' for on/off access, 'metered' for usage-tracked features, 'credit_system' for unified credit pools.
boolean, metered, credit_system For metered features: true if usage resets periodically (API calls, credits), false if allocated persistently (seats, storage).
Whether the feature is archived and hidden from the dashboard.
Event names that trigger this feature's balance. Allows multiple features to respond to a single event.
For credit_system features: maps metered features to their credit costs.
Display names for the feature in billing UI and customer-facing components.