Relm

The CRM for LLMs: a native MCP server so your AI agent manages contacts, companies, deals and notes, with self-correcting RFC-9457 errors.

View on relmcrm.com

Documentation

● Live - REST API + native MCP

The CRM your AI agent runs

Relm is an API-first CRM built for LLMs. Give Claude, ChatGPT, or any agent an API key and it reads and writes contacts, companies, deals and activities directly - over REST or native MCP. The dashboard is the thin part.

Start free → Read the docs

Free tier - 1,000 requests/mo - no credit card - test mode always free

your agent is running the pipelinelive

// drag a deal between stages, or watch the agent move one

curl · npm i relmcrm · MCP - read the quickstart →

ContactsCompaniesDeals ActivitiesPipelinesAutomationsWebhooks

Try it - no signup

Run a real API call right now

This hits Relm for real, in free test mode. Edit the values and go.

POST api.relmcrm.com/v1/contacts

Run →

the real response shows up here

No account, no card. Want your own live workspace? Start free →

Built by the team behind growth at

How it works

Three steps to an agent-run CRM

No boilerplate, no schema migration, no sales-ops onboarding. Mint a key, point your agent at it, go.

Create an API key

Sign up and mint a relm_live_ key. Test-mode keys are free and their data is invisible to billing - build against them for as long as you want.

Point your agent at it

Drop the MCP URL into Claude or hit the REST API from any language. Your agent reads the live schema first, so it is never confused about what fields or values exist.

Read & write CRM data

The agent creates contacts, moves deals across pipelines, logs activities and fires automations - the same primitives a human CRM has, exposed as clean function calls.

What's inside

Everything a real CRM needs. Nothing bolted on.

A complete object model, addressable as an API. Every endpoint has a matching MCP tool.

/v1/contacts

People with names, emails, phones, LinkedIn, type and custom fields. Email-optional - phone or LinkedIn-only leads are first-class.

/v1/companies

Accounts with domain-based dedup. Link contacts and deals to the organizations they belong to.

/v1/deals

Opportunities across multiple named pipelines, each with its own ordered stages. Moves emit events.

/v1/activities

One timeline for notes, calls, emails and meetings - with backdating, so imported history keeps its real dates.

/v1/automations

Event-triggered rules and multi-step drip sequences. Move a stage, log an activity, set metadata, send an email.

/v1/webhooks

Signed HMAC deliveries with retry and a dead-letter queue. Fan CRM events out to the rest of your stack.

/v1/connections

Bring your own Resend key (encrypted per workspace); automations send email via the send_email action. Test-mode sends are simulated, never delivered.

/v1/schema

A live, self-describing schema. Unknown values return valid options and a did-you-mean, so agents self-correct instead of failing blind.

test / live

A mode flag on every object. Test data is free, unlimited and invisible to your dashboard and billing.

Built for agents

Designed to be discovered and driven by AI

Relm is not a UI with an API stapled on. It is machine-first from the DNS record up.

Native MCP server

A full Model Context Protocol server - every CRM operation is an MCP tool with a typed schema. Batch many tool calls in one round-trip. Point any MCP client at api.relmcrm.com/mcp.

Self-describing errors

Every error is RFC-9457 problem+JSON with valid_options. An agent that sends a bad enum gets back the list of good ones - it fixes itself without a human.

Agent-discovery layer

/llms.txt, /.well-known/mcp.json, an A2A agent card and an AI-crawler-friendly robots.txt. Agents can find and understand Relm on their own.

Idempotent & predictable

Prefixed IDs (con_, deal_), cursor pagination, an Idempotency-Key header and versioned optimistic concurrency. The boring guarantees agents rely on.

See the agent-discovery hub →

Why Relm

Why not just a Postgres table or HubSpot's API?

Because your agent needs CRM behavior, not just storage - and it needs an interface built for a machine, not a sales rep.

Relm	Postgres table	HubSpot / Attio API
Native MCP server	Yes	Build it	No
Pipelines, deals, activities out of the box	Yes	Build it	Yes
Automations + drip sequences	Yes	Build it	Yes
Self-correcting errors for agents	Yes	No	No
Priced for machine traffic, not per seat	Yes	n/a	Per seat
Ready in one API call	Yes	No	Onboarding

Pricing

Start free. Pay when your agents get busy.

Priced per API request, not per seat - because your main user is a machine. Overage is metered, and you can set a hard spend cap.

Free

1,000 requests / mo

Full REST API + MCP server
All objects, pipelines & automations
Unlimited free test mode
Signed webhooks & custom fields Start free

Pro most popular

$29/mo

100,000 requests / mo

Everything in Free
Metered overage past the cap
Hard spend cap you control
Transactional email (BYO Resend)
Higher rate limits Start free, upgrade later

Scale

$249/mo

2,000,000 requests / mo

Everything in Pro
2M requests for chatty agent fleets
Top-tier rate limits
Priority support Start free

Overage is billed at $0.0001 / request. Set a spend cap to $0 and Relm hard-stops instead of billing you.

FAQ

Questions, answered

What is Relm?

Relm is an API-first CRM built for LLMs and AI agents. It exposes contacts, companies, deals and activities over a REST API and a native MCP server, so an AI agent with an API key can read and write your CRM directly. The web dashboard is a thin human view for the times you want to look.

What is a "CRM for LLMs"?

A CRM whose primary user is a language model, not a sales rep. Instead of forms and pipelines you click through, the agent drives everything through function calls: it creates records, moves deals, logs activities and triggers automations. Relm is designed so an LLM is never confused about your schema.

How do agents connect - MCP or REST?

Both, over the same data and the same API key. MCP clients like Claude connect to https://api.relmcrm.com/mcp and get every operation as a typed tool. Everything else uses the REST API at https://api.relmcrm.com/v1.

Is there really a free tier?

Yes - 1,000 API requests per month, no credit card. Test mode is always free and unlimited, so you can build and demo without touching your quota.

How is this different from HubSpot, Attio or Pipedrive?

Those are UI-first CRMs for human reps, with an API added later. Relm inverts it: the API and MCP server are the product; the dashboard is the thin part. If your "sales team" is a set of agents, a UI-first CRM fights you and an API-first one gets out of the way.

Can I use it without writing code?

Yes. Connect the MCP server to Claude (or any MCP client) and run the whole CRM in natural language - "import these 200 leads", "move everyone stuck in demo for 30 days to nurture". For custom apps, the REST API is a few lines.

Does it support multiple pipelines?

Yes. Pipelines are first-class - each workspace has one or more, each with its own ordered stages. The same stage key (like won) can live independently in several pipelines, and cross-pipeline moves emit their own event.

How do I authenticate?

A bearer token: Authorization: Bearer relm_live_.... Keys are workspace-scoped, shown once, SHA-256 hashed at rest, and come in live and test variants.