AICost Industry Solutions

Retail and e-commerce

3 AI automations this industry runs today, each with the process, the AICost engine chain that prices and governs it, and the evidence behind it.

Cost engine Governance engine Each step priced and controlled. Click any engine to open its calculator or playground.

Product content and catalog enrichment

Owner: Merchandising / catalog operations, e-commerce content, SEO

Scale: Walmart used LLMs to create or improve more than 850 million catalog data points, about 100x the headcount otherwise (Retail Dive)

How the work runs

  1. Ingest supplier product data and images
  2. Normalize attributes and fix missing or incorrect data
  3. Generate titles, descriptions and SEO copy
  4. Classify into the taxonomy and tag for search
  5. Human spot-check; publish to site and marketplaces

AICost engine chain

4 cost engines 2 governance engines

Each step priced and controlled. Click any engine to open its calculator or playground.

Where cost leaks

  • Regenerating content for the whole catalog on every model or prompt change
  • Using real-time API instead of batch pricing
  • Image (vision) calls for every SKU variant

Where risk sits

  • False product claims (health, safety, materials)
  • IP or brand copy issues
  • Low-quality content harming search ranking

Rules that apply

  • FTC Act Section 5 (deceptive claims) and the FTC rule on fake and AI-generated reviews (2024)
  • EU Digital Services Act and consumer law
  • product safety and labeling claims

Runs on

Salesforce Commerce CloudShopify (Magic)Akeneo / Salsify / Syndigo PIMSAP CommerceAdobe Commerce

Conversational shopping assistant (agentic commerce)

Owner: Digital / e-commerce product, search and personalization team

Scale: Amazon does not publish Rufus usage on its official page

How the work runs

  1. Shopper asks a need-based question in the search bar or chat
  2. Retrieve over catalog, reviews and Q&A
  3. Compare and recommend products
  4. Answer product-detail questions
  5. Add to cart or check out (including via third-party AI agents)

AICost engine chain

5 cost engines 2 governance engines

Each step priced and controlled. Click any engine to open its calculator or playground.

Where cost leaks

  • Inference cost per shopping session at peak traffic (holiday)
  • Long review corpora in context
  • Bot or scraper traffic consuming LLM calls

Where risk sits

  • Wrong product facts or prices (binding-statement liability, cf. Moffatt v. Air Canada)
  • Undisclosed sponsored ranking
  • Prompt injection through reviews or listings

Rules that apply

  • FTC Act Section 5
  • PCI DSS for any in-chat payment
  • GDPR / CCPA (CPRA ADMT rules)
  • EU AI Act Art. 50 chatbot transparency

Runs on

Amazon Rufus (now Alexa for Shopping)Walmart SparkyShopifySalesforce Agentforce CommerceGoogleOpenAI checkout integrations

Customer service agent (WISMO, returns, refunds)

Owner: Customer care / contact center operations

Scale: Klarna's AI-first support later rebalanced toward a human hybrid (PromptLayer analysis); no verified volume

How the work runs

  1. Customer contacts by chat, email or voice
  2. Identify intent (where is my order, return, refund, product issue)
  3. Agent calls OMS, shipping and payments tools to resolve
  4. Apply return or refund policy within limits
  5. Escalate to a human with a summary

AICost engine chain

3 cost engines 3 governance engines

Each step priced and controlled. Click any engine to open its calculator or playground.

Where cost leaks

  • Agent loops and retries on tool failures
  • Per-resolution vendor pricing on contacts that deflection would have handled
  • Voice minutes at peak season

Where risk sits

  • Unauthorized refunds or policy exceptions
  • Account takeover through social engineering of the bot
  • CSAT damage from over-automation

Rules that apply

  • PCI DSS
  • GDPR / CCPA
  • consumer protection refund rules
  • EU AI Act Art. 50 transparency

Runs on

Salesforce Service Cloud / AgentforceZendeskGorgiasShopifySierraDecagon

Reference chains are a starting point. Your volumes, models and vendors change the numbers; the engines recompute them from live prices.

Your process is not on the list, or runs differently? These chains are a starting point. We assemble the right engines for your workflow, your models and your vendors, and you run it over MCP or in the calculators.

📖 Data sources & methodology 172 text models · 9 embeddings · 44 vision · 62 audio · 8 vector DBs across 10 vendor pages · last verified 2026-10-15

Methodology

  • All prices are USD per 1 million tokens, current as of 2026-10-15.
  • Vendor-published values have no mark. Inferred/extrapolated values are marked with * and listed below.
  • Batch API discounts are 50% off standard rates across providers that offer Batch mode.
  • Prompt caching discounts vary by provider (typically 80-90% off cached input tokens).
  • Regional data-residency surcharges (Anthropic 1.1x, OpenAI 1.1x, Google regional tiers) are NOT included in base rates.
  • Long-context pricing tiers apply when input exceeds model threshold.
  • Embedding prices are input-only (no output tokens generated).

Primary sources

Last-verified date is the most recent successful daily snapshot (aicost_pricing_snapshots) or, when no snapshot exists yet, the latest successful crawler run (aicost_crawler_runs). 10 of 10 vendors are currently verified. Aggregator services (TokenCost, AI Pricing Guru, etc.) are not listed.

