changelog

What changed, and when

Dated changes to Entity Bind, newest first: the API fields a client reads, each accuracy run with its fractions and its fixture, the targets set and not yet met, and how access opens. The latest entry is dated .

Every entry names the record its date comes from, and none is written from a commit message. A change with no recorded date has no entry.

Subscribe: Atom feed
  1. Access

    Your own Entity Bind workspace, where you create your API keys

    After an application and a short conversation we open your Entity Bind workspace, and you create, list and revoke your own API keys in it. Each key is scoped to read or resolve, each raw key is shown once, and only its SHA-256 digest is stored.

    Open self-signup is not live yet, so a workspace still opens after a conversation. Paid plans and registry checks are switched on by us.

    Free starts with 300 credits and no card. Paid monthly plans are available in workspace Billing; VAT is added where applicable. Usage is tracked without automatic overage charges.

    Date from: The product's customer-workspace release record, which marks the hosted workspace verified on 2026-09-23.

    Start freeThe API referenceWhat metered but not yet charged means

  2. Access

    Applications open at /signup

    The way in became a short application at /signup, read by one person, in place of a request sent to /contact. A person reads each application and writes back.

    Date from: This site's own history: the /signup route was added on 2026-09-18.

    Start free

  3. Accuracy

    Continuous-integration gate report

    The regression gate that runs on every commit, reported on 2026-09-05. Its adjudication and research stages are deterministic offline stubs, so it measures the software rather than live model conversion. 1,176 labelled company pairs — 216 handwritten adversarial, 960 generated from a fixed seed — plus a 705-record fixture over 250 UK-registered companies.

    Normal runs pass the precision gate through an explicit, disclosed fallback for an under-powered zero-error population. A second mode, --strict-evidence, drops the fallback and demands the bound outright; it fails overall and on both gated tiers, purely on sample size, and it stays in the pipeline.

    • Precision on automated merges: 1.0000 observed on 357/357, a 95% Wilson lower bound of 98.94%, at 63.10% automation. The 95% Wilson lower bound of 357 error-free automated merges. Proving a 99% lower bound needs at least 381 consecutive clean merges, so this is 24 short of it — and we publish the bound rather than the point estimate.
    • Automation: 63.10%. 742 of 1,176 pairs were decided automatically in the September 5 saved gate report. This measures automation, separately from accepted-merge precision.
    • End-to-end resolution: 70.78% (499/705 records). End-to-end resolution on the internal gated acquisition fixture with offline stub models. All 499 accepted matches were correct in this fixture. The current 99% product-target diagnostic fails; this run does not measure live model conversion or independently establish calibration.
    • B-cubed cluster F1: 0.7584. B-cubed cluster F1 on the gate's own 705-record fixture, held as a regression ratchet against a 0.75 floor rather than offered as a headline. It reads far below the live recording's 0.9646 because an unresolved record is a predicted singleton and all 205 name-only arrivals on this fixture abstain by construction, splitting the families they belong to. The two cluster figures come from different instruments over different fixtures and are never averaged.

    Date from: The dated gate report the accuracy page reads its CI figures from.

    The gate, on the accuracy page

  4. Target

    A 99% minimum-input target, set and not yet met

    An unmet product target, set September 4: 99% accepted candidate-backed matches at confidence >= 0.90 for each minimum input of name plus context, domain, address, country or postcode. It supersedes the earlier 75% resolved-outcome goal and is not an achieved accuracy or global coverage claim.

    The minimum-input target diagnostic fails: name plus country accepts 0/205 on the internal regression fixture, and the other minimum-input populations are absent. A passing regression gate does not satisfy this product target.

    Date from: The product's accuracy document, which dates the current goal 2026-09-04; the accuracy page records it as set on September 4.

    The target and the blend, on the accuracy page

  5. Coverage

    Regional parity measured, and five registers counted for name uniqueness

    The same engine, measured on the United Kingdom's own instrument in other registers, with no model spend at all. Combined parity probability 0.999955, against a bar of 0.9565 declared before the run. Scope: United Kingdom, United States (Colorado) and EMEA (France and Norway).

    Measured with no model spend at all, on identifier and digital tiers plus retrieval and fragmentation, using the same seeded, sibling-complete builder in every register. It does not carry the live-adjudicated name tiers across, which rest on jurisdiction-free calibration keys and have been recorded in the UK only.

    SEC EDGAR, 6,471 tickered filers with complete rows, is 99.91% unique on name. Reported beside the combined figure and never blended into it: closed-end fund families at one address measure lower on the digital tier, which is a register-shape finding rather than an engine one.

    The same report counted, for five registers, the share of live companies whose normalised name no other live company shares. That census is published as a study with its method, snapshots, licences and a CSV.

    Date from: The product's region-parity report, dated 2026-08-30.

    Company name uniqueness by registerParity on the coverage page

  6. Accuracy

    Live-adjudicated recording over 317 GB companies

    Historical live adjudication recorded on 2026-08-29: 1,827 paid verdicts costing $53.53. The September 5 replay uses legacy recordings and has missing calls; it is not a new live measurement.

    317 live GB companies sampled from the 2026-08-01 Companies House snapshot, with same-name siblings included. Identifier-rich arrivals seed the catalogue before the weaker input shapes are evaluated.

    • Identifier (a company number or an LEI): 100% (317/317).
    • Name and website (a company name and its domain): 100% (197/197). Measured separately, at zero model spend, on 197 individually verified company-to-domain pairs. Those companies are large and well known, so this is the tier's behaviour on famous names rather than a register-wide sample.
    • Name, country and town prose (a company name, GB, and a sentence naming the registered town): 99.37% (315/317) 95% CI [97.7, 99.8]. Historical 2026-08-29 recording with earlier identifier arrivals seeding the catalogue. This does not measure a business description, email footer or generic verification purpose alone. Two same-stem groups remained unresolved.
    • Name and postcode (a company name and a registered postcode): 98.74% (313/317).
    • Name and country (a company name and nothing else but the country): 98.42% (312/317). Forecast at low-to-mid nineties and measured higher, because a representative register is about 99% unique on company names. The collision-dense fixture this was first tested on had hidden that.
    • Name and town (a company name, country and a typed registered town): 98.42% (312/317).
    • Truncated name (a name whose ending has been cut off by a field-length limit): 58.10% (61/105). 44 of 105 come back as an abstention with a shortlist, which is the correct answer for a name whose missing tokens were the discriminating ones.
    • Blend across the fixture: 95.75%. A historical 2026-08-29 blend across six input shapes in a preloaded UK catalogue. Its value depends on that mix: truncated names measured 58.10% while the blend measured 95.75%. Neither establishes the current minimum-input target.
    • False binds, every tier: 0. Zero wrong bindings were observed across the historical six-shape recording and the separate domain fixture. Observed correctness was 1.0000 on accepted outcomes; this does not guarantee an error-free new workload.

    Historical results on an internal UK fixture with a preloaded catalogue. The September 5 replay has no full-prompt-verified calls and cannot establish current calibration. No independent customer holdout or global coverage claim.

    Date from: The recording's own date, as the accuracy page publishes it.

    Every row, on the accuracy page

  7. API

    match_confidence added, and confidence deprecated

    Every resolve response carries match_confidence, the one comparable quantity, and match_confidence_basis, which names the population it was measured over. Threshold on match_confidence.

    confidence is deprecated and stays in the payload only so existing clients do not break. The measurement that retired it: the lowest value any binding response ever returned was 0.9000, so a confidence >= 0.85 rule admitted all 791 bindings and 254 of the 382 abstentions with them.

    Date from: The product's architecture decision record for the change, accepted on 2026-08-13.

    Do not threshold on confidence, in the API reference

the ask

Start with your own company records.

Create your workspace, verify your email and run your first company file. The Free plan needs no card. Create API keys in your workspace when you need an integration.

Start freePlans and prices

300 credits. No card.

For a guided review of your file, explore the Merge Safety Sprint →