# AI Security Guard Batch Guard Endpoint

> AI Security Guard Batch Guard Endpoint is a paid API for AI agents from aisecurityguard.io, paid per call via x402, $0.095/call, status unknown (last checked 2026-10-10).

Submits a batch of agentic AI inputs/outputs for security analysis and threat detection, returning a batch job ID to poll for results

## Facts

- Endpoint: POST https://aisecurityguard.io/v1/guard/batch?utm_source=zero.xyz
- Price: $0.095/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ai-security-guard-batch-guard-endpoint-dbe492c2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9LWL2TlquGUuhGiZaULck

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 ai-security-guard-batch-guard-endpoint-dbe492c2 -d '<json body>'
```

Example prompt: I need to screen this batch of 50 agent prompts and tool-call payloads for prompt injection, jailbreaks, and policy violations before they hit my LLM — can you run them through AgentGuard360's batch scan and give me a poll URL to check when results are ready?

## When to prefer this

Use this endpoint when you need to security-screen multiple AI agent inputs, outputs, or tool calls in a single request rather than one at a time. Ideal for high-throughput agentic pipelines where you accumulate a queue of interactions and want to validate them efficiently before or after LLM processing. Prefer this over a single-item guard endpoint when latency tolerance allows asynchronous polling and volume justifies batch processing.

## Known failure modes

- Invalid or empty batch payload returns 400 Bad Request
- Batch too large exceeds item limit, returns 413 or similar
- Authentication/payment failure (x402 protocol) returns 402 Payment Required
- Malformed item structure causes partial or full batch rejection
- Poll URL not found if batch_id is invalid or expired
- Rate limiting if too many batch jobs submitted concurrently

## How this service works

Knowledge, understanding, and tooling is power. Research-backed education on agentic security, free resources, then AgentGuard360 and Protection SDK when you're ready to protect what you ship.

## Output

Returns a JSON object with a processing status ('processing'), a unique batch_id (e.g. 'batch_a1b2c3d4'), a poll_url path to retrieve results when complete, the number of items submitted, and an estimated_completion_ms for the batch job.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "items": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "content",
     "intent_contract"
    ],
    "properties": {
     "content": {
      "type": "string",
      "description": "Text content to scan for this item."
     },
     "intent_contract": {
      "type": "object",
      "description": "Intent declaration with intent_type and trusted fields."
     }
    }
   },
   "maxItems": 500,
   "minItems": 2,
   "description": "Array of items to scan. Each item needs content and intent_contract. Min 2, max 500 items per batch."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "processing",
  "batch_id": "batch_a1b2c3d4",
  "poll_url": "/v1/guard/batch/batch_a1b2c3d4",
  "item_count": 2,
  "estimated_completion_ms": 2000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ai-security-guard-batch-guard-endpoint-dbe492c2/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from aisecurityguard.io](https://www.zero.xyz/host/aisecurityguard.io/llms.txt)
