● Covered by 1 source · 1 reportLow impact1 neutral
Anthropic's Files API saves time but not money compared to pasting for LLM prompts
Key points
- Anthropic launched its Files API and browser-use toolset.
- The Files API allows single document uploads referenced by ID.
- Testing showed Files API saves time but not tokens or money.
- Pasting content into prompts remains a common alternative.
Anthropic's Files API Release
Anthropic officially moved its Files API and computer-use toolset out of beta on August 19, simultaneously launching a new browser-use toolset. This API enables developers to upload a document once and then reference it using a unique ID in subsequent requests to Anthropic's models. This contrasts with the common practice of pasting the entire document's content into every prompt.
Testing Methodology
To evaluate the new Files API, a test was conducted using a simulated API reference for an invoicing company, Ledgerline, approximately 1,200 words long. This reference covered various API functionalities such as authentication, rate limits, and webhooks. The scenario involved a developer support bot designed to answer specific questions based solely on this reference document.
Test Scenarios and Questions
Five specific developer questions were formulated, each with a precise answer within the Ledgerline API reference. These questions addressed complex scenarios like distinguishing 403 errors, safely retrying payments, verifying webhook signatures, creating bulk invoices, and handling committed API tokens. The test aimed to assess token usage, accuracy, and setup effort across different methods.
Comparison Arms
The five questions were run through claude-sonnet-5 using three distinct approaches. The first arm involved pasting the full reference document into every request. The second arm utilized the new Files API, uploading the reference once and then referencing its file ID in each request. A third arm, prompt caching, was also included based on initial results, where the reference was pasted once into the system prompt with caching enabled.
Initial Setup Challenges
During setup, two issues were encountered: the API rejected a temperature setting of zero, which is deprecated on claude-sonnet-5, and one response led with a thinking block that caused printing code to crash. Both issues were resolved with minor code adjustments. The Files API upload process itself was straightforward, resulting in a single file ID.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
The daily brief
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Today's brief
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's brief
New every morning, and the back catalogue is archived by date.
Reporting from
Anthropic released its Files API and browser-use toolset, allowing developers to upload documents once and reference them by ID in subsequent requests to large language models. A test comparing this method to pasting content directly into each prompt found that while the Files API saves development time, it does not reduce token usage or cost.