Introduction
Learn how Saber turns company and contact research into structured, cited answers for CRM enrichment, qualification, and GTM automation.
Saber is a sales intelligence platform for turning company and contact research into structured, cited answers. Teams use Saber to enrich CRM records, qualify inbound leads, prioritize accounts, prepare for meetings, and automate GTM research workflows.
Quick Start
Choose the entry point that matches how your team works.
HTTP API
Call the REST API directly from your product, workflow, or data pipeline.
CLI
Run repeatable Saber workflows from a shell, CI job, or agent session.
MCP Server
Connect Saber tools to an MCP-compatible AI client.
Skills
Run Saber GTM workflows from your AI agent.
What is an Enrichment?
An enrichment answers one specific research question about a company or contact and returns a structured, cited result. A good question is observable, structured, and useful downstream. For example, "Is this company hiring account executives?" is easier to route and score than "Is this a good account?"
Each enrichment run:
- Researches the target using available public and connected sources.
- Analyzes the evidence against your question.
- Returns the answer in the requested shape.
- Includes confidence and source context where available.
Enrichments support multiple answer types: open_text, number, boolean, list, percentage, currency, url, and json_schema.
"Signal" means something specific in Saber. A signal is an occurrence emitted by a monitor — a funding round detected, an answer that changed — not a research answer. Research answers are enrichments. (The question-answering endpoints once called the "Signals API" are now the Enrichments API; the legacy /v1/…/signals routes keep working until their announced sunset.)
Core Concepts
Companies and contacts Research companies by domain and contacts by profile or enriched contact data. Company enrichments are best for account qualification, timing, and market context. Contact enrichments are best for persona research, outreach personalization, and meeting preparation.
Lists Use lists when a target segment or audience should survive beyond a one-off search. Lists give you a stable boundary for review, enrichment, scoring, CRM sync, and recurring monitor runs.
Templates Enrichment templates standardize reusable questions and answer types. They are useful when multiple people, agents, or jobs need to score accounts using the same evidence, and a watch monitor re-runs one on a schedule.
Monitors A monitor is a standing watch that emits signals — occurrences such as a changed answer or a detected funding round — over time. Use monitors when you care about what changed, not a one-off answer.
Connectors Connectors link Saber to external systems such as HubSpot and LinkedIn Sales Navigator. Check connector status before workflows that depend on CRM or contact source data.
How it works
The fastest first call is a prebuilt enrichment — pass a domain and get a structured, evidence-backed answer, with no question to design:
const res = await fetch('https://api.saber.app/v1/companies/enrich/funding', {
method: 'POST',
headers: {
Authorization: 'Bearer <your-api-key>',
'Content-Type': 'application/json',
},
body: JSON.stringify({ domain: 'openai.com' }),
});
// A fresh run returns `202` with `Location: /v1/enrichment-runs/{runId}` — poll
// that run or pass a `webhookUrl` for delivery. A cache serve returns `200`
// inline (free). Both carry the `enrichment_run` envelope.
const run = await res.json();
console.log(run.result);When your question is specific to your niche — something no prebuilt type covers — write a custom enrichment with your own question and answerType:
const res = await fetch('https://api.saber.app/v1/companies/enrich/custom', {
method: 'POST',
headers: {
Authorization: 'Bearer <your-api-key>',
'Content-Type': 'application/json',
},
body: JSON.stringify({
domain: 'openai.com',
question: 'What AI products does this company offer?',
answerType: 'open_text',
}),
});
const run = await res.json();
console.log(run.result);Both routes return the enrichment_run envelope: 202 starts a fresh run (poll GET /v1/enrichment-runs/{runId} or receive the result via webhookUrl), and 200 serves a cached answer inline. GET /v1/enrichment-runs lists runs across both entity types.
AI Tooling
Saber is designed for both programmatic integrations and AI-native workflows:
- Use the CLI for repeatable terminal, CI, and agent-session workflows.
- Use the MCP Server when an AI assistant should call Saber tools directly.
- Use Skills when an agent should follow a complete GTM workflow such as market mapping, list building, scoring, or outreach.
Next Steps
Enrichments
Run a prebuilt enrichment from just a domain — or write your own custom question.
Monitors
Stand up a watch that emits signals when answers change or events occur.
Installation
Connect Saber to your preferred tools.
Authentication
Create an API key and protect it correctly.
API Reference
Call the REST API directly from your product or workflow.
CLI
Use Saber from a shell, CI job, or agent session.
MCP Server
Connect Saber tools to an MCP-compatible AI client.
Skills
Run Saber GTM workflows from your agent.