# Conquest Planning API: access, auth, sandbox and MCP (checked Oct 2026)

> Conquest says it offers an open, two-way API to its SAM engine but publishes no developer documentation. It also describes an MCP server that firms enable through a short setup and agreement with Conquest.

- Vendor: Conquest Planning Inc. (Conquest Planning Inc.)
- Website: https://conquestplanning.com/
- Category: Financial planning (core)
- API access: Not found
- Last checked: 2026-10-17
- Id: `conquest-planning` · JSON: https://wealthtech.dev/products/conquest-planning.json

## Developer surface

| Field | Value | Source and quote | Checked |
|---|---|---|---|
| API access | Not found | Not found. Vendor states an open two-way API (FAQ) but publishes no developer docs or access process. Pages tried: /platform, /resources/financial-planning-platform-faq, /en-us/digital, /solutions/mcp. Vendor states an open two-way API (FAQ) but publishes no developer docs or access process. Pages tried: /platform, /resources/financial-planning-platform-faq, /en-us/digital, /solutions/mcp. | 2026-10-17 |
| Developer docs | Not found | Not found. No developer documentation URL found on the pages tried. No developer documentation URL found on the pages tried. | 2026-10-17 |
| API style | Not found | Not found. Not stated; the vendor says only 'open, two-way API'. Not stated; the vendor says only 'open, two-way API'. | 2026-10-17 |
| Authentication | Not found | Not found. Not stated for the API. The MCP page says connections are authenticated and firms opt in. Not stated for the API. The MCP page says connections are authenticated and firms opt in. | 2026-10-17 |
| How to get access | For the MCP server: a short setup and agreement with the Conquest team. For the API no process is published. | Checked on the source's own page. [conquestplanning.com](https://conquestplanning.com/solutions/mcp) "turning it on involves a short setup and agreement with your Conquest team" | 2026-10-17 |
| Sandbox | Not found | Not found. Not stated. Not stated. | 2026-10-17 |
| Rate limits | Not found | Not found. Not stated. Not stated. | 2026-10-17 |
| Webhooks | Not found | Not found. Not stated. Not stated. | 2026-10-17 |
| SDKs | Not found | Not found. Not stated. Not stated. | 2026-10-17 |
| OpenAPI spec | Not found | Not found. No spec or developer portal found. No spec or developer portal found. | 2026-10-17 |
| Partner program | Not found | Not found. No partner-application page found on the pages tried. No partner-application page found on the pages tried. | 2026-10-17 |
| Public integration list | Not found | Not found. No integration list found on the pages tried. No integration list found on the pages tried. | 2026-10-17 |
| Ways to connect | Native API, MCP | Checked on the source's own page. [conquestplanning.com](https://conquestplanning.com/resources/financial-planning-platform-faq) "We offer an open, two-way API that lets your firm integrate our Strategic Advice Manager® (SAM)" | 2026-10-17 |

## MCP servers and AI connectors

- [Conquest MCP Server](https://wealthtech.dev/mcp/conquest-mcp): Remote MCP server, Announced

## What the docs don't say

- Conquest describes an open, two-way API but publishes no endpoints, authentication, sandbox or access process.
- The MCP page describes the server and says enabling it needs a setup and agreement with Conquest; no public endpoint is given.

## Changes

No changes recorded since this record was first published.
---
Source: https://wealthtech.dev/products/conquest-planning · Facts licensed CC BY 4.0 (attribution "wealthtech.dev"). Every fact states where it was checked and when; check the source before relying on it.