> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Global - Core Intelligence Service

> Performs a series of checks across multiple data partners and returns risks associated with each data point. Authoritative real-time identity lookup for Global. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;GLB&#x22;,&#x22;services&#x22;:&#x22;glb_intelligence_service&#x22;,&#x22;phone&#x22;:&#x22;+15550101000&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

Performs a series of checks across multiple data partners and returns risks associated with each data point. Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results.

## Coverage

* **Coverage:** —
* **Country:** Global
* **Service ID:** `glb_intelligence_service`
* **Data domain:** Telecom
* **Category:** Telecom

## Inputs

| Field         | Required | Example        |
| ------------- | -------: | -------------- |
| `phone`       |      Yes | `+15550101000` |
| `vendor_data` |       No | `user-1234`    |

* **Required inputs:** `phone`
* **Optional inputs:** `vendor_data`
* **Consent:** Not required
* **Workflow availability:** Standalone API only
* **Coverage:** —
* **Price:** \$0.41 per successful query

## Body parameters

<ParamField body="issuing_state" type="string" required default="GLB" placeholder="GLB">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `GLB`
</ParamField>

<ParamField body="services" type="string" required default="glb_intelligence_service" placeholder="glb_intelligence_service">
  Array containing this service ID. Pinning the service keeps the request scoped to this exact database.

  Example: `glb_intelligence_service`
</ParamField>

<ParamField body="phone" type="string" required default="+15550101000" placeholder="+15550101000">
  Phone number in international format.

  Example: `+15550101000`
</ParamField>

<ParamField body="vendor_data" type="string" default="user-1234" placeholder="user-1234">
  Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.

  Example: `user-1234`
</ParamField>

## Input rules & validation notes

* Send the fields listed above exactly as captured from the user or document.
* Didit validates required fields before calling the database. Requests rejected before source lookup are not charged.

## How to call it

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://verification.didit.me/v3/database-validation/" \
    -H "x-api-key: YOUR_API_KEY" \
    -F "issuing_state=GLB" \
    -F "services=glb_intelligence_service" \
    -F "vendor_data=user-1234" \
    -F "phone=+15550101000"
  ```
</RequestExample>

<ResponseExample>
  Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it.

  **`MATCH`** — The registry confirmed the identity and every checked field matched.

  ```json 200 OK — MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Approved",
    "issuing_state": "GLB",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "glb_intelligence_service",
        "service_name": "Global - Core Intelligence Service",
        "source_data": {},
        "validation": {
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`NO_MATCH`** — The registry returned no match for the submitted data.

  ```json 200 OK — NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "GLB",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "glb_intelligence_service",
        "service_name": "Global - Core Intelligence Service",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```
</ResponseExample>

## Returned data

The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `glb_intelligence_service` currently documents this normalized shape:

* Varies by registry response.

## Pricing & SLAs

Global - Core Intelligence Service queries are billed only when Didit receives a conclusive result from the validation source.

* **Per-call price:** \$0.41 USD.
* **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
* **Latency:** typical p95 \< 2 s.
* **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset.

## Continue reading

* [Global Database Validation overview](/api-reference/database-validation/global)
* [Database Validation overview](/core-technology/database-validation/overview)
* [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)