# CAPI2 Agent Commerce – Ad Claim Guard

> CAPI2 Agent Commerce – Ad Claim Guard is a paid API for AI agents from capi2-agent-commerce.vandurmedries.workers.dev, paid per call via x402, $0.12/call, status unknown (last checked 2026-09-14).

Validates advertising claims against prohibited terms and destination URLs, returning an allow/deny decision with tamper-evident verification status for autonomous agents.

## Facts

- Endpoint: POST https://capi2-agent-commerce.vandurmedries.workers.dev/v1/ad-claim-guard
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/capi2-agent-commerce-ad-claim-guard-17727733
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JlXykADZ6Vpr5wlMC1lNo

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 capi2-agent-commerce-ad-claim-guard-17727733 -d '<json body>'
```

Example prompt: Check if this ad claim is compliant: 'Our product cures all diseases overnight, guaranteed!' — screen it against prohibited terms like 'cures', 'guaranteed', and 'overnight', and verify the destination URL https://example.com/product is acceptable.

## When to prefer this

Choose this endpoint when you need automated, policy-enforced validation of advertising claims before publication — especially in agentic workflows where AI-generated ad copy must be screened against a custom blocklist and a destination URL must be verified. It is ideal for compliance pipelines that require tamper-evident receipts and micropayment-gated access via x402. Prefer it over generic content moderation APIs when the use case is specifically advertising claims with a prohibited-terms list and URL destination checking.

## Known failure modes

- Claim text shorter than 3 characters or longer than 1200 characters returns a validation error
- Invalid or malformed destination URL format causes a rejection
- More than 30 prohibited terms in the array triggers an input limit error
- Payment failure via x402 protocol results in a 402 response blocking the call
- Ambiguous or borderline claims may receive inconsistent allow/deny decisions
- Destination URL may be unreachable or unsupported, affecting the verification status

## How this service works

Programmable authority checks and tamper-evident receipts for autonomous agents, sold through sustainable x402 commerce.

## Output

Returns a JSON object with a 'decision' field ('allow' or 'deny'), a 'destination_checked' boolean indicating whether the destination URL was evaluated, and a 'verification_status' string (e.g. 'supported') indicating the tamper-evident verification outcome.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "claim": {
   "type": "string",
   "maxLength": 1200,
   "minLength": 3
  },
  "destination_url": {
   "type": "string",
   "format": "uri"
  },
  "prohibited_terms": {
   "type": "array",
   "maxItems": 30
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "decision": "allow",
  "destination_checked": true,
  "verification_status": "supported"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/capi2-agent-commerce-ad-claim-guard-17727733/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from capi2-agent-commerce.vandurmedries.workers.dev](https://www.zero.xyz/host/capi2-agent-commerce.vandurmedries.workers.dev/llms.txt)