OVERVIEW / GET STARTED

Build on the wider account.

Find a company. Understand its group. Research where to expand. Follow what changes.

This developer guide brings together the APIs and MCP connection used for EntityReach’s account expansion workflows. API calls and MCP tools access Global Database through separately provisioned credentials.

REST BASE URLhttps://api.globaldatabase.com/v2HTTPS · Token authentication

RESEARCH

Regis AI

Ask a company research question. Receive a streamed answer and the underlying data.

UNDERSTAND

KYB & corporate trees

Resolve legal entities, retrieve company profiles and traverse corporate relationships.

Watch companies

Follow selected companies and turn supported changes into account review signals.

CONNECT

MCP & AI agents

Connect company-data tools to your AI client. Research the wider account in your own workflow.

01 · Authenticate REST requests

Store your API key in a server environment variable named GLOBAL_DATABASE_API_KEY. REST requests use Authorization: Token YOUR_API_KEY. Keep the key on your server; your website should call your own authenticated backend.

Access and usage

Regis, KYB and monitoring require the appropriate API entitlements. EntityReach website search allowances do not grant or define API usage. Confirm your API scope and quotas during setup. For MCP, follow the separate connection and authentication guide.

02 · Find your customer

Use a company name and location to resolve the correct legal entity. The response contains company IDs to use for profile, hierarchy and monitoring requests.

cURL · first request

curl --request POST 'https://api.globaldatabase.com/v2/kyb/search' \
  --header "Authorization: Token $GLOBAL_DATABASE_API_KEY" \
  --header 'Content-Type: application/json' \
  --data '{"name":"GLOBAL DATA INTELLIGENCE","location":"GB"}'

The sample uses a company from the provider documentation. Confirm the matching country and registration number before selecting an ID.

Download OpenAPI 3.1 Read the expansion recipe →

The downloadable specification covers the REST endpoints in this guide. MCP tools are discovered through the MCP connection. It is maintained by EntityReach, with provider-reference gaps called out in descriptions.

NEXT STEPExplore the KYB reference

Source: Global Database API v2 reference ↗ · Reviewed 14 September 2026