Skip to main content
POST
/
privilege
/
v1
/
detect
{
  "privileged": true,
  "confidence": 0.5,
  "categories": [
    {
      "type": "<string>",
      "detected": true,
      "confidence": 123,
      "rationale": "<string>",
      "indicators": [
        "<string>"
      ]
    }
  ],
  "policy_rationale": "<string>"
}

Authorizations

Authorization
string
header
required

API key starting with sk_case_

Body

application/json
content
string

Text content to analyze (required if document_id not provided)

document_id
string

Vault object ID to analyze (required if content not provided)

vault_id
string

Vault ID (required when using document_id)

categories
enum<string>[]

Privilege categories to check. Defaults to all: attorney_client, work_product, common_interest

Available options:
attorney_client,
work_product,
common_interest
jurisdiction
enum<string>
default:US-Federal

Jurisdiction for privilege rules

Available options:
US-Federal
include_rationale
boolean
default:true

Include detailed rationale for each category

model
string
default:casemark/core-large

LLM model to use for analysis

Response

Privilege analysis completed

privileged
boolean
required

Whether any privilege was detected

confidence
number
required

Overall confidence score (0-1)

Required range: 0 <= x <= 1
categories
object[]
required
recommendation
enum<string>
required

Recommended action for discovery

Available options:
withhold,
redact,
produce,
review
policy_rationale
string
required

Policy-friendly explanation for privilege log