CRM for Developers
The CRM Developers Actually Want to Build On
500+ API endpoints. 136 MCP tools. 3 MIT-licensed SDKs. Rate limits that scale with your plan, not against you. Documentation that does not lie. The same API our own app runs on, available on every plan.
The challenge
Why most CRMs fail developers
CRM APIs have a reputation, and most of it is earned. The fragmentation across HubSpot's REST + GraphQL + a-dozen-versioned-microendpoints. The Salesforce SOAP-API archaeology you only discover when you need it. The Pipedrive rate limits that throttle bulk operations into multi-day cron jobs. The webhook payloads you have to wrap in retry logic because the vendor will not. The "API access" tier that costs more than the CRM tier. We built Conduyt's developer surface to be the opposite of every one of those frictions. The API is the product, dogfooded daily. The MCP server is native, not a community port. The SDKs are MIT-licensed and auto-generated from the OpenAPI spec so they stay in sync. Rate limits are visible in headers, generous by default, and lifted on request when you can justify it.
Why Conduyt
Why developers choose Conduyt
Four reasons teams like yours make the switch.
535 REST endpoints, fully documented
REST + JSON, OpenAPI 3.1 spec, versioned at /api/v1. Every endpoint documented with request/response examples, error schemas, and pagination semantics. Cursor-based pagination on list endpoints. The Conduyt app itself runs on this same API — if an endpoint is slow, we feel it first.
Native MCP server with 136 tools
136 tools across 28 modules covering contacts, deals, pipelines, companies, automations, messaging, calendar, forms, documents, dialer, reporting, and admin. Any MCP-compatible AI client connects. Setup takes under 10 minutes. Scoped permission requirements and full audit-log integration.
3 MIT-licensed SDKs
TypeScript (@conduyt/sdk), Python (conduyt-python), and Go (github.com/conduyt/conduyt-go). Auto-generated from the same OpenAPI spec so language ergonomics match. First API call in under 60 seconds. Public GitHub repos, fork and contribute.
127 webhook event types, HMAC-signed
HMAC-SHA256 signed payloads, documented event catalog, dead-letter queue for failed deliveries with a 72-hour replay window. Idempotency keys supported on all retryable events. Rate limits: 600/min on Starter, 1,000/min on Professional. Burst-safe headers tell you exactly how many requests remain.
Use cases
Common use cases for developers
How teams like yours actually use Conduyt day-to-day.
- Custom in-app onboarding flows that create contacts, deals, and tasks via direct API call
- Real-time PLG conversion pipelines from product analytics into the CRM via webhook
- AI agents that triage inbound messages, classify intent, and route deals via MCP server
- Custom reporting dashboards built on the underlying data via API export
- Multi-tenant integrations where your product writes back to customers' Conduyt workspaces
Recommended plan
Which plan fits developers?
Our recommendation based on how developers typically use Conduyt.
Professional
$499/mo
API access is included on every plan, including the 20-day free trial. Most developer teams running production workloads land on Professional at $499/mo for the higher rate-limit ceiling (1,000/min vs 600/min), the longer webhook replay window, and priority support. Sandbox API keys available with one POST request, no credit card.
- Everything in Starter (unlimited users, contacts, pipelines)
- Priority support
- Dedicated onboarding
- Advanced automations
- Full API access
- Custom branding
- Dedicated success manager
“We had our first integration running in under an hour. The OpenAPI spec is accurate, the SDKs actually work, and the webhook signing is standard HMAC. After years of fighting CRM APIs, this was refreshingly normal.”
The math
How Conduyt compares
Real numbers, real savings.
HubSpot has a broad API surface but fragmented across REST, GraphQL, and multiple versioned microendpoints; API access on higher tiers costs more. Salesforce has the deepest CRM API but carries SOAP-era complexity and steep learning curves. Pipedrive has a clean REST API but rate limits throttle bulk operations and the MCP surface is not native. Attio has a modern API gaining traction with developer-first teams. Where Conduyt sits: a single, consistent REST surface with native MCP, MIT-licensed SDKs, and rate limits that do not punish production workloads.
Frequently asked questions
Your team uses AI? See how AI agents drive Conduyt →
Start your 20-day free trial - built for developers
No credit card. No per-seat pricing. Just a CRM that works the way developers actually sell.
Get started free →