Introduction

Salty is a developer-first CRM. Every CRM in 2026 was built for humans first and bolted AI on later — Salty is the inverse. The interface surface is a clean REST API, an MCP server, a CLI, and signed webhooks. The agent does the work; Salty is the database underneath. See trysalty.com for the product overview, pricing, and sign-up.

Hosts at a glance

Every code sample in these docs uses environment variables for hostnames. Set these once per shell:

export SALTY_API=https://api.trysalty.com   # REST API
export SALTY_MCP=https://mcp.trysalty.com      # MCP server
export SALTY_WEB=https://trysalty.com          # admin UI + /signup + /pricing

Bearer tokens go in $SALTY_API_KEY. The Scalar API explorer is always at $SALTY_API/reference.

Three ways to call the API

curl — for one-off probing.

curl $SALTY_API/people \
  -H "Authorization: Bearer $SALTY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email":"jane@acme.com"}'

SDK — for application code.

import { Salty } from '@salty/sdk';
const salty = new Salty({ apiKey: process.env.SALTY_API_KEY! });
const { data, error } = await salty.people.postPeople({
  body: { email: 'jane@acme.com' },
});

Scalar explorer — for interactive exploration. Open $SALTY_API/reference, paste your sk_live_… key in Authorize, send requests from the page.

Quickstart — sign up, get a key, hit the API in 60 seconds
API Reference → Introduction — conventions, errors, pagination
Concepts → Authentication — sk_live_ keys, Supabase JWTs, OAuth tokens
Concepts → Schema engine — how custom_attributes validation works
Concepts → Billing — plans, hard caps, upgrade/cancel flow
MCP server — connect Claude/Cursor/ChatGPT via OAuth
Webhooks — receive signed events when data changes

Get Started

Use cases

Concepts

Introduction

Hosts at a glance

Three ways to call the API

Next

​Hosts at a glance

​Three ways to call the API

​Next

Hosts at a glance

Three ways to call the API

Next