Reference
Storage and providers
A storage connection is a configured resource. A provider adapter is the runtime implementation that actually performs an operation. Keeping those concepts separate lets the API show what is configured without claiming that an unimplemented data path is live.
| Surface | Current status | What it means |
|---|---|---|
| Mpalo-managed memory | available_mock | Managed backend storage executes the current deterministic text path after storage and consent checks. |
| BYO vector storage | control_plane_only | Mind Platform can represent a connection. v1 memory operations do not dispatch to it. |
| Application-managed model | available_mock | The application may use returned context with its own model. That model is outside Mpalo attribution. |
| Mpalo-managed external LLM | not_available | The integration is disabled. Saving a provider credential cannot enable transfer. |
Discover before dispatch
The infrastructure capability response includes a versioned storage_providers manifest. Read it before attaching or dispatching a connection. available_mock means the current backend mock path can execute the listed operation. control_plane_only means the connection can be configured, but the data plane rejects it before data, metering, or billing work. not_deployed means the deployment mode has no promoted adapter.
GET https://api.mpalo.com/api/v1/infrastructure/capabilities storage_providers.contract_version storage_providers.providers[].provider storage_providers.providers[].status storage_providers.providers[].data_plane storage_providers.providers[].operations
The manifest is discovery metadata, not permission to bypass the authenticated storage preflight. The server still verifies the key attachment, connection state, scope, consent, and deployment capability for every memory operation.
Mpalo-managed memory
The current managed adapter retains submitted text in the tenant and user scope when an API key has an active connection and private-memory consent is granted. It supports the backend lifecycle around model substitution, including authentication, persistence, lexical retrieval, usage, test billing, export, deletion, and observability.
mpalo-local-mock with deterministic lexical behavior and explicit model substitution.Bring your own vector storage
BYO storage is a valid product direction, but it is not an executable v1 data-plane capability. A configured custom connection does not establish compatibility, dimensions, metric, tenant isolation, credential safety, retention, or deletion responsibility.
You may see managed and custom storage connections in the control plane. Only an active Palo Managed Memory connection enters the current memory runtime. An active BYO connection returns MEMORY_STORAGE_PROVIDER_UNAVAILABLE before persistence, retrieval, deletion, metering, billing, or model substitution. It does not send data to a custom endpoint or silently fall back to managed storage.
Before execution is enabled, Mpalo must define the provider protocol, representation dimensions and metric, namespace rules, credential rotation, payload limits, timeouts, retries, partial writes, export, deletion, correction, migration, billing, region, subprocessors, and transient-data boundary.
External models and providers
The current application-managed boundary means that a developer may pass returned context to a model they operate. Mpalo does not claim that the downstream model ran, and it does not attribute that model's output, tools, or decisions to the memory API.
Mpalo-managed external LLM connections are disabled. Re-enabling them would require an allowlist, provider-specific terms, regional and retention controls, subprocessor records, secret handling, billing attribution, privacy disclosures, liability treatment, and a visible opt-in security setting. A saved credential alone must never activate data transfer.
What a provider adapter must preserve
A future provider can change implementation details, but not the shared request meaning.
| Stage | Required behavior |
|---|---|
| Resolve | Bind verified tenant, user, API key, connection, namespace, and request ID. |
| Authorize | Check connection state, consent, permission, region, provider policy, and limits. |
| Execute | Use bounded timeouts and an explicit provider mode. Never fall back to mock silently. |
| Record | Attribute provider, representation, latency, retries, usage, billing, and failures independently. A successful receipt must match the requested operation and configured provider identity. |
| Reconcile | Make replay, export, correction, deletion, and charge state agree with provider state. |
Promotion gate
A storage or provider integration becomes a supported capability only after it has a versioned contract, a real adapter that cannot fall back to mock, isolation and consent tests, deletion and correction evidence, outage and replay behavior, correlated usage and billing, legal and security review, and measured latency, cost, capacity, and retention.
Until those conditions are met, the public status is intentionally precise: configuration is available; execution is not. See Data boundaries and provenance for what the current runtime stores and returns.
Was this page helpful?
Your feedback helps us improve our documentation.