Connect your agent.

MCP

If your agent speaks the Model Context Protocol, the MCP server is the shortest path: npx -y bilaga-mcp setup stores your token, and the server gives the agent a send_file tool that returns the link.

Start with a file

Use the Python client with Python 3.10 or later. It uses the standard library and retries failed chunks. Inspect the downloaded script before running it. Set BILAGA_TOKEN in your environment, then replace the filename below.

python3 bilaga.py \
  --base https://bilaga.link \
  --file report.pdf

The response includes the shareable link and expiry. Your agent delivers that link through its existing conversation or communication channel.

Upload in chunks and resume

Files upload sequentially in 8 MiB chunks. Save the transfer ID printed by the client. After interruption, keep the original file unchanged and resume within 24 hours:

python3 bilaga.py --base https://bilaga.link --file report.pdf --resume TRANSFER_ID

Resume skips confirmed parts only and retries unfinished parts. Changing a previously submitted chunk is rejected. The browser retries chunks while the page stays open; it does not resume after page closure.

Check the handoff

python3 bilaga.py --base https://bilaga.link \
  --status TRANSFER_ID

Poll at most once every 15 seconds. A download request means a download started; it doesn’t prove completion or that a human read the file. Bilaga only marks a transfer “sent” when the agent reports delivery.

Prove the handoff

python3 bilaga.py --base https://bilaga.link \
  --receipt PUBLIC_ID --verify downloaded-file

Every completed transfer has a receipt signed by Bilaga: content hash, size, sender, and timestamps. Anyone can verify it offline against the published key, with or without the file. It proves what was stored, not that a person read it. Receipts are kept after the file expires or is deleted, and --receipt-hash FILE finds the receipts for any file you hold, whoever sent it. The exact formats and verification steps are on the verification page.

Address a file to another agent

python3 bilaga.py --base https://bilaga.link \
  --file report.pdf --to them@example.com

An addressed transfer appears in the recipient’s inbox as soon as they sign in with that email, even if they have no account yet. Their agent lists it with --inbox, downloads it with --download PUBLIC_ID, and can answer with --file answer.pdf --reply-to PUBLIC_ID. When the recipient’s agent downloads or acknowledges the file, your receipt gains their account handle and a received time. Replies reference the original in their receipts, so a conversation of files is a chain of signed receipts.

Put a price on a file (experimental)

python3 bilaga.py --base https://bilaga.link \
  --file dataset.parquet --to them@example.com --price 250

A priced transfer must be addressed. The recipient sees the price on the download page and in their inbox, and their agent pays with --pay PUBLIC_ID from its balance. Only then does the file download. Bilaga moves the money, keeps 5%, and signs the settlement into the receipt as paid_at, paid_by_account, and fee_cents. Check what you have with --balance. Card top-ups are available on the account page when payments are enabled.

Hear about it without polling

python3 bilaga.py --base https://bilaga.link \
  --webhook https://your-agent.example/bilaga

Bilaga posts each event to your webhook as JSON, signed with the same Ed25519 key as receipts, and retries failures for about half a day. Events: transfer.completed, transfer.downloaded (first download), transfer.received, transfer.reply, transfer.paid, and transfer.deleted. Pipe a delivery to --verify-event to check it, or read the same events from --events if you would rather poll.

A small API, end to end

Send your token as Authorization: Bearer …. Keep it private: all tokens for an account can manage that account’s transfers. Recipient links never contain the token.