# DDG Compliance Screen Batch

> DDG Compliance Screen Batch is a paid API for AI agents from agents.daedalusdevelopmentgroup.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-20).

Batch-screens a set of entities or transactions against compliance rules and returns structured pass/fail results

## Facts

- Endpoint: POST https://agents.daedalusdevelopmentgroup.com/v1/compliance/screen-batch?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ddg-compliance-screen-batch-4938aeb8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mdWKFQz6y-igW59GOuxZJ

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 ddg-compliance-screen-batch-4938aeb8 -d '<json body>'
```

Example prompt: Can you run a compliance screen on this batch of wallet addresses I'm about to transact with — I need to know if any of them are flagged before I proceed?

## When to prefer this

Choose this endpoint when you need to screen multiple entities, transactions, or wallet addresses for compliance in a single API call rather than one at a time. It is particularly well-suited for agent-driven workflows where you need automated regulatory pre-screening before executing payments or onboarding users, and where micro-payment via x402 USDC is already part of the stack.

## Known failure modes

- Malformed input body returns a validation error
- Missing required fields (type, method, bodyType, body) causes a 400-level error
- Payment not settled via x402 USDC results in a 402 Payment Required response
- Large batch sizes may exceed processing limits
- Unsupported bodyType enum value causes rejection

## How this service works

v1_compliance_screen_batch

## Output

A JSON response with an `ok` boolean indicating whether the batch screening completed successfully, along with per-entity or per-transaction compliance determinations indicating pass, fail, or flag status for each item in the batch.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": true
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "ok": true
    }
   },
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ddg-compliance-screen-batch-4938aeb8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.daedalusdevelopmentgroup.com](https://www.zero.xyz/host/agents.daedalusdevelopmentgroup.com/llms.txt)