Northwind Insurance · Analytics

Identity API

Beta

Resolve a BRC-100 identity key or a DID to the document recorded on chain, and the transaction that set it.

Endpoint reference

Identity lookups returning stale documents

Lookups still succeed, but a document may be a few minutes behind the tip. Check the transaction reference in the response if freshness matters for your use.
Lookups, 30 days
0

0 a day

Metered spend
$0.00

drawn from credits

Per lookup
$0.0010

no plan needed

Latency
—

platform 310 ms

Try a lookup

Runs against this workspace's network, using a key you already have.

Mainnet

Nothing to hand? that resolves.

Request

curl "https://api.whatsonchain.com/v1/bsv/main/identity/<identity-key>" \
  -H "API-KEY: <your analytics key>"
Resolved locally in this prototype. The real endpoint reads an on-chain index; the sample here shows the response shape so an integration can be written against it, and only the sample values resolve.

What resolves, and what does not

Point lookup

Give an identity key or a DID and get the current document plus the transaction that set it. This is what the endpoint does, and it is fast because it is an index read.

Not discovery

There is no search across identities, and no way to list them. Discovery needs a different index and raises questions about who may enumerate whom, so it is deliberately absent rather than half-built.