DealerMAX Developers
DealerMAX Developers has three public surfaces: the read-only Dealer Public API for single-dealer backend integrations, the public DealerMAX MCP Server for AI-agent discovery, and PartnerMAX Enterprise for approved partners managing multi-dealer networks and write-side workflows.
Choose your path
| Dealer Public API | Use this when you need to read one dealer's inventory,
NLT (long-term rental) offers, and DealerMAX-generated content. Access: a dealer API key generated and rotated inside DealerMAX. Scope: single dealer per key. Methods: GET-only.
Base URL: catalog.dealermax.app. |
|---|---|
| DealerMAX MCP Server | Use this when an MCP-aware AI client needs to query the
DealerMAX network without scraping. Access: public, read-only, no account, no API key. Scope: cross-network public discovery. Transport: streamable HTTP on mcp.dealermax.app/mcp/.
Latest registry version: 1.2.1. |
| PartnerMAX Enterprise | Use this when you are an approved platform partner
onboarding or operating multiple dealers. Access: Standard Trial Path for self-service evaluation, or Enterprise Onboarding Path for support-managed procurement and production rollout. Scope: multi-dealer networks owned by the partner. Workflows: provisioning, dealer lifecycle, partner-scoped NLT configuration, vehicle ingestion, key management, and subscription-gated access. |
Read-only by design
Only GET endpoints are part of the Dealer Public API.
Write-side workflows live behind PartnerMAX Enterprise permissions.
One dealer per key
The public contract is intentionally dealer-scoped. Use separate dealer-issued keys when you operate separate dealer frontends.
Backend-first
Use a BFF, backend, SSR, or SSG job. Do not put
DEALERMAX_API_KEY in browser JavaScript.
Agent-ready
MCP access is intentionally keyless and read-only, so compatible AI clients can query public DealerMAX data without touching dealer credentials.
Primary surfaces
| Dealer Public API | Canonical read-only REST contract on catalog.dealermax.app. |
|---|---|
| MCP Server | Public read-only Model Context Protocol endpoint for AI clients and agentic workflows. |
| Official SDKs | PartnerMAX SDKs are published as partnermax. The dealer read-only SDK is pre-release; generate from OpenAPI until official packages are linked here. |
| Quickstart | cURL plus safe Node/TypeScript BFF and Python backend examples. |
| Security posture | API key handling, coordinated disclosure, subprocessors, and audit controls. |
What you can build
- Custom dealer websites backed by live DealerMAX inventory.
- Server-rendered stock and NLT offer pages.
- Internal dashboards, exports, and marketplace sync jobs.
- AI-ready surfaces that consume structured dealer data without scraping.
Where to go next
- Need credentials for a dealer website or BFF? Start with Quickstart and the Dealer Public API reference.
- Building a DMS, CRM, marketplace, or SaaS platform that manages dealer accounts? Review PartnerMAX Enterprise.
- Need AI-agent discovery rather than an API key? Use the DealerMAX MCP Server.