# Entity Bind: agent evaluation quickstart

REST reference: https://entitybind.com/api
MCP setup and tools: https://entitybind.com/mcp
Evidence and limitations: https://entitybind.com/accuracy
Pricing: https://entitybind.com/pricing

## Getting access

Start free: https://app.entitybind.com/app?signup=1
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.
For a full-pipeline evaluation, contact: mailto:hello@entitybind.com?subject=1%2C000-credit%20Entity%20Bind%20evaluation&body=I%20would%20like%20access%20to%20the%20planned%201%2C000-credit%20full-pipeline%20evaluation.%0ACompany%20or%20project%3A%20%0AInput%20fields%20and%20jurisdictions%3A%20%0ARequired%20enrichment%3A%20
An agent may apply on behalf of a named person, using that person's own details and with their consent, or draft the application email for them to send. It must never invent an identity.

## Base URL and key

The hosted base URL is https://app.entitybind.com. Set ENTITYBIND_BASE_URL to that origin. Self-hosted deployments use their own configured base URL.
Set ENTITYBIND_BASE_URL to your base URL and ENTITYBIND_API_KEY to a key you created in your Entity Bind workspace.
Use that base URL, not the marketing website, for /v1 calls.
Reference endpoints require the same bearer key; these reads cost no credits.

## Inspect configured enrichment

curl -sS "$ENTITYBIND_BASE_URL/v1/reference/enrichment-fields" \
  -H "Authorization: Bearer $ENTITYBIND_API_KEY"

## First resolve

Reference: https://entitybind.com/api#post-v1-resolve
The company below is a real UK company. Verify its identity against the register:
https://find-and-update.company-information.service.gov.uk/company/00617987
Expected identity: HSBC Holdings plc, GB company number 00617987.
This is an input and expected identity, not a recorded API response or guaranteed result.
Also test companies you choose yourself; one identifier lookup does not establish match quality.

curl -sS -X POST "$ENTITYBIND_BASE_URL/v1/resolve" \
  -H "Authorization: Bearer $ENTITYBIND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
        "name": "HSBC Holdings plc",
        "registration_number": "00617987",
        "jurisdiction": "GB",
        "country": "GB",
        "depth": "research",
        "client_ref": "identity-check"
      }'

## Inspect the decision

Reference: https://entitybind.com/api#get-v1-decisions-decision-id
Set ENTITYBIND_DECISION_ID to the decision_id returned by the resolve.

curl -sS "$ENTITYBIND_BASE_URL/v1/decisions/$ENTITYBIND_DECISION_ID" \
  -H "Authorization: Bearer $ENTITYBIND_API_KEY"

Every error code, with a fragment per code: https://entitybind.com/api#errors

Try it on companies you can already check

Start with a handful of companies whose identity you can verify yourself, then bring the awkward ones out of your own data — the same-name pairs, the subsidiaries, the rows carrying a name and not much else. Open the identity and the receipt behind each answer, run the alternatives on the same inputs, and you finish with a result about your data rather than about our fixture.

Access: 1,000 free credits. The full resolution pipeline. 1,000 one-time credits, valid for 30 days from your first resolution. No card required. Full resolution depth, with configured sources and their existing licence terms. 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. Public documentation is open now. Live calls need a key you create in your Entity Bind workspace, which you create online, and the base URL that comes with it. The existing Free plan is a separate tier: shallow decisions only, for wiring up an integration.

1. Ask the deployment what it can do, before you spend anything
Two reads with your key tell you what is wired up: /v1/reference/sources lists the registers and feeds this deployment can reach, and /v1/reference/enrichment-fields lists the fields that can come back and what you are permitted to resell. Both are free. A field appearing in that list means the deployment can supply it, not that any particular company has a value for it. Over MCP, the same answer comes from get_enrichment_fields.

2. Resolve a company where you already know the answer
Begin with a company number and the register it belongs to. Then take the identifier away and send what your own records actually hold — name plus domain, name plus country, name plus address, name plus a line of context — one input shape at a time, so you can see which of them carry and which do not. Keep your independently verified company number as the expected answer and mark the results against it. Sending it inside a test meant to measure name-plus-domain resolution only proves we can read a company number back.

