# SafePay402 — x402 Payment Guardian

> SafePay402 — x402 Payment Guardian is a paid API for AI agents from guard.46-225-25-237.sslip.io, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Performs pre-payment security checks on x402 payment targets and returns an explainable ALLOW/REVIEW/BLOCK/UNKNOWN verdict with risk signals before an AI agent sends funds.

## Facts

- Endpoint: GET https://guard.46-225-25-237.sslip.io/v1/guard/check
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/safepay402-x402-payment-guardian-c5a1d42f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YuUkfEQD-usOOihD64tvY

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 safepay402-x402-payment-guardian-c5a1d42f
```

Example prompt: Before paying 0.025 USDC to wallet 0x1234abcd5678ef on Base for this resource URL https://api.example.com/v1/data, run a SafePay402 security check — tell me the verdict and any risk signals so I know whether it's safe to send.

## When to prefer this

Use this endpoint when an AI agent is operating autonomously with a crypto wallet and needs a pre-flight safety check before executing any x402 micropayment — especially when the payee address or resource URL is unfamiliar, user-supplied, or discovered dynamically. It is the right choice when explainability (human-readable signals and verdicts) and policy enforcement (allowed networks, assets, max amounts) matter more than raw speed. Prefer it over skipping verification entirely whenever autonomous fund transfers are involved.

## Known failure modes

- Missing required query parameters (resource_url or payee_address) returns a 400 error
- Unpaid request returns HTTP 402 with x402 payment requirements — the caller must pay 0.02 USDC before receiving a verdict
- Invalid EVM address format for payee_address causes a validation error
- Unreachable resource_url may result in a UNKNOWN verdict with reduced confidence
- Rate limiting or upstream sanctions/onchain data unavailability may delay or degrade response quality

## How this service works

Pre-payment security checks for x402 payments. Explainable ALLOW/REVIEW/BLOCK/UNKNOWN verdicts with risk signals, before an AI agent sends funds. The paid endpoint is monetized via the x402 protocol (USDC on Base): an unpaid request returns HTTP 402 with payment requirements.

## Output

A JSON object containing: a verdict (ALLOW, REVIEW, BLOCK, or UNKNOWN), a numeric risk_score (0-100), a confidence value (0-1), an array of risk signals each tagged with type (positive/negative) and source (sanctions, onchain, live_probe, historical_x402), a human-readable summary and recommendation, the sources checked, the ruleset_version used, and a checked_at timestamp.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "resource_url",
      "payee_address"
     ],
     "properties": {
      "asset": {
       "type": "string",
       "description": "Payment asset symbol, e.g. USDC"
      },
      "amount": {
       "type": "string",
       "description": "Payment amount in asset units, e.g. 0.025"
      },
      "policy": {
       "type": "object",
       "description": "Optional agent policy: allowed_networks[], allowed_assets[], max_amount"
      },
      "network": {
       "type": "string",
       "description": "CAIP-2 network id, e.g. eip155:8453 (Base)"
      },
      "payment_id": {
       "type": "string",
       "description": "Optional idempotency key — repeated calls return the cached verdict"
      },
      "resource_url": {
       "type": "string",
       "description": "The x402 resource URL the agent is about to pay"
      },
      "payee_address": {
       "type": "string",
       "description": "EVM address (0x…) that would receive the payment"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "signals": [
   {
    "type": "positive",
    "source": "live_probe",
    "description": "Live check: the endpoint's 402 response demands exactly this payee address"
   },
   {
    "type": "positive",
    "source": "onchain",
    "description": "Payee wallet has existed for over 10 months"
   }
  ],
  "sources": [
   "sanctions",
   "onchain",
   "live_probe",
   "historical_x402"
  ],
  "summary": "No significant risk signals. The payee and payment terms look trustworthy.",
  "verdict": "ALLOW",
  "checked_at": "2026-07-21T09:15:33Z",
  "confidence": 0.87,
  "risk_score": 12,
  "recommendation": "Payment can be executed safely.",
  "ruleset_version": "2026.07.1"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/safepay402-x402-payment-guardian-c5a1d42f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from guard.46-225-25-237.sslip.io](https://www.zero.xyz/host/guard.46-225-25-237.sslip.io/llms.txt)