Manual guides are useful now
The source guides explain provider routes you can follow independently. You do not need a SEED subscription to request an export and keep a copy. Read the supported account, device, format and scope before beginning; not every route produces a complete or independently readable archive.
Assistance still depends on the provider
Our planned collection experience will help you choose the source and scope, approve access, and see what was received. Some sources may support an official connection; others may require a prepared export or a device handoff. A convenient interface cannot remove a provider’s waiting period or recover material your account cannot access.
An approved connection is not the same as a successful collection. The useful result is a receipt of the saved records, with gaps and failures visible. Preserved files and searchable files can also be different stages of the process.
An agent needs a defined boundary
An assistant should work only with the source, task and destination you approved. Keep original packages unchanged while organizing working copies. A list of filenames or a successful extraction is not proof of complete history.
SEED’s API and MCP material is an integration preview. There is no public SEED MCP endpoint or installation command offered here. A protocol can connect tools, but it does not itself grant permission to your accounts or guarantee source coverage.
Sharing archive contents with an outside assistant is a separate choice from keeping them in a private vault. Begin with the material needed for the task and retain a copy you can open independently.