# SML Verdict Protocol – Seal Endpoint

> SML Verdict Protocol – Seal Endpoint is a paid API for AI agents from verdict.scriptmasterlabs.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Seals a decision capsule without running a jury, returning an HMAC-signed, persisted receipt with an approval status

## Facts

- Endpoint: POST https://verdict.scriptmasterlabs.com/seal?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/sml-verdict-protocol-seal-endpoint-00be03da
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aKhNsVkMLAnIkALb3M1xv

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 sml-verdict-protocol-seal-endpoint-00be03da -d '<json body>'
```

Example prompt: Seal this decision capsule and give me a signed receipt I can use as an audit trail — no jury needed, just lock it in with the seal tier.

## When to prefer this

Choose the /seal endpoint over /decide when you need a lightweight, fast decision record without the overhead or cost of five-juror deliberation — ideal for low-risk decisions, pre-logging actions, or scenarios where the agent itself has already made the determination and simply needs a cryptographically signed, persisted receipt for audit or compliance purposes. Use /decide when you need multi-juror consensus for high-stakes capital decisions.

## Known failure modes

- Missing or malformed 'capsule' field returns a validation error
- Capsule already sealed may result in a conflict or duplicate error
- Invalid action enum value other than REQUEST_DECISION may be rejected
- Payment failure (x402) if USDC payment is not properly attached
- Malformed order object may cause processing errors
- Network timeout if the signing or persistence layer is slow

## How this service works

SML Verdict Protocol seal receipt (no Jev jury)

## Output

Returns a JSON object containing: 'approved' (boolean indicating whether the decision passed), 'receipt' (an HMAC-signed, persisted receipt object capturing the sealed capsule state), and 'tier' (enum value 'seal' indicating this was a seal-only operation without jury deliberation).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "capsule"
 ],
 "properties": {
  "order": {
   "type": "object"
  },
  "action": {
   "enum": [
    "REQUEST_DECISION"
   ],
   "type": "string"
  },
  "capsule": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "approved",
  "receipt"
 ],
 "properties": {
  "tier": {
   "enum": [
    "verdict",
    "seal"
   ],
   "type": "string"
  },
  "receipt": {
   "type": "object"
  },
  "approved": {
   "type": "boolean"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/sml-verdict-protocol-seal-endpoint-00be03da/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verdict.scriptmasterlabs.com](https://www.zero.xyz/host/verdict.scriptmasterlabs.com/llms.txt)