Association graph
See the earlier claims an evaluation connects to, and which kind of identifier connects them.
The association graph shows the earlier claims that one claim connects to through shared identifiers, and which kind of identifier makes each connection. GET /v1/evaluations/{id}/graph returns it for any evaluation in your workspace.
Why it matters
A result tells you what happened. The graph shows the context. When you review a claim, allowed or denied, the graph shows every earlier claim it connects to. When you investigate a wave of repeat claims, it shows how far the cluster reaches.
Key capabilities
- Connections across every identifier. Email addresses, user IDs, phone numbers, payment methods, devices, networks and your custom identifiers all form connections.
- Beyond direct matches. The graph includes claims connected through other claims, so a chain of accounts that share identifiers in turn appears together.
completeflag. Large clusters are capped so the graph returns quickly. When it is capped, the response says so.- Scoped to your workspace and benefit. The graph only ever contains claims from your own workspace, for the same benefit.
Connections are evidence, not identity
A shared device or network doesn't prove that two accounts belong to one person. Use the graph to understand a decision and to investigate. Don't treat it as proof of identity.
Response data
{
"object": "evaluation_links",
"evaluation": "eval_3f6c2a1e-8b4d-4c7a-9e2f-5d1b7a0c4e93",
"links": [
{ "outcome": "out_6e3b9a12-4c7d-4f58-b0a9-1d2e8c5f7a36", "family": "identity" },
{ "outcome": "out_6e3b9a12-4c7d-4f58-b0a9-1d2e8c5f7a36", "family": "device" },
{ "outcome": "out_0d5c8e27-1b4a-4f93-8c62-a7e9b3d1f045", "family": "benefit_history" }
],
"linked_outcomes": 2,
"complete": true
}| Field | Meaning |
|---|---|
links | One entry for each connection. outcome is the connected outcome. family is the kind of identifier behind the connection: identity, device, network or benefit_history. Device and browser identifiers both report device. Two outcomes can be connected by more than one family. |
linked_outcomes | How many different outcomes the graph connects to. |
complete | false when the cluster was larger than the graph returns. The links shown are then a subset. |
Open any connected outcome with GET /v1/outcomes/{id}, and its evaluation with GET /v1/evaluations/{id}.
How the graph starts
An allowed claim's graph starts from its outcome and shows everything that outcome connects to. A denied claim has no outcome of its own, so its graph starts from the identifiers its evaluation recorded. That makes the graph the fastest way to see the earlier outcomes behind a prior-claim denial. Read it together with the evaluation's reason and inputs, and the signal family assessments in its evidence.
Configuration
- The identifiers you send. Every identifier you send can form connections. Custom identifiers bring in connections only your business can see.
- Scopes. Reading the graph needs the
evaluations:readscope.
Programmatic access
| Interface | Use |
|---|---|
| AbuseZero REST API | GET /v1/evaluations/{id}/graph, GET /v1/outcomes/{id} |
| AbuseZero Node.js SDK | evaluationGraph(), getOutcome() |
| AbuseZero CLI | abusezero evaluations graph, outcomes get |
| AbuseZero MCP server | abusezero_get_evaluation_graph, abusezero_get_outcome |
| Dashboard | Evaluations, with Show linked claims on an evaluation |
Next steps
How is this guide?
Last updated on