# Get a file from the agent's sandbox or another service into storage

> Get a file from the agent's sandbox or another service into storage: 12 companies fully do it, 1 with a limit, 14 carry the tag. Every listing in File storage & sharing with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/file-storage.agent-upload/
- Markdown: https://www.anchorterminal.com/niches/file-storage.agent-upload/index.md (~1,450 tokens)
- Slim: https://www.anchorterminal.com/niches/file-storage.agent-upload/index.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/file-storage.agent-upload/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 12 | 1 | 14 | 17 | 6 |

## What counts as done

The file stored byte-for-byte at the named path without the model emitting its contents as a tool argument, through an upload URL, a local path or a server-side fetch, in no more than three calls.

Measured, for our own tests: a 25 MB binary arrives with a matching checksum.

How agents ask for it: save this deck to Box; upload the PDF I just made to OneDrive; put this attachment in the shared drive; copy the CSV into the bucket

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Amazon S3 (Amazon Web Services, Inc.)**: A presigned PUT, or multipart upload of up to 10,000 parts, takes bytes outside the model, and CopyObject copies server-side.
- **Azure Blob Storage (Microsoft Corporation)**: A SAS-signed Put Blob or Put Block List (block blobs to about 190.7 TiB) takes bytes outside the model, and Copy Blob From URL copies server-side.
- **Backblaze B2 (Backblaze, Inc.)**: Presigned PUT and per-part upload URLs from the MCP or S3 API keep bytes out of the model, with server-side copy. The MCP's inline put is capped near 1 MiB over HTTP (acc-09, open), so the URL path is the one to use.
- **Bunny Storage (BunnyWay d.o.o.)**: PUT raw bytes to the HTTP API from the sandbox with the zone password and a SHA-256 Checksum header, or use S3 multipart up to 10,000 parts; a bad checksum is refused (BadDigest).
- **Cloudflare R2 (Cloudflare, Inc.)**: Presigned PUT URLs and multipart upload (10,000 parts, objects to 4.995 TiB) keep bytes out of the model; CopyObject and UploadPartCopy copy server-side, and CRC64NVME full-object checksums are supported.
- **DigitalOcean Spaces (DigitalOcean, LLC)**: Presigned PUTs and S3 multipart (10,000 parts, 5 TB) keep bytes out of the model. Presigned PUTs through the CDN are capped at 7.91 MiB, so they go to the origin host.
- **Dropbox API + MCP (Dropbox, Inc.)**: save_url fetches a file from a URL server-side (15-minute limit), and upload sessions take 150 MiB per request with sessions lasting 7 days, so a sandbox can stream a local file without the model emitting it.
- **Fastio (VividEngine, LLC (doing business as Fast Technologies))**: Web upload imports from a public HTTPS URL server-side, and chunked upload takes CRC-32C, SHA-256 or MD5 hashes; single calls stop at 4 MB, so larger files go chunked.
- **Google Cloud Storage (Google LLC (Google Cloud EMEA Limited and other regional entities by billing address))**: Signed PUT URLs and resumable uploads keep bytes out of the model. The MCP server's writes are text-only and capped at 8 MiB, so binaries go through REST.
- **Google Drive API + MCP (Google LLC)**: Resumable uploads from the sandbox keep bytes out of the model, and files.copy copies server-side. acc-12, a community server failing on attachment URLs, is closed; the preview MCP's create_file schema isn't published.
- **OneDrive and SharePoint files (Microsoft Graph) (Microsoft Corporation)**: createUploadSession returns an uploadUrl that a sandbox can PUT to in byte ranges under 60 MiB, keeping bytes out of the model. acc-03, acc-10 and acc-11 were failures in a community MCP server, all closed.
- **Tigris (Tigris Data Inc.)**: Presigned PUT URLs from the S3 API or the MCP's sharing tools let a sandbox upload without the model carrying the bytes, through standard AWS SDKs at t3.storage.dev.
- **Wasabi Hot Cloud Storage (Wasabi Technologies LLC)**: Presigned PUT URLs and S3 multipart through standard AWS SDKs keep bytes out of the model, and Wasabi documents MD5 and CRC checksums on upload.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **Box API + MCP (Box, Inc.)**: Chunked upload sessions over REST, and the MCP's get_upload_url keeps bytes out of the model, but that tool is off until an admin enables it and works only in code-executing clients. acc-08 saw binary passed as text corrupted.

- not this job: ONLYOFFICE Apps MCP Server (Ascensio System SIA): upload_file accepts only txt and md, so a binary such as a PDF or deck can't be stored byte-for-byte through the server.

## What stops agents finishing

- the only MCP upload takes base64 or text in the tool argument
- the HTTP transport caps the request body below the documented upload limit
- the sandbox cannot reach or see the URL the tool returns

## Around it

Before: code-sandboxes.run, mailbox-access.get-attachment. After: file-storage.share-temp-link.

## Where this comes from

Weight 17 of 100 in File storage & sharing: 6 of 36 links; MCP server issues on Box, B2 and Microsoft Graph

As data: https://www.anchorterminal.com/api/v1/use-cases/file-storage.agent-upload.json, or the MCP tool get_use_case with id file-storage.agent-upload. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
