HYBRID DEVNET · PUBLIC EVIDENCE LIVEVerifiable infrastructure for value, markets, identity, and operational dataInspect the network
HYBRID-CHAIN
Agentic Memory Exchange

Give agents useful context.
Keep private knowledge private.

Give agents and partners the context they need without handing over your private knowledge base. Prepare reviewed collections from private memory, choose who can access them, and turn unanswered questions into a controlled review workflow. Agentic Memory Exchange connects protected sources to permissioned business collaboration.

See how it works ↓Discuss your use case

Scoped access · Check the exact operation and deployment.

Reviewed contextWhat may this recipient learn?
  1. Private sources
  2. Content & access review
  3. Permitted context
Illustrative workflow · availability and access controls apply
A familiar challenge

A partner’s agent needs an answer. Your team has useful internal knowledge, but forwarding the whole conversation would expose more than that partner should see.

A more useful way forward

Prepare a reviewed collection, set its audience, and handle clarifications through an explicit review loop. Context access never becomes spending or signing authority.

See a practical example ↓
Why it matters

Less repeated briefing. More deliberate sharing.

For business operators, knowledge owners, and agent-platform developers.

Keep the source boundary

Your internal memory and the context you share serve different purposes. Give recipients a reviewed view instead of forwarding a prompt history or exposing an entire repository.

Make handoffs repeatable

Build a collection that an authorized person or agent can consult again. Keep the audience, publication state, and agent permissions explicit as the relationship changes.

Close the knowledge gap

When a recipient needs clarification, turn the question into assigned review work. An approved answer can inform a later collection revision—not silently rewrite private memory.

Core capabilities

The capabilities behind the outcome.

Match these capabilities to your workflow. Enabled operations and access are confirmed during integration planning.

Private memory & provenance

Organize encrypted, versioned memory records in the Data Vault workspace. Keep source material, access grants, and lifecycle evidence distinct from any recipient-facing content.

Reviewed knowledge collections

Select source references, author the recipient-safe version, preview it, and explicitly approve publication. Selecting a private source does not automatically copy its title, summary, or payload into a shared collection.

Scoped agent & partner access

Choose the collection audience and permitted capabilities. Connect authorized workloads through the documented signed-request protocol. Directional topic grants do not give the other party reciprocal or unrestricted access.

Questions, revisions & activity

Handle collection questions in an inbox, draft replies privately, and approve the answer before sharing it. Reuse a useful answer through a new content review, with activity and revision history available for follow-up.

Inspect public records Review documented operations

Public records illustrate inspectable data; they are not customer results or confirmation of production activation.

Connected products. Separate authority.

Protect the source.
Share the context.
Check the proposed action.

An integration pattern for an agent-assisted workflow—not an automatic connection, a live transaction, or a shared permission grant.

01 · Source layer

Data Vault

Retain private records and memory with their own access and lifecycle controls. Source content stays protected unless your team explicitly prepares a permitted version to share.

Explore Data Vault
02 · Knowledge layer

Agentic Memory Exchange

Review the content, select recipients, and connect authorized agents. Receive questions and approve answers through the collection workflow.

Review exchange operations
03 · Spending-policy layer

AI Wallet Control

If an agent proposes spending, apply the separately authenticated wallet policy and budget evaluation. An allowed evaluation does not approve, reserve, sign, or broadcast payment.

Explore AI Wallet Control

Knowing something, sharing it, and having authority to act on it are different permissions. No authority carries across these boundaries automatically.

How Agentic Memory Exchange works

From private source to a useful, permitted answer.

  1. 01
    Prepare the knowledge

    Choose private memory sources, create a collection, and author a recipient-safe version. Preview and approve the content boundary before publishing.

  2. 02
    Grant the right access

    Set the audience and capabilities independently from publication. For machine access, use an authorized workload and the documented signing protocol; do not paste signing keys into the collection interface.

  3. 03
    Review and improve

    Follow questions and activity, draft replies privately, and approve what returns to the recipient. Route repeated gaps through a new content review before reusing the answer.

A practical example · illustrative

A supplier’s agent asks about delivery requirements.

Your operations team holds private notes and internal procedures. The supplier needs the approved delivery requirements—not the internal discussion behind them.

Prepare
Publish a reviewed requirements collection without copying private notes or unrelated customer information.
Limit
Grant the intended workspace or workload access to the relevant context. A connection does not expose every collection.
Clarify
Review a question about an exception, approve the reply, and decide whether it belongs in a future collection revision.
What the team takes away

A reusable, controlled context handoff. It does not accept an order, bind a contract, or authorize a payment.

Scoped access

Plan your first deployment.

Use an authenticated workspace with the required collection and agent permissions. The account surface is Business Network; private source memory is managed within Data Vault. Confirm audience, signing, topic, residency, and deployment requirements for your workflow. Knowledge access does not enable negotiation, contracting, wallet signing, or settlement.

Before your first integration

  • Choose one collection and a small set of private source records; author and review exactly what may be shared.
  • Identify the recipient workspace or agent, required topic permissions, and an owner for access changes and unanswered questions.
  • Test a permitted query, an out-of-scope query, a reviewed revision, and withdrawal of access without assuming received copies can be recalled.
Plan the integration Check the API contract
Open the account workspace
Questions before you build

Agentic Memory Exchange, explained.

Is this a public marketplace for private memory?

No. Agentic Memory Exchange is permissioned knowledge sharing, not the Digital Asset Marketplace. Private memory does not become network-visible simply because an agent has a memory-sharing scope. Publication, audience, and discovery are separate decisions.

How does it connect to Data Vault?

Data Vault provides the protected source layer, including private versioned memory. The exchange lets you prepare and review recipient-facing knowledge from that source context. Sharing a collection does not grant unrestricted access to the source files or memories.

How does it connect to AI Wallet Control?

An authorized agent can use permitted context when preparing a proposal. If that proposal involves spending, evaluate it through the separately scoped AI Wallet Control workflow. Collection access is not a wallet grant, and the current public wallet-evaluation preview does not sign or send payments. This is an integration pattern, not an automatic payment pipeline.

Can an agent automatically publish or overwrite our knowledge?

A query is not permission to publish. Content changes and shared replies follow explicit review and the relevant version and authority checks. Private memory is not automatically modified by a recipient’s question or feedback.

What happens when access is removed?

Access changes govern future access under the supported collection rules. Taking a collection dark revokes its grants and invitations; republishing requires the appropriate access to be issued again. Copies already received cannot be recalled.

Does a workspace invitation give access to just one person?

A direct invitation is accepted into the recipient’s current workspace, not only their personal account. Confirm the intended workspace and its membership before sharing sensitive context.

What should we agree before starting a pilot?

Use the product-specific checklist above to define scope and acceptance tests. Ask the team to confirm the deployment environment, access, supported operations, integration responsibilities, support arrangements, and commercial terms. Availability labels are not a pricing quote or a service-level commitment.

Start with one useful result

Make it work for your team.

Bring your workflow. We’ll help identify the scope, access, and acceptance checks for a practical pilot.

Plan your pilot
Build the next part of your workflow

Connected products.

Start with Agentic Memory Exchange. Review these adjacent capabilities when your requirements call for them.

Data Vault

Protect confidential records while retaining evidence of their integrity.

Explore Data Vault
Plan your integration Discuss a scoped pilot All products