useautumn/skills
Overview
This skill adds feature gating and usage tracking to your agent using Autumn. It wires backend-enforced checks, records metered usage, and supports credit-style pools so you can control access and billing. The implementation focuses on a simple check → work → track flow to avoid overcounting and ensure security.
How this skill works
The skill performs a server-side check to ask Autumn whether a customer is allowed to perform a feature. If allowed, your code performs the work and then calls Autumn.track to record usage. For credit systems, you always track the metered feature (Autumn will deduct credits automatically). Frontend checks are supported for UX but must be backed by a secure backend enforcement.
When to use it
- Limit API calls, image generations, or other metered features per customer
- Gate premium features behind plan entitlements or boolean flags
- Implement credit pools that cover multiple metered features
- Show real-time usage and remaining balance in the UI
- Prevent unexpected overage by enforcing limits on the backend
Best practices
- Always run the check and tracking on a trusted backend; frontend checks are for UX only
- Follow the check → work → track pattern and only track after successful work
- Track the underlying metered feature, not the credit pool, so Autumn handles deductions
- Use idempotency_key on track calls to avoid double-counting for retries
- Batch operations by increasing the track value for bulk actions
Example use cases
- Protect an API endpoint by checking 'api_calls' before processing and tracking 1 per request
- Gate message-sending UI: perform a check client-side for UX, then enforce on the server
- Charge image generation against a credit system by tracking the image_gen feature
- Display remaining balance and included usage in account settings using the customer object
- Process a bulk import and call track with value equal to the number of items processed
FAQ
No. Frontend checks are only for UX; enforcement must occur on the backend because frontend logic can be bypassed.
When should I use idempotency keys?
Use idempotency_key on track calls for operations that may be retried or triggered multiple times to prevent double-counting.
How do credit systems work with tracking?
You should track the metered feature (e.g., image_gen). Autumn will deduct the correct number of credits from the credit pool automatically.
4 skills
This skill helps you integrate feature gating and usage tracking with Autumn to enforce limits and monitor consumption.
This skill helps you integrate Stripe checkout and manage subscriptions with Autumn, streamlining payments and upgrades for customers.
This skill helps you integrate Autumn billing and entitlements over Stripe, guiding setup, checkout, and usage tracking with best practices.
This skill helps you configure Autumn billing and create customers by guiding integration setup and API usage across frontend and backend.
