> ## Documentation Index
> Fetch the complete documentation index at: https://sendmux.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Existing integrations

> Keep your existing service addresses, credentials and published developer tools working with Qubrics.

Your existing integration keeps working. With Qubrics, you can keep the same service addresses, API keys and account settings.

## Service addresses

The existing `app.sendmux.ai`, `smtp.sendmux.ai`, `mail.sendmux.ai`, `mcp.sendmux.ai` and `a2a.sendmux.ai` service addresses remain supported without a sunset, and Qubrics uses the corresponding `qubrics.com` addresses for new setup instructions.

## Developer tools and contracts

Follow each setup guide's exact instructions. Published packages, CLI commands, marketplace entries and SDK exports can retain their existing identifiers, including the package names, commands and imports shown in those guides. An installed dependency or an accepted protocol identifier does not change when the product is renamed.

Existing `X-Sendmux-*` headers, `SENDMUX_*` environment settings, MCP tool names and `sendmux_message_id` remain supported. The `sendmux.test` webhook event, OAuth resource identifiers and signed MCP Registry identity also retain their exact spelling. Keep these values when your integration uses them. See [Compatibility names](https://sendmux.ai/docs/ai-integrations/mcp#compatibility-names) for Qubrics aliases and retained names.

> [card] [Choose a setup guide](https://sendmux.ai/docs/developer-tools/sdks)
>
> Find the package, credentials and API surface your application needs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.