Gammatica AI
Freemium
Sales teams using CRM with AI assistance
CRMKit
FreeOpen SourceAPISelf-Hosted
Every agent project that starts by dumping contacts into a markdown file eventually hits the same wall: stable IDs go missing, duplicate records multiply, and concurrent writes from two agents corrupt the whole thing. crmkit exists to absorb that plumbing before you reinvent it.
Similar tools
Gammatica AIFreemiumThe platform pairs three named agents — Gammatica AI for proposals and client history, Zuna for…
HowAICiteFreemiumThe platform queries ChatGPT, Claude, Perplexity, and Gemini through each provider's API and…
ClearList.meFreemiumClearList targets exactly that grind: drop photos, get AI-generated titles, descriptions…
ConvoForms.aiPaidConvoForms puts an AI dispatcher called Gus on your phones, fielding calls you can't answer…
Get This Tool
License: MIT Any use incl. commercial
Local-run terms: Download binary or source from GitHub repo; run the HTTP API server locally under MIT terms.
Pricing
- Model
- Free
Summary
The vendor describes crmkit as a headless, agent-first CRM with no dashboard and no UI — your agent is the interface. It exposes a plain HTTP API covering contacts, companies, deals, deduplication, audit history, and schema validation, so agents have a shared system of record instead of a scratch table. Setup is a single prompt pasted into Claude, Claude Code, or ChatGPT. The self-hosted path is MIT-licensed and open-source. The ceiling appears when your workflow needs a human to review, approve, or edit records — there is no interface for that, which means you build one yourself.
Bottom line: Pick crmkit when you need agents to write and query CRM state without standing up a database schema from scratch — skip it when any human on the team needs to open a dashboard and edit a deal without touching an agent.
Find your fit
Before you choose CRMKit
More options in Sales & CRM. Compare pricing, platforms, and features side by side.
HowAICite
Freemium
Marketing and sales teams tracking AI visibility
Pros
- Plain HTTP API covering contacts, companies, deals, deduplication, and audit history out of the box, which means agents never write custom database schema or relationship logic per project.
- Single-prompt setup — the agent reads its own configuration from a URL and initializes itself — so the time from 'I need persistent CRM state' to 'agents are writing records' is measured in minutes, not sprints.
- Handles concurrent writes and stable ID management at the infrastructure level, which means two agents running in parallel against the same pipeline do not corrupt each other's records the way a shared markdown file would.
- MIT-licensed and self-hosted, so teams with data-residency requirements or cost ceilings on external APIs can run the full stack on their own infrastructure without a paid dependency.
- MCP connector support for ChatGPT alongside direct Claude and Claude Code integration, which means the same CRM backend works across whichever agent runtime a team standardizes on.
Cons
- There is no human-facing interface — no dashboard, no record editor, no approval view. Any workflow where a sales rep, account manager, or reviewer needs to open and edit a deal directly requires the team to build that UI against the HTTP API themselves, adding a frontend project that was not in the original scope.
- The headless-only design means teams that later need their CRM to send automated emails, trigger sequences, or integrate with an existing sales stack through native connectors will find no such surface here. At that point teams move to a product like HubSpot or Pipedrive that ships those integrations, and port the data out.
- Because setup is mediated entirely through the agent reading a URL and following instructions, the reliability of onboarding is coupled to the agent's ability to follow multi-step instructions correctly — a model that misreads or truncates the setup flow leaves the workspace in a partially configured state with precious little fallback UI to inspect or repair it.
About
- API Available
- Yes
- Self-Hosted
- Yes
- Last Updated
- July 8, 2026
Best For
Who it's for
- AI agents that need persistent CRM state
- Headless automation of sales pipelines
- Projects avoiding custom markdown or database plumbing
What it does well
- Agent-managed contact and deal tracking
- Natural-language queries against CRM data
- Self-setup of a shared system of record for multi-agent projects
Integrations
Frequently Asked Questions
- Is CRMKit free?
- CRMKit offers a free option. Hosting, model usage, or optional services may have separate costs; check the pricing details and official terms.
- Is CRMKit open source?
- Yes. CRMKit is open source.
- Does CRMKit have an API?
- Yes. CRMKit exposes a developer API. See the official documentation at https://crmkit.ai for details.
- Can I self-host CRMKit?
- Yes. CRMKit supports self-hosting on your own infrastructure.
A CRM that an agent manages through a scratchpad file works fine for the first dozen contacts. Then stable IDs, relationship graphs, deduplication, concurrent writes from parallel agents, and audit history all arrive at once — and what looked like a weekend’s plumbing becomes a month of it. crmkit is a headless CRM built specifically so AI agents can drive a battle-tested CRM core over plain HTTP, without any of that infrastructure being written per-project. The core workflow: paste one prompt (or hand the agent a URL) and the agent reads its own setup instructions, configures itself, and starts managing contacts, companies, and deals through a conversational interface.
The differentiating design decision is that there is no app. No dashboards, no click interface, no forms. The agent is the only interface — which means the API surface is the product. The vendor states the system handles stable IDs, contact-company-deal relationships, search, deduplication, validation, audit history, schema changes, limits, and concurrent writes. That is the exact list of problems teams discover after shipping a markdown-based approach, which is the point.
CRMkit fits projects where agents need persistent, queryable CRM state and humans do not need to interact with that state directly — headless sales pipeline automation, multi-agent projects that share a system of record, or natural-language querying of deal and contact data. It breaks down the moment a human needs to open a view, edit a record, or approve an action. There is no UI to give them. Teams that hit this wall either build a thin frontend against the HTTP API or move to a CRM product that ships with a human-facing interface.
The vendor states compatibility with Claude, Claude Code, OpenClaw, and ChatGPT (via a custom MCP connector). The codebase is MIT-licensed, a self-hosted path exists, and the API is documented at the /start endpoint which the agent reads directly.
Contribute
- Work on CRMKit? Claim this listing.
- Embed a badge for your README or site.
Sign in to rate this tool or suggest an edit.