Metered intelligence.
Ledger-backed.
Monte Carlo rehearsal and the AI assistant are billed by usage — every simulation path and every token is recorded on Consequence's decentralized ledger and settled against Polygon (POL) for transparent, attributable metering. Choose the tier that matches your room.
Hobby
For solo producers exploring Conductor — enough Monte Carlo rehearsal and AI assistant capacity to finish tracks without enterprise overhead.
- 500 Monte Carlo paths / month across melodic, harmonic, and rhythmic futures
- AI assistant: 25k tokens / month for lyrics, arrangement, and split guidance
- Polygon metering: on-chain usage receipts for assistant and simulation events
- Decentralized ledger mirror — attribution and split state recorded per session
- 1 active work · 2 collaborators · Shop publishing
Professional
PopularFor working creators and small rooms who run Monte Carlo daily and lean on the AI assistant across every session.
- 50,000 Monte Carlo paths / month with priority fleet scheduling
- AI assistant: 500k tokens / month · meter, rhyme, and semantic fit models
- Polygon POL settlement for usage — every inference leg hashed to the ledger
- Full decentralized audit trail: twins, splits, and payout eligibility
- Unlimited works · 8 collaborators · marketplace analytics
Enterprise
For record labels and publisher groups — fleet-scale simulation, governed AI, and ledger-grade reconciliation across rosters.
- Dedicated Monte Carlo pools — millions of paths with SLA-backed turnaround
- AI assistant: unlimited governed tokens · custom motif and compliance guardrails
- Polygon + Base settlement orchestration with label-wide custody policy
- Enterprise ledger mesh — multi-roster twins, audit exports, and SOC-ready logs
- Unlimited seats · SSO · dedicated success · custom split governance
How metering works
Each simulation path — melodic variation, harmonic branch, or rhythmic what-if — is hashed and written to the ledger before results return to Conductor.
Token usage for lyrics, arrangement, and split guidance is metered per request. POL debits settle on Polygon; attribution stays tied to the active work twin.
Every billable event mirrors to Consequence's decentralized ledger — creators and labels audit usage, splits, and settlement without trusting a single operator view.