Free cloud tools for AI agents: file transfer, static site hosting, memory & handoff

Two commands, one handoff

Send a file (one request, up to 512 MB)

curl -F "file=@report.zip" https://upload.83blue.com/api/upload

The JSON response contains the share url, the password and a ready-made download command. Optional fields: expires_days (1-180) and a custom password. Files up to 2 TB use the resumable chunked API.

Receive a file

curl -fL -OJ "https://upload.83blue.com/api/download?token=TOKEN&password=PASSWORD"

That is the whole handoff: agent A uploads and shares the url and password, agent B downloads. Downloads support HTTP Range, so interrupted transfers resume. Fetching this page with a curl or wget user agent returns these instructions as plain text.

Or connect over MCP

claude mcp add --transport http transfer https://upload.83blue.com/mcp

The remote MCP server at https://upload.83blue.com/mcp (Streamable HTTP, no authentication) exposes seven tools: share_text, share_file, share_conversation, receive_file, deploy_site, list_sites and delete_site. It works with Claude Code, claude.ai custom connectors, Cursor, VS Code and ChatGPT developer mode. Setup for each client. Speaking A2A instead? The agent card lives at /.well-known/agent-card.json and the endpoint at /a2a.

How do I send a file from one AI agent to another?

Upload it here, then pass two strings to the other agent: the url and the password. The receiving agent downloads with one request, whether it lives in another terminal, another cloud, another chat window or another company. No shared filesystem, no SSH keys, no cloud bucket permissions.

Better still, every upload gets a handoff url. Paste that single url into any chat with any model: fetching it returns a markdown briefing, the file manifest and the exact download commands, so the receiving model immediately knows what it has and what to do. The share_conversation MCP tool packages a whole working context (transcript plus files, with HANDOFF.md at the bundle root) behind one such url:

Pick up where I left off. Fetch this url for the full briefing and files:
https://upload.83blue.com/h/TOKEN/KEY

Building on Google's A2A protocol? Its FileWithUri parts deliberately leave file hosting out of scope. A transfer url here works as the uri your FilePart points at.

Host a static website in one call

Coded a site, landing page, demo, prototype or report and need to show a human or hand it to another agent? Send the files and get back a live public url straight away. No signup, no account, no API key.

curl -X POST https://upload.83blue.com/api/site \
  -H "Content-Type: application/json" \
  -d '{"files":[{"path":"index.html","text":"<h1>Hello</h1>"}]}'

The JSON response contains the live url (https://upload.83blue.com/s/{slug}/, a fresh path per site) and a manage_key. Include an index.html at the root; you can also send CSS, JS, JSON, images, fonts and media. Optional slug (3-40 characters, a-z 0-9 and hyphens) and expires_days (1-30). Over MCP the same server exposes deploy_site, list_sites and delete_site.

Sites are served as pure static files: server-side code is never executed (.php and other scripts are refused). A published page is public by design, so treat it as public, not private. Up to 50 MB and 300 files per site. Sites auto-expire after 30 days; redeploy with the same slug and manage_key to renew or update. Suspicious sites may be flagged for review and taken down.