Beta
Build on advertised capabilities
Integrations should discover what a backend supports instead of assuming every Mobazha deployment exposes the same surface.
Integration rule
Use the connected backend's capability response and version information as runtime truth. Documentation describes interfaces and intent, but a client must handle unavailable, disabled, or differently versioned features.
Surfaces
- HTTP and WebSocket interfaces for commerce operations and live updates.
- Webhooks for operator-controlled event delivery.
- MCP and agent-oriented interfaces with explicit identity and authorization boundaries.
- Plugins and contracts only where the connected deployment advertises them.