Guide
From contract test to controlled deployment
A production integration is more than a successful memory request. It needs a credential boundary, an attached storage connection, bounded retries, durable usage attribution, observable health, and a release record that can be audited after the fact.
Provision the control plane
Create the storage connection first, then create an API key and attach the storage. Keep the key scoped to the application or environment that will use it. Do not put a model provider key in the Mpalo control plane when the application is responsible for its own model call.
palo auth login palo mind storage create palo mind keys create palo mind keys list palo mind me
The key creation flow asks whether to create a managed storage or attach an existing connection. BYO storage is configured as a connection resource, not as an unvalidated request parameter.
Deploy with explicit configuration
Inject secrets through the deployment platform. Pin the API contract version in the client. Keep the base URL at the canonical origin in production and use a separate profile or environment for local testing.
PALO_BASE_URL=https://api.mpalo.com PALO_API_KEY=managed-by-secret-store
from palo import Palo
client = Palo(
api_key=secret_manager.get("MPALO_API_KEY"),
base_url="https://api.mpalo.com",
timeout=30,
max_retries=2,
)Verify before traffic
Record the deployment version, contract version, capability manifest, health response, and one safe test operation. Verify that the operation's provenance and billing state match the environment you intended to test.
palo infra capabilities --json palo infra health --json palo infra status --json palo infra metrics --json palo memory write "synthetic release check" --namespace release-check --json palo memory delete --namespace release-check --confirm-namespace release-check --json
In the current mock environment, a release check proves transport, authentication, storage attachment, response parsing, and telemetry wiring. It does not prove model behavior, model quality, or production charge settlement.
Operate the integration
| Signal | Record | Response |
|---|---|---|
| Availability | Health status, deployment version, checked timestamp. | Page or route traffic only when required services are unavailable. |
| Request quality | Request count, errors, timeouts, latency percentiles, blocked rate. | Investigate changes against a known baseline, not against a single sample. |
| Runtime truth | Execution mode, provider, model version, capability status. | Do not report mock success as model execution. |
| Cost truth | Operation units, pricing version, recorded and invoiced charge state. | Reconcile usage before making billing or quota decisions. |
Use the SDK or API for durable monitoring. Use the CLI for an operator view and JSON export. Alert on sustained error rate, timeout rate, latency regression, blocked requests, unexpected provider or model changes, and billing reconciliation gaps.
Rollback and incident evidence
A rollback should preserve evidence. Export the relevant namespace and redacted infrastructure state before deleting or rotating resources. Revoke a compromised key, create a replacement, and verify that the old key no longer authenticates.
palo infra export --namespace release-check --json > incident-export.json palo infra events --limit 500 --offset 0 --json > incident-events.json palo mind keys list --json # Rotate or revoke through the explicit key management command.
The CLI requires exact resource identity for destructive confirmation. Keep the exported evidence in an approved incident location and treat it according to the data policy for that namespace.
Was this page helpful?
Your feedback helps us improve our documentation.