# Selun SCE Case Relevance Evaluator

> Selun SCE Case Relevance Evaluator is a paid API for AI agents from selun.sagitta.systems, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-15).

Evaluates whether historical security case data and threat families are relevant to a proposed DeFi/crypto action, returning a relevance score and matched doctrine tags for execution preflight.

## Facts

- Endpoint: POST https://selun.sagitta.systems/agent/x402/sce/case-relevance
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/selun-sce-case-relevance-evaluator-f1bc6bb7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Js7jVX_jQIAEm_sUC3uym

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability selun-sce-case-relevance-evaluator-f1bc6bb7 -d '<json body>'
```

Example prompt: Before I execute a rotation on Aave (protocol: aave) on Ethereum mainnet (chain_id: 1), check Sagitta SCE case relevance — my doctrine tags are emergency_rotation_policy and user_warning_policy, threat families are DeFi Protocol Incident and Admin Key / Access Control, and the requested action is asset_rotation. How relevant are the known security cases and how confident is the match?

## When to prefer this

Use this endpoint when an autonomous agent needs to preflight a DeFi action against Sagitta's indexed security case library — specifically when doctrine-tagged policies (e.g. emergency_rotation_policy) and known threat families (e.g. Admin Key / Access Control) must be checked for relevance before execution. Prefer this over generic risk APIs when you need doctrine-aware, case-matched confidence scoring tied to Sagitta's SCE framework.

## Known failure modes

- Missing required fields (decisionId or requested_action) returns 400 validation error
- Unknown doctrine_tags or threat_families may return low relevance score with no matches rather than an error
- Expired or stale case index may reduce confidence score accuracy
- Payment not processed (x402 flow incomplete) results in 402 Payment Required before evaluation runs
- Invalid chain_id may return empty or unmatched results

## How this service works

Classifies whether a protocol or threat family is active in the SCE corpus. Returns `relevance_level` (NONE | LOW | MEDIUM | HIGH), `relevance_score`, `matched_threat_families`, and `matched_doctrine_tags`. Only call when you already have specific threat context to evaluate — not a default preflight. Pass `threat_families`, `doctrine_tags`, or `protocol_name` to get a meaningful result.

## Output

Returns a JSON object containing a relevance level (e.g. HIGH), a numeric relevance score (0-100), a confidence object with label and score, matched doctrine tags, matched threat families, reason codes explaining the match, a validity timestamp, and a unique SCE evaluation ID — all structured under a selunWrapper response envelope.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain_id": {
   "type": "integer"
  },
  "decisionId": {
   "type": "string"
  },
  "asset_types": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "doctrine_tags": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "protocol_name": {
   "type": "string"
  },
  "threat_families": {
   "type": "array",
   "items": {
    "type": "string"
   }
  },
  "requested_action": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "result": {
    "sce": {
     "confidence": {
      "basis": "Matched indexed threat families and doctrine tags",
      "label": "high",
      "score": 0.78
     },
     "valid_until": "2026-06-17T11:56:44Z",
     "reason_codes": [
      "family_match",
      "doctrine_tag_match",
      "high_severity_cases_present"
     ],
     "schema_version": "sce.case_relevance.v1",
     "relevance_level": "HIGH",
     "relevance_score": 82,
     "matched_doctrine_tags": [
      "emergency_rotation_policy",
      "user_warning_policy"
     ],
     "matched_threat_families": [
      "DeFi Protocol Incident",
      "Admin Key / Access Control"
     ]
    },
    "validUntil": "2026-06-17T11:56:44Z",
    "selunWrapper": true,
    "sceEvaluationId": "sce_relevance_8a66e19f06184e1e",
    "sceSourceEndpoint": "/v1/sce/case-relevance"
   },
   "status": "completed",
   "endpoint": "/agent/x402/sce/case-relevance",
   "productId": "sce_case_relevance",
   "decisionId": "sce-case-001"
  },
  "success": true,
  "executionModelVersion": "Selun-1.0.0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/selun-sce-case-relevance-evaluator-f1bc6bb7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from selun.sagitta.systems](https://www.zero.xyz/host/selun.sagitta.systems/llms.txt)