3. Check the identity, then open the receipt behind it
Compare what came back with the identity you expected: a company number qualified by the register that issued it, or a legal entity identifier. Then fetch the decision itself at /v1/decisions/{decision_id}. match_confidence_basis records which population the confidence was read from, and the cited sources name the pages the evidence came from. Read entity_created carefully — it can mean a company newly adopted from a register, or an identity minted with no register behind it. An HTTP 200 and a fresh entity id tell you a call succeeded, not that the answer is right.

4. Send the ambiguous cases, then add the missing clue
Now try the ones you would not want to get wrong: two live companies sharing a name, a context line pointing at the wrong one, a record with too little evidence to settle. Four outcomes are worth telling apart. unresolved and clarification mean the evidence did not support an answer and nothing was invented to fill the gap — a safe abstention, and a useful result. depth_capped and escalation_unavailable mean the work stopped at a budget cap or could not reach a source, which is a different finding and not a statement about your data. Resubmit with the clue it asked for and check the identity again.

5. Write down what the sample actually showed
Count three things across all the distinct cases you sent: identities accepted and correct, identities accepted and wrong, and abstentions. Split those counts by input shape and by jurisdiction, because a single pooled rate hides the shapes that fail. Keep runs against a cold catalogue separate from runs made after known identities were seeded into it, and treat an exact replay as a test of reliability rather than of new coverage. A small trial can show fit, and evidence you can open; it cannot establish a global accuracy rate.

Cost: A decision settled by matching alone costs 1 credit; one that needed a model to adjudicate it or an agent to go and read a register costs 5. The planned 1,000-credit evaluation therefore covers up to 1,000 shallow or 200 deep chargeable decisions, depending on how much work each one needs. An abstention costs 0, and so does a byte-identical replay: 0. Reading a receipt, an entity or a reference collection costs nothing. The planned allowance includes up to 1,000 deep attempts, including those that abstain. Credits and attempts are separate limits. Provider-spend protection may pause work explicitly; unused credits stay visible and the pipeline is never silently downgraded.

Know which company fields you can get
Once a decision has settled which company a record refers to and admitted that identity, its exact identifiers retrieve the financial and business facts held against it. Find out which fields exist before you build on them, and read every returned fact together with its source, its reporting date and its licence.
A line describing what a company does helps pull back and rank same-name candidates, by weighing activity words alongside the name. On its own it does not establish a match. Country names and codes are normalised on the way in; accepting the name of a country is not a claim that we hold a register for it.
The optional company-data feed supports financial metrics, company descriptions, sector classifications, employees, funding and technology data from an authorised operator-managed export. No commercial supplier, dataset or continuous market-data refresh is bundled. Missing values remain absent. Storage permission does not imply resale permission.
Every returned fact carries where it came from and what you may do with it: provider and provider_record_id name the supplier and its own id for the record, licence_reference names the grant where a supplier gives one, and licence_permits_resale and resellable say whether the fact may leave your systems. Source citations and timestamps sit alongside them. Who supplied a fact and what its licence permits are recorded as two distinct observations.

September 5 minimum-input diagnostics
The existing 197-company UK domain register, using local fixtures and stub models.
On a separate 197-company UK source corpus, name plus domain matched 197/197 and name plus postcode matched 188/188 eligible companies, all correctly, in both cold and preloaded catalogues. Nine companies lacked a postcode. The respective 95% Wilson lower bounds are 98.09% and 98.00%; these reused company families must not be pooled as additional independent observations.
Separate 20-query samples of name plus town prose, verification purpose, typed city or country each accepted 0/20 with stub models in both catalogue states. This shows the remaining dependence on adjudication for weaker clues. It does not measure live model conversion, and no business-description-only customer holdout is available.
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.
Source: entity-resolution/docs/IMPROVEMENT-STATUS-2026-09-05.md

## Evidence limits

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.