Deliver a Python report to your SEAL inbox

A Python job has produced a PDF, CSV or archive. The next step is making that file available to the person who needs it. A path on the machine running the job is useful to the program; the recipient still needs a way to collect the result.

This guide is from the SEAL team. It uses the public sealnet Python API to deliver a finished report to a user’s paired inbox. The example is a starting point for your own environment, with a non-confidential report you already have permission to send.

1. Prepare the report and Python environment

Use Python 3.9 or later. Install or update the sealnet package in your project environment with pip install -U sealnet. Keep the report in the script’s working directory, or replace report.pdf below with its approved path. File generation remains your existing code.

The package supports synchronous calls and an asyncio interface. The example below uses synchronous calls so the human pairing step is easy to follow. Its API names follow the public PyPI package documentation, version 2.0.0, checked on 20 October 2026.

2. Pair the destination, then deliver

Run the script in your own environment. Open the pairing page it displays, compare the words shown by the script and the page, and connect the intended inbox. After pairing completes, the send call puts the report in that inbox.

import sealnet

keys = sealnet.keygen()
ask = sealnet.pair(
    secret_key=keys.secret_key,
    name="Report delivery",
)
print("Open this pairing page:", ask.url)
print("Compare these words:", ask.words)

owner = sealnet.wait_pair(
    ask.id, secret_key=keys.secret_key
)
sealnet.send(
    "report.pdf",
    owner=owner.address,
    secret_key=keys.secret_key,
)
print("Report sent to the paired inbox")

This example creates a fresh identity each time it runs. A recurring workflow needs deliberate key management and reuse of the intended identity. Keep the seed private; do not paste it into chat, put it in source control or publish it with a tutorial.

3. Confirm the human result

Open the inbox on the recipient’s device and collect the report. Confirm that the expected file opens and that the recipient has the right version. An upload receipt or a successful program exit alone does not tell you that a person has collected a usable result.

The example deliberately does not print a recipient link or management token. Review the agent host’s permissions and logs when adapting it: a program or agent with access to local files may still be able to read their contents. Use the documented expiry and access settings for your delivery window, and keep your own archive.

SEAL has free and paid transfer tiers; check current allowances for the file you plan to send. Revoking a transfer stops future access through that transfer, but cannot erase a copy already downloaded.

Python package and API examples

Read SEAL documentation