API, CLI & MCP

Send files from your code.

A file transfer API for the moment a script, a build or an AI agent needs to hand a big file to a real person: a documented REST API, a command-line client, and a read-only MCP server.

Before

The build finished. Now what?

The export is 8 GB and the client needs it today. So someone babysits a browser tab, drags it into a website and pastes the link into an email — every single time.

With Yungle

One command, and a link comes back.

Send a folder from the terminal, a script or a CI job, and get a transfer link in return — with the same encryption, receipts and recipients as sending from the website.

How it works

Three steps. No manual.

  1. 1

    Create a key

    In your account settings. It works on the free tier for sending transfers.

  2. 2

    Send from anywhere

    Three REST calls and the bytes, or one command with the CLI.

  3. 3

    Hand over the link

    Email it to recipients straight from the call, or pass it on however your pipeline likes.

The details

Everything else worth knowing.

  • REST, documented

    A public OpenAPI 3.1 spec and docs at yungle.co/developers, readable without an account.

  • A real CLI

    Ship a folder from the terminal without keeping a browser tab open.

  • Read-only MCP

    Your AI agent can look things up, but it cannot send, delete or invite anything.

  • Downloads are free

    Uploads include a monthly allowance and are metered after that. Downloads are never metered.

  • Receipts, by polling

    There are no webhooks yet — ask the API whether a transfer has been downloaded.

What the API can’t do (yet)

  • There are no webhooks yet; poll for download receipts instead.
  • The vault and end-to-end encrypted transfers are not reachable through the API, the CLI or the MCP server — their keys never reach us.
  • API uploads include a free monthly allowance and are metered after that; downloads are never metered.

Questions, answered.

Ask us something else
Is the API available on the free tier?

Yes. Free accounts can create and send transfers through the API and the CLI. Collections and contacts over the API come with a plan.

Where is the documentation?

Everything is public at yungle.co/developers, with no account needed — authentication, uploads, transfers, collections, errors and limits, plus the OpenAPI spec.

Can my AI agent send files on my behalf?

Not through the MCP server, which is read-only by design. An agent can send through the API or CLI with a key you give it, which keeps that decision with you.

Next featureTransfersSend up to 10 GB free, with no account and no ads. Uploads survive a dropped connection, and you see who downloaded your files and when.

Send your first file in ten seconds.

10 GB, free, right now — no account, no card, no ads. Pay us only when you want your work to stay put.

  • Cancel anytime
  • iDEAL, card or SEPA
  • Export or delete everything, yourself