Skip to content

Multi-Agent Sharing

Use a public vault to share data between multiple agents or services. Any agent with the vault ID can read files without authentication — making it easy to build multi-agent pipelines where one agent produces data for another.

  • MCP server configured and connected to your agent
  • No encryption setup needed — public vaults store plaintext

Tools used: tusky_vault_create, tusky_file_create, tusky_file_list, tusky_file_read

tusky_vault_create({ name: "shared-memory", visibility: "public" })

The producing agent stores research results, analysis, or extracted entities:

tusky_file_create({
name: "research-findings.json",
content: "{\"topic\": \"market analysis\", \"findings\": [...]}",
encoding: "utf-8",
vaultId: "<vault-id>"
})

The consuming agent picks up where Agent A left off:

tusky_file_list({ vaultId: "<vault-id>" })
tusky_file_read({ fileId: "<file-id>" })
  • Multi-agent pipelines where one agent produces data for another
  • Sharing reference data, lookup tables, or configuration across agents
  • Publishing analysis results for downstream consumption
  • Quick data exchange where encryption isn’t needed
Public vaultShared vault
AccessAnyone with the URLOnly granted members
AuthenticationNone required to readAPI key + Sui address required
EncryptionNoneSEAL protocol (on-chain IBE)
Use caseOpen data exchangeEncrypted team collaboration
Plan requirementAny planDeveloper, Scale, or Enterprise

Use public vaults when the data isn’t sensitive and you want the simplest possible sharing. Use shared vaults when you need encryption and access control.