Anthropic
2026-10-14
https://www.anthropic.com/pricing
Daily snapshot since Sep 2023 · 700 days captured
Anthropic Docs
2026-10-14
https://platform.claude.com/docs/en/about-claude/pricing
Daily snapshot since Sep 2023 · 700 days captured
OpenAI
2026-10-14
https://openai.com/api/pricing/
Daily snapshot since Sep 2023 · 701 days captured
Google AI
2026-10-14
https://ai.google.dev/gemini-api/docs/pricing
Daily snapshot since Dec 2023 · 676 days captured
Google Vertex
2026-10-14
https://cloud.google.com/vertex-ai/generative-ai/pricing
Daily snapshot since Dec 2023 · 676 days captured
DeepSeek
2026-10-14
https://api-docs.deepseek.com/quick_start/pricing
Daily snapshot since May 2024 · 615 days captured
xAI
2026-10-14
https://x.ai/api
Daily snapshot since Nov 2024 · 533 days captured
Mistral
2026-10-14
https://mistral.ai/pricing
Daily snapshot since Dec 2023 · 674 days captured
Cohere
2026-10-14
https://cohere.com/pricing
Daily snapshot since Sep 2023 · 700 days captured

Inferred values (marked with * in calculator tables)

Derived from industry conventions, not directly published by the vendor. Typical conventions: cached input = 10% of base (90% off), Batch API = 50% of base (50% off).

Vendor / Model Field Why it’s inferred
Anthropic — Claude Sonnet 4.6 cachedInput Derived at 10% of input rate — Anthropic publishes 90% cache-hit discount on this tier.
Anthropic — Claude Sonnet 4.5 cachedInput Derived at 10% of input rate; same 90% cache-hit convention as Sonnet 4.6.
Anthropic — Claude Sonnet 4.5 batchInput Derived at 50% of standard input — Anthropic documents uniform 50% Batch discount.
Anthropic — Claude Sonnet 4.5 batchOutput Derived at 50% of standard output — Anthropic documents uniform 50% Batch discount.
Anthropic — Claude Haiku 4.5 cachedInput Derived at 10% of input rate — Anthropic 90% cache-hit discount convention.
OpenAI — GPT-5.4 Mini cachedInput Derived at 10% of input — OpenAI documents automatic 90% discount on cache hits across GPT-5.x tier.
OpenAI — GPT-5.4 Nano cachedInput Derived at 10% of input — OpenAI 90% cache-hit convention.
OpenAI — GPT-5.4 Nano batchInput Derived at 50% of input — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Nano batchOutput Derived at 50% of output — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Pro cachedInput Derived at 10% of input — OpenAI 90% cache-hit convention.
OpenAI — GPT-5.4 Pro batchInput Derived at 50% of input — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.4 Pro batchOutput Derived at 50% of output — OpenAI Batch API uniform 50% discount.
OpenAI — GPT-5.2 cachedInput Derived at 10% of input; no residency uplift.
OpenAI — GPT-5.2 batchInput Derived at 50% of input.
OpenAI — GPT-5.2 batchOutput Derived at 50% of output.
OpenAI — GPT-5 cachedInput Derived at 10% of input.
OpenAI — GPT-5 batchInput Derived at 50% of input.
OpenAI — GPT-5 batchOutput Derived at 50% of output.
OpenAI — GPT-5.5 Pro cachedInput Derived at 10% of input — OpenAI does not publish a cached rate for *-pro models; using the family convention.
OpenAI — GPT-5.5 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5.5 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5.2 Pro cachedInput Derived at 10% of input — pro-tier convention.
OpenAI — GPT-5.2 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5.2 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5.1 batchInput Derived at 50% of input.
OpenAI — GPT-5.1 batchOutput Derived at 50% of output.
OpenAI — GPT-5 Pro batchInput Derived at 50% of input.
OpenAI — GPT-5 Pro batchOutput Derived at 50% of output.
OpenAI — GPT-5 Nano cachedInput Derived at 10% of input.
OpenAI — GPT-5 Nano batchInput Derived at 50% of input.
OpenAI — GPT-5 Nano batchOutput Derived at 50% of output.
Google — Gemini 3 Flash cachedInput Derived at 10% of input — Google caching discount convention ~90%.
Google — Gemini 3.1 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 3.1 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 3.1 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
Google — Gemini 2.5 Pro cachedInput Derived at 10% of input.
Google — Gemini 2.5 Flash cachedInput Derived at 10% of input.
Google — Gemini 2.5 Flash-Lite cachedInput Derived at 10% of input — Google caching convention.
Google — Gemini 2.5 Flash-Lite batchInput Derived at 50% of input — Google Batch API uniform 50% discount.
Google — Gemini 2.5 Flash-Lite batchOutput Derived at 50% of output — Google Batch API uniform 50% discount.
xAI — Grok 4 (legacy) cachedInput Extrapolated at 25% of base.

Pricing is cross-verified against the LiteLLM community registry when available. Daily snapshots are kept in aicost_pricing_snapshots; every change is logged to aicost_price_changelog with old & new values for full audit trail. Read the full methodology →