> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.6mm.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.6mm.com/_mcp/server.

# Integration Information Template

Use this template when preparing a new integration or moving an existing integration into production.

<h2 id="partner-information">
  Partner information
</h2>

| Field            | Description                                                                         |
| ---------------- | ----------------------------------------------------------------------------------- |
| Partner name     | Legal or project name used for the integration.                                     |
| Product type     | App, wallet, broker portal, white-label exchange, institutional platform, or other. |
| Primary contacts | Business, technical, operations, and emergency contacts.                            |
| Launch regions   | Countries or regions where the integration will be exposed.                         |

<h2 id="technical-information">
  Technical information
</h2>

| Field             | Description                                                                                   |
| ----------------- | --------------------------------------------------------------------------------------------- |
| Frontend domains  | Domains that will load the widget or entry pages.                                             |
| Backend domains   | Server domains used for Agent SDK or API calls.                                               |
| Webhook URL       | Production webhook endpoint and expected IP allowlist requirements.                           |
| Integration scope | Trading Widget, Agent SDK, REST API, WebSocket, white-label system, or liquidity integration. |

<h2 id="operational-information">
  Operational information
</h2>

* Expected launch date.
* Expected traffic or active user range.
* Support hours and escalation owner.
* Monitoring owner and incident contact.

<h2 id="security-and-review-information">
  Security and review information
</h2>

* Authentication method and API Key permission scope.
* Secret storage, rotation owner, and approved source IPs.
* Webhook signature verification and idempotency design.
* Logging, monitoring, reconciliation, rollback, and incident-response owners.
* Target markets, user type, custody model, and the entity responsible for user-facing obligations.

Do not include production secrets, full access tokens, private keys, or unredacted user data in this template.

Use the [production launch checklist](/resources/production-launch-checklist) for final approval and the [support request template](/resources/support-request-template) for issue escalation.