What problem does it solve?
Translating a pricing idea into Autumn's data model of features, plans, and plan items is error-prone: choosing between prepaid and usage-based billing, handling plan versioning, variant propagation, and customer migrations all require careful decisions. This Skill guides an AI agent through modeling and safely updating an Autumn pricing catalog via autumn.config.ts, the atmn CLI, or MCP/API tools.
Core Features & Use Cases
- Pricing Model Design: Translate pricing intent into features, plans, and plan items covering subscriptions, credits, seats, overage, prepaid, volume tiers, free plans, one-off purchases, and trials.
- Safe Catalog Updates: Follow a preview-decision-apply loop using catalog.preview_update or atmn headless push, surfacing versioning choices, variant propagation, and migration drafts before any write.
- atmn CLI Workflows: Manage code-defined catalogs in autumn.config.ts with headless push/pull flows and explicit decision flags for plan intents and migrations.
- Use Case: A startup wants to charge $20/month plus $1 per 1,000 API calls over a 10,000 included allowance. The Skill models a metered consumable feature with a usage-based plan item, previews the catalog change, and applies it after confirmation.
Quick Start
Ask the agent to design an Autumn pricing plan with a monthly base fee and usage-based overage for your API product.