# CAPI2 Agent Commerce x402 Payment Safety

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

Validates an x402 payment request against a policy and returns a safety verdict with risk score and approved payment option

## Facts

- Endpoint: POST https://capi2-agent-commerce.vandurmedries.workers.dev/v1/x402-payment-safety
- Price: $0.005/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-x402-payment-safety-930554a2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yMseVXCuHxdmL1I7nIIUX

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-x402-payment-safety-930554a2 -d '<json body>'
```

Example prompt: Before I pay this x402 invoice for 10000 units on Base (eip155:8453), run it through the payment safety check using my current policy to make sure the risk score is acceptable and I get a verdict and approved option back.

## When to prefer this

Use this endpoint when an AI agent needs to screen an x402 payment request against a configurable policy before executing a payment — especially in autonomous agent pipelines where safety guardrails, verifiable receipts, and risk scoring are required before any funds move. Prefer this over generic payment processors when you specifically need x402 protocol support with policy-based allow/deny verdicts and evidence-backed findings on the Base network.

## Known failure modes

- Missing or malformed 'policy' object results in validation error
- Missing or malformed 'payment_required' object returns error response
- Network not recognized or unsupported chain ID causes rejection
- Payment amount exceeds policy limits resulting in 'deny' verdict
- Service unavailable on Cloudflare Workers edge returns 5xx error

## How this service works

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

## Output

Returns a JSON object containing: a 'verdict' field ('allow' or 'deny'), a 'findings' array with any policy violations or risk signals, a numeric 'risk_score' (0 = no risk), and an 'approved_option' object specifying the approved payment amount and network (e.g. eip155:8453 for Base).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "policy": {
   "type": "object"
  },
  "payment_required": {
   "type": "object"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "verdict": "allow",
  "findings": [],
  "risk_score": 0,
  "approved_option": {
   "amount": "10000",
   "network": "eip155:8453"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/capi2-agent-commerce-x402-payment-safety-930554a2/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)
