Anthropic’s new Files API vs. pasting: It will save you time, but it won’t save you money.

6.7 relevance

Practical API comparison for AI agent file handling, directly actionable for developers using Anthropic.

General thenewstack.io

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For a solutions architect optimizing LLM costs in multi-turn agent workflows or support bots, this reveals that Anthropic's Files API doesn't save tokens over pasting, but prompt caching does—if you can batch requests within the cache TTL.

Key Takeaways

Use prompt caching instead of the Files API for repeated document references in short-burst workloads, but design your agent's request cadence to stay within the five-minute cache window.

Anthropic’s new Files API vs. pasting: It will save you time, but it won’t save you money.

Summary

Anthropic's Files API, now out of beta, lets developers upload a document once and reference it by ID, avoiding pasting content into every prompt. Testing against a 1,200-word API reference with five nuanced questions showed all three approaches (pasting, Files API, and prompt caching) produced identical correct answers, but the Files API actually cost 125 more input tokens across five requests due to overhead. Prompt caching, which bills the document once as a cache write at a 25% premium and subsequent reads at one-tenth the rate, was the only method that reduced token costs, though it requires requests within a five-minute cache window.

Author

Jessica Wachtel