Entity Bind and Snowflake

1. 01

   Decide what leaves the warehouse

   Send the identifying columns and the key you want back, and nothing else. A resolve needs at least one identifying field — a name, a website, a domain, an email, a phone, a registration number, an LEI, a VAT number, a D-U-N-S, an ISIN, a ticker, or previous and trading names — and a request carrying none of them is rejected with a 422 before anything runs. Country and postcode do not count: they narrow an identity rather than being one, so a row carrying nothing but a country has asked no question.

2. 02

   Unload, in batches of 500

   The batch endpoint takes up to 500 records per request, treats them as an unordered set, recognises a repeated idempotency key as the same request rather than a new one, and writes one ledger row per outcome rather than a single summed row. It is not a queue: batches run one at a time, so a 300,000-row table is an overnight window to plan rather than a throughput figure to assume. Size the job around that before you promise anybody a refresh schedule.

   Unload, in batches of 500

   -- The shape of what leaves the warehouse. Your key rides along as
   -- client_ref and comes back verbatim on every row, so the result set
   -- joins to this table on your own identifier rather than on ours.
   SELECT
       account_id            AS client_ref,
       account_name          AS name,
       website               AS domain,
       billing_country       AS country,
       billing_postcode      AS postal_code
   FROM analytics.crm.accounts
   WHERE account_name IS NOT NULL;

3. 03

   Post the batch

   One request, up to 500 records, and an idempotency key so that a retry after a network failure does not pay twice. depth sets how far through the stages a record may go and defaults to research; setting it to probabilistic caps the spend and turns what would have been deep answers into abstentions rather than into cheap guesses.

   Post the batch

   curl -sS -X POST "$ENTITYBIND_BASE_URL/v1/batch" \
     -H "Authorization: Bearer $ENTITYBIND_API_KEY" \
     -H "Content-Type: application/json" \
     -H "Idempotency-Key: crm-accounts-2026-09-02-part-001" \
     -d @batch-001.json

4. 04

   Load the results back, including the ones that did not resolve

   Three result sets rather than one, and it is the second two that are worth modelling properly. Resolved rows carry an entity id, a confidence and a decision id. Abstentions carry a typed reason, a ranked shortlist and the column that would have decided — that is your work list, and it is free. A new entity minted because nothing matched is a third thing again: it is not a match, the number it carries is not a calibrated match confidence, and it must never be folded into an accepted-match count.

Snowflake sits with Salesforce and Python on the same shelf: nothing to install. If you are weighing a shipped integration against a pattern, the line between the two shelves is drawn on the hub.