Replay
The definition as the field writes it comes first, weaknesses and all. What Entity Bind does about it comes last, in its own paragraph, so you can take one without the other. Filed under decisions and evidence.
What the system returns, what it refuses to return, and what a decision can be redeemed for afterwards.
every figure, with its population →What replay means
Replay is serving a decision the system has already made, for content it has already seen, instead of computing it a second time. Real pipelines resubmit the same rows constantly: a nightly job, a re-run after a partial failure, the same supplier file loaded twice. Recomputing those costs money and, where a model is involved, can produce a different answer for the same input, which makes the whole system non-reproducible.
Replay handles it by binding a decision to the exact content that produced it, so an identical submission returns the identical answer at zero cost. The design questions are what counts as identical, how long the binding lives, and what happens when the replayed decision would no longer be acceptable under today's policy.
That last question is where most implementations are unsafe. A cached weak match served after the threshold has been raised launders an old decision past a new rule. The correct behaviour is to withhold it rather than re-serve it.
Entity Bind replays per tenant, per exact content, with no expiry, at zero credits. A weak cached binding replays as unresolved rather than being laundered into a match, and a cached replay whose inherited confidence has fallen below the confidence floor is withheld rather than re-served. A reviewer-approved binding replays stamped as human review, so it never re-enters the automated population that accuracy figures are measured over.
Where this shows up in Entity Bind
Three pages where this term stops being vocabulary and starts changing an answer, a payload or a price.
- The API referenceThe REST surface: payloads, the decision outcomes, the error model, the usage block and the ceiling on the confidence field.Open
- Pricing and the credit ruleWhat a decision costs, what a deep attempt costs, and the three things that cost nothing at all.Open
- The audit packThe fixtures, the verdict logs and the replay path: what an evaluator needs to re-run a published rate for themselves.Open
The fastest way past a definition is a file: which of your rows are the same company, which of your existing matches we would not have made, and what we could not decide.
Start freeThe terms next to this one
Each with its own sentence, because the next question is usually about the word beside this one.
Content fingerprint
A content fingerprint is a hash of the meaningful content of a submitted record, used to recognise that the same thing has been sent before regardless of when, in what order, or under what key.
Idempotency
An operation is idempotent when performing it repeatedly has the same effect as performing it once, which is what makes a retry after a timeout safe rather than duplicating work.
Confidence floor
A confidence floor is the score below which a system refuses to return a match at all, expressed as an acceptance contract rather than as a promise about accuracy.
Decision receipt
A decision receipt is the durable, retrievable record of why a particular match was made — the features, the probability, the thresholds in force, the sources cited and the version of the pipeline that decided — addressable by an identifier returned with the answer.
Review queue
A review queue is where records the system refused to decide are held for a human, and the quality of a resolver is largely determined by how small, how well-evidenced and how accountable that queue is.
- IntegrationPythonNo package on the index and no generated SDK. The API is plain JSON over HTTPS with a bearer token, and thirty lines are what a wrapper would hold.
- IntegrationSnowflakeAn integration pattern over the HTTP API rather than a connector. Unload the rows, post them in requests of up to 500, and load the results back.
The other 8 terms on this shelf
What the system returns, what it refuses to return, and what a decision can be redeemed for afterwards.
Internal fixtures only. The historical 2026-08-29 per-tier recording covers 317 GB companies with identifier-rich arrivals seeding the catalogue first; the context tier includes country and registered-town prose. Its legacy replay has no full-prompt-verified calls and cannot certify current calibration. The September 5 CI reports cover 1,176 labelled pairs and 705 records over 250 companies using offline stubs. These are not independent customer holdouts or live production validation; the 99% minimum-input product target remains unmet. Scope is company and organisation identity only — not people, vessels, bank-account ownership, sanctions or emissions. Results may not be used for eligibility decisions about individuals, including employment, credit and tenancy.
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.
300 credits. No card.
For a guided review of your file, explore the Merge Safety Sprint →