The trade-intelligence workspace for compliance officers, trade-finance underwriters and global sourcing leads. The same graph that powers Signal Routes and CrestAPI, exposed as a queryable analyst's desk rather than a stack of dashboards.
The CrestLens workspace opens to a search bar and a watchlist. The search bar accepts entity names — fuzzy, transliterated, or registered — beneficial-ownership chains, HS codes with optional country qualifiers, lane identifiers, counterparty bank names, freight bookings, and direct queries against the trade graph in a compact query language. The watchlist is the analyst's own; alerts fire only when the underlying graph state has materially changed against the watch parameters, and the alert always names the change rather than the entity, so that an analyst opening their morning queue sees what actually moved.
Beyond the search and the watch, the workspace is a small number of operations performed many times. The analyst pivots from a hit to its trade graph; from the trade graph to the bank chain behind it; from the bank chain to the entity resolution evidence; from the evidence back into a briefing report draft. The verbs are search, pivot, evidence, report. There is no fifth verb.
| Verb | What it does | Output |
|---|---|---|
| Search | Resolve a query against the live graph | Ranked entities · lanes · counterparties |
| Pivot | Move from a hit to its trade or bank graph | Adjacent entities · hops · weights |
| Evidence | Open the primary sources behind a hit | Filings · list versions · appointments |
| Report | Compose a briefing report from the trail | 4 – 9 page report · citations intact |
Entity resolution, sanctions screening with version receipts, beneficial-ownership traversal, dual-use goods flags, end-use checks against destination lanes. The workspace defaults to a per-query audit hook and a per-user evidence log.
Counterparty quality, bank chain hops, exposure against designated parties, lane-level risk for L/Cs and SBLCs. The trade-finance workspace adds a per-deal audit hook and a watchlist scoped to active facilities.
Supplier discovery by HS code, country and lane; second-source mapping against an existing supplier; supplier-risk monitoring with lane and counterparty inputs. The sourcing workspace exposes a structured "qualify" template.
Beneficial-ownership traversal across jurisdictions, bank-chain reconstruction, time-resolved entity movement, and the underlying customs and sanctions evidence for each hop. The investigations workspace adds a frozen-snapshot mode for evidence preservation.
Read-only access for invited regulators against a frozen evidence window. The methodology page accompanying every finding is mandatory in the regulator workspace and cannot be turned off.
Across the five, the workspace shares the same graph, the same evidence, the same versioned methodology. The differences are columns, defaults and audit hooks — not data.
CrestLens is, deliberately, not a replacement for an existing screening platform or trade-finance system of record. It sits beside them, with two integration patterns supported out of the box. The first is single-sign-on against the customer's existing identity provider (Okta, Entra, Google Workspace), with role-based access mapped to the same groups the customer already operates against the rest of their stack. The second is event hooks: when an alert fires in CrestLens, the event can be posted to a destination of the customer's choice — a webhook, a queue, a ticketing system, an SBLC management platform.
Where a customer also runs CrestAPI, the two are linked: an analyst hit in CrestLens carries the same entity identifiers that the API returns; an investigation built in CrestLens can be exported as an API query for batch use. The link is bidirectional and audit-logged on both surfaces.