# HARK questionnaire

HARK

Status: LIVE
Price: $0.005 USDC
`GET /api/calc/hark`
HTML: https://magentlab.com/docs/hark
Markdown: https://magentlab.com/docs/hark.md

Not a medical device. Not a diagnosis, dose, or listing recommendation.

## What it computes

Sum the four Sohal 2007 HARK items and return whether one or more answers are affirmative.

## When to use

When an agent needs the published HARK point total and Sohal 2007 ≥1 screen and must not invent a diagnosis of intimate partner violence or interview the patient.

## When not to use

- Not a medical device and not a diagnosis of intimate partner violence.
- magent does not interview the patient.
- The caller assigns each flag. magent does not interpret individual items.
- This is Sohal 2007 HARK only (four yes/no flags; screen-positive at score ≥1). Not HITS 1-5 scoring. magent does not apply the AAS pregnancy item (HARK removed it).

## Formula

```
HARK = humiliation + afraid + rape + kick; each 1 if true; max 4
```

## Citation

[The sensitivity and specificity of four questions (HARK) to identify intimate partner violence: a diagnostic accuracy study in general practice](https://doi.org/10.1186/1471-2296-8-49)
Sohal H, Eldridge S, Feder G
BMC Fam Pract. 2007;8:49
DOI: [10.1186/1471-2296-8-49](https://doi.org/10.1186/1471-2296-8-49)

## Worked example

### All items false

Given: `afraid=false, humiliation=false, kick=false, rape=false`

1. score = 0
2. screen_positive false (threshold is ≥1)


### Humiliation only

Given: `afraid=false, humiliation=true, kick=false, rape=false`

1. score = 1
2. screen_positive true


## Also searched as

- HARK
- HARK questionnaire
- Sohal HARK
- humiliation afraid rape kick
- HARK score
- intimate partner violence screen
- Sohal 2007 HARK
- IPV four questions

## Parameters

- `humiliation` (boolean, required): Within the last year, humiliated or emotionally abused in other ways by partner or ex-partner (HARK H; Sohal 2007). true or false as assigned by the caller. magent does not interview the patient.
- `afraid` (boolean, required): Within the last year, afraid of partner or ex-partner (HARK A; Sohal 2007). true or false as assigned by the caller. magent does not interview the patient.
- `rape` (boolean, required): Within the last year, raped or forced to have any kind of sexual activity by partner or ex-partner (HARK R; Sohal 2007). true or false as assigned by the caller. magent does not interview the patient.
- `kick` (boolean, required): Within the last year, kicked, hit, slapped or otherwise physically hurt by partner or ex-partner (HARK K; Sohal 2007). true or false as assigned by the caller. magent does not interview the patient.

## Bulk (POST)

POST the same path with a JSON items array. The first item is the GET unit; each additional item is $0.002. Invalid items return HTTP 400 before settlement.

Method: `POST /api/calc/hark`
Max items: 25
Price: unit_amount + extra_item_amount * (n - 1) (unit 5000 atomic, extra 2000 atomic)
Status: PREVIEW

- 1 to 25 items. Each item uses the same keys as the GET query parameters.
- POST of 1 item costs the same as GET. Lists longer than 25: chunk into multiple POSTs. Extra items still execute; do not pad dummy rows.
- The first invalid item fails the whole request (index in the 400 JSON). You are not charged.
- HTTP 200 is {count, path, items}. Each items[i] is the GET 200 body for that row.
- Catalog misses (empty matches, found=false) stay paid 200s inside that slot.
- x402 resource URL is this path plus n and body_sha256. Browsers that prefer text/html get the same paywall as GET; Pay retries POST with the same items.

Example request:

```json
{
  "items": [
    {
      "afraid": "false",
      "humiliation": "false",
      "kick": "false",
      "rape": "false"
    },
    {
      "afraid": "false",
      "humiliation": "false",
      "kick": "false",
      "rape": "false"
    }
  ]
}
```

Human paywall (two-item fixture): https://api.magentlab.com/paywall/bulk/hark

Example 200:

```json
{
  "count": 2,
  "path": "/api/calc/hark",
  "items": [
    {
      "components": [
        {
          "factor": "humiliation",
          "points": 0,
          "present": false
        },
        {
          "factor": "afraid",
          "points": 0,
          "present": false
        },
        {
          "factor": "rape",
          "points": 0,
          "present": false
        },
        {
          "factor": "kick",
          "points": 0,
          "present": false
        }
      ],
      "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
      "citation": {
        "authors": "Sohal H, Eldridge S, Feder G",
        "doi": "10.1186/1471-2296-8-49",
        "id": "sohal-2007",
        "pmid": "17727730",
        "source": "BMC Fam Pract. 2007;8:49",
        "title": "The sensitivity and specificity of four questions (HARK) to identify intimate partner violence: a diagnostic accuracy study in general practice"
      },
      "formula": "hark",
      "formula_expression": "HARK = humiliation + afraid + rape + kick; each 1 if true; max 4",
      "max_score": 4,
      "score": 0,
      "screen_positive": false
    },
    {
      "components": [
        {
          "factor": "humiliation",
          "points": 0,
          "present": false
        },
        {
          "factor": "afraid",
          "points": 0,
          "present": false
        },
        {
          "factor": "rape",
          "points": 0,
          "present": false
        },
        {
          "factor": "kick",
          "points": 0,
          "present": false
        }
      ],
      "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
      "citation": {
        "authors": "Sohal H, Eldridge S, Feder G",
        "doi": "10.1186/1471-2296-8-49",
        "id": "sohal-2007",
        "pmid": "17727730",
        "source": "BMC Fam Pract. 2007;8:49",
        "title": "The sensitivity and specificity of four questions (HARK) to identify intimate partner violence: a diagnostic accuracy study in general practice"
      },
      "formula": "hark",
      "formula_expression": "HARK = humiliation + afraid + rape + kick; each 1 if true; max 4",
      "max_score": 4,
      "score": 0,
      "screen_positive": false
    }
  ]
}
```

## Response fields

- `formula` (string): hark
- `formula_expression` (string): Exact expression used
- `score` (integer): HARK points 0-4
- `max_score` (integer): 4
- `screen_positive` (boolean): true iff score ≥ 1 (Sohal 2007 ROC-optimal cut-off). Not a diagnosis of intimate partner violence.
- `components` (array): Per-item points
- `citation` (object): Sohal BMC Fam Pract 2007 citation
- `disclaimer` (string): Not-a-device notice

## Example JSON

Frozen fixture. Not a live lookup.

```json
{
  "components": [
    {
      "factor": "humiliation",
      "points": 0,
      "present": false
    },
    {
      "factor": "afraid",
      "points": 0,
      "present": false
    },
    {
      "factor": "rape",
      "points": 0,
      "present": false
    },
    {
      "factor": "kick",
      "points": 0,
      "present": false
    }
  ],
  "disclaimer": "Not a medical device. Deterministic published-formula or published-code output for autonomous agents. A licensed clinician remains responsible for patient care and billing submissions.",
  "citation": {
    "authors": "Sohal H, Eldridge S, Feder G",
    "doi": "10.1186/1471-2296-8-49",
    "id": "sohal-2007",
    "pmid": "17727730",
    "source": "BMC Fam Pract. 2007;8:49",
    "title": "The sensitivity and specificity of four questions (HARK) to identify intimate partner violence: a diagnostic accuracy study in general practice"
  },
  "formula": "hark",
  "formula_expression": "HARK = humiliation + afraid + rape + kick; each 1 if true; max 4",
  "max_score": 4,
  "score": 0,
  "screen_positive": false
}
```

## Errors

- HTTP 400 `invalid_flag`: boolean clinical flags must be true or false Returned before settlement; you are not charged.
- HTTP 400 `invalid_items`: POST body must be a JSON object with only an items array Returned before settlement; you are not charged.
- HTTP 400 `invalid_item_count`: items must be an array of 1 to 25 objects Returned before settlement; you are not charged.
- HTTP 400 `invalid_item`: each items entry must be a JSON object Returned before settlement; you are not charged.

Shared HTTP 402 and 503: https://magentlab.com/docs/payments

## Related tools

- [HITS](https://magentlab.com/docs/hits) — Sum four caller-assigned Sherin 1998 HITS integers (hurt, insult, threaten, scream; each 1-5) and return the published total (4-20) and ≥10 screen.
- [PHQ-9](https://magentlab.com/docs/phq-9) — Sum nine caller-assigned Kroenke 2001 PHQ-9 integers (0-3) and return the published total (max 27), severity cutpoints, and ≥10 screen.
- [GAD-7](https://magentlab.com/docs/gad-7) — Sum seven caller-assigned Spitzer 2006 GAD-7 integers (0-3) and return the published 0-21 total, 5/10/15 severity cuts, and ≥10 case-finding flag.

## Payment

Unpaid requests return HTTP 402 even if query parameters or POST items are missing or invalid, so CDP and agents can index the path. After a PAYMENT-SIGNATURE, invalid params return HTTP 400 JSON before settlement. magent does not charge. Fix the params, then request a new 402 quote for that complete URL. Catalog misses (empty matches, found=false) are valid paid 200s.

- GET the tool with Accept: application/json (do not send Accept: text/html unless you want the human paywall).
- HTTP 402 means you have not paid. Decode the base64 PAYMENT-REQUIRED header. HTTP 503 is not a new quote.
- Sign accepts[0] (exact, EIP-3009) with validBefore = now + maxTimeoutSeconds (600 seconds), or accepts[1] (batch-settlement deposit/voucher) on product GET. Ping and POST {items} stay exact. Magent retries transient facilitator 429/5xx before answering.
- Retry the same URL with PAYMENT-SIGNATURE (base64 JSON of accepted and payload). Magent attaches canonical extensions.bazaar on CDP verify/settle; echoing 402 bazaar is optional.
- Success is HTTP 200 JSON plus PAYMENT-RESPONSE. exact settles before the tool. batch-settlement verifies (and deposit-settles) before the tool and commits the charge after HTTP 2xx. HTTP 503: retry the same PAYMENT-SIGNATURE. Mint a new exact nonce only after a new HTTP 402.

- offered `exact` on eip155:8453: Fixed-price USDC on Base. The buyer authorizes the advertised amount (EIP-3009). magent settles before the tool runs (paymentFlow upfront). extra.assetTransferMethod=eip3009 extra.paymentFlow=upfront.
- offered `batch-settlement` on eip155:8453: Payment-channel vouchers claimed later in batches. Exact stays accepts[0]. Same-path POST {items} is still exact. extra.assetTransferMethod=eip3009 extra.paymentFlow=authorization.

- not offered `upto`: Not offered. Usage-based: buyer authorizes a ceiling, seller settles the actual amount after work. Reserved for a future metered tool. Not for current calculators or code search.

Same-path POST {items} is still scheme exact: one EIP-3009 authorization for GET unit plus $0.002 per extra item. That is not x402 batch-settlement (payment channels / vouchers).

Shared HTTP 402 and 503 table: https://magentlab.com/docs/payments

Stdio MCP (one process per host): https://magentlab.com/docs/mcp

## Guarantees

- HTTP 402 is unpaid, including a missing query. After PAYMENT-SIGNATURE, invalid parameters return HTTP 400 before settlement. You are not charged. HTTP 402 never includes the tool JSON.
- exact: settlement finishes before the tool (paymentFlow upfront). batch-settlement: verify/deposit before the tool; chargedCumulativeAmount commits after HTTP 2xx. Uncertain or failed settlement fails closed (HTTP 503). Retry the same PAYMENT-SIGNATURE.
- HTTP 402 is unpaid only. Do not sign a second authorization because of a 503.
- Execution is timeout-bounded and concurrency-capped.
- Calculator inputs are stored encrypted for allowlisted operators (Magent Console). They are not in public logs, SSH lookups, catalog, or rollups. Request logs store path without query.
