The live scoring API

What it represents

The live scoring API scores a record at the moment it arrives, instead of waiting for the next scheduled run. There are two ways in: a batch endpoint that takes an array of records, and a single-record webhook endpoint that suits form handlers and automation tools.

You mint keys in the product, and you enable API access per scoring route, so a score is only reachable over the API when you have said it should be.

How it’s calculated

A request carries a key and the field values for the record. The model scores it exactly as a scheduled run would. The single-record endpoint returns the score with its band; the batch endpoint returns a score per record and takes up to 1,000 records at a time. Ask for reasons on either and the top factors come back with the scores.

Usage is metered monthly against your plan’s included allocation, and the meter in the product shows where you stand. Going over does not cut you off at the line: scoring continues through a grace band up to twice your included amount, and only then does the API return an over-limit response. Free tier, with no included allocation, stops at zero.

Test keys are a separate flavor with their own cap, so integration work does not eat your live allocation.

Cold records get an honest answer rather than a padded one. The batch response marks each record as enriched or not. Send a record flagged as new, or one with no CRM id, and it comes back not enriched: it was scored on the fields in your request and nothing else. A record with history here has its stored features merged in first, and comes back with its previous score and the change since. Nothing is invented to make a thin record look better informed than it is.

What it means for you

Worked example: you post 200 records in one batch. Most carry ids ax1om has scored before and return enriched, with a previous score and a delta. Twenty are flagged new and return at face value, one of them at 63 and not enriched. That 63 is real, and it is thin. Routing it to a rep is reasonable. Treating it as equivalent to a 63 on a record with two years of engagement behind it is not.

Use the flag. It is the difference between a system that tells you how much it knows and one that hides it.