Reducing AI API Costs Without Sacrificing Quality

AI API costs can spiral quickly. A few careless patterns in your code, and you're looking at hundreds of dollars in unexpected charges. This guide covers practical strategies to reduce costs without degrading your results.

Understanding AI API Pricing

Most AI APIs charge per token. A token is roughly 4 characters or 0.75 words in English. You pay separately for input tokens (your prompt) and output tokens (the response).

Current approximate pricing for popular models (as of early 2025):

Key insight: Output tokens cost 3-5x more than input tokens. Controlling output length has the biggest impact on costs.

Strategy 1: Use the Right Model for the Task

The most impactful change is matching model capability to task complexity.

Task-to-model mapping

Implementation pattern

function selectModel(taskType: string): string {
  const modelMap: Record<string, string> = {
    classify: "google/gemini-2.5-flash",
    summarize: "google/gemini-2.5-flash",
    generate_code: "openai/gpt-5-mini",
    analyze: "openai/gpt-5-mini",
    research: "openrouter/auto",
  };
  return modelMap[taskType] || "openrouter/auto";
}

Savings: Using Haiku instead of Sonnet for simple tasks saves ~75% on those requests.

Strategy 2: Control Output Length

Output tokens are expensive. Most applications don't need 4000-token responses.

Set appropriate max_tokens

// Bad: Default allows massive responses
const response = await client.responses.create({
  model: "openrouter/auto",
  input: prompt,
});

// Good: Limit based on expected response
const response = await client.responses.create({
  model: "openrouter/auto",
  input: prompt,
  max_output_tokens: 500, // Enough for most tasks
});

Ask for concise responses in your prompt

Add explicit instructions:

Respond concisely in 2-3 sentences.

or

Provide a brief answer (under 100 words).

Savings: Reducing average output from 1000 to 300 tokens saves 70% on output costs.

Strategy 3: Trim Your Prompts

Long system prompts and unnecessary context inflate input costs.

Before: Bloated prompt

const systemPrompt = `
You are a helpful AI assistant. You should always be polite and professional.
Your goal is to help users with their questions. You have access to various
tools and capabilities. Please think carefully before responding. Make sure
your responses are accurate and helpful. If you're not sure about something,
say so. Always prioritize user safety and privacy...
[500 more words of instructions]
`;

After: Focused prompt

const systemPrompt = `
You are a customer support assistant. Be concise and helpful.
If you don't know something, say so.
`;

Only include relevant context

Don't dump entire documents into every request. Extract relevant sections first.

// Bad: Send entire document
const prompt = `Analyze this document: ${entireDocument}`;

// Good: Send relevant excerpt
const relevantSection = extractRelevantSection(entireDocument, query);
const prompt = `Analyze this excerpt: ${relevantSection}`;

Savings: Cutting prompt length from 2000 to 500 tokens saves 75% on input costs.

Strategy 4: Cache Repeated Prompts

Prompt caching can reduce costs dramatically for repeated prompts.

When you send the same system prompt or context repeatedly, some providers cache it and charge much less for subsequent uses.

const response = await client.responses.create({
  model: "openrouter/auto",
  input: `${longSystemPrompt}\n\n${userQuery}`,
});

Savings: For applications with consistent system prompts, this can reduce input costs by 80-90%.

Strategy 5: Batch Non-Urgent Requests

Many providers offer batch APIs or async discounts for requests that do not need immediate responses.

Good for:

• Nightly report generation
• Bulk content processing
• Background analysis tasks

// Submit batch job
const batch = await client.batches.create({
  requests: items.map((item) => ({
    custom_id: item.id,
    params: {
      model: "openrouter/auto",
      input: item.prompt,
    },
  })),
});

// Results available within 24 hours

Savings: 50% on all batched requests.

Strategy 6: Implement Smart Caching

Don't call the API for queries you've already answered.

import { createHash } from "crypto";

const cache = new Map<string, string>();

async function cachedQuery(prompt: string): Promise<string> {
  const hash = createHash("md5").update(prompt).digest("hex");

  if (cache.has(hash)) {
    return cache.get(hash)!;
  }

  const response = await callAPI(prompt);
  cache.set(hash, response);
  return response;
}

For production, use Redis or a similar persistent cache with TTL.

Savings: Varies by use case, but common queries hitting cache can save 90%+.

Strategy 7: Use Streaming Wisely

Streaming doesn't change token costs, but it can help you:

1. Stop early: If the response is going off-track, cancel the stream
2. Reduce perceived latency: Users see results faster, reducing retry attempts

const stream = await client.responses.stream({
  model: "openrouter/auto",
  input: prompt,
  stream: true,
});

let response = "";
for await (const chunk of stream) {
  response += chunk.delta?.text || "";

  // Cancel if response looks wrong
  if (response.includes("I cannot") && response.length > 100) {
    stream.controller.abort();
    break;
  }
}

Real-World Example: Email Triage

Here's how these strategies combine for an email triage application:

Monitoring and Alerts

Set up tracking to catch cost spikes early:

1. Log every request with model, token counts, and cost
2. Set daily/weekly budgets in your provider dashboard
3. Alert on anomalies (2x normal daily spend triggers investigation)

function logAPICall(model: string, inputTokens: number, outputTokens: number) {
  const cost = calculateCost(model, inputTokens, outputTokens);
  console.log(
    JSON.stringify({
      timestamp: new Date().toISOString(),
      model,
      inputTokens,
      outputTokens,
      cost,
    })
  );
}

Summary

Start with model selection and output limits. These require minimal code changes and have the biggest impact. Add caching as your usage grows.