Skip to content
docs
Browse the docsMigrating from destroy.network

Get started

Migrating from destroy.network

destroy.network is now dissolve.email. What changed for API callers, OAuth apps, MCP clients, the SDK and the CLI, and what keeps working untouched.

In November 2026 destroy.network became dissolve.email: a new name, new hosts and new package names. Accounts, inboxes, keys and tokens moved with it. Most integrations need one change, the base URL, and many need none at all yet.

What keeps working

Status
API keys sk_live_Unchanged. Keys made on destroy.network work on dissolve.email.
OAuth tokens dna_at_, dna_rt_, codes dna_ac_, client secrets dna_cs_Unchanged prefixes, accepted for good. Issued tokens were not invalidated.
OAuth scope namesUnchanged. A scope is never renamed.
MCP tool namesUnchanged. A tool is never renamed or removed, only added.
Mail to @destroy.network addressesStill arrives, for as long as inboxes and aliases exist on it.
/api/v1/... pathsStill served beside /v1/..., for SDKs and CLIs built for destroy.network.
The other /api/... routes the old SDK calledStill served under https://api.dissolve.email/api/...

Base URL

BeforeNow
APIhttps://destroy.networkhttps://api.dissolve.email
Versioned API/api/v1/... on destroy.network/v1/... (or /api/v1/...) on api.dissolve.email
Appdestroy.networkhttps://app.dissolve.email
MCP servermcp.destroy.networkhttps://mcp.dissolve.email/mcp and /mcp-oauth
Docsdestroy.network/docshttps://docs.dissolve.email

destroy.network keeps answering API calls until the cutover, then sends its web pages to dissolve.email and keeps API paths answering for old SDKs and CLIs. Move to the new host when you next deploy.

Shell
# Before (destroy.network base)
curl "$OLD_BASE/api/v1/inboxes" -H "Authorization: Bearer $KEY"
# Now
curl https://api.dissolve.email/v1/inboxes -H "Authorization: Bearer $DISSOLVE_API_KEY"

Two old routes are gone rather than moved: the separate public marketplace API (its old public path) and the old agent identity routes outside /v1. Both are covered by /v1: inboxes, messages and agent identities under /v1/identities.

TypeScript SDK

The package is now @dissolve-email/sdk (it was @buun_group/destroy-network-sdk, now deprecated).

Shell
npm uninstall @buun_group/destroy-network-sdk
npm install @dissolve-email/sdk
TypeScript
// Before
// import { DestroyNetwork } from '@buun_group/destroy-network-sdk';
import { Dissolve } from '@dissolve-email/sdk';

const client = new Dissolve(); // reads DISSOLVE_API_KEY, then DESTROY_NETWORK_API_KEY
  • DestroyNetwork and DestroyOAuthError remain as deprecated aliases, so old code compiles.
  • The default host is https://api.dissolve.email. Pass baseURL: 'https://destroy.network' to keep using the old host while it answers.
  • Plain http: is refused except to localhost.
  • An OAuth token (dna_at_) sent anywhere but client.v1 throws before the request.
  • The paths for templates, API keys and webhooks were fixed. The domains resource was removed: the feature it served is switched off.

The SDK page has the rest.

CLI

The npm package is now @dissolve-email/cli (it was @buun_group/dna). The program is still dna, so scripts keep working, and is also installed as dissolve.

Shell
npm uninstall -g @buun_group/dna
npm install -g @dissolve-email/cli
  • On first run, ~/.config/dna/config.json is copied to ~/.config/dissolve/config.json. The old file stays, so the old CLI still works. A saved destroy.network address is replaced by the new default; any other custom address is kept.
  • DESTROY_* environment variables are still read; DISSOLVE_* wins when both are set.
  • dna verify --pattern now runs on your machine against the matches the server found: the server no longer takes a regular expression. Use --from to filter by sender on the server.

See CLI.

OAuth apps

The issuer is now https://api.dissolve.email, with its metadata at /.well-known/oauth-authorization-server. The old issuer's metadata stays on destroy.network until every registered client has moved.

  • Existing tokens and refresh tokens keep working; refreshing gives tokens from the new issuer.
  • An authorization response carries iss=https://api.dissolve.email. If your client checks iss, accept it.
  • Dynamically registered clients should register again against the new server (Authentication).
  • The SDK's OAuth helpers use the new issuer by default.

MCP clients

Point your client at https://mcp.dissolve.email/mcp-oauth (OAuth) or https://mcp.dissolve.email/mcp (API key) and sign in again. Tool names and scopes are the same, so prompts and skills keep working. MCP server has the setup for each client.

The app and sessions

The app moved to app.dissolve.email and its session cookie is now dissolve_session. Everyone signs in once more with an emailed code; the old destroy_session cookie is still read during the move. Sessions are only for the app; API callers are not affected.

Something wrong or missing on this page? Tell us at support@dissolve.email.View as Markdown