📁
Files API — Persistent Content Storage
Upload files once, reference across multiple conversations
P1Infrastructure
Summary
The Files API enables uploading documents, images, and data files to Anthropic's servers for persistent storage. Files can be referenced across multiple API calls and sessions without re-uploading. Supports PDFs, images, code files, and structured data. Eliminates the need to embed large documents in every request.
Technical Details
File lifecycle:
• Upload: POST /v1/files with multipart form data
• Reference: include file_id in message content
• Reuse: same file_id works across sessions and agents
• Delete: explicit deletion when no longer needed
Pipeline use cases:
- m590: upload research papers for knowledge compilation
- m553: store generated media assets for cross-session access
- m8100: cache search results as files for m590 ingestion
- m595: store game scenario files for testing
Token optimization: a 100-page PDF uploaded as a file costs tokens once. Referenced in 50 sessions, it saves 49× the token cost vs. embedding.
Architecture Insight
Files API converts context window from per-request resource to persistent asset. This enables the 'upload once, reference everywhere' pattern that large knowledge pipelines require.
Official / Public Basis
Files API documented at docs.anthropic.com/en/docs/build-with-claude/files. Available for all Claude models.
Governance Concerns
Uploaded files stored on Anthropic servers — evaluate data sensitivity. File retention policies must be defined. Access control needed for shared files.
LightHope Ecosystem Mapping
m590 research paper ingestion, m553 media asset storage, m8100 search result caching, m595 scenario file management