What you can do through the API
Look up an address
Call the lookup endpoint. URL-encode the address when needed. You can look up any address: there’s no requirement to have an active or pending transaction with it. Only workspaces that participate in Address Registry can query it.
There’s no separate field for “verified” —
leiData is that signal. Anything else is based on Fireblocks data without that independent check.
A lookup returns information about the legal entity only: its name, jurisdiction, and LEI if declared. It never returns anything about that entity’s own customers or account holders, and the registry holds no link between vault addresses and identified individuals.
The lookup returns not_found when the counterparty isn’t a Fireblocks customer, has opted out, or is on an unsupported environment. A not_found result doesn’t mean the address is unhosted, illicit, or non-compliant.
You can only look up a specific address: you can’t enumerate the registry or query in reverse. To prevent bulk data extraction, lookups are also authenticated, rate limited, capped daily, and monitored, so the number of queries stays proportional to your transactions. See Acceptable use.
Manage participation
You can opt out your whole workspace, or only specific vault accounts, at any time, and opt back in later. Opting out has three effects:- Lookups against your opted-out addresses return
not_found. - A workspace that has opted out can’t look up addresses itself.
- Compliance workflows built on Address Registry, including About Address Registry Screening, stop working until you opt back in.
Limitations
- European and Swiss-hosted workspaces aren’t supported. Lookups against addresses from these workspaces return
not_found. - Developer Sandbox workspaces don’t support Address Registry.
- Coverage is limited to addresses within the Fireblocks network.
Acceptable use
Address Registry exists only to verify counterparties in connection with digital asset transactions. You must not:- Use it for any other purpose.
- Scrape, bulk-download, or systematically extract data from it.
- Resell, redistribute, or commercialize query results, or any data obtained from it.
- Attempt to identify, profile, or de-anonymize individual people using its data.
- Use it for surveillance or competitive intelligence.
- Circumvent technical controls, authentication requirements, or rate limits.