# Risk API - Retry Safety Check

> Risk API - Retry Safety Check is a paid API for AI agents from risk-api-production-af85.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Determines whether a payment has already settled or is safe to retry, preventing double-charges on timed-out transactions.

## Facts

- Endpoint: GET https://risk-api-production-af85.up.railway.app/retry-safe?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/risk-api-retry-safety-check-0180ff9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tXI1c6jpXxbSzhcRXkgkm

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 risk-api-retry-safety-check-0180ff9c
```

Example prompt: Before I retry that payment, can you check if it already settled so I don't accidentally double-charge the customer?

## When to prefer this

Use this endpoint when you need to safely handle payment retries after a timeout or network failure, specifically to avoid double-charging. It is best suited for agentic payment flows on Base or x402-style micropayments where confirmation receipts may be lost. Prefer this over a raw transaction lookup when you need a clear go/no-go signal on retry safety rather than raw transaction data.

## Known failure modes

- Missing or invalid payment/transaction identifier returns an error
- Transaction too recent to have a definitive settlement status
- Network timeout reaching the Railway-hosted service
- Unrecognized transaction type or method returns a validation error
- Payment hash not found on-chain returns unknown status

## How this service works

Check if a payment settled or is safe to retry. Prevents double-charging on timeout.

## Output

Returns a status indicating whether the payment has already settled and whether it is safe to retry, allowing callers to avoid double-charging on ambiguous or timed-out payment attempts.

## 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",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/risk-api-retry-safety-check-0180ff9c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from risk-api-production-af85.up.railway.app](https://www.zero.xyz/host/risk-api-production-af85.up.railway.app/llms.txt)