Pricing and credits, answered in full.

It depends on the columns rather than the row count, and you can work it out yourself. A row decided by identifier rules or probabilistic scoring is 1 credit; a row that needed adjudication or research is 5; an abstention, a byte-identical replay and a row that normalised to no identifying signal are all 0. So 100,000 rows all carrying company numbers is 100,000 credits, and the same file where every row went deep is 500,000. At the Scale rate of $0.032 a credit, the cheapest paid rate we publish, that is roughly $3,196 and $15,980. That is more credits than any priced plan includes and there is no overage rate, so a file this size is a Scale conversation, quoted against your volume. Before any quote, we run a free preview over your file. It makes no model or registry calls, tiers your rows and reports composition, never a predicted resolution rate. Then we talk it through. Start free, then choose a paid plan in Billing.

Yes, for paid monthly subscriptions purchased through Stripe in workspace Billing. Review the recurring price, applicable VAT and payment terms before purchase; Stripe provides the subscription invoices. Free needs no card. Usage metering is separate: calls are recorded in the ledger, and usage creates no automatic usage or overage charge. The usage block states whether quota enforcement is enabled for the deployment; an `enforced: false` response means the call is metered without enforcing the usage quota, not that a paid subscription is free. The plan prices are defined in code and served from the same constants that meter, so the number in a response and the number on the page cannot drift apart.

An unresolved identity costs zero credits even when adjudication or research did the work. Deep attempts are tracked separately, because those calls still carry a provider cost. Existing monthly plans can reduce depth when their attempt quota runs out. The planned 1,000-credit evaluation instead requires an explicit limit response or a disclosed pause when research cannot continue, so a budget limit cannot be mistaken for an evidence-based abstention. That change is not live yet.

No. Resolution is bound to a content fingerprint — the SHA-256 of the submitted record with the server-minted id excluded — so resubmitting the same bytes returns the same binding at zero credits, on every plan, with no expiry. It is not a cache with a 24-hour window, which would be a promise about our infrastructure that you cannot verify; it is a property of your data. Two caveats travel with that claim. It is per tenant, so there is no cross-customer discount for a company somebody else has already resolved. And it is per exact content: one corrected postcode, one added phone number or one trailing space is a different fingerprint and a fresh resolution.

On the open-licensed subset, on the Scale plan, and with attribution. It is enforced by the write path rather than by a clause: every fact carries a licence tier, and the repository raises before any write on a pass-through fact, so a violation cannot even partially persist, and the field-by-field assembly of the golden record drops pass-through material before the record is built. Resale rights are published per field — `licence_permits_resale` is a property of the data's own licence, `resellable` is that plus the right your plan bought — and an unreadable licence reads as not-resellable rather than as permitted. Companies House is OGL v3.0 and SIRENE is Licence Ouverte 2.0, and both require attribution. Talk to us before you build a redistribution product on it.

The existing Free plan includes 300 credits a month, no deep resolutions, and a probabilistic depth cap. It makes no model or registry calls, so it is useful for wiring an integration but does not test research coverage. Every Entity Bind workspace starts on it, and a CSV upload in Matching mode runs there. The planned 1,000-credit evaluation is a separate one-time offer with full research depth. Request access to test that pipeline on your own companies; a sample file is optional. The full-pipeline evaluation is arranged separately and is not activated by signup. Request it for your workspace; we confirm availability, sources and the start date before activation.

Because it is a price rather than a measured cost ratio, and the code comment says so. The measured input is narrower: one LLM adjudication was measured at £0.0240 over 243 live calls, and the cost model carries $0.0293 per adjudication verdict; at about 1.73 verdicts per escalated record, that is about $0.051 for a record that escalates. Per thousand rows it is about $0 for an identifier-rich file and about $50 for one that is all names, because escalation is the whole cost: on the gated acquisition fixture 0 of 250 identifier-bearing records and 1 of 250 digital-tier records escalated, against 205 of 205 name-only ones. The 5:1 multiple is charged identically whether the answer came from one adjudication or a full research pass, and research costs several times more. Shadow-mode metering exists to check that ratio against reality before anybody is billed on it.