DeliveryFiles is preparing reliable handoffs between your computer, agents, services, and people—without rebuilding upload infrastructure for every destination.
Join early access and help shape reliable delivery for agents, services, and people.
The first preview will be free with bounded limits. Runtime access is not live yet.
The agent-first preview is designed around an immutable transfer and an intended recipient—not a loose public link.
A small local companion will read a file you authorize and upload it without putting raw bytes into model context.
The preview is designed for large transfers that can continue after a dropped connection instead of starting over.
Recipients get short-lived, audience-bound access—not your filesystem path, bucket credentials, or a permanent public link.
Byte length, media type, and content hash identify the immutable file before another service accepts it.
SciContext will be the first dogfood integration. Broader destinations will be selected from actual user demand.
The same transfer lifecycle will later power polished delivery pages for creators and small studios.
A local agent cannot safely give a remote service a filesystem path. A remote service should not need your storage credentials. DeliveryFiles is being designed to bridge that gap with resumable ingest, verified identity, scoped recipient access, acknowledgement, and expiry.
Agents are the first surface because they need very little UI and expose the hard infrastructure early. A focused creator and small-studio experience can then use the same reliable transfer lifecycle for polished client delivery.
DeliveryFiles is the modern way to deliver files to people, applications, and agents. The first planned surface combines a local uploader with a cloud MCP for transfer control.
Not yet. This page is collecting design partners for the agent-first preview; it does not represent a live upload or delivery service.
MCP is used for transfer metadata and control. Raw file bytes use a resumable HTTP path so large transfers do not enter model context or a JSON-RPC payload.
No. Agent delivery comes first because it proves the shared infrastructure with less UI. Professional client-delivery pages remain the next major surface.