For RevOps: the enrichment waterfall and ICP fit, as one API

The waterfall, routed

• Company first, by domain. Most of what decides fit is about the company. A person lookup runs only when you ask for person fields.
• A second vendor only when the first falls short — no match, an error, or under half the fields. Vendors bill per match, so the default never pays twice for the same hit.
• One vocabulary. Every vendor’s industry, seniority and department is mapped into the same closed lists, so “director and above in fintech” means one thing regardless of who answered.
• Cached for 30 days. The same company is not bought twice in a month.
• A receipt per vendor on every response: who was asked, what they returned, how long it took, what it cost.

curl -X POST https://api.sortance.com/v1/enrich \
  -H "Authorization: Bearer $SORTANCE_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "email": "mia@acme.com", "context": { "fields": ["person", "company"], "max_cost_usd": 0.5 } }'

The response is one profile shape whichever vendor answered, with coverage telling you how much of what you asked for came back. Treat a profile at coverage 0.2 as what it is.

ICP fit is a rubric you can argue with

Describe your ideal customer in a paragraph. Sortance drafts it into weighted criteria — industry 30 points, 50–500 employees 25, director or above 20 — and you edit and confirm them. The score is that arithmetic and nothing else: no model produces it, it is not trained on anything, and the same facts always give the same number.

• Every score comes with coverage: the share of the rubric that could actually be evaluated. A 70 built on a third of the rubric is not a 70.
• Every score lists which criteria matched, missed or were unknown, so a rep can see why a lead is a 70.
• Once outcomes flow, segment reports show whether strong fit actually converts better than no_fit. If it does not, the rubric is wrong — and you can change it in a minute.

ICP is scored inside /v1/decide, not /v1/enrich. To score a prospect, call decide with purpose: "outbound" and enrich: "always", and a max_cost_usd high enough for a person lookup; the icp object comes back beside the profile. See the ICP reference.

What it is not

• Not a data vendor. Sortance holds no enrichment data of its own; every fact was bought from a named vendor and says which.
• Not a CRM sync. Nothing is written anywhere. You take the profile and put it where it belongs.
• No bulk enrichment. Enrichment is one address per call, with no batch endpoint. Verification has a CSV upload; the list guide covers it and the loop, and the same loop works for enrichment.
• Not priced yet. Enrichment sits outside the verification rate and its pricing is not published. See pricing.