# SuperSentinel Threat Model

> SuperSentinel Threat Model is a paid API for AI agents from supersentinel.supercapital.fun, paid per call via x402, $0.3/call, status unknown (last checked 2026-10-21).

Generates a security threat model for a described system architecture, identifying attack surfaces, vulnerabilities, and risks before attackers can exploit them.

## Facts

- Endpoint: POST https://supersentinel.supercapital.fun/threat-model?utm_source=zero.xyz
- Price: $0.3/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-21
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/supersentinel-threat-model-6f89d277
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ENZcmW7ZtuhVWXMV7k9jJ

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 supersentinel-threat-model-6f89d277 -d '<json body>'
```

Example prompt: Can you run a threat model on my system? It's a Node.js API behind a reverse proxy, uses JWT auth, talks to a Postgres database and an Ethereum smart contract for settlement, and runs on AWS ECS — I want to know the main attack surfaces and risks before we go live.

## When to prefer this

Choose SuperSentinel's threat model endpoint when you need automated, on-demand security threat modeling for a specific architecture description — especially useful for pre-launch security reviews of smart contracts, Web3 protocols, or traditional cloud applications. Prefer this over general-purpose LLM security advice when you want a structured, payable security intelligence output with a receipt. Best suited for architects and developers who can articulate their system components, data flows, and auth mechanisms in text form.

## Known failure modes

- Empty or too-vague architecture description returns unhelpful or generic threat model
- Input exceeding 8000 characters is rejected
- Payment failure results in 402 response with no threat model output
- Ambiguous component descriptions may produce incomplete threat identification
- Network or service downtime returns HTTP 5xx error

## How this service works

Security intelligence. Audits contracts and code before attackers do.

## Output

Returns a JSON object containing a job ID, a detailed threat model output (identifying attack surfaces, threat actors, attack vectors, risk ratings, and mitigation recommendations for the described architecture), and a payment receipt with transaction hash, amount, and network.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "maxLength": 8000,
   "minLength": 1,
   "description": "Describe the architecture: components, data flows, auth and where it runs."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "jobId": "j_…",
  "output": "…",
  "receipt": {
   "tx": "0x…",
   "amount": "100000",
   "network": "base"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/supersentinel-threat-model-6f89d277/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from supersentinel.supercapital.fun](https://www.zero.xyz/host/supersentinel.supercapital.fun/llms.txt)