← All Business solutions
AICost Business Solutions

IT service desk and employee help

3 AI automations this team 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.
Employee self-service IT agent (password resets, access, software)Ticket triage, routing and summarization for IT agentsResolution notes and knowledge article drafting

Employee self-service IT agent (password resets, access, software)

Owner: IT service desk manager / employee experience

See a chain run live Build this chain for our stack
Scale: WWT: 12,000 employees, 15-20 desk agents, 30% fewer service desk calls

How the work runs

  1. Employee asks in Teams, Slack or the portal
  2. Agent understands the request and checks policy
  3. Agent resets the password, unlocks the account, grants access or installs software
  4. Approvals routed to the manager when needed
  5. Hard cases become a ticket with a summary
  6. Ticket auto-closed and logged

AICost engine chain

4 cost engines 4 governance engines

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

Where cost leaks

  • Every chat message routed through a large model, even simple ones
  • Per-employee platform licences for staff who rarely use it
  • Repeat conversations when actions fail and users ask again

Where risk sits

  • Access granted without the right approval (unauthorized actions)
  • Social-engineering of password resets
  • Wrong instructions that break devices or data

Runs on

  • ServiceNow
  • Moveworks
  • Jira Service Management
  • Microsoft Entra ID / Active Directory
  • Okta
  • Microsoft Teams
  • Slack

Evidence

moveworks.com ↗servicenow.com ↗

Ticket triage, routing and summarization for IT agents

Owner: Service desk operations / ITSM process owner

See a chain run live Build this chain for our stack

How the work runs

  1. Ticket comes in by email, portal or chat
  2. AI classifies category, priority and assignment group
  3. AI links similar tickets and known issues
  4. AI summarizes the history for the assigned agent
  5. Agent works the ticket with suggested fixes

AICost engine chain

3 cost engines 2 governance engines

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

Where cost leaks

  • Summarizing long ticket threads repeatedly on every update
  • Large models used where a small classifier would do
  • Per-agent AI add-on licences

Where risk sits

  • Wrong priority delaying a major incident
  • Misrouted tickets exposing HR or security matters to the wrong team
  • PII in tickets sent to outside models

Runs on

  • ServiceNow
  • Jira Service Management
  • Freshservice
  • Zendesk
  • BMC Helix

Evidence

usefini.com ↗menlovc.com ↗

Resolution notes and knowledge article drafting

Owner: Knowledge manager / service desk leads

See a chain run live Build this chain for our stack
Scale: ServiceNow internal: about 80% time saved per resolution note

How the work runs

  1. Agent resolves a ticket
  2. AI writes the resolution notes
  3. AI spots repeat issues with no article
  4. AI drafts a knowledge article from resolved tickets
  5. Knowledge owner reviews and publishes
  6. Article used by the self-service agent

AICost engine chain

3 cost engines 2 governance engines

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

Where cost leaks

  • Regenerating articles that already exist
  • Processing all closed tickets instead of a sample
  • Review time for low-quality drafts

Where risk sits

  • Wrong fixes published and then repeated by the self-service agent
  • Customer or employee data left in published articles
  • Out-of-date articles never retired

Runs on

  • ServiceNow Now Assist
  • Jira Service Management / Confluence
  • SharePoint

Evidence

servicenow.com ↗

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.

Industry solutions → Build my chain
📖 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
Voyage AI
2026-10-15
https://docs.voyageai.com/docs/pricing

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 →