Algolia integration now supports per-environment Applications via Cloud Catalog
Opsphere's Algolia integration now maps each Cloud Catalog environment — dev, staging, production, or your own catalog slugs — to its own Algolia Application. Configure Application IDs, default indexes, and restricted Search API keys per environment in admin Cloud Catalog; MCP Search API tools accept optional env so requests like "list indexes in staging" resolve the correct Application instead of production. Global cluster diagnostics remain credential-free.
Enterprise storefronts often run separate Algolia Applications per tier. This update aligns Opsphere with that model and prevents cross-environment credential leakage. Legacy single Application ID and API key configuration remains supported for single-app tenants.
Integration detail and API reference copy on the site now describe multi-environment setup alongside the existing search and index triage workflows.
