pricing

Update AI model pricing data and aliases in Splitrail.

216|23|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/Piebald-AI/splitrail --skill pricing-piebald-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pricing
Source: https://github.com/Piebald-AI/splitrail/tree/main/.claude/skills/pricing
Command: npx skills add https://github.com/Piebald-AI/splitrail --skill pricing-piebald-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Update and maintain accurate AI model pricing data in Splitrail.

Core Features & Use Cases

  • Update flat-rate and tiered pricing structures for AI models.
  • Document model aliases and ensure correct alias mappings.
  • Validate pricing data against source references and use cost calculation utilities when estimates are needed.

Quick Start

Update the pricing data for a new AI model directly in the repository.

Frequently Asked Questions about pricing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update AI model pricing data in Splitrail?

Update AI model pricing data in Splitrail by modifying the MODEL_INDEX with pricing, caching, and is_estimated fields. This ensures accurate cost tracking when adding new models or adjusting existing prices.

How do I manage model aliases for AI cost calculations?

Manage model aliases by updating the MODEL_ALIASES mapping in the repository. This ensures correct alias resolution during cross-model cost comparisons and when utilizing models::calculate_total_cost() for estimates.

Can I validate AI model pricing against source references?

Yes, you can validate AI model pricing data against source references when updating the repository. This validation ensures flat-rate and tiered pricing structures remain accurate before utilizing cost calculation utilities.

What's the best way to handle tiered pricing structures for AI models?

Handle tiered pricing structures by updating the MODEL_INDEX with appropriate pricing and caching data. This approach supports accurate cost estimates when using models::calculate_total_cost() for cross-model comparisons.

When do I need to use models::calculate_total_cost() for pricing estimates?

Use models::calculate_total_cost() when you need cost estimates for AI models, particularly during cross-model cost comparisons. This function relies on accurate pricing data maintained in the MODEL_INDEX.