# Docs

- Getting Started
  - [Getting Started](/getting-started): Create an API key, run your first company enrichment, and choose the Saber interface that best fits your workflow.
  - [Introduction](/getting-started/introduction): Learn how Saber turns company and contact research into structured, cited answers for CRM enrichment, qualification, and GTM automation.
  - [Installation](/getting-started/installation): Connect Saber through the REST API, MCP server, HubSpot, Clay, n8n, Make, and other tools used in GTM workflows.
- Companies
  - [Companies](/companies): Find target accounts, save reusable company lists, run AI research enrichments, and score companies for sales and CRM workflows.
  - [Search Companies](/companies/search): Preview companies that match a target filter before saving an account segment, running enrichments, or syncing results to downstream tools.
  - [Company Lists](/companies/lists): Create durable company segments from validated filters so teams can review accounts, run enrichments, score fit, and sync CRM workflows.
- Enrichments
  - [Overview](/enrichments): Enrichments answer research questions about companies and contacts — prebuilt types at per-type prices, custom questions in your own answer shape.

  - **Prebuilt**
  - [Funding](/enrichments/funding): Detect a company's most recent funding round and public/IPO status from just a domain, with investors and cited source URLs.
  - [M&A](/enrichments/mna): Detect whether a company was acquired or made acquisitions in the recent window, with counterparty, deal status, and value where disclosed.
  - [Tech](/enrichments/tech-stack): Detect which ERP or CRM a company uses, or verify a specific technology, from a domain — confirmed with public web evidence, not vendor data alone.
  - [Open Jobs](/enrichments/open-jobs): Summarise what a company is hiring for from public job postings — total openings, function areas, technologies, and locations — from a domain.
  - [Firmographics](/enrichments/firmographics): Return a company's base profile plus a Saber-derived category that refines the coarse public industry tag, with cited web evidence, from a domain.

  - **Custom**
  - [Custom Enrichments](/enrichments/custom): Ask your own structured research question about companies and receive cited AI answers that can power scoring, qualification, and CRM fields.
- Monitors
  - [Monitors](/monitors): Standing watches over your lists or the market that emit signals — occurrences like a changed answer or a detected funding round — over time.
  - [Signals](/monitors/signals): A signal is one real-world occurrence a Monitor detects and emits — a funding round raised, a job posted, an IPO announced.
- Contacts
  - [Contacts](/contacts): Search for people at target accounts, save reusable contact lists, and run AI research enrichments before outreach or CRM sync.
  - [Search Contacts](/contacts/search): Find contacts by person, role, tenure, geography, industry, company size, company type, and recent job change.
  - [Sales Navigator industry values](/contacts/industry-values): Current LinkedIn Sales Navigator industry labels accepted by contact search.
  - [Contact Lists](/contacts/lists): Save contact search results as reusable snapshots for review, contact enrichments, outreach, and CRM workflows.
  - [Contact Enrichments](/contacts/enrichments): Ask structured questions about contacts and receive cited AI answers that support personalization, qualification, and outreach workflows.
- Connectors
  - [Connectors](/connectors): Check which CRM, HubSpot, LinkedIn Sales Navigator, and sales-tool integrations are connected before running Saber workflows.
- Authentication
  - [Authentication](/authentication): Create Saber API keys, send Bearer-token requests, and follow key handling practices for secure production integrations.
- Rate Limits
  - [Rate Limits](/rate-limits): Understand Saber API rate-limit headers, retry behavior, and polling guidance for reliable enrichment, list, and automation workflows.
- Pricing
  - [Pricing](/pricing): Standard credit costs for every metered Saber API operation.
- API Reference
  - [API Reference](/api): Browse the Saber public API reference for company research, contact intelligence, lists, connectors, scoring, and signal workflows.

  - **Enrichments**
  - [Enrichments](/api/enrichments): ## Enrichments

The entity-first successors of signals: `POST
/v1/{companies,contacts}/enrich/custom` run the same research engine at
the same price as custom signals, the prebuilt types (`POST
/v1/companies/enrich/{firmographics,funding,mna,open-jobs,tech-stack}`)
run the prebuilt signal contracts at their own per-type prices, and
every execution is an **enrichment run** you can poll at
`GET /v1/enrichment-runs/{runId}`. The legacy `/signals` paths keep
working (and keep their pricing) until their announced sunset — a
result either surface produced is served from the shared cache, and
your organization never pays twice for the same answer.
  - [Enrichment Templates](/api/enrichment-templates): ## Enrichment templates

A **template** is a user-authored custom question you can reuse across
enrichments (`enrich/custom` accepts a `signalTemplateId`). Templates
are entity-agnostic and free to manage. Distinct from enrichment
*types*, which are system-registered contracts (funding, tech-stack, …).
The legacy `/v1/companies/signals/templates` routes keep working until
their announced sunset.
  - [Summaries](/api/summaries): ## Summaries

