Your agent wrote the email. Now it can hand over the file.

A1DD gives an AI agent one tool call that turns a local file into a link a person can open. You decide how long it lives and how often it can be downloaded, and you see when it was.

Paste this to your agent to set it up:

Fetch https://a1dd.dev/setup.md and follow the instructions to set me up with A1DD.
Get a key
send_file( path: "/work/acme/Q3-report.pdf", recipient: "dana@acme.example", expires_in_hours: 72, max_downloads: 3)

Q3-report.pdf

48 MB, link valid for 72 hours, 3 downloads

  1. Sent by claude-code
  2. Link placed in the email to Dana
  3. Page opened on an iPhone
  4. Downloaded, 2 left
  5. Link expires and the file is deleted
An example. Your agent reads this trail back with get_transfer.

Set up in three steps

It works with any agent that speaks the Model Context Protocol: Claude Code, Claude Desktop, Cursor, Codex and others.

  1. Get a key

    Enter your email below and confirm the link we send. Set the key as A1DD_API_KEY where your agent runs.

  2. Let your agent install it

    Paste the prompt from the top of this page. Your agent reads a1dd.dev/setup.md, adds the A1DD server, and writes a short usage note into its own instructions file so it knows when to use it.

    Or install it by hand
    claude mcp add a1dd -e A1DD_API_KEY=a1dd_live_... -- npx -y a1dd-mcp
    {
      "mcpServers": {
        "a1dd": {
          "command": "npx",
          "args": ["-y", "a1dd-mcp"],
          "env": { "A1DD_API_KEY": "a1dd_live_..." }
        }
      }
    }
  3. Ask it to send something

    "Email Dana the Q3 report." The agent uploads the file, puts a download card in the email, and can tell you later whether Dana opened it.

You stay in control of what leaves

An agent that can upload files needs limits. These are on from the first send.

Links that end
Every link has an expiry, 7 days unless you say otherwise, and an optional download limit. The file is deleted when the link ends.
Revoke
You or your agent can withdraw a link at once. The page then shows nothing about the file, not even its name.
Receipts
Each view and download is recorded against the transfer, and your agent can read the record back.
Folders you allow
The agent can only send from folders you name. Keys, .env files, dotfiles and credential folders are refused.
A key per agent
Each agent gets its own key, so every link traces back to the agent that made it.
Nothing for the recipient to install
They get a card in the email and a plain page with a download button. No account.

Pricing

The beta is free. Paid plans are not on sale yet, and the prices below may change before they are.

PlanPriceForIncludes
BetaopenFreeTrying it with one agent50 transfers a day, 2 GB in 30 days, files up to 200 MB, links up to 90 days, receipts, revoke, 3 keys
ProplannedUSD 19 a monthOne person, a few agents3 agent keys, larger files, webhooks, signed packages
TeamplannedUSD 79 a monthSmall teams10 agent keys, verified sender domain, recipient rules, approval before a link goes live, audit export

How paying will work

Your agent should not need you to open a billing page. When paid plans open, a request that needs a plan will come back with a payment link the agent can show you, and an account holder can set a monthly budget the agent may spend within on its own.

This is not live. Nothing on this site charges you today.

Get a key

We email you a link. Confirm it and your key is shown once. The beta is free.

We use the address to send your key and service notices about your account.

Questions

Why not attach the file to the email?

Mail providers reject large attachments, and an attachment cannot be withdrawn or tell you it was opened.

Why not a cloud drive link?

Drive links either need the recipient to have an account or stay open to anyone forever. A1DD links end, and each one is tied to the agent that created it.

Does A1DD send the email?

No. Your agent sends it with the email tool it already has. A1DD supplies the link and the card that goes in the message.

Where are files stored?

On Cloudflare R2 until the link expires or is revoked, then they are deleted. Files are not encrypted end to end yet.

Can the recipient check who sent a file?

Not yet. Signed packages, where each agent signs what it sends and the recipient can verify it, are being built.