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 a Signal?
A signal is an AI-powered research result that answers one specific question about a company or contact. A good signal 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?"
When you create a signal, Saber:
- 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.
Signals support multiple answer types: open_text, number, boolean, list, percentage, currency, url, and json_schema.
Core Concepts
Companies and contacts Research companies by domain and contacts by profile or enriched contact data. Company signals are best for account qualification, timing, and market context. Contact signals 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 signal runs.
Templates Signal templates standardize reusable questions and answer types. They are useful when multiple people, agents, or jobs need to score accounts using the same evidence.
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
For a direct HTTP integration, start with the sync company signal endpoint:
const signal = await fetch('https://api.saber.app/v1/companies/signals/sync', {
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 result = await signal.json();
console.log(result.answer);The sync endpoint waits for processing and returns the answer inline. Use async endpoints when you want webhook delivery, polling, or high-volume batch work.
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
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.