A **summary** condenses a company's completed enrichments into one
narrative. Generation is metered (one LLM pass over answers you
already paid for); reads are free. The legacy
`/v1/companies/signals/summaries` routes keep working — and stay free —
until their announced sunset.

  - **Monitors**
  - [Monitors](/api/monitors): ## Monitors

A **monitor** is a standing watch that emits **signals** over time:
watch monitors re-check the entities on one of your lists with an
enrichment template and emit `result_changed` when an answer changes;
discovery monitors watch the market for occurrences (funding raised,
jobs posted, IPO stages). Configuration, lifecycle, and reads are
free — each emitted signal is charged under the `monitor-signals`
feature (see /pricing for the current rate; silent no-change watch
runs are free). The legacy `/v1/companies/signals/subscriptions` and
`/v1/market-signals` routes keep working (and keep their pricing)
until their announced sunset.

  - **Contacts**
  - [Contacts](/api/contacts): ## Contacts

Open-ended contact research (an AI-written dossier from a LinkedIn
profile) and live contact search over Sales Navigator.

  - **Legacy (deprecated)**
  - [Signals](/api/signals): ## Signals

A **signal** is an AI-powered research request that answers a specific
question about a company or contact. Saber researches the target,
verifies findings against public sources, and returns a structured
answer with confidence scores and citations.

**Prebuilt signals** answer the most common company questions from just
a domain — no question or answer type to design:

| Signal | Key | Answers |
|---|---|---|
| [Funding](/signals/funding) | `funding` | Most recent funding and public/IPO status |
| [M&A](/signals/mna) | `mna` | Whether the company was acquired or made acquisitions |
| [Tech](/signals/tech) | `tech` | Which ERP/CRM it uses, or whether it uses a specific technology |
| [Open Jobs](/signals/open-jobs) | `open-jobs` | What the company is currently hiring for |
| [Firmographics](/signals/firmographics) | `firmographics` | Base profile plus a refined Saber category |

Each is available **async** (`POST /v1/signals/{key}` — returns a
`processing` signal to poll or receive via `webhookUrl`) and **sync**
(`POST /v1/signals/sync/{key}` — blocks until the result is ready;
recommended for interactive and agent workflows). Every completed
answer is a `json_schema` payload conforming to the signal's documented
answer schema. **Cost:** 2 credits per run.

**[Custom signals](/signals/custom)** ask your own question in your own answer shape —
supply `question`, `answerType`, and optionally `outputSchema` to
`POST /v1/companies/signals/sync` (company) or
`POST /v1/contacts/signals/sync` (contact), with async and batch
variants below. Supported answer types: text, numbers, booleans, lists,
percentages, currency, URLs, and contacts.

