# MNEMOS Compliance Screening

> MNEMOS Compliance Screening is a paid API for AI agents from mnemos-agent.onrender.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Screens a transaction counterparty and amount through an autonomous compliance decision engine, returning a pass/abstain result with reasoning

## Facts

- Endpoint: POST https://mnemos-agent.onrender.com/v1/compliance/screen
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mnemos-compliance-screening-b874c21e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ad_IYD2CwZz1pY8Sgo1Bc

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 mnemos-compliance-screening-b874c21e -d '<json body>'
```

Example prompt: Before I send 500 USDC to 0xAbc123...def456, run a compliance screen on that counterparty address and amount through MNEMOS and tell me if it passes.

## When to prefer this

Choose this endpoint when you need an autonomous, AI-driven compliance decision on a transaction before execution — particularly for crypto/USDC payments where you need AML, sanctions, or counterparty risk reasoning in real time. Prefer this over static rule-based screeners when you need a natural-language reason for the decision, or when integrating compliance into an agentic payment workflow that already uses x402 micropayments.

## Known failure modes

- Missing or malformed counterparty identifier returns an error or abstained:true result
- Insufficient payment (x402) causes a 402 Payment Required response before processing
- Engine abstention (abstained:true) when confidence is low or data is insufficient
- Network timeout from the hosted Render instance under load
- Invalid amount type (non-number) causes schema validation failure

## How this service works

MNEMOS autonomous decision/memory engine. Four /v1 capability operations are x402 v2 paid; health/status/dashboard/operator routes are not x402 paywalls.

## Output

A JSON object containing a module label ('compliance'), a human-readable reason string from the live decision engine explaining the outcome, and an 'abstained' boolean indicating whether the engine rendered a definitive decision or declined to rule

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "amount": {
   "type": "number",
   "description": "Transaction amount when available"
  },
  "counterparty": {
   "type": "string",
   "description": "Counterparty identifier/address when available"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "module": "compliance",
  "reason": "<live-engine-result>",
  "abstained": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mnemos-compliance-screening-b874c21e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mnemos-agent.onrender.com](https://www.zero.xyz/host/mnemos-agent.onrender.com/llms.txt)