# stall-row Guard — x402 Endpoint Payment Safety Verdict

> stall-row Guard — x402 Endpoint Payment Safety Verdict is a paid API for AI agents from stall-row-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-18).

Returns a pay/caution/avoid safety verdict for a single x402 endpoint before an agent pays it, combining live 402 signal checks, payTo address screening against OFAC/rotation registries, and resource history analysis.

## Facts

- Endpoint: POST https://stall-row-production.up.railway.app/v1/guard?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/stall-row-guard-x402-endpoint-payment-safety-verdict-b34b3e28
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RWaIi5Pa4nKrGr4FMwOVO

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 stall-row-guard-x402-endpoint-payment-safety-verdict-b34b3e28 -d '<json body>'
```

Example prompt: Before you pay that x402 endpoint at https://api.example.com/premium-data, run a guard check on it — I want to know if the payTo address is flagged, whether the 402 signal looks real, and whether we should pay, caution, or avoid it entirely.

## When to prefer this

Use this endpoint whenever an AI agent is about to autonomously pay an x402 resource it has not previously verified. Prefer it over manual wallet checks or generic OFAC screeners because it combines live 402 signal parsing, SDK validation, OFAC screening, rotation/vanishing detection, and history context into a single actionable verdict — all without requiring the agent to actually make the payment first.

## Known failure modes

- URL not reachable or does not return a 402 response — verdict may default to CAUTION or error
- payTo address not extractable from 402 headers — OFAC screening skipped
- OFAC snapshot may be dated — real-time sanctions changes may lag
- Unknown resource history always caps verdict at CAUTION regardless of other signals
- Malformed or non-x402 URL input returns validation error

## How this service works

Guard — one pay / caution / avoid verdict for one x402 endpoint, composed from the row's inspector tools: the live 402 sign read and SDK-checked, the payTo screened against the bad-payTo registry (OFAC plus rotation/vanishing flags, evidence attached), and the resource's recorded history — unknown history caps the verdict at CAUTION. Every verdict carries its reasons; the one probe inside is unpaid. Use this when your agent is about to pay an endpoint it does not know.

## Output

A structured verdict of PAY, CAUTION, or AVOID for the given x402 endpoint URL. Includes reasons for the verdict, live 402 signal read and SDK validation result, payTo wallet address screened against OFAC SDN list and rotation/vanishing flag registry with evidence attached, and resource history classification (unknown history caps at CAUTION). The probe itself is unpaid.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/stall-row-guard-x402-endpoint-payment-safety-verdict-b34b3e28/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from stall-row-production.up.railway.app](https://www.zero.xyz/host/stall-row-production.up.railway.app/llms.txt)
