Step 1

Trust Score Profile config for Person (flat REST body). node_classification controls which nodes get scored; schedule is one of THREE_HOURS/SIX_HOURS/TWELVE_HOURS/DAILY; each dimensions[].weight is between 0 and 1 (weight = 0 means computed-but-ignored).

{
  "project_id": "your_project_gid",
  "name": "person-trust-score-profile",
  "display_name": "Person Trust Score Profile",
  "description": "Trust Score profile for Person nodes. Combines verification, origin and freshness with equal weights; completeness and validity are present but weighted 0 (still computed, not used in _final_score).",
  "node_classification": "Person",
  "schedule": "THREE_HOURS",
  "dimensions": [
    {
      "name": "VERIFICATION",
      "weight": 1
    },
    {
      "name": "ORIGIN",
      "weight": 1
    },
    {
      "name": "FRESHNESS",
      "weight": 1
    },
    {
      "name": "COMPLETENESS",
      "weight": 0
    },
    {
      "name": "VALIDITY",
      "weight": 0
    }
  ]
}

Step 2

Capture two contrasting Person nodes. The metadata object on each property is the actual input to the scoring dimensions - verified_time, source, and update times.

{
  "nodes": [
    {
      "external_id": "knightrider",
      "type": "Person",
      "is_identity": true,
      "properties": [
        {
          "type": "email",
          "value": "knightrider@demo.com",
          "metadata": {
            "verified_time": "2026-05-10T08:00:00Z",
            "source": "id-verifier.gov"
          }
        },
        {
          "type": "name",
          "value": "Michael Knight",
          "metadata": {
            "verified_time": "2026-05-10T08:00:00Z",
            "source": "id-verifier.gov"
          }
        }
      ]
    },
    {
      "external_id": "satchmo",
      "type": "Person",
      "is_identity": true,
      "properties": [
        {
          "type": "email",
          "value": "satchmo@demo.com",
          "metadata": {
            "source": "user-self-attested"
          }
        },
        {
          "type": "name",
          "value": "Louis Armstrong",
          "metadata": {
            "source": "user-self-attested"
          }
        }
      ]
    }
  ]
}

Step 3

CIQ Policy. The trust score appears on the subject just like any other node attribute via subject.trust_score._final_score, so it can be ANDed into the regular filter.

{
  "meta": {
    "policy_version": "1.0-ciq"
  },
  "subject": {
    "type": "Person"
  },
  "condition": {
    "cypher": "MATCH (subject:Person)",
    "filter": [
      {
        "operator": "AND",
        "operands": [
          {
            "operator": "=",
            "attribute": "subject.external_id",
            "value": "$subject_external_id"
          },
          {
            "operator": ">",
            "attribute": "subject.trust_score._final_score",
            "value": 0.66
          }
        ]
      }
    ]
  },
  "allowed_reads": {
    "nodes": [
      "subject.external_id",
      "subject.property.email",
      "subject.property.name",
      "subject.trust_score._final_score"
    ]
  }
}

Request to create the policy.

{
  "project_id": "your_project_gid",
  "description": "CIQ policy that returns the requested Person record ONLY when its computed Trust Score _final_score is above the hardcoded threshold (0.66). The Trust Score Profile must already be active for node_classification = Person; otherwise subject.trust_score._final_score is undefined and the filter rejects every row.",
  "display_name": "policy - person with trust score filter",
  "name": "policy-trust-score-filter",
  "policy": "{\"meta\":{\"policy_version\":\"1.0-ciq\"},\"subject\":{\"type\":\"Person\"},\"condition\":{\"cypher\":\"MATCH (subject:Person)\",\"filter\":[{\"operator\":\"AND\",\"operands\":[{\"operator\":\"=\",\"attribute\":\"subject.external_id\",\"value\":\"$subject_external_id\"},{\"operator\":\">\",\"attribute\":\"subject.trust_score._final_score\",\"value\":0.66}]}]},\"allowed_reads\":{\"nodes\":[\"subject.external_id\",\"subject.property.email\",\"subject.property.name\",\"subject.trust_score._final_score\"]}}",
  "status": "ACTIVE",
  "tags": []
}

Step 4

Knowledge Query - returns the subject's own profile plus subject.trust_score._final_score.

{
  "nodes": [
    "subject.external_id",
    "subject.property.email",
    "subject.property.name",
    "subject.trust_score._final_score"
  ]
}

Request to create the Knowledge Query.

{
  "project_id": "your_project_gid",
  "description": "Returns the requested Person's profile but ONLY if their Trust Score _final_score is above the policy threshold (0.66). The trust score itself is included in the response so you can see why a subject was accepted or excluded.",
  "display_name": "knowledge query - my profile if trustworthy",
  "name": "kq-my-profile-trusted",
  "policy_id": "your_policy_gid",
  "query": "{\"nodes\":[\"subject.external_id\",\"subject.property.email\",\"subject.property.name\",\"subject.trust_score._final_score\"]}",
  "status": "ACTIVE"
}

Execute for Knight Rider (high-quality data): input_params.subject_external_id = knightrider. His _final_score 0.83 clears the policy's 0.66 threshold.

{
  "id": "your_query_gid_or_name",
  "input_params": {
    "subject_external_id": "knightrider"
  }
}

Response: profile returned, _final_score = 0.83 is included as a regular field in the result row.

{
  "data": [
    {
      "nodes": {
        "subject.external_id": "knightrider",
        "subject.property.email": "knightrider@demo.com",
        "subject.property.name": "Michael Knight",
        "subject.trust_score._final_score": 0.83
      }
    }
  ]
}

Execute for Satchmo (self-attested data): input_params.subject_external_id = satchmo. His _final_score 0.42 does not clear the 0.66 threshold.

{
  "id": "your_query_gid_or_name",
  "input_params": {
    "subject_external_id": "satchmo"
  }
}

Response: empty data array. The Person exists but the trust score is below the threshold, so the filter drops the row.

{
  "data": []
}