Exporting Containers

An export is how you take your data with you. Wire builds an archive of everything you and your agents put into a container, in open formats you can read without Wire, and emails you a download link when it’s ready. The link works for 7 days. You can export any container you have access to, including ones in the trash.

What’s in the archive

The archive holds the whole container: your files, every record, every link between records, the knowledge graph Wire built, and the way you set the container up.

Included	Description
Original files	Every file you uploaded, in its original format and bytes
Records	Every record in the container, with the same ids, tags, and fields: what you and your agents wrote (via wire_write, the dashboard, or the REST API), the text Wire read out of your files, and the records analysis created. A long record comes out whole, under its id.
Links	Every link between records: the ones your agents made with wire_write (a visit linked to the place it was at, a note linked to what it’s about) and the ones analysis found. Each link says where it came from.
Knowledge graph	The entity types, attributes, and relationship types Wire found in your records
Settings	Custom tools you defined, which tools are switched on, the container’s analysis settings, and its name, description, and visibility
Manifest	A manifest.json with counts and provenance for each file (uploader, upload time, archive path)

What’s not in the archive

Only what is internal to Wire is left out.

Excluded	Why
Vector embeddings and search indexes	Tied to the model and index that made them, and rebuilt from the text
Activity history and audit records	Kept by Wire for its retention period
Agent installs	Belong to the agent that installed them; reconnect the agent to set them up again

Archive layout

container-export-<jobId>.zip
├── manifest.json     # Counts, container details, and per-file provenance
├── entries.jsonl     # One record per line
├── links.jsonl       # One link per line: { from, to, type, properties, createdAt }
├── graph/
│   ├── entities.jsonl
│   ├── canonical_attributes.jsonl
│   ├── attribute_clusters.jsonl
│   ├── predicate_clusters.jsonl
│   └── typed_edges.jsonl
├── settings.json     # Custom tools, tool switches, analysis settings
└── files/
    └── <fileId>/
        └── <originalFilename>

Every .jsonl file is plain JSON Lines, one object per line. A link’s from and to are record ids from entries.jsonl, so the files together keep how your records connect.

How to export a container

1. Open the container in the Wire dashboard
2. Go to the Settings tab
3. Find the Export this container section
4. Click Export Container and confirm

You’ll see a “Snapshot of this container as of …” panel appear once the archive is ready, with a Download archive button. The same link is emailed to you.

Note

Only one export of a container runs at a time. If you ask for another while one is being built, you get that one back, and the email comes when it is ready.

Limits

Wire builds at most one new archive of a container a day, and at most five a month.

• One a day. If the container’s last export started less than 24 hours ago, asking again gives you that export instead of a new one. If it is still being built, you get the one in progress. If it is done, you get the same archive and download link. After 24 hours, asking again builds a fresh archive.
• Five a month. Each container can have five new archives per calendar month, counted in UTC. Exports that failed don’t count. Once a container has had five, Wire tells you the date you can export it again, which is the first day of next month.

These limits are per container, not per organization, and they apply whoever asks: you, a teammate, or an agent through the agent API. The dashboard’s Last export panel shows whichever archive is current.

Snapshot semantics

The archive captures the container’s most recently saved state. For a container that isn’t being used, that is everything. For one that agents are writing to right now, the last few minutes of writes may not be in it yet; request a new export once a day has passed to pick them up.

Soft-deleted containers

You can still export a container that’s in the trash, anytime within the 14-day recovery window. This is useful when you’ve moved a container to trash and decide you want a permanent local copy of its contents before it’s permanently deleted.

Permissions

Anyone with at least viewer access to a container can export it. The export covers the same data that viewer-level access already lets that person read in the dashboard or via MCP, so it doesn’t expand who can see what.

Download links

The signed download link works for 7 days from when the export completes. If the link expires, you can request a new export from the same Settings page. Wire holds onto the archive in storage during those 7 days, then cleans it up automatically.

Your export is stored in your container’s region, alongside the container’s own data. If you permanently delete the container, its exports are deleted with it.