Orbis Delegated Access

Strise’s standard global coverage is powered by Sayari. If your team already has a Bureau van Dijk (BvD) Orbis contract, Orbis Delegated Access lets you plug that contract into Strise so search and enrichment pull from Orbis instead — using your own license, delivered through Strise’s UI and Connect API.

See Orbis Delegated Access — technology notes for the GraphQL schema and matching details.

When to Use It

Use Orbis Delegated Access if:

• You already pay for Orbis and want to reuse that contract inside Strise rather than relying on Strise’s bundled Sayari data.
• You need the specific coverage or field set that Orbis provides in jurisdictions where Sayari is thinner.
• Your policy requires every global entity you review to be sourced from Orbis rather than an aggregated third-party provider.

If neither of those apply, the default Sayari-backed Global Entities coverage is generally a better starting point — it requires no extra contract and is enabled by default for Strise customers with global exposure.

What You Get

• Search. Orbis companies appear in global search alongside Knowledge Graph entities. Each result is scored for confidence (HIGH / MEDIUM / LOW); scores at 80% or above are treated as reliable matches.
• Enrichment. Once an Orbis company is linked to a Strise entity, you can pull in:
  • Core company data (registration number, address, incorporation, industry codes).
  • UBOs holding 10% or more — direct and indirect.
  • Board members and key personnel, using BvD’s BoardMnemonic classification.
• Ownership chart enrichment. One-click enrichment of a company’s upward ownership chain using Orbis data.
• Deduplication. Strise generates deterministic IDs from the source data so re-running enrichment updates the existing Strise record instead of creating duplicates.

Setup

1. Get a BvD API token. Contact your BvD account rep for an ApiToken.
2. Provide the token to Strise. Your CSM will wire the token into your team’s Orbis integration configuration. Tokens are stored encrypted and never leave Strise’s infrastructure.
3. Verify access. Run a global search or ownership enrichment on a test entity to confirm results arrive as expected.

How It Compares to Sayari-Backed Global Entities

Permissions

Integration configuration is managed by Strise staff. Day-to-day use (searching Orbis, triggering enrichment) is available to all users on the team once the integration is active.