> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lusha.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Score contacts and companies by signal activity

> Turn active buying signals into a single [0, 1] score per contact or company, with the signal breakdown behind it - up to 100 records per call.

Signal Score collapses a record's active buying signals into one number you can sort and threshold on. Where [Signals](https://docs.lusha.com/signals/overview.md) tells you *what* is happening, Signal Score tells you *how much* is happening - so you can rank a list rather than read it.

Every score comes with the signal breakdown behind it, so a high score is always explainable.

> [card] [Score Contacts](https://docs.lusha.com/api-reference/signals/score-contacts-by-signal-activity.md)
>
> `POST /v3/contacts/signal-score` - up to 100 contacts per call.

> [card] [Score Companies](https://docs.lusha.com/api-reference/signals/score-companies-by-signal-activity.md)
>
> `POST /v3/companies/signal-score` - up to 100 companies per call.

## The score

`signalScore` is a value in `[0, 1]` reflecting the fraction of the record's active signals. Alongside it you get:

* `signalTypes` - the active signal breakdown
* `noActiveSignals` - set when the record resolved but has nothing currently firing

## Identifying records

Identity is resolved server-side before scoring. **This is identity resolution only - no PII is revealed and no enrichment credits are spent on it.**

> [tab] Contacts
>
> Provide one of:
>
> * `id` - encrypted Lusha contact ID
> * `linkedinUrl`
> * `email`
> * `firstName` + `lastName` + (`companyName` or `companyDomain`)

> [tab] Companies
>
> Provide exactly one of:
>
> * `id`
> * `domain`
> * `name`
> * `email`

## Reading the results

Each entry in the response is one of three outcomes:

| Outcome | Meaning |
| - | - |
| **Scored** | `signalScore`, `signalTypes`, and `noActiveSignals` are populated. |
| **`NOT_FOUND`** | Identity resolution failed for the identifier you supplied. |
| **`NO_SCORE`** | The record resolved, but the scoring engine returned nothing for it. |

> [!NOTE]
>
> `NOT_FOUND` and `NO_SCORE` mean different things and deserve different handling. `NOT_FOUND` is an identifier problem worth retrying with a better identifier; `NO_SCORE` means the record is genuinely unscored right now.

## Billing

1 credit is charged per scored record. Entries returned as `NOT_FOUND` or `NO_SCORE` are not charged.

## Related pages

* [Signals overview](https://docs.lusha.com/signals/overview.md) - the underlying signal types
* [Contact signals](https://docs.lusha.com/signals/contact-signals.md) and [company signals](https://docs.lusha.com/signals/company-signals.md)
* [ICP Fit Score](https://docs.lusha.com/icp-fit-score/overview.md) - score the same records by fit to your Target Profiles
* [Buying Group](https://docs.lusha.com/buying-group/overview.md) - who to contact once you've picked the account


## Related topics

- [Score Contacts by Signal Activity](https://docs.lusha.com/api-reference/signals/score-contacts-by-signal-activity.md)
- [Detect contact and company signals with Lusha](https://docs.lusha.com/signals/overview.md)
- [Score Companies by Signal Activity](https://docs.lusha.com/api-reference/signals/score-companies-by-signal-activity.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.