Orqestria Download
← Back to AI automation and cost control

Skill · Version 1.0.0

Versioned pricing calculations

Calculates costs against immutable effective-dated rates while keeping internal cost separate from customer charges.

versioned-pricing-cost-calculation

Team members using this skill

See how it helps

When is it useful?

Use when rates change but historical usage must retain its original accounting basis.

What does it help you do?

  • Stores pricing versions and the rate applied to each calculation.
  • Handles dimensions, tiers and exact monetary units explicitly.
  • Keeps repricing simulations separate from approved accounting corrections.

Try asking this

Calculate usage spanning a price change and show a hypothetical new-rate comparison without rewriting historical charges. Split usage at the effective-date boundary and retain each applied rate. Present hypothetical savings separately so historical invoices still reconcile to their original calculations.

Detailed documentation

Read the skill’s original instructions, examples and checks in their authored language.

Details…Show less

Versioned Pricing & Cost Calculation

Provider rates and custom enterprise contracts change over time. Changing a price table today must never retroactively alter closed accounting periods unless an explicit repricing simulation or backfill is requested.

Workflow

  1. Model effective-dated, immutable rate cards:
    • Represent every rate entry with (provider, service, metricUnit, region, tier, effectiveFrom, effectiveTo, rateVersionId):
      • effectiveFrom (inclusive UTC timestamp) and effectiveTo (exclusive UTC timestamp, NULL for active rate).
      • Prevent overlapping intervals for the same (provider, service, metricUnit, region, tier) key via constraints or validation tests.
    • Support workspace-specific rate overrides (negotiated enterprise discounts or BYOK zero-markup passthrough) separate from upstream provider list prices.
  2. Distinguish internal COGS from customer billable rates:
    • Calculate and store internal provider cost (COGS) separately from external billable amount (managed by the billing specialist):
      • providerCostMicros: What the platform pays the upstream cloud/LLM provider.
      • listCostMicros: Standard list-price valuation (useful when running on pre-purchased commitments or credits).
    • Stamp each rated ledger entry with rateVersionId, unitPriceNumeric, and pricedAt so every row records the exact rate formula used.
  3. Support multi-dimensional and tiered pricing:
    • Per-unit linear rates: e.g., $3.00 / 1,000,000 input_tokens.
    • Context-length or processing tiers: e.g., higher per-token rates above 200k context tokens, or priority vs. batch/flex discounts (0.5x).
    • Graduated vs. volume tiers: Implement graduated tiers (first $N$ units at rate A, additional units at rate B) vs. volume tiers (entire volume repriced above threshold).
  4. Controlled repricing and simulation:
    • Match event.occurredAt (never recordedAt or NOW()) against [effectiveFrom, effectiveTo).
    • Provide a non-destructive simulation mode that evaluates historical usage against a candidate rateCardId without overwriting committed ledger entries.

Anti-Patterns to Avoid

  • Hardcoding model prices in code constants: Scattering const MODEL_PRICE = 0.03 makes rate updates require deploys and corrupts history.
  • Joining current price tables without occurredAt bounds: Computing last quarter's cost with today's price hides historical spend.
  • Silent fallback to $0 on unknown SKUs: Flag unknown models as pricingStatus: 'unpriced_sku' and alert rather than recording $0.00.

Included files 1

  • SKILL.md