# Agent Security Gateway – List Count Validation Check

> Agent Security Gateway – List Count Validation Check is a paid API for AI agents from agent-security-gateway.onrender.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Validates that an actual list item count matches an expected count, returning a pass/fail security check result for AI agent workflows.

## Facts

- Endpoint: POST https://agent-security-gateway.onrender.com/api/validate/list_check
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-security-gateway-list-count-validation-check-738d27ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WTPOQljg4B8fPCMB8LHDj

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 agent-security-gateway-list-count-validation-check-738d27ec -d '<json body>'
```

Example prompt: Run a list count validation check: I expected 10 items in my results list but only got 7 back — label it 'search_results_check' and tell me if the counts match.

## When to prefer this

Use this endpoint when an AI agent needs to assert that a list or collection contains the expected number of items as a security or integrity check — for example, confirming search results weren't truncated, verifying a dataset wasn't tampered with, or performing pre-payment validation in an agentic pipeline. Prefer this over general-purpose validation libraries when you need a pay-per-use, stateless microcheck with x402/USDC payment integration.

## Known failure modes

- Missing required fields (actual_count or expected_count) returns a 400 or validation error
- Non-integer values for count fields cause schema validation failure
- Payment not completed via x402 USDC results in 402 Payment Required response
- Service unavailable on Render free tier due to cold start or downtime
- Empty response body due to undocumented response schema

## How this service works

Pay-per-request security APIs for autonomous AI agents using x402. Detect Japanese prompt injection, validate content, scan for threats, and perform pre-payment security checks. Built for USDC/Base payments.

## Output

A validation result indicating whether the actual_count matches the expected_count, likely including a pass/fail status, the label if provided, and details about any mismatch detected.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "actual_count",
  "expected_count"
 ],
 "properties": {
  "label": {
   "type": "string"
  },
  "actual_count": {
   "type": "integer"
  },
  "expected_count": {
   "type": "integer"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-security-gateway-list-count-validation-check-738d27ec/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-security-gateway.onrender.com](https://www.zero.xyz/host/agent-security-gateway.onrender.com/llms.txt)