Send a file.Or receive one.

A link for the file you send. An address for the files that come back. This handbook is the whole thing.

Send a file The inbox A public link

Start here

Send a fileA link, then a pickup.
The pickup pageWhat they see.
Your accountOne email. One plan.
The inboxOne address. Files arrive here.

Using Pink Jeepney

Notes, mail, passwords, burnThe switches on a send.
PlansWhat each plan holds.
PJ LinksDon’t download it just to send it.
TricycleA room for this afternoon.
Your logo on the pickup pageTheir download, your name.

CLI

Install the CLIsend a file, or pull a public URL.
Send, link, list, burnA file on disk, or a public URL.

API

APIA file you have, or a public URL.
Send with the APIUpload bytes, or pull a URL.
List, status, burnAfter the file is gone.

Agents and IDEs

Agents, IDEs, and the terminalWhere the key goes.
TerminalYour own shell.
CursorThe editor agent.
Claude and Claude CodeChat versus Claude Code.
ChatGPT and CodexChat versus Codex.
OpenCode and other IDEsOpenCode and the rest.

Four ways a file moves

Send. You drop a file. They get a link.
Receive. You have one address, /me/your-name. Trusted people land in the inbox. A first sender waits in the lobby.
Bring. Paste a public Drive or Dropbox link. We fetch it. You send ours, or you put it straight in your inbox.
Agents. A Professional or Business key lets a terminal, Cursor, Claude Code, or Codex do the same send.

What a plan changes

The plan is the size of the file, how many you can send, and how long it stays. Free is enough to try it. Paid plans add a password, a longer stay, and, on Professional and Business, a key for an agent.