**Reading results:** prebuilt and custom company signals share the same
read path — poll [`GET /v1/companies/signals/{signalId}`](#get-a-company-signal-by-id),
list signals with filtering, or supply a `webhookUrl` on create to have
the completed signal delivered to your endpoint.

Guides for every signal live in the [Signals section](/signals).
  - [Signal Templates](/api/signals-templates): ## Signals Templates

Create reusable signal templates to standardize your research questions across multiple companies.

**Benefits:**
- Consistent research questions across your organization
- Reuse qualification criteria and answer types
- Efficient batch signal creation
- Version control for your research methodology

**Workflow:**
1. Create a template with your question and criteria
2. Use the template ID when creating signals (or in batch requests)
3. Update templates as needed - changes create new versions
4. Delete templates when no longer needed (soft-delete for history)

Templates support all answer types (text, number, boolean, list, etc.) and
qualification criteria to automatically score companies based on their answers.
  - [Signal Subscriptions](/api/signal-subscriptions): ## Signal Subscriptions

Subscriptions schedule recurring signal executions against a signal template.
Each subscription ties a template to a frequency, timezone, and optional
targeting (list or domain).

**Lifecycle:**
1. Create a subscription via `POST /v1/companies/signals/subscriptions`
   (references an existing template or creates one inline)
2. Activate it with `POST /v1/companies/signals/{signalId}/start`
3. Optionally update schedule parameters via `PUT .../subscriptions/{id}`
4. Pause with `POST /v1/companies/signals/{signalId}/stop`

The response merges the template definition with the schedule configuration
so you get the full picture in a single object.
  - [Subscription Actions](/api/subscription-actions): ## Subscription Actions

Actions define delivery mechanisms for subscription results. Each action
specifies where and how signal outputs should be sent when the subscription
triggers.

**Supported action types:**
- `webhook` — Deliver results to an HTTP endpoint

Multiple actions of the same type are allowed on a single subscription,
up to a maximum of **10 actions** per subscription.

> **Note:** Subscription action webhooks are currently delivered without
> HMAC signatures. Do not rely on request signatures to authenticate
> incoming payloads from subscription actions.
  - [Signal Summaries](/api/signals-summaries): ## Signals Summaries

Generate AI-powered summaries that consolidate insights from multiple signals into
structured, actionable data points.

**Use cases:**
- Create company profiles from multiple research signals
- Generate qualification scorecards
- Build comprehensive intelligence reports
- Track changes over time

**How it works:**
1. Create multiple signals for a domain
2. Wait for signals to complete (or use batch with `generateSummaryOnComplete: true`)
3. Request a summary via POST `/v1/companies/signals/summaries`
4. Retrieve the summary with structured data points and qualifications

Each data point includes:
- Description of the insight
- Reference questions used
- Qualification score (disqualified → excellent)
- Supporting sources with URLs and snippets

Summaries can be automatically generated when batch signals complete, making it easy
to research multiple companies in parallel.
  - [Market Signals](/api/market-signals): ## Market Signals

Market Signals let you set up automated monitoring subscriptions that continuously scan external data
sources and deliver matching signals to your webhook.

**Supported signal types:**

| Type | What it monitors |
|---|---|
| `JOB_POSTS` | New job postings matching title, skill, company, and location criteria |
| `LINKEDIN_POST` | LinkedIn posts matching keyword and AI-based persona/content filters (requires Sales Navigator) |
| `FUND_RAISED` | Fund closings and fundraising events (web news + RSS + SEC EDGAR Form D) |
| `RECENT_INVESTMENT` | Recent investment rounds and funding announcements (web news + RSS) |
| `IPO` | IPO filings and public listing announcements (web news + RSS; for filing-derived coverage use `IPO_LIFECYCLE`) |
| `IPO_LIFECYCLE` | Deterministic US IPO lifecycle events — filing, amendment, pricing, prospectus, listing, Form 5500 (SEC EDGAR + newswires + DOL EFAST) |

**Typical workflow:**

1. `POST /v1/market-signals/subscriptions` - Create a subscription with type, filters, and webhook URL
2. Subscription automatically polls on the configured interval (daily or weekly)
3. New matching signals are delivered to your webhook as batched payloads
4. `GET /v1/market-signals/subscriptions/{id}/signals` - Browse delivered signals
5. Use pause/resume/trigger endpoints to control the subscription lifecycle

**AI-powered filter generation (JOB_POSTS):**

Instead of manually defining filters, you can provide a natural language `prompt` and the AI
will generate complete filter configurations. You can also combine a prompt with partial filters
for hybrid mode, where the AI augments your filters with additional criteria inferred from
the prompt.

**LinkedIn integration:**

LINKEDIN_POST subscriptions require a connected LinkedIn Sales Navigator account via the
Saber Chrome extension. The subscription uses boolean keyword search combined with AI-based
content quality and persona/company filtering to surface high-relevance posts.

  - **Lists**
  - [Company Lists](/api/company-lists): ## Company Lists

Company Lists let you build and manage curated sets of companies based on
filter criteria such as industry, size, location, and more.

**Typical workflow:**
1. `POST /v1/companies/search` — preview up to 50 companies matching a filter (no list created)
2. `POST /v1/companies/lists` — save the filter as a named list
3. `GET /v1/companies/lists/{listId}/companies` — page through matching companies
4. `PUT /v1/companies/lists/{listId}` — update the list name or filter
5. `DELETE /v1/companies/lists/{listId}` — remove the list

**Caching:** Results are cached for 5 minutes per unique filter and caller.
Write operations (create, update, delete) automatically invalidate the cache
for the authenticated caller.
  - [Contact Lists](/api/contact-lists): ## Contact Lists

Contact Lists let you capture a snapshot of people at a company who match specific criteria — job titles, keywords, and/or countries — using LinkedIn Sales Navigator.

**Typical workflow:**
1. `POST /v1/contacts/lists` — provide a company LinkedIn URL and at least one filter; the API runs a live Sales Navigator search and stores the results as a snapshot
2. `GET /v1/contacts/lists/{listId}/contacts` — page through the stored contacts at any time, no new Sales Navigator call needed
3. `GET /v1/contacts/lists` — list all your saved contact lists
4. `PUT /v1/contacts/lists/{listId}` — rename a list
5. `DELETE /v1/contacts/lists/{listId}` — remove a list and its contacts

**What gets stored:**
Each contact in the list is stored as a point-in-time snapshot including name, role, company, location, headline, seniority, positions, avatar, and Sales Navigator profile URL. The snapshot reflects what Sales Navigator returned at creation time and is not updated automatically.

**Sales Navigator requirement:**
Creating a list requires a LinkedIn Sales Navigator connection on your account. If Sales Navigator is not connected, the `POST` returns a connector error and no list is created. Reading existing lists (`GET`) works regardless of connector status.

  - **Platform**
  - [Companies](/api/companies): ## Companies

Company search returns blurred previews for free; revealing companies
is priced through list creation (quoted up-front by count-preview).
  - [Billing](/api/billing): ## Billing

Credit balance reads. Per-operation credit costs are annotated on each
operation (`x-credit-cost`) and listed on the Pricing page.
  - [Connectors](/api/connectors): ## Connectors

Connectors are integrations that link your CRM and sales tools to Saber, enabling enriched
research and automated data syncing.

Use this section to list all configured connectors and inspect their connection status.
This is useful for verifying that the integrations your workflows depend on are active before
running signals or batch operations.

**Supported connectors:**
- **LinkedIn Sales Navigator** (`salesNavigator`) — Contact search and profile enrichment
- **HubSpot App** (`hubspotApp`) — OAuth-based HubSpot marketplace app installation
  - [Organization](/api/organisation): ## Organisation

Read and update your organisation's profile data: name, website, and description fields
(general overview, products, use cases, value proposition).

This endpoint is designed for use with the Saber CLI and MCP server so that tools like
AI coding assistants can automatically pull in your organisation context and use it when generating
outreach, research summaries, or signal queries — without requiring manual copy-paste.
  - [Scoring](/api/scoring): ## Native scoring framework

Configure how Saber turns signal results into structured, explainable **fit** and
**urgency** scores (0–100) for companies and contacts. Scoring sits on top of the
signal layer — the engine is signal-agnostic, so any data the signal layer can ingest
becomes scoreable.

### How it fits together

1. **Profile** — a named, org-scoped configuration bound to a single object type
   (`company` or `contact`). E.g. *"EMEA Enterprise"*, *"Mid-Market SaaS"*. A single
   object can be assigned multiple profiles of the matching type.
2. **Rule** — within a profile, maps one signal template to point values for one
   dimension (`fit` or `urgency`). The shape of `pointValues` depends on the signal's
   answer type (boolean, number/percentage/currency ranges, or list choices).
3. **Assignment** — links a profile to a specific company or contact. Triggers an
   immediate recompute so the score appears without waiting for the next signal run.
4. **Score result** — the computed score for one `(profile, object, dimension)`
   triple. Includes a per-rule contribution breakdown so the number is always
   explainable, plus the previous score for delta views.

### Computation semantics

Score is `(earned / maxPossible) * 100`. **All rules in a profile/dimension count
toward the denominator regardless of whether a signal answer exists** — unanswered
rules earn 0 points but their max still counts. This keeps low-coverage scores
conservatively low so they don't falsely look high. `signalCoverage` and `totalRules`
are returned alongside the score so consumers can see how complete it is.

### When scores recompute

In v1 scoring is manual-trigger:

- Assigning a profile to an object → immediate recompute
- Upserting or deleting a rule → recompute every object assigned to the profile
- Calling `POST /v1/scoring/compute` directly

Auto-trigger on signal completion is on the v1.5 roadmap.
  - [Email Finder](/api/email-finder): ## Email Finder API

Resolve a verified email address for a contact when you know their
full name and the domain of their employer. Functional parity with
the equivalent Findymail endpoint so existing integrations can swap
providers with minimal client-side change.

### How it works

Saber maintains a global, hit-counted pattern store. Common
corporate email shapes (`{first}.{last}`, `{first}{last}`,
`{f}{last}`, etc.) are tried in order of historical success at the
requested domain — when a known pattern verifies, the lookup
returns in ~1 second. Domains we've never seen before fall through
to a parallel sweep of every common template against the
verification engine, finding a match in ~2-5 seconds.

### Pricing & rate limits

v1 endpoint is unmetered (no per-call credit charge). Standard
`/public/v1` rate limits apply.

### What we store

The pattern templates themselves (e.g. `{first}.{last}`) are
cached server-side for future warm-path lookups. The returned
email and the contact name are **never** persisted by Saber — the
response is the only place they appear, and you're responsible
for storing them if your application needs them.
- CLI
  - [Saber CLI](/cli): Run Saber signal research, list management, scoring, connector checks, and credit inspection from a terminal, CI job, or agent session.
  - [Installation](/cli/installation): Install the Saber CLI on macOS or Linux, verify the binary, and prepare your shell for repeatable API-driven workflows.
  - [Authentication](/cli/authentication): Configure the Saber CLI with an API key, verify login state, and understand how local credentials map to Saber access.
  - [Command Reference](/cli/commands): Browse the main Saber CLI command families, global flags, and examples for signals, lists, templates, scoring, connectors, and org context.
  - [Workflows](/cli/workflows): Follow practical Saber CLI workflows for company research, list building, reusable templates, scoring, and CRM-oriented automation.
  - [JSON and CI](/cli/ci-json): Use machine-readable Saber CLI output in scripts, CI jobs, and agent workflows without exposing API keys in shared logs.
  - [Troubleshooting](/cli/troubleshooting): Resolve common Saber CLI authentication, API-key, network, JSON output, and rate-limit issues during local or CI usage.
- MCP Server
  - [MCP Server](/mcp): Connect Saber sales intelligence tools to MCP-compatible AI clients so assistants can research companies and contacts directly.
  - Getting Started
    - [Installation](/mcp/getting-started/installation): Connect Claude Code, Cursor, or another Streamable HTTP MCP client to the hosted Saber MCP server and authorize with your API key.
    - [Basic Usage](/mcp/getting-started/basic-usage): Try practical Saber MCP examples for company research, contact discovery, enrichment checks, and account intelligence inside an AI assistant.
  - Capabilities
    - [Capabilities](/mcp/capabilities): Browse the Saber MCP Server tool categories for company enrichments, contact intelligence, account management, and reusable templates.
    - [Company Enrichments](/mcp/capabilities/company-enrichments): Use Saber MCP company enrichment tools to ask structured research questions and retrieve cited AI answers about target accounts.
    - [Enrichment Templates](/mcp/capabilities/enrichment-templates): Use Saber MCP template tools to create and manage reusable question sets for standardized research across a team.
    - [Contact Intelligence](/mcp/capabilities/contact-intelligence): Use Saber MCP contact tools to find people at target accounts, run contact research, and retrieve profile-level enrichment answers.
    - [Account Management](/mcp/capabilities/account-management): Use Saber MCP account-management tools to check connector status and monitor API credit balance before large workflows.
  - [Prompts](/mcp/prompts): Use built-in Saber MCP prompt templates for common sales intelligence workflows such as company research and contact enrichment.
  - [Resources](/mcp/resources): Read the MCP resources exposed by Saber, including the assistant-facing guide to available tools and recommended workflows.
- Skills
  - [Saber Skills](/skills): Use open-source GTM workflow skills that help AI agents research markets, build lists, activate signals, and manage sales motions.
  - [Installation](/skills/installation): Install Saber Skills for Codex, Claude Code, Cursor, Gemini CLI, or another agent, then connect the CLI or MCP server for richer workflows.
  - [Catalog](/skills/catalog): Browse Saber Skills by GTM motion, including market research, list building, signal activation, outreach, CRM sync, and pipeline workflows.
  - [Workflows](/skills/workflows): Understand how Saber Skills hand off between ICP discovery, signal generation, account research, outreach, and CRM sync workflows.
  - [Skills and CLI](/skills/cli): See how Saber Skills use the CLI for authenticated signal research, list management, scoring, and CRM workflows when it is available.
  - [Authoring Skills](/skills/authoring): Guidance for contributing a Saber Skill.
  - Skill Reference
    - [Skill Reference](/skills/reference): Every Saber Skill, grouped by the GTM workflow it supports.
    - [build-account-list](/skills/reference/build-account-list): Build a target account list and run company signals against it. Works with the Saber CLI, Apollo, HubSpot, or any available prospecting tool — with a manual fallback.
    - [build-contact-list](/skills/reference/build-contact-list): Build a target contact list and run contact-level signals against them. Works with the Saber CLI, Apollo, LinkedIn, HubSpot, or manual research.
    - [build-sequence](/skills/reference/build-sequence): Design a multi-step outreach sequence (email + LinkedIn) with messages personalised using Saber signal results and timing tied to signal triggers.
    - [competitive-intel](/skills/reference/competitive-intel): Map the competitive landscape for a target market — identify competitors, compare positioning, surface common objections, and build battle cards for your sales team.
    - [create-company-signals](/skills/reference/create-company-signals): Activate company-level signal tracking. Runs signals via the Saber CLI if available; without it, outputs a research playbook and suggests alternative tracking methods.
    - [create-contact-signals](/skills/reference/create-contact-signals): Activate contact-level signal tracking using the Saber CLI — creates signals for contacts in a contact list.
    - [deal-coaching](/skills/reference/deal-coaching): Analyse a deal in progress — assess health, identify risks, map the buying committee, and recommend specific next steps to move it forward.
    - [enrich-contacts](/skills/reference/enrich-contacts): Find and add contact information (email, phone) to a Saber contact list using available enrichment providers such as Apollo or Cognism. Detects available MCPs and CLIs automatically.
    - [extract-icp](/skills/reference/extract-icp): Research a company domain and extract a structured Ideal Customer Profile (ICP) — including target company profile, buying committee, pain points, buying triggers, and existing customers.
    - [find-expansion-accounts](/skills/reference/find-expansion-accounts): Identify existing customers showing buying signals for upsell or cross-sell opportunities. Works with Saber, HubSpot, or any available customer data source.
    - [generate-signals](/skills/reference/generate-signals): Generate 12–15 structured, weighted research signals from a structured ICP, ready to activate in Saber. Each signal includes answer type, weight, and interpretation rules for automatic scoring.
    - [import-from-hubspot](/skills/reference/import-from-hubspot): Pull a HubSpot company list, view, or segment into Saber as a target account or contact list, ready for signal activation.
    - [manage-signals](/skills/reference/manage-signals): View, pause, resume, and adjust your active Saber signal subscriptions.
    - [market-map](/skills/reference/market-map): Map a target market — size, segments, key players, adjacent verticals, and entry points. Helps GTM teams understand the landscape before building lists or running signals.
    - [objection-handler](/skills/reference/objection-handler): Build or extend an objection library for your ICP — common objections mapped to the real concern underneath, with response frameworks your team can use in live deals.
    - [persona-research](/skills/reference/persona-research): Build a deep profile of a buying persona — motivations, challenges, buying behaviour, language they use, and where to find them. Helps reps understand who they're selling to before they reach out.
    - [pipeline-review](/skills/reference/pipeline-review): Audit pipeline health from CRM data — identify at-risk deals, surface stalled opportunities, flag forecast risk, and recommend where to focus.
    - [qualify-inbound](/skills/reference/qualify-inbound): Qualify an inbound lead by running your defined signals against their company domain and producing a scored qualification summary.
    - [research-account](/skills/reference/research-account): Deep research on a single company — signals, hiring, news, tech stack, and LinkedIn presence. Uses the Saber CLI for signal data and any available MCP tools for broader research.
    - [score-accounts](/skills/reference/score-accounts): Score and rank a list of accounts by signal strength to surface the highest-priority targets for outreach. Works with Saber signal results, Apollo data, HubSpot properties, or any pasted signal data.
    - [signal-discovery](/skills/reference/signal-discovery): Guided entry point for defining your ICP and buying signals — runs extract-icp then generate-signals in sequence. Start here before creating signals or building lists.
    - [sync-to-hubspot](/skills/reference/sync-to-hubspot): Push Saber signal results back to HubSpot as contact or company properties, keeping your CRM up to date with the latest intent data.
    - [write-outreach](/skills/reference/write-outreach): Write personalised cold outreach — email and LinkedIn — using Saber signal results and contact data as personalisation context.
- Changelog
  - [Changelog](/changelog): Product updates, API changes, deprecations, maintenance notices, and other important Saber changes.
  - [Contact search consistently names the newest current role](/changelog/2026-08-31-contact-search-newest-current-role): For people with several current positions, role and companyName now come from the position with the latest start date.
  - [Contact search says if a position is a recent move](/changelog/2026-08-26-contact-search-move-classification): Each current position in contact search now returns moveType, inferred from role tenure and company tenure.
  - [Contact search adds mover and firmographic filters](/changelog/2026-08-20-contact-search-mover-and-firmographic-filters): Contact search can filter by recent job change, tenure, industry, company headcount, and company type, and returns both supplier tenure values for each current position.
  - [Email Finder and company signal reliability updates](/changelog/2026-07-28-email-finder-and-company-signal-reliability): Email Finder now separates retryable results from definitive misses, while company signals apply stricter evidence rules and preserve structured registry data.
  - [Safer signal answers and source matching](/changelog/2026-07-21-safer-signal-answers-and-source-matching): Saber now keeps refreshed signal answers aligned with their current evidence, refuses obvious namesake-domain sources, and retries transient model-capacity failures across EU endpoints.
  - [Technology-filtered list builds handle duplicate job data](/changelog/2026-07-20-technology-list-duplicate-job-handling): Technology-filtered company list builds now deduplicate repeated job postings before saving them, preventing those builds from aborting.
  - [Pricing, subscription, and webhook updates](/changelog/2026-07-16-pricing-subscription-and-webhook-updates): Saber now publishes complete API credit pricing, shows when canceled plans end, and documents direct signal webhook delivery behavior.
  - [Saber CLI adds prebuilt signal commands and fractional credit support](/changelog/2026-07-09-saber-cli-prebuilt-signals-and-fractional-credits): Saber CLI v0.1.13 adds commands for five prebuilt company signals, contact-search filters, subscription output schemas, and support for fractional credit balances.
  - [More reliable Sales Navigator access detection](/changelog/2026-07-09-sales-navigator-access-reliability): Saber now avoids disconnecting LinkedIn connectors that do not have a Sales Navigator seat and can recover stale access flags from the live connector session.
  - [Five prebuilt company signals](/changelog/2026-07-08-five-prebuilt-company-signals): Saber now provides documented prebuilt signals for funding, M&A, technology, open jobs, and firmographics, each with a stable structured response.
  - [Bulk Email Finder API](/changelog/2026-07-08-bulk-email-finder-api): Email Finder now accepts asynchronous batches of up to 1,000 contacts and returns explicit found, not-found, and row-level error statuses.
  - [Email Finder single calls now use fractional credits](/changelog/2026-07-08-email-finder-fractional-credit-billing): A single Email Finder request now costs 0.1 credits when Saber performs verification work, while validation and pre-filtered requests remain free.
  - [IPO signals now include SEC S-1 and F-1 filings](/changelog/2026-07-08-sec-filing-coverage-for-ipo-signals): IPO market signals now discover official SEC EDGAR S-1 and F-1 filings and can be filtered to filing-only results.
  - [More reliable MCP tool setup and sessions](/changelog/2026-07-08-mcp-tool-setup-and-session-reliability): Saber MCP now handles a wider range of OpenAPI input schemas during tool setup and uses bounded memory for stateful sessions.
  - [More accurate company matching across domains and brands](/changelog/2026-07-08-more-accurate-company-matching): Saber improved company identity matching for shared domains, sub-brands, foreign domains, and companies with the same name.
  - [More reliable long-running signals and large batches](/changelog/2026-06-24-long-running-signals-and-batches): Long-running signals and large batches now have aligned workflow, credit, and cleanup time budgets, with faster indexed company lookups.
  - [Faster technology-based company list reads and exports](/changelog/2026-06-16-faster-technology-based-company-lists): Company lists built with technology filters now read and export from the materialized match set instead of scanning a broad firmographic result set.
  - [Signal failures are now returned in the response body](/changelog/2026-06-12-signal-failures-now-returned-in-the-response-body): The Signals API now returns HTTP 200 for any retrievable signal, including failed ones, and conveys failure in the response body with a new retryable field instead of a 422 or 500 status code.
  - [API docs, contact lookup, and HubSpot sync updates](/changelog/2026-06-11-api-docs-contact-lookup-and-hubspot-sync): Saber fixed direct access to API docs, updated contact lookup identity handling, and tightened HubSpot sync and API validation behavior.
  - [More reliable signal creation and source coverage](/changelog/2026-05-29-signal-creation-timeouts-and-source-coverage): Saber improved signal creation reliability for long-running requests and expanded company research coverage for commonly requested business sources.
  - [Contact research, docs routing, and connector reliability](/changelog/2026-05-28-contact-research-docs-routing-and-connector-reliability): Saber added contact-level research lookups, improved public docs routing, and made Sales Navigator connector sessions more resilient.
  - [Email Finder API](/changelog/2026-05-21-email-finder-api): Saber added an Email Finder API so teams can programmatically enrich contacts with verified email discovery workflows.
  - [More reliable MCP streaming sessions](/changelog/2026-05-21-more-reliable-mcp-streaming-sessions): Saber MCP streaming sessions now stay connected more reliably when clients or networks leave server-sent event streams idle.
  - [HubSpot panel account summaries](/changelog/2026-05-20-hubspot-panel-account-summaries): The Saber browser extension now adds account summaries to the HubSpot panel, making it easier for sellers to understand account context before reviewing individual signals.
  - [Public docs portal](/changelog/2026-05-20-public-docs-portal): Saber launched a public docs portal with product guides, API documentation, MCP resources, CLI documentation, skills guidance, and changelog-ready static publishing.
  - [Browser extension signal feed for HubSpot](/changelog/2026-05-18-browser-extension-signal-feed-and-hubspot-panel): The Saber browser extension now shows relevant company signals directly in HubSpot, so sales teams can review account context without leaving the CRM.
  - [Browser extension side panel](/changelog/2026-05-12-browser-extension-side-panel-launch): The browser extension now opens as an in-page side panel, giving teams more space to review Saber context while they work in supported sales tools.
  - [Department and seniority filters for contact search](/changelog/2026-05-03-contact-search-department-and-seniority-filters): Contact search now supports department and seniority filters, helping teams find the right buying roles faster.
  - [Signal scoring for account prioritization](/changelog/2026-05-01-signal-scoring-for-account-prioritization): Saber added scoring support so teams can rank accounts and contacts by signal strength instead of reviewing every result manually.
  - [Browser extension v2](/changelog/2026-04-30-browser-extension-v2): Saber shipped a refreshed browser extension experience with improved sign-in behavior and more reliable access to Saber context in supported tools.
  - [Scoring support for API and HubSpot users](/changelog/2026-04-29-scoring-support-for-api-and-hubspot-users): Scoring became available to API and HubSpot-connected teams, helping customers bring Saber prioritization into their existing systems.
  - [Clearer rate limits and billing reconciliation](/changelog/2026-04-23-rate-limit-and-billing-reconciliation-updates): Saber improved usage visibility for API and billing activity, making it easier for teams to understand limits, credits, and checkout state.
  - [HubSpot deal stage triggers](/changelog/2026-04-20-hubspot-deal-stage-triggers): HubSpot-connected teams can now use deal stage changes as a trigger for Saber activity, keeping sales intelligence aligned with deal movement.
  - [Stronger account security controls](/changelog/2026-04-09-stronger-account-security-controls): Saber added stronger controls for account access and sign-in, improving protection for customer workspaces.
  - [Legacy research and messaging surfaces retired](/changelog/2026-04-03-legacy-research-and-messaging-surfaces-retired): Older research and messaging pages were removed so customers use the current Saber experience for account signals, contact signals, and outreach.
  - [Market signal detail pages](/changelog/2026-04-02-market-signal-detail-pages): Market signals now have clearer detail pages so teams can inspect context, evidence, and results before acting on a signal.
  - [Invoices and credits for market signals](/changelog/2026-03-26-billing-invoices-and-market-signal-credits): Workspace owners can now review invoice and credit activity tied to market signal usage more clearly.
  - [Saber CLI sign-in and command updates](/changelog/2026-03-16-saber-cli-sign-in-and-command-updates): The Saber CLI gained more reliable sign-in and command behavior for customers who use Saber from local terminals or agent tools.
  - [Market signals for news, filings, IPOs, and RSS](/changelog/2026-03-12-market-signals-for-news-filings-ipos-and-rss): Saber added market signal coverage for news, company filings, IPO activity, and RSS sources.
  - [Scheduled signals and contact lists](/changelog/2026-03-03-scheduled-signals-contact-lists-and-subscription-actions): Teams can now monitor companies and contacts on a recurring schedule, with clearer controls for subscriptions and contact lists.
  - [Saber MCP support for more clients](/changelog/2026-02-27-multiple-mcp-clients-and-smithery-readiness): Saber MCP support expanded to more client environments, making Saber easier to connect to agent tools.
  - [Contact engagement signals](/changelog/2026-02-24-contact-engagement-signals): Saber added contact engagement signals so teams can identify relevant buyer activity at the person level.
  - [Saber MCP and public signal endpoints](/changelog/2026-02-20-saber-mcp-and-public-signal-endpoints): Developers can connect Saber signals to external tools through MCP and public API endpoints.
  - [Batch signals for large account lists](/changelog/2026-02-15-async-batch-signals-for-large-lists): The Signals API can now handle larger account lists asynchronously, making high-volume signal runs easier to manage.
  - [HubSpot field mapping for completed signals](/changelog/2026-02-06-hubspot-field-mapping-for-signal-completion): HubSpot-connected teams can map completed Saber signal results back into CRM fields more easily.
  - [More structured signal results](/changelog/2026-01-23-structured-signal-results): Saber made signal results more structured, helping API customers use results more consistently in external systems.
  - [LinkedIn post market signals](/changelog/2026-01-09-linkedin-post-market-signals): Saber added LinkedIn post signals so teams can monitor relevant public activity from accounts and buyers.
  - [Hiring signals for company research](/changelog/2025-12-31-job-search-evidence-for-company-signals): Saber improved hiring and job-posting signals so teams can better identify companies showing growth or hiring intent.
  - [Market Signals API early access](/changelog/2025-12-18-public-developer-docs-and-market-signals): Saber introduced early Market Signals API access for teams that want to retrieve and monitor market signals programmatically.
  - [Run Saber signals from HubSpot](/changelog/2025-11-26-run-saber-signals-from-hubspot): HubSpot users can run Saber signals from inside HubSpot and review richer signal summaries in the CRM.
  - [Reusable signal templates](/changelog/2025-11-18-signal-templates-and-diffs): Saber added reusable signal templates and clearer change tracking, helping teams keep signal definitions consistent.
  - [Easier asynchronous signal results](/changelog/2025-11-12-easier-asynchronous-signal-results): The Signals API can now return results more smoothly for longer-running signal requests.
  - [API keys and Signals API](/changelog/2025-10-29-api-keys-and-signals-api): Developers can create API keys and use the Signals API to connect Saber signals to external tools.
  - [API access for Saber signals](/changelog/2025-10-20-api-keys-and-signals-functionality): Saber introduced the first API access needed for customers to use signals outside the web app.
  - [Webhook delivery logs and manual triggers](/changelog/2025-09-29-webhook-delivery-logs-and-manual-triggers): Developers can inspect webhook delivery history and manually trigger webhook deliveries when testing or troubleshooting integrations.
  - [List prompts and research activity](/changelog/2025-09-18-list-prompting-and-research-activity-stream): Saber made list-based research easier to guide and added clearer activity history for research sessions.
  - [Self-serve onboarding and faster enrichment](/changelog/2025-08-29-self-serve-onboarding-and-faster-enrichment): New teams can get started with Saber more easily, and enrichment runs return results faster.
  - [Account research history and editable outreach](/changelog/2025-08-11-account-research-history-outreach-and-integrations): Saber added saved account research history, editable outreach, and clearer integration controls for sales teams.
  - [Salesforce connector settings and webhooks](/changelog/2025-07-23-salesforce-connector-settings-and-webhooks): Salesforce-connected teams gained clearer connector settings, account sync support, and webhook options.
  - [Salesforce and CRM sync improvements](/changelog/2025-06-26-salesforce-and-crm-sync-improvements): Saber improved Salesforce and CRM syncing so connected teams can keep account and contact data more consistent.
  - [Shared research templates](/changelog/2025-06-16-shared-research-templates): Teams can use shared research templates to keep account research consistent across users and use cases.
  - [Territory settings and source freshness](/changelog/2025-05-29-territory-and-source-freshness-improvements): Saber added territory-aware search improvements and clearer source freshness indicators for account research.
  - [Personalized outreach and HubSpot sync](/changelog/2025-04-25-personalized-outreach-and-hubspot-sync): Saber improved personalized outreach, added more language support, and made HubSpot sync more useful for sales teams.
  - [Use case library and account overview improvements](/changelog/2025-04-03-use-case-library-and-account-overview): Saber added a use case library and improved account overview pages so teams can start research faster.
  - [Contact research, Sales Navigator search, and preferred sources](/changelog/2025-03-26-contact-research-sales-navigator-and-preferred-sources): Saber improved contact research with Sales Navigator search support, preferred sources, and better contact profile context.