# Script Master Labs — Compliance Anomaly Detection API

> Script Master Labs — Compliance Anomaly Detection API is a paid API for AI agents from mcp-x402.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Reports a compliance anomaly event for a specific bank, triggering a flagged record via pay-per-call USDC settlement on Base.

## Facts

- Endpoint: POST https://mcp-x402.onrender.com/x402/compliance-anomaly
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/script-master-labs-compliance-anomaly-detection-api-c77670b7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KnGhTvEKvucIrrymwLlYx

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 script-master-labs-compliance-anomaly-detection-api-c77670b7 -d '<json body>'
```

Example prompt: Flag a compliance anomaly for bank ID 'FNB-00234' — the trigger is 'unusual_wire_transfer', the detail is 'Multiple large international transfers detected in a 24-hour window', severity is 'high', and my agent ID is 'agent-7712'.

## When to prefer this

Choose this endpoint when you need to programmatically report or log a compliance anomaly for a specific U.S. bank and want pay-per-call settlement via USDC on Base rather than a subscription API. It is purpose-built for agent-driven compliance workflows where anomaly events must be submitted with structured triggers and severity levels.

## Known failure modes

- Missing required fields (bank_id, detail, trigger, agent_id) returns a 400 validation error
- Insufficient USDC balance or failed x402 payment returns a 402 Payment Required error
- Invalid bank_id format may result in a rejection or unmatched record
- Malformed severity enum value may cause processing errors
- Service unavailability on Render deployment may cause 503 timeouts

## How this service works

Pay-per-call crypto, RWA, federal, SEC, Section 8/HUD housing, and compliance APIs via x402. Primary: USDC on Base (eip155:8453). Also accepts Global Dollar (USDG) on Robinhood Chain (eip155:4663) via sovereign X-PAYMENT-TX. Hyphen routes only (e.g. /x402/gas-tracker, /x402/pha-lookup, /x402/sec-8k). MARKETPLACE REVIEW: use free /x402/playground/* (no key, no payment). Production /x402/* returns 402 unless paid via x402 or X-Api-Market-Key / X-API-Key from seller dashboard.

## Output

A confirmation that the compliance anomaly event has been recorded, along with any relevant response data from the federal compliance system, settled via USDC payment on Base through the x402 protocol.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "detail": {
   "type": "string"
  },
  "bank_id": {
   "type": "string"
  },
  "trigger": {
   "type": "string"
  },
  "agent_id": {
   "type": "string"
  },
  "severity": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/script-master-labs-compliance-anomaly-detection-api-c77670b7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mcp-x402.onrender.com](https://www.zero.xyz/host/mcp-x402.onrender.com/llms.txt)